Database Develop

[Q] I've bricked my phone- HELP! :C

okay so I thought bricking android would be complicated but as it turns out it's quite simple.
Please cut me some slack because I am a n00b at all this. I am already googling for a solution and looking on forums but I haven't found anything YET so after a desperate hour of googling I thought of posting here (I will keep on trying to find a solution though).
Here is what I did:
A long while ago I rooted my Galaxy S. Rom was ClockworkMod (recovery says ClockworkMod Recovery v3.0.0.5) and the kernel was Talon. No problem with this.
Now I wanted to do a factory reset so I dialed that number yo need for a factory reset. I got a red text message warning me NOT to touch any button and it would reboot. The phone rebooted and I think I got into the recovery mode.
The icon was a top cat in an orange circle with an arrow. I guess that's part of the Talon kernel.
Anyways on recovery mode screen I saw an option called "wipe/factory reset" I've selected it - I was told it can't be undone- I've said OK- It said everything went fine so I selected reboot.
Now the phone won't reboot. It is stuck in a loop. It will always try to reboot.
So all I see is a GALAXY S i9000 screen followed by a Talos screen with a loading bar followed by the GALAXY S i9000 screen again and it will just loop.
No idea what to do :C
help, please! thanks a million everyone!

Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered

zodiaxe66 said:
Try flash the talon kernel again or if u got a rom on your SD card flash that.
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
well I've tried to put an update.zip on the internal storage of the phone because I don't have an external SD card.
I mounted the phone as mass storage device in the recovery mode but my win xp 32 bit would say it is a Samsung Galaxy S but there was an error with the new hard ware and it couldn't be mounted fff
so no idea what to do now?

This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA

Diablob555 said:
This is normal, you delated youre whole System. First of all dont panik you able to enter ist downloadmode ? If so, than you'll bei able to install a new rom and you will be able to boot I'm also New here had the same problem with my phone. This is called a soft-brick. I was able to go in DM and flash a new rom with my galaxy s plus
Sent from my GT-I9001 using XDA
Click to expand...
Click to collapse
vielen lieben dank
yeh i guess i did a soft brick. So what exactly do I do now?
I have managed to copy an update.zip file I've found on my computer to the phone but the download mode gives me an error and says it can't install it.
Can you link me to the files I need to install on it with the help of the download mode? Thanks a lot

so I have already tried installing different roms which seemed to have worked fine
I have tried just any random rom (Simplicity) I could find on this forum. It installed but I am still stuck in a boot loop. I don't see the Talon graphic anymore but the Galaxy S animation but I am still stuck in a loop.
help :C

zodiaxe66 said:
If this doesn't work.search for ezbase 3.0 and follow instructions on how to flash a rom with ODIN.
U can also find ezbase on "insanity rom" thread in the op(1 of the links)
And now your phone is recovered
Click to expand...
Click to collapse
http://www.theandroidsoul.com/ezbase-rom-v3-0-full-installation-guide-w-video/
is what ive found when googling. of course ALL THE FILES are offline again. what a surprise.
really a shame. this looked so promising :C
i've flashed a different ROM in the mean time but it doesn't let me flash anything else anymore. that recovery mode is awful so i can only suggest no one uses simplicity rom

You need to flash a new firmware using odin, partition with 512 pit. Check this link for instructions and firmware. http://forum.xda-developers.com/showthread.php?p=14273101
Sent from my GT-I9000 using xda premium

[Q] weird bug. need expert advice + solution

