Database Develop

I think i have big problem with my n1

Hello,
I have big problem with my rooted nexus one !!
Detail :
the phone hang in boot ( x rainbow ) and i can't open recovery mod !
What i can do ??
Thank you
* : Sorry for my bad English lang

Wrong forum, this oughta go in Q&A.
Anyhow: when did the problem start? Were you flashing a radio, or did you just decide to reboot your phone?

Max-via said:
Hello,
I have big problem with my rooted nexus one !!
Detail :
the phone hang in boot ( x rainbow ) and i can't open recovery mod !
What i can do ??
Thank you
* : Sorry for my bad English lang
Click to expand...
Click to collapse
reflash recovery using fastboot

i think you have another big problem, you are not able to read the stikies so you posted in the wrong section.

I think you need to explain what you've tried to do.
Then some of the clever people on this site, may be able to work out what has happened, more info needed!

Luckily its not really a big problem. You should be able to remove battery, and go to recovery by holding power and volume down, then recovery... if not you will have to re flash recovery like www said.

tjsimmons said:
Wrong forum, this oughta go in Q&A.
Anyhow: when did the problem start? Were you flashing a radio, or did you just decide to reboot your phone?
Click to expand...
Click to collapse
The problem start after root the device directly, i did not flash the radio
Thank you for reply
www1 said:
reflash recovery using fastboot
Click to expand...
Click to collapse
i'll try
Thank you for reply
paratox said:
i think you have another big problem, you are not able to read the stikies so you posted in the wrong section.
Click to expand...
Click to collapse
Then I'll write in the correct section
Thank you for reply
Amdathlonuk said:
I think you need to explain what you've tried to do.
Then some of the clever people on this site, may be able to work out what has happened, more info needed!
Click to expand...
Click to collapse
Okay,
when i received the device i rooted after that i take the memory card to my old nokia becouse i need the contacts when insert the memory i turn on and his hang !!
Thank you for reply
rjhay22 said:
Luckily its not really a big problem. You should be able to remove battery, and go to recovery by holding power and volume down, then recovery... if not you will have to re flash recovery like www said.
Click to expand...
Click to collapse
I'll try, i hope it's not big problem
Thank you for reassuring and reply

after i reflash the recovery his hang too!
i think the system is dead how i can to keep renewing it for life ??
where are you guys !

Try this
Wipe EVERYTHING in recovery (including ext partition if you have one). Wipe the dalvik cache, everything. Then try reflashing. If it doesn't work try a different rom. If that doesn't work make sure it's plugged in and has a good charge and flash a new radio and then a new image. If not, contact HTC.

Straight from Seraph1024's stickied post:
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Sorry to hear.

brashmadcap said:
Wipe EVERYTHING in recovery (including ext partition if you have one). Wipe the dalvik cache, everything. Then try reflashing. If it doesn't work try a different rom. If that doesn't work make sure it's plugged in and has a good charge and flash a new radio and then a new image. If not, contact HTC.
Click to expand...
Click to collapse
I can't open recovery mod but i can enter the bootloader and fastboot
i try to reflash the recovery from fastboot mod but his still not working
cue_32 said:
Straight from Seraph1024's stickied post:
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Sorry to hear.
Click to expand...
Click to collapse
But i can see the bootloader and fastboot or "Hboot" !!

Is there any one that wants to help me ??

Pm me what's up and what you've done so far to try and fix it. ill try to help you.

I try Everything i want to format Everything in phone and do it again like a new device, but how ??
plz reply !!

