Related
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
kim2rock said:
Hi,
I was trying to flash a Ultimate Honeycomb v3.1.1 theme on my VZN Fascinate using CWM, but after flashing and rebooting, it just sits there on the booting screen (flashing honeycomb) while the phone vibrates occasionally. Can someone tell me how to fix this or why it's happening? I didn't have problem flashing gingerbread theme by nitsuj17.
I have SC2.9.2 voodoo/EB01
many thanks,
Click to expand...
Click to collapse
Download might have been corrupted or you flashed SC and then flashed the theme without rebooting in between.
Thanks jonesya13!
I'm pretty sure I rebooted in between, but I will try to re-download the file and then flash the theme again as you suggested.
This happened to me on both the 3.1 & 3.1.2 with superclean 2.9.2. I booted fully into superclean as well before flashing the theme after a cache/dalvik wipe. Battery pull worked both times. Rebooted normally after that.
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
kim2rock said:
Thanks garywojdan81!
I tried to flash with a newer ultimate honeycomb (3.1.2), it flashed without a hitch but I found out that menu & home button didn't work. So I went back to SC2.9.2... I will try battery pull & wiping cache/dalvik then reflash the 3.1.2 theme.
Click to expand...
Click to collapse
I had the menu and home button problem as well, ended up flashing, I think the EC10 kernal, and it fixed that problem for me.
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
kim2rock said:
Thanks jonesya13 and garywojdan81!
I tried reflashing the theme after wiping cache/dalvik - that did the trick!
I have not tried the EC10 kernel yet. So far, I'm satisfied with EB01, so I'll try sticking with it until it causes problems.
Click to expand...
Click to collapse
You might as well as update to jt's ec10. BLN + Sound + Color.. Epiiiic
Just wipe cache/dalvik
Rocking Frankenclean 2.9.2 Voodoo/EC10+Sound+BLN+Color/Nitro Ultra Honeycomb v3.1/XDA Premium
xHoLyx,
What might be some advantages of jt's EC10 over regular EB01, in your opinion? I'm not too familiar with kernel replacement, so reading relevant posts might take some time. thx!
I tried 2.2 out a few weeks ago and decided I couldn't live without Voodoo Sound and BLN so I decided to wait it out. Obviously we have these enhancements available for Froyo now, so I made the jump to JT's initial EC10 release.
Everything worked fine, I just didn't feel that "snappiness" I had before. I thought maybe it had something to do with being undervolted (even though only slightly.) I saw that there were some problems with imnuts initial kernals he posted and waited to flash the updated (fixed) link for 0328_imnuts_sv_voodoo.zip. I flashed last night, booted up, and played around for a little bit and everything was working great. I had it plugged in to charge overnight. That brings me to my issue...
I woke up this morning, reached over to turn my phone on and I got NOTHING. No boot, samsung, lights, nada...I thought "****, I really bricked my phone now." I tried booting into recovery using the 3-button combo, plugging it in my computer to try download mode, plugging my charger in different outlets,etc...The phone seemed like there was no sign of life. I was ready to head to Verizon before work then decided to plug in my car charger for ****s and giggles and sure enough...IT WORKED! It started charging and I turned the phone on. Now I am at work and the phone seems to be working just fine...I even have the usb plugged in my computer and it is charging now (The same one that didn't work this morning.) This has never happened to me before and it was pretty scary. I have had to ODIN before, but I was worried that wasn't even an option. Thanks god everything SEEMS to be working fine right now, though that made me a little concerned.
Do anyone have ANY idea what might have happened!? Thanks in advance.
EDIT: After a couple hours, I saw my battery start to wig out. It went from being at like 34% to flashing the "low battery" warning. It then turned off and did the exact same thing. I had to go out to use my car charger to get into recovery. I wiped cache/dalvik cach, and re-installed SC. Not sure if it's kernal/ROM/Theme with 3rd party battery supprt...
Voodoo'd Samsung Fascinate
Kernal: 0328_imnuts_sv_voodoo
ROM: Superclean 2.9.2
Theme: Nitro's Ultimate Honeycomb v3.1.2
Details of my problem are here: http://code.google.com/p/atrix-dev-team/issues/detail?id=115&can=1&start=100
Samcripp asked me to open an issue, but it was later closed as its not related to CM7.
Basically after updating to 0.19 Faux kernel and OCing, my bluetooth does not work (does not turn on) and my wifi says "error" and reboots if I try to turn it on. Logcats are attached in the link above.
Before this, I also tried the 1.35 Radio but I'm pretty sure it worked after flashing back to 1.77.30P.
I've tried everything from erasing via fastboot and clean installing stock 2.3.4, alien and CM7 -still nada. Tried restoring pds partition, nada. Tried different radios, nada. Only thing I didn't try was to SBF to stock. Can someone point me in the right direction to a SAFE SBF that I can used on an unlocked ATT Atrix?
Here is the dmesg: http://db.tt/92GSbZ4
Says something about buffer overflow, vdd.
Any help?
Sent from my MB860 using XDA App
Here is another (see bottom)
http://db.tt/3I2A7ca
Sent from my MB860 using XDA App
I got it to work momentarily but then phone froze and went back to error. I had followed these instructions: http://forum.xda-developers.com/showthread.php?t=1077329 and then did a dalvik cache wipe.
What could this be? Hardware?
Think its definitley a hardware issue. I can get the bluetooth/wifi to work by taking out the battery and tapping on the back of the phone..but then it dies later.
Next question: Any way to get "Unlocked" from showing on the bootscreen?
Had a similar issue
I once had a similar issue with my wifi after installing the same kernel. Consider restoring the stock kernel before you consider your phone broken. When you change kernels, since the kernel is central often, hardware is messed upOA component,
Have tried stock kernel, 1.83 kernel, faux kernel and kholk's kernel..all the same. Wiped cache/dalvik cache after all.
Getting replacement device from ATT. Just trying to figure out if I should send back with "Unlocked" text or not.
Theres got to be a solution, somewhere ... I can't get it replaced.
Someone...
was there a solution to this i am having the exact same problem
ive been running jokersax cm9 shortly after flashing 0.33 i noticed i no longer was hooked up to wifi. After looking into it i noticed bluetooth is also a no go.
it never gets past "turning wifi on" i have since done a complete format/factory reset, flash .33 and .4, went back to Cm7 still no change i have also flashed multiple kernels.
Last try was flashing radio N_01.77.37p still no luck
Having the same problem. Wonder if we can buy just the system board of this phone
Sent from ATRIX (CM7) using the XDA Premium App
Yes, Wifi/Bluetooth is a hardware issue! My phone just died of this same fate. If you want to take advantage of your warranty, then flash the 2.3.6 SBF after wiping all user data. BE CAUTIOUS. And can we make a big sticky for this problem? There are literally dozens of threads about this
Hey, My wi-fi/hotspot shows up as error when i go to settongs and wireless networks. i had the problem with alien#4 so i decided to switch to cynanogen 7.1 and still nothing :/ is it a hardware problem or i need to flash a different baseband/kernel or what? thanks for the help in advance if anyone reples. it would mean alot haha
I had that issue when I installed one of faux123 kernels.I re-flashed the kernel wipped cache and dalvik and rebooted.I didn'tn have the issue afterwards,hope this helps out.
thanks. I tried flashing a 1.30 ghz kernel by faux123 and i have a bootloop :/
try flashing a different kernel.I notice the 1.3 works better than 1.45 for me no bootloops.try going into cwm and clear cache dalvik and fix permissions.
ok,im using tenfars recovery. should i be using clockwork mod?
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Atrixn00b said:
i don't know what the problem is :/ i still have error for wi-fi.. but i flashed 145 cause that's all that would work
Click to expand...
Click to collapse
Tenfa'rs recovery is outdated. Use romracer's instead (he just updated today).
*Edit* I ran into this same problem early on when I started flashing customs mods. Ended up having to go back to my "stock" backup before wi-fi started working again. After that, I haven't had it re-occur. That might be your best bet to get it functioning again. If not, it may be a hardware issue.
haha I just got this thing 3 months ago...hopefully it's not a hardware issue. but i'll try that
MY phone is completely effed right now..like the "soft keys" on the bottom don't work and the screen sensitivity is really low..it's like my phone is destroying itself or something.
Sounds like a hardware issue. I had the same exact issue.
Wifi error, some random reboots especially after trying to turn it on.
after much testing, reading, and playing around i started getting constant reboots. You could get too the lock screen, then it would reboot.
Before jumping to conclusions about hardware go back to your stock backup.Also use RomRacers newest recovery.then start flashing kernels again and see if the problem persists.Its easy to blame everything on hardware issues but often that's not the problem.
Not the same as what Noob4Life is posting.
First of all, I'm in the UK and was running the stock 2.2 or whatever was the stock was for Orange in the UK a month back, until I finally decided to upgrade to CM7.
A few weeks went by, all was awesome. Until last week my Wifi stopped working, my bluetooth stopped working and my Mobile hotspot stopped working. And looking around on a few posts on here, it seems that it is hardware based.
So what I'm asking is, does anyone know of a way I can go back to the stock 2.3 that has just been released in the UK? So it seems like I never did anything to the phone and then I can see if it is infact hardware, or software based. So if it is hardware related, I'm hoping I'll be able to get a free repair / replacement, as I have insurance. But from what I've seen, it will cost me if I take it in with CM7 on.
Thanks for any help anyone is able to provide.
piemanpm said:
Not the same as what Noob4Life is posting.
First of all, I'm in the UK and was running the stock 2.2 or whatever was the stock was for Orange in the UK a month back, until I finally decided to upgrade to CM7.
A few weeks went by, all was awesome. Until last week my Wifi stopped working, my bluetooth stopped working and my Mobile hotspot stopped working. And looking around on a few posts on here, it seems that it is hardware based.
So what I'm asking is, does anyone know of a way I can go back to the stock 2.3 that has just been released in the UK? So it seems like I never did anything to the phone and then I can see if it is infact hardware, or software based. So if it is hardware related, I'm hoping I'll be able to get a free repair / replacement, as I have insurance. But from what I've seen, it will cost me if I take it in with CM7 on.
Thanks for any help anyone is able to provide.
Click to expand...
Click to collapse
I had that problem with cm7...so thought it was my phone. Tried a different rom....worked again...tried cm7 again. And it started working.....just reflash.....obviously wipe it.
Sent from my MB860 using xda premium
Like Sexywacko said, first try out a fruitcake or another rom - best to take the new AT&T with the corresponding radio found here.
If it still doesn´t work, try another one. If all goes bad, you have to get the SBF from the OrangeUK GB-Update found here - extract the system, boot and webtop + the radio and fastboot flash those. This comes as close to stock as you can get without using SBF+RSDlite...This post will help you.
And don´t be afraid - I read on multiple occasions, that people had no problem getting their unlocked/rooted devices repaired without any waranty-problems. Just don´t tell them!
Thanks for the help guys.
Just put Fruitcakes "2.3.5 System and Boot NO Webtop" on, and turning wifi on is still causing " error " and causing a reboot.
How do I install new radio things? I'm a complete noob at this, and only put Cyanogenmod on using a guide ( http://forum.xda-developers.com/showthread.php?t=1336232 )
And now it's stuck rebooting all the time because it's trying to turn Wifi on.
Flash the 36P radio from the Fruitcakes thread through CWM in the same way you flashed 2.3.5. Remember to wipe cache first in CWM.
Well installing the 36p seems to have done the trick. Thanks alot dude!
Updated to Fruit Cakes 2.3.5 System and Boot NO Webtop with ATT 1.77-36p radio. Seems to have fixed the problem.
Don't want to risk putting Cyanogen back on incase it stops working again.
Thanks for your help again guys
piemanpm said:
Updated to Fruit Cakes 2.3.5 System and Boot NO Webtop with ATT 1.77-36p radio. Seems to have fixed the problem.
Don't want to risk putting Cyanogen back on incase it stops working again.
Thanks for your help again guys
Click to expand...
Click to collapse
I am using CM7 weekly #3 with Faux stopgap+ 1.0GHz kernel and 36P radio with no issues. Works very well for me.
It's stopped working again. Stupid thing. Going to try and restore it to stock orange ROM and see if that fixes it.
Anyone able to help?
Think I'm just going to give up and " Accidently " drop my phone in the bath and claim on insurance. This having no wifi is doing my head in. I've tried CM7 with " ATT .91 Radio " and " ATT 1.77-36p " radios. And I've tried Fruitcakes 2.3.5 System and Boot NO Webtop with " ATT .91 Radio " and " ATT 1.77-36p " radios and still no success in getting wifi to work for over 2 hours without crashing my phone / not working again.
Motorola Phone Tools isn't picking my phone up properly, it's just picking up my IMEI number, not my Carrier or Model.
Must say I'm at my wits end.
Its obviously. A hardware issue do. A insurance clame. On it cause it sours like the radio is broken
Sent from my MB860 using xda premium
I'm afraid it's looking that way.
Well I've decided to try RSD as my last resort to try and get my phone wifi working. I unlocked the bootloader and installed cyanogen using this Guide. I then put Fruitcakes 2.3.5 System and Boot NO Webtop on and the radio mentioned in this Thread with little success at getting it fully working.
My phone info ATM:
System Info
4.5.133.MB860.ATT.en.US
Android Version
2.3.5
Baseband version
N_01.77.36p
Kernel version
2.6.32.9 [email protected] #2
Build number
4.5.133
I'm thinking of using this: http://forum.xda-developers.com/showpost.php?p=19657465&postcount=248
What I'm asking is, realistically, what is the chance of bricking?
Looking to do the same, currently unlocked and rooted running CM7.
Is it possible to install the official 2.3.4 orange UK and have it locked with root access removed?
arukanferu said:
Looking to do the same, currently unlocked and rooted running CM7.
Is it possible to install the official 2.3.4 orange UK and have it locked with root access removed?
Click to expand...
Click to collapse
I downloaded the latest RSD and downloaded this image
Booted phone up in RSD mode ( power button + Volume Up ) then plugged it into my computer. Waited for all the drivers to install. Opened RSD, loaded the image and set it going. Do not unplug it at all until it says " Please boot up phone manually " or something along those lines.
Once it'd done it was loop booting, so I booted it into Android Recovery after pulling my battery out ( Power Button + Volume Down ) and then pressed the Volume up and Volume Down buttons together to get the menu up, then chose " Wipe date/Factory reset " and then " Wipe cache partition " and let it boot up again. Didn't solve my Wifi problem though.
Phoned Orange up today, explained that my wifi, bluetooth and hotspot all stopped working and that I'd already done a factory reset and updated to gingerbread. The guy was shocked that I'd basically done everything on his menu to try and solve the problem. They are sending a guy out tomorrow to give me a replacement phone for £25 on my insurance. Winner!
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha)
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Mankey Magic said:
I've been ripping my hair out the last couple days trying to figure this out.
In the process of flashing a ROM and kernel I did a number of things:
-Carrier unlock (I feel like this is the culprit)
-Unlocked the bootloader
-Flashed Wet Dream (2.3.6 build)
-Installed webtop
-Attempted to root, unsuccessfully (let me know when the 2.3.6 root is available, haha) <-- i think this one no need to do
After all this, everything was working fine--including wifi. But somewhere along the lines, maybe 15 minutes after I complete all these steps, out of the blue my wifi won't connect. It just says "obtaining IP address" and never connects.
So I got pissed and went on a wiping/reflashing spree. Got everything reset. The wifi was working great again. Then randomly, it just stopped working again.
Question:
Does anyone know why this is happening and what I can do to fix it?!
I'm dying here. Just as a side note in case you need this information, I think I'm going to flash to the 2.3.4 Wet Dream so I can root my device. Also, I don't mind going back to stock. If that's what fixes, it then I'll be more than happy to go stock. I plan on running webtop2sd as well.
Thanks in advance.
Click to expand...
Click to collapse
try check in: settings-- battery & data manager--battery mode ( see what presets u use).
then try check: settings--wireless & network settings--wifi settings--advanced (press menu key(the left touch key in bottom)--wifi sleep policy-- set to never.
btw, wetdream should be already rooted. correct me if im wrong.
hope this help.
benjat said:
hope this help.
Click to expand...
Click to collapse
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Mankey Magic said:
Benjat, thanks for the reply.
My battery settings were set to "Nighttime saver". I set it to "Performance mode".
I set my wifi sleep policy to Never.
Still have the same problem.
My understanding was that WD was already rooted, but Busybox wasn't installing so I ran Root Check Basic from the Market and it said my device did not have root access
Click to expand...
Click to collapse
maybe try reboot the phone after change the setting?
im not sure about busybox. what apps u running that require busybox? i want to try install it.
*i just try download root check basic. got message "your device isn't compatible with this item" hehe
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Mankey Magic said:
Reboot and still no dice.
Ahhhh! So frustrating!
I was mid webtop2sd install and busybox is required for one of the steps to work. I'm actually not sure what it does.
Click to expand...
Click to collapse
last try.. remove all wifi network added.. double check all the things i post before.. switch off wifi.. power off ur phone.. 10 sec then switch it on back, then on wifi. if still cant, i dont have anymore idea..
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Mankey Magic said:
Thanks for all the help benjat. Unfortunately, it didn't work. Hopefully, someone else who has gone through this can help me out.
Click to expand...
Click to collapse
nvm.. maybe do full wipe again..
what ver of WD u using? with what addon? im using WD 1.4.3 full
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Mankey Magic said:
I've already done a cache/date wipes to no avail.
I'm using 1.4.4 lite. I'm thinking of flashing the 2.3.4 based WD though (is that 1.4.3?).
I could flash something else too, I guess. I really need webtop (with xfce mod) and I heard Wet Dream works well with it.
If this really is a software problem and it is the ROM's fault, then does anyone have a webtop compatible ROM recommendation?
Click to expand...
Click to collapse
i cant tell if its problem with rom or what.. 1.4.3 is 2.3.6 base. and yes webtop work well with it.
here's normaly what i do..
Boot CWM Recovery
Wipe data/factory
wipe cache
wipe dalvik
flash rom
reboot to fastboot and do fastboot-w & then fastboot reboot.
let it boot for 1st time (until stable/full load) i left it around 10 mins
then reboot back to CMW to flash addon. usually i flash 1 then boot.. continues untill flash all.. maybe a bit fussy step.. but i prefer all loaded before flashing another
*i never tried webtop2sd yet.. still dont buy bigger mem card coz funding for lapdock
** maybe can try this one to make it clean wipe.. http://forum.xda-developers.com/showthread.php?t=1421522&highlight=fastboot+-w
Yeah I realized too late that everything cost me way more than I had originally intended to spend. SD cards have come down in price but still pretty pricey for a 32 GB card.
And thank you for the link. I'll try it out tomorrow and report back. It's 1:00 AM here in Seattle!
Hey Mankey,
Have you tested different Wifi networks to ensure that the issue is not with the phone or the ROM at all?
Also, check if someone else on Wet Dream thread had WiFi issues, if this happened with someone else, then they should have fix for sure!
Usually I do what bejnat mentioned and usually works.
Also, about the root, try to follow a root process again. It happened with me before, then I had to install a .zip file through Recovery mode to have root access again.
Hope this helps!
wouldn't just flashing the radio or a newer radio maybe fix his issue??
Yeah it doesn't work with other networks either. And as for root I don't think there's a direct way to root 2.3.6 yet.
Sk8trix, I think I'll try that after I flash back to stock 2.3.4. I've tried just about everything but the radio. Kernels don't fix it.
I'll post an update in a couple days. I really want to get this fixed.
I had the same problem with my dark side when I 1st got it and to fix it I flashed another ROM ,loaded it then flashed back ,cleaned delvik cache and flashed gapps then rebooted and 1st boot fixed my problem was using 2.3.6 with webtop2sd+nebtop app hope this helps you
Sent from my ics+darkside multiboot mb860 using xda premium