Today I tried to update my phone to a new custom rom.
I followed the instructions of the threads and tried to get it to work.
Of course it didn't work or else I wouldn't be here right now asking for help.
Here's the current situation.
I am able to boot into download mode + recovery mode and also boot into cwmr and install a different kernel.
I used pc odin to install it each time and it does pass and the rom (i've tried installing a gingerbread rom so that I can try everything again) does install.
the problem is that it is currently stuck in a boot loop at the "Samsung galaxy note gt-N7000" screen.
I have looked up dr.ketan's posts and tried some too.
currently i am booting abyss note kernel 42cwt touch original. (I know for sure it is a workable kernel because I've been using it this whole time.
here's what i've done. please tell me what i've done wrong and the possible ways to reverse it.
1. backed up everything
2. went into recovery
3. factory reset/cache clear
4. use pc odin to install new kernel (since I was looking into switching to another kernel anyways)
5. use pc odin again to install gingerbread rom (I do get the green light saying it did get installed
6. phone auto reboots
7. it gets stuck at the boot loop like i have mentioned above
i will try to attach a few pictures of my note as soon as I can so you can see what's going on with it.

What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?

nokiamodeln91 said:
What rom is there on the phone now ? if you boot into recovery .. what recovery do you get now ? CWM or stock ardroid 3e recovery ?
Click to expand...
Click to collapse
Right now it reboots to 3e recovery.
The rom that I tried to inject to it is currently a the stock gingerbread rom from dr. Ketans thread.
The rom that I had on it is the official ics rom for the hk region.
The rom that I wanted to inject to it was a custom jb rom that uses hydracore as a kernel.
Thanks!!

try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..

nokiamodeln91 said:
try installing a prerooted Gb rom or an ICS stock rom using PC odin.. if you choose ICS, after flash install a safe kernel..
Click to expand...
Click to collapse
If I do a stock ics update can I just do it through kies or do I have to do it through pc odin? Also. Would abyss or hydracore considered as a safe kernel???

yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels

nokiamodeln91 said:
yes if kies can do it then good but at this situation i dont think. its better to use PC odin for now. yes both are safe kernels
Click to expand...
Click to collapse
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.

Well I am not sure but I soft bricked my phone when I tried that Abyss Kernel. In my view Hydracore is safe. Philz is super safe.
Flash ICS which matches your region using Odin. If phone boots flash Philz, If not, then be ready to read a lot of stuff or get phone repaired.

asian_boi said:
I've tried your suggestions...and it didn't seem to work out too well.
I am able to flash to different kernels and get in and out of different recovers and such, but ya...still no luck with running a rom.
Click to expand...
Click to collapse
instead of flashing kernels. flash a complete rom using PC odin.

nokiamodeln91 said:
instead of flashing kernels. flash a complete rom using PC odin.
Click to expand...
Click to collapse
You have so much patience
Sent from my Amazon Kindle Fire using Tapatalk 2

the only thing i have...

Hey guys. my note seems to have cooperated and allowed me to flash a new rom and also a new kernel. Here's the catch though, now it's stuck in the samsung logo and won't boot beyond that. Any suggestions of what to do? I am continually searching on the forums to find a solution.
At least I'm happy to know it's not a brick that can't be fixed.
Thanks nokiamodeIn91 for your help so far. I really appreciate it.

which rom did you flash and which kernel? how?

He spent a lot of time helping you. Be sure to hit thanks button

Sent from my GT-N7000 using Tapatalk 2

I currently flashed the abyss note kernel 42 cw touch and I downloaded an old gb rom from sammobile .
Here's what I did.
1. Put my phone into download mode
2. Run as admin on PC Odin
3. Selected the Abyss kernel then flashed it.
4. Boot into the cmw, wiped cache then booted the phone into download mode again.
5. Then I installed the old GB Rom on to my phone and restarted it.
6. Phone starts, loads past the GT-N7000 logo and goes into the samsung boot logo.
7. Phone repeats the animation of the samsung logo a time or two then restarts on its own. This loops until the phone is completely drained. I know that the rom works because that was the rom that I used to root my phone. I definitely don't mind downloading another rom if I have to.
my current goal, if we can fix this, is to quickly just update to the official jb rom for n7000 and not play around with the rooting and such until I have even more time to learn more.
at least I know for sure my phone isn't hardbricked, I would imagine I have either missed a step or something that caused the problem.
I have read through the forum and I did come across one post talking about checking my phone's partition and such.
I got to be honest, I'm really not technically skilled enough at this point in time to dare to mess around with that type of thing yet especially with so much coding to make sense of it. (I know this is kind of dumb to say especially when I rooted my phone and screwed up this bad). More importantly, I don't even know for sure if I need to do a partition or not.
Please let me know what I did wrong and how I can fix it.
I got a question though (out of curiosity), how come there's no toolkit for the n7000 like the S3 and also the note 2???

this is the name of the old gb rom that I tried flashing.
N7000ZSKJ6_N7000OZSKJ6_N7000XXKJ6_HOME.tar
I actually have tried several other roms as well (from GB-JB, official and custom) and all of them so far has gotten to the samsung boot logo
I have read on the forums to try using Philz-cwm 6 kernel but I don't know if it'd solve my problem.
let me show you one of the threads I have read, if I dived into the wrong material let me know and I won't consider using it (or learn how to use it) for my current situation
http://forum.xda-developers.com/showthread.php?t=1661590&highlight=samsung+logo+bootloop&page=2
like I was saying before, I really have no experience in coding so all the things that really made near no sense to me. I understand the basic concept of what its trying to do it's just seems like a very unsafe method for me to try especially when I lack the necessary knowledge in this area of expertise.

did you flash the GB rom using the standard PIT file ?
also you could try with the 5 file flashing method from this thread
http://forum.xda-developers.com/showthread.php?t=1530501

Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2

asf58967 said:
Hello..
Why are you only wiping cache.
You should have done a factory reset on that step.
Sent from my GT-N7000000000 using Tapastalker 2
Click to expand...
Click to collapse
Yeah true... should also format system..
**** if you can boot into recovery , do a facotry wipe now

Galaxy S GT-I9000 not starting after using Oding to root

Hi everyone,
I was trying to root my Samsung GALAXY S GT-I9000 to install some custom roms. I followed this tutorial to install ClockWork via Odin:
http://theunlockr.com/2012/10/22/how-to-root-the-samsung-galaxy-s-i9000-cf-kernel-method/
Click to expand...
Click to collapse
everything went fine in Odin, no error messages, but my phone is stuck on the initial loading screen (that one with the samsung logo) and it's not loading properly.. I tried to wait like 10 minutes, but nothing changed..
How can I restore everything as it was before? Or flash properly a new rom??
Please help, I'm afraid I broke it..
Thank you in advance for any advice

BeNdErR said:
Hi everyone,
I was trying to root my Samsung GALAXY S GT-I9000 to install some custom roms. I followed this tutorial to install ClockWork via Odin:
everything went fine in Odin, no error messages, but my phone is stuck on the initial loading screen (that one with the samsung logo) and it's not loading properly.. I tried to wait like 10 minutes, but nothing changed..
How can I restore everything as it was before? Or flash properly a new rom??
Please help, I'm afraid I broke it..
Thank you in advance for any advice
Click to expand...
Click to collapse
Hello!
Can you get into download or recovery mode?
If you can go to recovery try wipe cache and if it doesnt work try wipe data but remember it deletes all apps!!

BeNdErR said:
Hi everyone,
I was trying to root my Samsung GALAXY S GT-I9000 to install some custom roms. I followed this tutorial to install ClockWork via Odin:
everything went fine in Odin, no error messages, but my phone is stuck on the initial loading screen (that one with the samsung logo) and it's not loading properly.. I tried to wait like 10 minutes, but nothing changed..
How can I restore everything as it was before? Or flash properly a new rom??
Please help, I'm afraid I broke it..
Thank you in advance for any advice
Click to expand...
Click to collapse
Don't worry, it is just a digestion problem (bootloop). CF-root doesn't work with every firmware. If yours wasn't compatible, bootloop is normal reaction. Check my last thread and there you can find step-by-by step guide how to unbrick it.

BeNdErR said:
Hi everyone,
I was trying to root my Samsung GALAXY S GT-I9000 to install some custom roms. I followed this tutorial to install ClockWork via Odin:
everything went fine in Odin, no error messages, but my phone is stuck on the initial loading screen (that one with the samsung logo) and it's not loading properly.. I tried to wait like 10 minutes, but nothing changed..
How can I restore everything as it was before? Or flash properly a new rom??
Please help, I'm afraid I broke it..
Thank you in advance for any advice
Click to expand...
Click to collapse
Here you go!!!
Don't worry. It is just a little thing.
Read my post here in the below given link. The solution is given in easiest steps.
forum.xda-developers.com/showthread.php?p=47034690#post47034690

Thank you so much guys it's working now, (even though I put the original one)!
I'll try to root it again asap!
tetakpatak said:
If yours wasn't compatible, bootloop is normal reaction.
Click to expand...
Click to collapse
How do I know if it's compatible or not? What should I check?
_Flasher_ said:
Can you get into download or recovery mode?
If you can go to recovery try wipe cache and if it doesnt work try wipe data but remember it deletes all apps!!
Click to expand...
Click to collapse
Sorry for the late reply: anyway no, the only thing I could do was watch the phone reboot and reboot and reboot and reboot and, finally, reboot
Thank you again!

BeNdErR said:
Thank you so much guys it's working now.
How do I know if it's compatible or not? What should I check?
Click to expand...
Click to collapse
Great, mate- I'm glad it works again
CF-Root is made AMAIK for Gingerbread ROMs only, and if you have Froyo it is enough to flash SpeedMod root kernel that already features CWM recovery, Busybox and SU. You should always ready very carefully the first posts of the files you flash, so you will void many potential problems.
If you did it after my unbrick guide thread, backup your IMEI No as soon as you root your phone (described how to)
Just click "thanks" button beyond posts which were useful for you, it is our way to express it on this forum (and many us here are visiting the forum to help each other)

GT-I9000 blackout, can only go to download mode after Odin
I also tried rooting my GT-I9000 with Odin, I got a FAILED message and my phone will no longer boot, it can only go to download mode, so I tried restoring via Odin. Sometimes I get FAILED and 1 time got pass but the unit is still in the same condition, black out except to go into download mode. Please help.

jaysonuao said:
I also tried rooting my GT-I9000 with Odin, I got a FAILED message and my phone will no longer boot, it can only go to download mode, so I tried restoring via Odin. Sometimes I get FAILED and 1 time got pass but the unit is still in the same condition, black out except to go into download mode. Please help.
Click to expand...
Click to collapse
Which Odin version did you use and what exacactly did you try to flash? Which system / Android version is installed om the phone?
tetakpatalked from N7100

Stuck on Philz boot

It's been months since I had the rom 4.2.1 official from samsung with root access. The phone is somehow a lot slower than earlier and I wanted a fresh rom install. I tried to download the latest cyanogen through CWM but it gave me error. I wanted to flash the omni 4.4 kitkat through Philz but it was always giving me an error no file_contexts set_metadata_recursive and aborting installation.
I then had the insane idea of clicking 'factory reset - wipe data' I thought it would bring back to the last rom flashed....but it didn't. Now whatever I do, I go into the philz menu (i have all my data backed up I only worry about putting a fully working and FAST rom, the phone was getting stuck every few seconds).
I can access to philz and I can access to odin. What is your advice? What could I flash next? I also read that kitkat is not running well on the gt n7000....anything recommended for my situation?
******SOLVED
I flashed from Philz 5 with CWM 6.0.3.2 a cyanogen 10.1.3 from the microsd and it worked. I wrote on the microsd from a microsd reader.

Flash stock rom through odin.
Enviado desde mi GT-N7000 usando Tapatalk 4

majaretilla said:
Flash stock rom through odin.
Enviado desde mi GT-N7000 usando Tapatalk 4
Click to expand...
Click to collapse
odin detects the device on com port, kies detects the phone and I installed the usb drivers. BUT kies stays stuck on 'connecting...'
The only possibilities I have are philz and odin. Device is detected but cannot connect looks like. So I cannot flash anything apparently.

¿Did you try Odin with phone in download mode? Vol- + home + power
Enviado desde mi GT-N7000 usando Tapatalk 4

yes phone is in odin download mode. i connect the phone, kies stuck on 'connecting'. odin on windows find the com port but cannot connect.
If I try to flash .zip files from microsd through philz 5 interface, i get the "set metadata recursive some changes failed" error....followed by 'installation aborted' press any key.
This means I am stuck because I cannot flash stuff with odin from windows, and I cannot install zips on the phone from the phone.

rogermorse said:
odin detects the device on com port, kies detects the phone and I installed the usb drivers. BUT kies stays stuck on 'connecting...'
The only possibilities I have are philz and odin. Device is detected but cannot connect looks like. So I cannot flash anything apparently.
Click to expand...
Click to collapse
Remove Kies completely.

ThaiDai said:
Remove Kies completely.
Click to expand...
Click to collapse
i just installed it....today exactly because i had to connect the phone for odin...

should kies recognize the device even while in odin download mode ???

rogermorse said:
i just installed it....today exactly because i had to connect the phone for odin...
Click to expand...
Click to collapse
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.

ThaiDai said:
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.
Click to expand...
Click to collapse
i think something has changed just now. i'll wait till i finish downloading the stock rom to flash with odin and then see what happens.
But actually main question is: why can't i flash a rom with philz? I have put two roms on the microsd (one omnirom and one cyanogen official stable) and I keep getting the installation aborted message

ThaiDai said:
Use a separate Samsung USB driver package (please search for it yourself) , do not install it with Kies.
Click to expand...
Click to collapse
I agree, that should be ur next step.
Enviado desde mi GT-N7000 usando Tapatalk 4

rogermorse said:
i think something has changed just now. i'll wait till i finish downloading the stock rom to flash with odin and then see what happens.
But actually main question is: why can't i flash a rom with philz? I have put two roms on the microsd (one omnirom and one cyanogen official stable) and I keep getting the installation aborted message
Click to expand...
Click to collapse
Did you ever consider (in the nearly 5 years of XDA membership) that it might be a good idea to read the installation instructions for the rom you want to install or to search for an error happening to you. If you didn't consider this until now: the time has come to start.
And if you do not like to accept the help members offer it is essential to do these two activities youself.

ThaiDai said:
Did you ever consider (in the nearly 5 years of XDA membership) that it might be a good idea to read the installation instructions for the rom you want to install or to search for an error happening to you. If you didn't consider this until now: the time has come to start.
And if you do not like to accept the help members offer it is essential to do these two activities youself.
Click to expand...
Click to collapse
I read instructions of course....my problem was not related to instructions (although i think my recovery mod was not compatible with the omni rom i was trying to install) and that kies thing was an anomaly. I had to wait till the stock rom finished downloading to reboot (windows asked to reboot after some time....maybe related to the installation of usb drivers but i am not sure).
Finally through Philz I was able to install a cyanogen 10.1.3 from the microsd....why I got the error with those other roms is only part of my ignorance, as I said maybe the recovery i have was not compatible (???)
thanks anyway, if I need odin to recover root access or something I'll follow your instructions in case it still doesn't recognize the connected device.

Of course your problems are related to instructions and not reading/understanding. Because these problems occured many times and were solved and got part of tutorials, q&a etc.

i searched the forum, found a couple thread entitled exactly like mine. I think one of them even had the tag 'solved' in the title. Problem is, who solved the problem never included the solution, so what is the point....And I don't get this aggression, obviously if I have a problem I try everything to fix it. I would read instructions and I also googled a lot to understand why i was getting that error from the recovery zip installation....it is not like I don't try, why wouldn't I want to solve my own problems? Also people were receiving that same error with compatible recovery / roms images....and got around the problem with many tries but I did not find any particular solution written anywhere.

Am I bricked?

Last Time i thought about little OC on my phone so I downloaded some ROM and bravely flashed it. (not the smartest thing to do I know, I know)
firstly the problem was the strange boot screen with random colours.
the after 2-3 months it started shutting down and displaying this "STD_STATE 0x00...00d0d1"
so because me is smart i did a formatting of EVERYTHING.
i found a android that should work (5.0.0 lollypop).
it had some issues like robooting instead of Everything.
but now only thing that works is a:
white inscription Android
red error, STD_STATE 0x0...000
and download mode
when i try to go into recovery mode(yes i have a clockwork mod) only thing is a black screen ( I have a suspitcion that it works but just don`t display anythig because if i click like i would to reboot i clock it reboots)
Any help, reprimand or downloads ?

Try downloading all stock files and flash it via Odin and download mode

Did you actually use everything designed for the S3 MINI? List links where you downloaded. And CWM is a fairly robust recovery so you can make a mistake if not careful.

Grumpy Cat said:
Did you actually use everything designed for the S3 MINI? List links where you downloaded. And CWM is a fairly robust recovery so you can make a mistake if not careful.
Click to expand...
Click to collapse
I can't give a link now, later I will upload files to media fire and link them here.
And i'm preety sure all files were designed for s3 mini but you know
Aaand about the CWM I know it'sounds powerful tool and it might be that I have taken a step too far
xNombre said:
Try downloading all stock files and flash it via Odin and download mode
Click to expand...
Click to collapse
Can I get links?

Blazej7 said:
Can I get links?
Click to expand...
Click to collapse
Firmware here and tutorial here. Hope that helped.

TVD1903 said:
Firmware here and tutorial here. Hope that helped.
Click to expand...
Click to collapse
Ok i`m now downloading the firmware and it`d gonna take a while. Realy appriciate it by the way .
i`, gonna keep you updated

Ok soooo...
I followed the tutorial and averything seems perfect till odin multi downloader just won`t see my phone. all the other odins work but not this one.
i`ve tried rebooting, turning odin on and off but it just won`t work. any advice?

Ok i know what`s wrong there is no version of odin multi downloader for my phone I think i am going to stay bricked unless you got any ideas?
@edit, Ok ive me a crown and call me a King I did it! I have a CWM now can anybody of you guys give me some links to Get my android back? because now i`m stuck at android screen

Ok i did it here is the list of things i did:
-found working CWM (Not touch!) despitse wrong wersion installed, it worked.
-did a Hard Wipe
-Downloaded OmniRom
-Flashed
-downloaded OC Kernel
-Flashed
-And voilà it works!