[TUTORIAL] Fool-proof method to install latest CM7/MIUI without losing Baseband/IMEI

Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
If you have installed or updated CM7/MIUI and lost your baseband, IMEI, or both, this should help you. Due to the amount of people currently having this problem, I would recommend this be stickied at least temporarily until things are straightened out, so people can find it easily.
For Windows only, I do not have a Mac.
Step 1 - Read the entire post and understand everything involved before you attempt this. This is a long ride, probably 30-40 minutes from start to end. This is not for new people, and will assume you have a certain amount of knowledge because you attempted to flash CM7/MIUI.
DO NOT SKIP OR SHORTCUT ANY STEP IN THIS PROCESS, UNLESS I SPECIFICALLY STATED YOU MET THE CRITERIA TO DO SO. DO NOT EVEN THINK ABOUT TRYING THIS UNLESS YOU CAN REACH DOWNLOAD MODE AND RECOVERY USING BUTTONS WITH THE PHONE OFF!
Step 2 - Gather what you need...
1 - The AIO Vibrant Toolbox : http://forum.xda-developers.com/showthread.php?t=954509
Install according to directions in the post. Donate to this guy. He spent alot of time making this easy for you to do.
2 - The old CM7 install files : http://www.mediafire.com/?gn4qoonoe3cjyp6
Unzip to a location that is easy to get to.
3 - The new version of CM7/MIUI you want to install, from the thread of your choice. Donate to the developer you are using, they spend alot of their free time making your phone better. They don't get paid for it, and they dont charge you for it.
4 - Your phone, with a full battery.
Step 3 - Odin to JFD and install Clockwork 2.x
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but power it down and pull your battery. See that sticker under it that says IMEI? Write it down! You will be referencing it a few times throughout the process. Start Odin and select your pit and pda files, they should automatically come up if you are using the toolbox. Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should go to download mode, and see Odin connect. Hit start and let it fly. Once it reboots, unplug your phone. Go to settings/about phone and you should have a JFD baseband. Hit status, and check your IMEI. See how it matches the one you wrote down? Yay! Move on to the next item. If it does not, you have some reading to do because you really screwed something up, and it is beyond my power to help you...
2 - Mount phone and put the following files on the root of the sd card:
vibrant-efsbackup.zip (if you already have a backup/efs folder on your sd card you do not need this)
cm7-vibrant-initial-20110224.zip
The zip file of the new CM7/MIUI rom you want to flash.
3 - Download ROM Manager and install clockwork recovery 2.x (if you already have the update.zip on your sd card, which you should, you can also skip this) and power down your phone.
4 - Boot into recovery using the 3 button method (holding volume up and down and power, releasing power when the word VIbrant appears on your screen), hit reinstall packages, you may have to hit it twice to get to clockwork recovery. Choose to install zip from sd card, and select vibrant-efsbackup.zip. Let it do its thing. Then select reboot, and when it does, check your sd card for a backup/efs folder. Got it? Good. Power down the phone. (Obviously, if you already have the efs backup completed, you could have skipped this step.)
Step 4 - Install Clockwork 3.x and Old CM7
1 - Fire up the AIO Toolbox. Do not connect your phone yet, but pull your battery. Start Odin and hit the pda button, select the file cm7-vibrant-initial-kernel.tar from the CM7 package you unzipped (Remember, in a place that is easy to find). THIS IS IMPORTANT - UNCHECK AUTO REBOOT!!! Hold down your volume up and down buttons, and insert your USB cable, then insert your battery. You should enter download mode, and see Odin connect. Hit start and let it fly. Once it is finished, pull the usb cable. With the download mode screen still on your phone, boot into recovery using the 3 button method. You should now be in clockwork recovery 3.x. Move on to the next item! If you did not get in, you can try to pull your battery, replace it and boot into recovery from there. If you still can't get there, you get to go where the people who do not properly follow instructions go... back to Step 1.
2 - In clockwork 3.x, choose factory reset, and let it do it's thing. Then go to mounts and storage, and format system, data, and cache. Choose install zip from sd card and choose cm7-vibrant-initial -20110224.zip. As it is installing, one of the last things you see should be "restoring efs". Hit reboot when finished, and boot into CM7. When it boots, make sure you toggle the lockscreen a couple times so it connects to service. Check baseband and IMEI again. Baseband should have changed to KB1. IMEI still the same right? Awesome! Power down the phone, move to the next step! It's not? You my friend, get to meet all your other friends back at Step 1.
Step 5 - Installing what you really want...
1 - Boot into recovery using the 3 button combo. Do a factory reset, wipe cache partition, go to advanced and wipe Dalvik cache. Choose install zip from sd card, and pick that shiny new version of CM7/MIUI you picked out. You are almost there. Flash it! Reboot, and when it comes back up, take note of what time it is and DO NOT TOUCH THE PHONE FOR 15 MINUTES. You have no idea the amount of bugs this squashes. After that, check the baseband, it will be KB1 unless the rom you just flashed changed it. Check the IMEI, even though you already know it is right anyway. If it is not, do i have to say it again? You know where you are going...
2 - Destroy the paper you wrote your IMEI on, you would not want that info in the wrong hands...
3 - Enjoy your new rom
FAQ:
Q: I did everything you said, and it did not work!
A: You either skipped a step, or did not stop at the point I told you you were screwed.
Q: No, seriously, I did everything you said!
A: Seriously, I have done this 5 times in the past 3 days, and it worked every time.
Q: I installed CM7 nightly #9,10,or 11 with this method, and I have no sound on calls. What gives?
A: These builds have known issues with in call audio. Flash CM7.1
Q: Once I am on CM7/MIUI, do I have to do this every time or can I update normally?
A: Once you are on CM7 or MIUI with the proper IMEI and a good baseband, you should be able to update via the rom posting instructions. If you decided to switch from CM7 to MIUI or vice versa, I would go back to this process to get your initial installation.
Q: I installed CM7.1 and then tried to go to MIUI, and lost everything again, what happened?
A: There are changes betweeen CM7 to 7.1 that have made this difficult due to compatability issues, which is why I recommend doing this process again if you want to switch between the two.
Q: I thought there was an easier way to do this, why so many steps?
Read the first paragraph of the post, but I guess that is also asking too much...

