Database Users

Bricked Nexus S

I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark

You can mount your sdcard from recovery, there is an option for mounts in the first menu. Then transfer whatever file you want to flash.
Sent from my Nexus S using xda premium

It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.

Please post the exact model of your phone and the exact file you flashed, and the exact CWM recovery file you flashed.

Also, if you can get to recovery you haven't bricked your phone
If you haven't done it already I'd also flash superuser. If you are after a stable ROM based on CM7, I'm using NSCollab 1.0.39 and works very well.
Sent from my Nexus S using xda premium

mcdanish said:
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Click to expand...
Click to collapse
Which drivers do you have installed, just the ones from the Android SDK? what Windows do you have?
Sent from my Nexus S using xda premium

mcdanish said:
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
Click to expand...
Click to collapse
when you flashed cyanogenmod after flashing the kernel, cyanogenmod automagically overwrote the kernel that you flashed first, so thats not the issue. try wiping data, then reflash cyanogenmod and the gapps.

simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.

mcdanish said:
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
Click to expand...
Click to collapse
ahh, i misread what you wrote. im glad that it got straightened out anyways

Good to hear
NSCollab 1.0.39 is pretty stable with the Matr1x 5.5 kernel it comes with and you'll notice a better battery life too.
Sent from my Nexus S using xda premium

U8800-51 Black screen, no boot! PLEASE HELP

I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.

You installed u8800 rom to u8800-51???
Sent from my U8800 using Tapatalk 2

From the links I followed for the 8800-51, that was the ROM to use.
Sent from my Galaxy Nexus using xda premium

Can you still get to pink screen?
Sent from my locked MB865 on Ice Cream Sandwich.

thenewguy821 said:
I have a Huawei u8800-51 that I tried to install the official 2.2.2 ROM from Huawei, File name "U8800V100R001C00B138SP04CUSTESTC205D001 (Estonia Elisa)". I double checked that it wasn't the pro file.
It went through both steps fine, and said upgrade complete Rebooting. When it "Reboot", it vibrated slightly, but went no further, only a black screen. I left it alone for about 10 minutes, in case it was part of the upgrade process, but it never powered back on. I tried to reboot manually, with the same results, just a short vibration, and black screen. I have searched high and low, to no avail. I have tried putting the same dload file from the file on the SD card, pull the battery and plug to computer ( one of the possible fixes that I found ), but again, same results.
Is the phone officially bricked now, or can it be recovered? ANY help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Try connecting USB cable from PC to your phone with out battery....

krish_nank said:
Try connecting USB cable from PC to your phone with out battery....
Click to expand...
Click to collapse
Tried that as well
Sent from my Transformer TF101 using xda premium

Disk image
thenewguy821 said:
Tried that as well
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?

Somcom3X said:
You didn't make a disk image?
Can you give me a link to the rom/guide you followed?
Click to expand...
Click to collapse
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium

thenewguy821 said:
I was jumping back and forth between here, rootzwiki and another site, hard to follow the trail. I did do a backup in CWM Recovery, but I couldn't get into recovery to try to restore.
Ended up taking the phone into AT&T, told them the hone wouldn't boot after an update. They replaced the phone, no charge.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
I have the same problem. No one know how to fix this??

Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium

u8800-51 black screen, not booting at all. no pink/blue or even recovery. a little vibration and that's it..
any help is appreciated, thanks.

Somcom3X said:
Let me try making a disk Img for you
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
How can the disk image help if we cannot load without getting to a pink/blue screen?

when you took your phone to att
did you have service with them at the time?

http://forum.xda-developers.com/showthread.php?t=2000509
I have same problem after update ... any solution

Can't help due to it screwing up your process to motherboard connection

Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.

