Develop Bugs

[Q] Black Screen on to Galaxy Note LC1 after BootLoader with ODIN

Hi, soume one could help me
I have a black screen on my galaxy notes after a bootloader via ODIN. The screen is black even at the Power + Home + sound !!!
But the galaxy note appears onto the peripheriques windows and Odin seems to work normally.
I'm going to install the LC1 official ROM with Odin but it changes nothing. I'll install the very first ROM N7000XXKKA_N7000OXXKK5_XEF just to see.
Thank's

I got the same problem too, did tried many methods to hard reset but not work, phone keep booting itself, anyone help?

The solution
Must be installe the first ROM of your Galaxy Phone.
I found the solution on a French blog
http://galaxynotetests.blogspot.fr/2012/01/tuto-mettre-jour-son-galaxy-note.html
At the end of the update, restart your rating Galaxy .. If ever it does not start after a quarter of an hour, you can simply go to the page sammobile and start the flash ROM of the first Galaxy rating. This rom contains a. PIT that will be needed in ODIN in PIT. Then repeat with the latest ROM again. This recovery method can be effective if you ever have bugs. Problems of this kind occur mainly on mobile operators blocked.
If a referral ODIN [FAIL] for each test, make sure the USB cable is that of the Galaxy Rating, and unplug anything that could put him in conflict (USB gadgets, printers, USB 3G or wifi etc ...)

Please Help! SII Stuck On Firmware Upgrade encountered an issue screen

Basically My galaxy S2 was rooted and do not remember the root name etc... everything was working great until I installed a new font, the phone rebooted and was on start up screen for more than 3 hours.
After looking for solution and fielding with it, I ended up in worst place now!!
Cannot enter recovery mode anymore (volume up + Home + power)
The screen is Stuck on "firmware upgrade encountered an issue"
Cannot connect with Kies
However I can enter the Download mode and connect with ODIN
Tried to install many firmwares but ODIN fails!!

barzi3 said:
Basically My galaxy S2 was rooted and do not remember the root name etc... everything was working great until I installed a new font, the phone rebooted and was on start up screen for more than 3 hours.
Tried to install many firmwares but ODIN fails!!
Click to expand...
Click to collapse
Post in Galaxy S2 threads I'm sure there is the answer..
also provide more details i.e. Odin log/output

I did the same exact thing. Went to s2 forum and it shows u how to reset your phone to factory. Then all you need is to re root and voila. Back on game mode!!!::good:

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] device hangs in black boot screen after ...

I screwed up my SPH-D710 big time (see details here ...). I am starting a new question thread here as this doesn't have anything to do with the device constantly booting anymore.
I have now manged to get the device into a state, that it doesn't boot anymore, neither regular nor into recovery, but hangs in the black boots screen that says "Samsung Galaxy S II" in white letters.
I can still boot into Odin mode though - and I hope that's a good thing.
Last thing I put onto the device (also mentioned in the other thread) was Garwynn's SXTP+Agat Recovery kernel v0.3.0 from Rwilco12's repository.
Can I still save the device and how.
I really want some expert advice before I do the next step ...
Thanks in advance!

OK, so my device is officially bricked. I think I can still get into Odin mode (if I find a charged battery, as mine drained / didn't charge any more in the mean time).
In case I find a charged battery and can still get into ODIN mode, I want to try a [rooted] stock ROM - does it matter which one?
Eventually I want to load CM11.
Thanks.

Please follow these directions to return to stock latest rooted.
Download these files and place them onto your desktop named EpicStockRooted.
Choose between whether you want Data wiped, or not.
GB27 Rooted Data Wipe
GB27 No Data Wipe
Samsung Drivers
Make sure Samsung Kies, or other versions of Samsung Drivers are uninstalled first. Then install the Samsung Drivers.
Once you're finished start the executable GB27 file as administrator mode and wait for it to load. Once you're done, proceed to put the device into download mode. Hold Volume Down + Power button until you're on a Android Firmware dialogue with the green android, press volume up to proceed to the next screen.
Now plug in the device to the computer ( USB 2.0, original samsung usb to micro plug ) and let the device be recognized. you'll see a [COM:##] show up within the first white box, doesn't matter about the ##, as long as it's reading [COM:]
Proceed to click START! and wait for it to be finished, appx ~15 minutes to do so.
Once done the device should auto-reboot. Let it load up.
Setup your device and proceed to the home screen of the launcher, SuperSU will force close on you, don't worry about that, press YES and setup your Google Account for Play Store.
Update SuperSU via playstore, then install as /system app in SuperSU, you're done setting up now.
You're issue was installing a custom kernel for the wrong type of Android version for your ROM.
The latest Custom Kernel for Jellybean GB27 is Agat's Source version 1.4.2f. Use Odin 3.07, within PDA slot to flash the custom kernel. But make sure you're fully loaded on stock first.
If you happen to think about loading CM11, Please feel free to see this post HERE

Thank you very much Spark!
That's pretty much what I did after some heavy research here on this - very helpful - forum.
I downloaded and installed a rooted one-click GB27 and am back up and running - learned a lot from that experience.
Thanks also for explaining what I did wrong.
I am now in the process of downloading the necessary stuff for going to CM11.
I installed Mobile Odin (Lite) and am putting EL26 CWM recovery (StockCWM-EL26.tar.md5), an ICS modem (FL24.zip), gapps and CM11 (I will start with the stable milestone version from here, and then maybe try the latest nightly, if success ...) on my sdcard.
I read (and read again ...) this post on the "one Stop FAQ for Noobs" thread and hope that I won't run into any issues.
Thanks again!

You're welcome, it's all about trial and errors here, People can read and read but most posts around here do get confusing on what you should do and it is A LOT of reading. But once you get used to it, you'll be up to speed on what to do from there on.

I managed to get the device to CM11 and everything is working.
I followed the instructions in the "One Stop ... for Noobs" thread and the OP in the CM one. The only hickup that I had was that the EL26 recovery kernel only has CWM5 and one obviously needs CWM6 (probably in order to flash a KitKat ROM ... (?)), so I had to find a CMW6 recovery that I could flash with CWM5.

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.