Great post. Thanks for the info...

Pretty sure you can install the latest CM7 just via clockwork2.

i thought the baseband loss was due to kernel compatibility with the newer versions of CM7/Miui? Good post nonetheless hope it helps people out.

uurrnn said:
Pretty sure you can install the latest CM7 just via clockwork2.
Click to expand...
Click to collapse
Yes u can but some people loose baseband........didn't the op say that?

uurrnn said:
Pretty sure you can install the latest CM7 just via clockwork2.
Click to expand...
Click to collapse
Lets get this out of the way first. I am not responsible if you screw up your phone, but you are probably here because you already screwed up your phone. I have now been through this several times over the last few days. Some will say this process is overkill, but there is no denying that it always works, so please refrain from stating the obvious.
That is the first paragraph of my post. And it has already been stated that people are losing IMEI/Baseband anyway. This always works, period. Thanks for the input.

I did the steps properly and now my phone only boots to recovery...

yup i do this every time - the last few attempts with the quick two file flash method is causing all sorts of crap to go wrong on my phone even from a fresh odin - i am pdy05 and i approve this message
-screen tearing
-wifi drop
-incorrect model
-no cell connection etc....

PDY05 said:
yup i do this every time - the last few attempts with the quick two file flash method is causing all sorts of crap to go wrong on my phone even from a fresh odin
-screen tearing
-wifi drop
-incorrect model
-no cell connection etc....
Click to expand...
Click to collapse
Exactly why I went back to doing this. My last couple quick flash installs have been a disaster.
Sent from my MIUI powered Vibrant using the XDA app

Good info... subscribed for future reference. Any idea what is calling baseband/imei corruption; and why it is sporadic?
Sent from my SGH-T959 using XDA Premium App

I've done this twice now, and yet again I end up in a situation where my phone will only boot to Clockwork Recovery.
If it helps, Clockword always says E:no misc partition at the bottom. Never seen that before with all of my flashing endeavors.

darksonic said:
I've done this twice now, and yet again I end up in a situation where my phone will only boot to Clockwork Recovery.
If it helps, Clockword always says E:no misc partition at the bottom. Never seen that before with all of my flashing endeavors.
Click to expand...
Click to collapse
The e: thing means nothing, it is a old CM7 thing. At exactly what point are you getting stuck booting into recovery?
Is this your first time flashing CM7/MIUI?
Sent from my MIUI powered Vibrant using the XDA app

Great tut
I also posted something on this topic here:
http://forum.xda-developers.com/showthread.php?t=1089039
May help people that have already screwed up their EFS.

angryattheworld said:
The e: thing means nothing, it is a old CM7 thing. At exactly what point are you getting stuck booting into recovery?
Is this your first time flashing CM7/MIUI?
Sent from my MIUI powered Vibrant using the XDA app
Click to expand...
Click to collapse
Nope, I was previously running CM7.1. I said **** it and installed 7.1 from CWM2 and it worked perfectly. IMEI is correct and everything.
It seemed to **** up when ODINing the initial kernel.