eyeconic said:
Somewhere in the sticky section of this forum should be "Back the kcuf up!" with links to image backup instructions. I have started doing it routinely. I bricked my phone this morning with a mundane font manager (who'd a thunk?). An hour later it was working just fine.
Click to expand...
Click to collapse
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.

Somcom3X said:
Its a pinkscreen backup no? I use it rarely, more likely for Official roms such as froyo, ging.
Click to expand...
Click to collapse
Absolutely. I made one paperweight that CWM refused to restore from a blue screen. I have two scripts:
#!/bin/bash
dd if=/dev/sdb of=u8800.img bs=512
#!/bin/bash
dd if=u8800.img of=/dev/sdb bs=512
I'm sure that there is a WinDoze equivalent. Before installing any app that needs root, I do a complete BU.

Wi-Fi not working

Have been enjoying epinter's ROM, but recently been having some issues.
Last week, everything suddenly started misbehaving, and then it rebooted and went into a boot loop. I restored to an older NANDROID backup and it worked fine. But since that event, it has been rebooting quite regularly at random times. Sometimes, it goes into a bootloop. Have realised that if I take out the battery and leave it to cool down for a few mins, it starts working fine. I suppose this is to do with overheating.
I deleted FastDormancy.apk as suggested by epinter. Doesn't seem to have made a difference.
Since day before, it isn't detecting any Wi-Fi networks. I flashed the 20120922 version of epinter's ROM too, but still have the same problem. Tried the WiFi settings, but that didn't help.
Today I cleared data and cache, and reinstalled 20120922 version of the ROM, but still got the problem.
I also upgraded radios to 37p. Didn't help.
Any suggestions on how to diagnose it? Is it possible that Wi-Fi (hardware) is bust?
Sent from my MB860 using xda app-developers app

No suggestions?

Maybe hardware!
Sent from my MB860 using xda premium

Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium

Cab121 said:
Might suggest a full -w in fastoot. Load a different recovery via fastboot then a stable rom just to test with like Joker CM9 or Fruitcake.
If that don't work start checking antenna connections and ribbon cables for damage.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
What do you mean by 'Load a different recovery via fastboot'? I have used fastboot to wipe fully, but could you point me to the 'recovery' to be used?
Thanks

My phone is repeatedly rebooting now. It's not in a boot loop. It actually boots into ICS and then reboots after some time.
Really would appreciate any insights on this.

You can use fast boot to flash recovery files to the phone. You need to while recovery then use "fastboot flash recovery filename.img" for example. Assuming your file is in the same directory on your PC.
I only suggest out of practice. I typically find if any part of the hardware fails to boot or load with the rest of the phone I start with a clean cwm ,rom, and so on. Start at 0 essentially. If the problem goes away then its most certainly soft wear and you can trouble shoot from thwre
Sent from my MB860 using xda premium

Does Bluetooth work ?
Sent from my MB860 using Tapatalk 2

I've been using the 20120825 version of epinter's rom, and everything has been incredibly stable for me except wifi and bluetooth. Neither will turn on, and under advanced wifi settings my wifi chip is giving the mac address as not available.
I flashed CM7 a few weeks ago to see if that would fix it and CM7 gives an error when I try and turn wifi on, also showing not available for the wifi mac address.
I've seen around here a little bit that this might be a hardware issue that happens irrespective of what rom you use or if still on stock.
Has anyone found a fix for it?
EDIT: also using the 37P radio.
I also found this thread... http://forum.xda-developers.com/showthread.php?p=26163360

[Q] Need some help with boot loop on ColdFusionX

Well, i've flashed my Blade with ColdFusionX ROM and everything seems to be great.
Then i decided to restart it and it stays on boot loop. It can be solved by entering on recovery and wiping the Dalvik Cache, but i want to know if there is another way to solve it? It's kinda annoying making it everytime i need to restart or shutdown.
Another question is for a good app to make USB Thetering, since the one on this ROM works but drains battery faster then USB provides.
Thanks and sorry about the bad english.
link to ROM's page: http://forum.xda-developers.com/showthread.php?t=1429539

Update:
Now things are worst then ever. I've updated ROM Manager to last version and then i can't enter on recover anymore and cellphone can't start.
Is there any way to flash the recovery from outside the phone?

Method 2.
http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/
Sent from my GT-I9300 using xda premium

Do you have Blade drivers for Windows 8, that drivers are for 7 and they aren't working.

Tryed method 2 but it didn't work, adb can't see my device connected. Now i'm trying method 3.
How can I know what TPT should i use?
Sorry for being so noob.

If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium

UrbanDrawer said:
If you got your phone with 2.1 it is gen1, if 2.2 it is gen2.
Therefore, use gen2.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
It is with 4.0.4 gen2, but i don't know if i have to use chinese or european TPT.
It was manufactured in china, so I use the Chinese TPT, right? Seems obvious but i'm kinda scared.

Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)