darksonic said:
Nope, I was previously running CM7.1. I said **** it and installed 7.1 from CWM2 and it worked perfectly. IMEI is correct and everything.
It seemed to **** up when ODINing the initial kernel.
Click to expand...
Click to collapse
Glad it worked out for you anyway, may have been a bad download. Those are the exact files I use to do it... and I am on CM7.1 using this method after losing my IMEI trying to go from clockwork 2...
Was it when you tried to boot into clockwork 3 for the first time, or after you wiped and flashed the initial rom?
Sent from my MIUI powered Vibrant using the XDA app

Poser said:
Good info... subscribed for future reference. Any idea what is calling baseband/imei corruption; and why it is sporadic?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Completely clueless, but that is why I put this up, so after I had a definite way to fix mine, others could fix theirs. The problem itself seems to be more with MIUI than CM7, but it is happening with both. I would not be surprised if it happened to more people who have simply not checked their IMEI, and are working off a generic one because they have service.

Curious what happens if the imei is in the wrong hands and stolen
- excuse my grammar im using swype-

My external sd card is not recognized after successfully booting MIUI. This has been bother me for days now... I see sd card icon in the status bar and it says "sd card safe to remove" I tried mounting/unmounting/formating - I only see the main partition when i plug usb cable to windows. EMMC folder is empty as well.
Does anyone else experience this?!

what i dont understand is Rom manager premium made it so easy a baby could install it! download rom off rom manager premium CM7 nightlies make sure u flash clockwork recovery vibrant mtd and 3x and not 2x! install download and wait......way too easy!!!!!!!!!!!!!!!!!
Make sure u wipe data, wipe dalvik and backup rom when it asks its pretty simple.

I've got a better way, install Rom manager, select rom, click flash. TADA!!!!

Wrong way to install the CWR. My phone has a solution?

I'm so embarrassed to post this, but there we go.
CWM installed following the tutorial for the P920 using the 3D ROM MANAGER (rooted by superoneclick). Apparently installed successfully, but when trying to install the mod's ROMs (King_3d, and ThiaiZ KINGDROID), all of them will not boot completely and then turn off your device as you pressed the power button.
Trying to see what could be wrong, I saw on the back label that my device it's a P925. I was stupid and not able to make the backup old ROM.
I just killed my phone or there is still way out of it?
PS: I tried to run this rom from here http://forum.xda-developers.com/showthread.php?t=1270832 but this also does not boot completely, and the device shutting down.
Maybe a problem with the CWR?

Ratzenberger said:
I'm so embarrassed to post this, but there we go.
CWM installed following the tutorial for the P920 using the 3D ROM MANAGER (rooted by superoneclick). Apparently installed successfully, but when trying to install the mod's ROMs (King_3d, and ThiaiZ KINGDROID), all of them will not boot completely and then turn off your device as you pressed the power button.
Trying to see what could be wrong, I saw on the back label that my device it's a P925. I was stupid and not able to make the backup old ROM.
I just killed my phone or there is still way out of it?
PS: I tried to run this rom from here http://forum.xda-developers.com/showthread.php?t=1270832 but this also does not boot completely, and the device shutting down.
Maybe a problem with the CWR?
Click to expand...
Click to collapse
Just follow these directions: http://forum.xda-developers.com/showthread.php?t=1257588
Sent from my LG-P925 using XDA App

CallMeAria said:
Just follow these directions: http://forum.xda-developers.com/showthread.php?t=1257588
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Thanks, but i have no system running on phone to do this. I´m stuck on CWR with no rom.

How much battery do you have left? You should be able to boot completely with O3D ROMs, and for sure with the stock Thrill ROM. Also, are you doing a data wipe before hand?
If you can get into recovery, which sounds like you can, no need to reflash the recovery. As well, a boot loop usually means failure to wipe properly or wrong kernel (but that doesn't apply here at all).

pjcforpres said:
How much battery do you have left? You should be able to boot completely with O3D ROMs, and for sure with the stock Thrill ROM. Also, are you doing a data wipe before hand?
If you can get into recovery, which sounds like you can, no need to reflash the recovery. As well, a boot loop usually means failure to wipe properly or wrong kernel (but that doesn't apply here at all).
Click to expand...
Click to collapse
Battery it´s full! All attempts i wape the cache , data & factory, and dalvik too.
Without success, the phone keeps Shutting Down after booting the ROM's. (I can see "reading sd card" on the top bar before shutting down screen.
Thank you in advance for the assistance.

Ratzenberger said:
Battery it´s full! All attempts i wape the cache , data & factory, and dalvik too.
Without success, the phone keeps Shutting Down after booting the ROM's. (I can see "reading sd card" on the top bar before shutting down screen.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
Wait so you're actually able to boot into the operating system and then it just shuts off? Or does it reboot back to the boot screen? If its shutting off That sounds like something is wrong with the phone itself.
Try to redownload a fresh copy of the rom and push it to your SD card (check the md5 sums to be sure its right. If its not posted ask the dev to put it up). Boot into clockworkmod and go to mounts and storage. From there format /system /data and /cache. Now install the rom and reboot.
Sent from my LG-P925 using XDA App

CallMeAria said:
Wait so you're actually able to boot into the operating system and then it just shuts off? Or does it reboot back to the boot screen? If its shutting off That sounds like something is wrong with the phone itself.
Try to redownload a fresh copy of the rom and push it to your SD card (check the md5 sums to be sure its right. If its not posted ask the dev to put it up). Boot into clockworkmod and go to mounts and storage. From there format /system /data and /cache. Now install the rom and reboot.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Thanks to help-me again
I followed exactly as you instructed. Now with the ROM ThiaiZ again without success. Booting ROM (Break Dancing Droid) and then Power off
Shutting Down Screen

Ratzenberger said:
Thanks to help-me again
I followed exactly as you instructed. Now with the ROM ThiaiZ again without success. Booting ROM (Break Dancing Droid) and then Power off
Shutting Down Screen
Click to expand...
Click to collapse
There's no reason for the phone to shut off like that. Even if you are getting bad rom flashes. Unless..
I gotta ask...is the battery charged? You can lose a lot of battery being in recovery and going through reboots. It could actually be that the battery is not charged or is defective. Try charging and/or replacing the battery.
Sent from my LG-P925 using XDA App

CallMeAria said:
There's no reason for the phone to shut off like that. Even if you are getting bad rom flashes. Unless..
I gotta ask...is the battery charged? You can lose a lot of battery being in recovery and going through reboots. It could actually be that the battery is not charged or is defective. Try charging and/or replacing the battery.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
I have good news! Or bad news too. I just decided to turn on the device with the USB cable plugged in and booted it as well. He is not holding battery charge, consisting as 0% of charged. I tested another battery from a friend and did the same thing. If I unplug the USB cable the device shutting off immediately. It may be a software problem or a hardware problem coincidentally?

Ratzenberger said:
I have good news! Or bad news too. I just decided to turn on the device with the USB cable plugged in and booted it as well. He is not holding battery charge, consisting as 0% of charged. I tested another battery from a friend and did the same thing. If I unplug the USB cable the device shutting off immediately. It may be a software problem or a hardware problem coincidentally?
Click to expand...
Click to collapse
Edit: it appears they're having the same problem over in the O3D forums. Try restoring the stock firmware and stock recovery. I would also try formatting all your partitions individually (you will lose data so backup first).
Sent from my LG-P925 using Tapatalk

DELETED.
Sent from my LG-P925 using Tapatalk

CallMeAria said:
Edit: it appears they're having the same problem over in the O3D forums. Try restoring the stock firmware and stock recovery. I would also try formatting all your partitions individually (you will lose data so backup first).
Sent from my LG-P925 using Tapatalk
Click to expand...
Click to collapse
I set my phone for Stock & Recovery firm, unrooted. Nothing doing! I give up, nobody knows how to solve this problem. I'm totally frustrated with it.

Dead Samsung Galaxy Note. Need Suggestions.

I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-

cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
my suggestion is to read this and run before you get bombarded http://forum.xda-developers.com/showthread.php?t=1321268

I think you dont know what you are doing, as you dont know where to post so i think its better off you dont do anything with your phone

It should be in Q&A forum....Moderators please move it to appropriate forum.....

Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app

Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium

I have to place my threads in the correct category, and so do you.

first move to the right place
second give more details of what you have done, the steps, the kind of kernel, rom, otherwise we cant give you accurate solutions
Sent from my GT-N7000 using XDA

Start Thread and ask for donations, that's what we all do here.

Yes...I see that's the trend here... I suggest when they got, just buy themself an SG3

xlfate said:
Bro you should've use abyss kernel with red pill to downgrade to gb... cwm has some sort of bug even if its fixed . Be on the safe side and flash abyss
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Agree..use abyss kernel to wipe anything bfore flash any ics rom for ur own safety
Sent from my GT-N7000 using xda premium

Samsung service seems the only solution as you can't get into dl or cwmr modes.
Sent from my GT-N7000 using xda premium

http://forum.xda-developers.com/showpost.php?p=28744408&postcount=5713
This great solution comes from rocket thread, where else.

Galaxtus said:
Stop irritating him. How do you feel if your phone got bricked and don't know what to do.
Coming to the topic. You did not follow basic steps, you used the wrong method of rooting that to on ICS. Don't think that your phone is bricked. Did you flash any custom kernel. I think you were trying too many things and your phone is dead. This happened to me once, I thought my phone is bricked and didn't know what to do. But I remembered I had a external battery adapter charger and charged my battery separetly and know what it worked. Try charging your phone separetly.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I'll post it in right forum to get my queries answered..better to follow the rules...its not hard to understand.better to spend ur valuable time to read it and posting in the appropriate forum to get correctly answered rather than opening topics. Just a suggestion...
Nw come to the point. Please explain the situation what u did and what files u flashed? XDA are always here to help you.
Sent from my GT-N7000 using XDA Premium App

cyyong95 said:
I was trying to root and install a custom ROM on my phone when this happens.
I suffered 3 kinds of brick that I recognized from reading the forum's guides.
So here's the story:
I install SuperUser and CWM through the stock recovery mode.
After that I tried to wipe everything with CWM from my phone as I wanted to downgrade from my update Official ICS back to the stock GingerBread ROM. (This is to prevent any problems to install the new custom ICS. Read on forum also*)
During the wipe, CWM got stucked at somewhere at the start of the process (Forgotten what it was). It was about more than 15minutes before I made my decision to stop it by holding the power button. Obviously this caused a bootloop or something like a soft brick (Stuck at boot screen).
After the first brick encounter, I tried to fix it by flashing the stock GingerBread ROM directly with Odin without wiping anything as it was stucked in the first step. By doing this, I think I had a Super Brick as the installation also got stucked at loading factoryfs.img image file. There's no solution to this as I looked up in the forums for quite some time.
So, I cancelled the installation and my phone wouldn't start up again. There's no sign of battery charging when plugged in and it wouldn't start by holding the power button. Unable to access recovery/download mode. Odin also didn't recognize my device.
Can anyone here kindly advice me on what should I do now? In deep sad mode -.-
Click to expand...
Click to collapse
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.

I'm sorry to post in the wrong section of the forum. It was my mistake to not read instructions carefully.
Now I have sent it to the service center and waiting for their response. But I didn't do anything like put my phone in the microwave or anything.
So does that means they will find out that I did something to my phone and void my warranty?

smaiitm said:
Have you read the post quoted below?
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Please read and see if it helps. Or maybe you have already tried the process outlined.
All the best to you.
Click to expand...
Click to collapse
Thank you very much for the help but it was too late as my phone is already confirmed hard bricked.
Will try it if I got the chance to bring my phone back to life.

Changed a new note from samsung service LOL

cyyong95 said:
Changed a new note from samsung service LOL
Click to expand...
Click to collapse
Great! Have Happy Times Flashing Safely! Cheers.

brick my htc one needs help

I brick my htc one, what to do next, help me plzzzzz.

need a little more info than that

this is what happened
dinu5885 said:
I brick my htc one, what to do next, help me plzzzzz.
Click to expand...
Click to collapse
I did flashed android revolution hd on my htc one, and I thought something went wrong so I took the decision to re do it, and I was stocked at final step, showing 10% only, not moving any further, then I was out of juice and my phone went dead, and when I restart it, its just showing start up.screen not moving any further.

You need to boot in to recovery and flash it again. The installation didn't finish so of course it's not going to go any further. It happens all the time.
Sent from my HTC One using Tapatalk 4 Beta

I am layman
skinsfanbdh said:
need a little more info than that
Click to expand...
Click to collapse
I thought to root my mobile, unaware of benefits and risks, somehow I managed to root, then thought ti flash a Rom, just Googled it, decided to go for android revolution hd with twrp recovery, twice I use touch screen then I took the lesson to not to touch it, and finally I flashed it, but I was not able to download apps from store, so I took the worst decision of my life, to re do the procedure, and I did went upto final step of installing android revolution hd, there I was stucked at 10%, not moving any further. Finally when my battery was zero percent I tried ti switch on my mobile and I am stucked at start up screen.

not going into recovery, volume and on off switch making no sense at all.
xXxG0dzRAgexXx said:
You need to boot in to recovery and flash it again. The installation didn't finish so of course it's not going to go any further. It happens all the time.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
It's just not happening, not going into recovery mode.

What do you mean? Did you turn it off and when turning it on immediately hold down the volume down button so you can get to the screen to select recovery?
Sent from my HTC One using Tapatalk 4 Beta

dinu5885 said:
I thought to root my mobile, unaware of benefits and risks, somehow I managed to root, then thought ti flash a Rom, just Googled it, decided to go for android revolution hd with twrp recovery, twice I use touch screen then I took the lesson to not to touch it, and finally I flashed it, but I was not able to download apps from store, so I took the worst decision of my life, to re do the procedure, and I did went upto final step of installing android revolution hd, there I was stucked at 10%, not moving any further. Finally when my battery was zero percent I tried ti switch on my mobile and I am stucked at start up screen.
Click to expand...
Click to collapse
hold power+volume down with phone under a bright light until it boots to bootloader. you might want to try a rom that doesnt use aroma until your comfortable with recovering your phone when something happens

exactly
xXxG0dzRAgexXx said:
What do you mean? Did you turn it off and when turning it on immediately hold down the volume down button so you can get to the screen to select recovery?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
That's what I am doin, but I am again landing on start up screen only, htc
One tm.

dinu5885 said:
That's what I am doin, but I am again landing on start up screen only, htc
One tm.
Click to expand...
Click to collapse
plug it in to a computer open cmd and type adb reboot recovery

thanks
skinsfanbdh said:
plug it in to a computer open cmd and type adb reboot recovery
Click to expand...
Click to collapse
Lets see.

i suggest you use rayglobe or rgui as they dont use aroma so no freezes and less issues when upgrading

nothing seems to work
skinsfanbdh said:
i suggest you use rayglobe or rgui as they dont use aroma so no freezes and less issues when upgrading
Click to expand...
Click to collapse
I connected it to.computer, tried some command on cms. But as I am not in recovery, mobile is not accepting command.

dinu5885 said:
I connected it to.computer, tried some command on cms. But as I am not in recovery, mobile is not accepting command.
Click to expand...
Click to collapse
adb reboot bootloader if you get to bootloader select recovery if it starts recovery then backs right back out then fastboot erase cache then go to recovery

skinsfanbdh said:
adb reboot bootloader if you get to bootloader select recovery if it starts recovery then backs right back out then fastboot erase cache then go to recovery
Click to expand...
Click to collapse
What do u think, can htc people fix it, it starts n restarts, but not at all going in recovery.

you can fix it. if it turns on its fixable there are many threads around with people who have had the same issues as you and they fixed it with the help of others. just dont freak out.
what os are you running on your computer?

skinsfanbdh said:
you can fix it. if it turns on its fixable there are many threads around with people who have had the same issues as you and they fixed it with the help of others. just dont freak out.
what os are you running on your computer?
Click to expand...
Click to collapse
Windows xp

dinu5885 said:
Windows xp
Click to expand...
Click to collapse
do you have all in one toolkit?

skinsfanbdh said:
you can fix it. if it turns on its fixable there are many threads around with people who have had the same issues as you and they fixed it with the help of others. just dont freak out.
what os are you running on your computer?
Click to expand...
Click to collapse
When I connect Mobile to computer drivers r not getting installed, how do u think without that it is going ti accept any of the cmd command.

skinsfanbdh said:
do you have all in one toolkit?
Click to expand...
Click to collapse
Haven't heard of anything like that before, u just help me and I will buy u beer.