Flash another rom.
Sent from my GT-I9300 using xda premium

vittal said:
Update: Problem Solved!
I turned it in recovery mode, and it got stuck as was happening before. So I left it a while and when i plugged him on the computer, adb recognized it and I could use the fastboot of method 2.
But i still got the problem with the Boot-looping on ColdFusionX that I said on first post. Is there a way to fix this? (It can be fixed wiping the Dalvik Cache every boot, but it is annoying)
Click to expand...
Click to collapse
This will keep on happening because the rom u are using has stopped development. Soon u will also loose Google play.
Do what urbandriver said. I recommended konsta T' cm9 (Google it).
Sent from my Blade using xda app-developers app

Can't upgrade from 2.2

[Resolved]
Help, I downgraded from 2.3 to 2.2 for various reasons,but now when I try to upgrade again I just get the pink screen ,if I try using the option from settings/storage,it says key data couldn't be backed up , the installation will stop. Also if I boot into the system it runs fine for about a minute then locks up completely so I can't even continue to use it in 2.2 can anyone advise ?
Sent from my Nexus 7 using XDA Free mobile app

Try to put the 2.3 dload folder to a sd card, then remove the battery, plug in a USB cable to the computer and the phone, volume up+down+power (if I remember right lol). See if it will update that way.

no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app

totsy1972 said:
no, that's the usual way I've been flashing it, I can get to the image folder ,but it won't boot into recovery either
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Odd. Maybe try to flash the ICS pink screen unlocker? I had weird issues at some point too, then I flashed that and the problems went away. Afterwards flash ICS.

Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app

totsy1972 said:
Just tried that,still no luck,it doesn't even get to the unpacking screen,it just stays pink. beginning to think its beyond repair
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.

CrysisLTU said:
I think it's still possible to fix it. I was loosing hopes too, but I messed around with it anyway and got it working. Just try different dload's, different methods and maybe you'll get it running. Maybe other users will have some ideas too.
Click to expand...
Click to collapse
I've been trying all different ways, this is what I get when trying it from storage menu
Sent from my ST15i using XDA Free mobile app

@Moihack maybe you have any ideas? You've written this to me before:
Moihack said:
As long as your phone still gets power and pink/blue screen shows there is nothing to be afraid of yet,since this isn't a hardbrick.
Contact me on hangouts telling me what you have done resulting in the above issue.
I have bricked my u8800pro in every possible way both soft and hard brick (thank god warranty was still active back then).
Click to expand...
Click to collapse

Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
My suggestions:
1) Do a factory reset and then check if you can upgrade
2) Try re-installing your recovery(use cwm 5.0.27 by geno for best compatibility) or even replace the whole image folder with the froyo one from here: http://forum.xda-developers.com/showthread.php?t=2146856
Your phone is not beyond repair that's for sure. Since it boots fine.

Moihack said:
Hi there!
I think when you upgrade from software menu there is an option for data back-up.
Uncheck this option and the error should go away.
Also what do you mean with this: "Also if I boot into the system it runs fine for about a minute then locks up" ?
What do you mean it locks up? Touchscreen is not responsive for example?
Click to expand...
Click to collapse
I haven't noticed an option for data backup,will check again later on. And yes when it locks up touch screen becomes unresponsive and none of the buttons respond either. Also when I try to enter recovery ,both custom and stock, it displays the kernel logo then vibrates with a black screen for a second then back to kernel logo and continues to boot.
Sent from my Nexus 7 using XDA Free mobile app

Ok guys,I copied over the stock image folder and now it works ok, however I still can't upgrade from froyo. At least I can use it again though so thanks for your help, its much appreciated. Incidentally, there wasn't an option to back up data when upgrading, but that error has now gone, except it now just reboots instead, so I will just keep trying.
Sent from my U8800Pro using XDA Free mobile app
[Edit] Finally I've managed to upgrade to GB , had to put both step 1 and step 2 in the same dload folder and it worked. So cheers for the tips

You've put all steps in one folder?

DarkSkyGhost said:
You've put all steps in one folder?
Click to expand...
Click to collapse
Steps 1&2 in dload folder ,step 2 renamed to UPDATE_G.APP.
Didn't use step 3 as I was updating to ICS after that
Sent from my Nexus 7 using xda app-developers app