Related
My phone completely died yesterday and I left it charging all night, when I woke up this morning all of the widgets were gone. The shortcuts to apps were still there but all my widgets including stock Motorola ones and various downloaded from the market were gone. Im running stock 2.3.4 minus the kernel. I have faux kernel installed. Anyone know why this may have happened?
Thanks
thats weird the exact same thing happened to me last night into this morning. i wake up. they are all gone. lol
There's worse things that could happen Haha, but still I don't remember where half of mine were haha
add me to that list
I lost mine as well, several times now. Just installed ADW to see if it happens again. It's getting frustrating.
Same thing happened to me when I was using a restored back-up of settings and configuration ADW.. Every time i would reboot I would loose my widgets or get "problem loading widget." I then uninstalled ADW and re-installed and did not use a restored configuration I have not had the problem since..
Hope this helps someone.
Same Problem
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
its still happening to me
I often get "problems loading widget" after a reboot.
No idea what's causing it.
Im running ninja 0.4.5 faux 0.1.7 on bell ATRIX..
Dame thing happened with cherrypi...
Oh yeah ... this is all on Launch Pro...
Anyone has any ideas what's causing it?
I had this problem when I installed faux's kernel... Installing version 1.3 or going to the stock kernel fixed it. Go into recovery wipe cache and dalvik cache then install the stock or faux's 1.3 kernel then reboot. Add your widgets again then reboot again to double check that your widgets didn't disappear.
yeah when i switched to kholk's kernel it worked fine, also on stock it works fine. Idk why faux's kernel does this
Sun3vi1 said:
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
Click to expand...
Click to collapse
I just tried your solution and it totally worked for me...that's awesome! thanks!!
Fixing permissions in CWM or Rom Manager fixes this problem.
Assimilated via WinBorg 4G
CaelanT said:
Fixing permissions in CWM or Rom Manager fixes this problem.
Assimilated via WinBorg 4G
Click to expand...
Click to collapse
that's good to know!
Sun3vi1 said:
Funny, I had the same problem shortly after updating pudding (the unlocker SBF file that you install to unlock bootloader) and installing a custom kernel. For some reason, the two pieces work against each other to cause this problem.
All I did was flash the older pudding, called "Unlock SBF File" available at the page below, and reinstall my faux kernel, and my phone resumed fairly normal operation.
Unlock SBF page:
briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Hope that this helps
Click to expand...
Click to collapse
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
---------- Post added at 09:35 PM ---------- Previous post was at 08:37 PM ----------
hoodlikegaza said:
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
Click to expand...
Click to collapse
WOW! After a week of getting owned by this disappearing widget issue and going back to the stock kernel, it seems this might be the solution.
The only thing is I did it the opposite from what you did. I originally unlocked with the zomgunlock-lite.sbf. I'm currently on the unlocked and pre-rooted gb SBF.
So I went to the pudding thread and downloaded the newer pudding sbf from that thread (4547-fix-try2.sbf), flashed it, and after about 10 battery pulls, I still have my widgets!
I didn't even have to oem unlock again, I was expecting to be soft bricked, but to my surprise the phone booted up normally, and everything worked correctly!
hoodlikegaza said:
It seems that the zomgunlock-lite.sbf, is what's in the zip on briefmobile now. Were you referring to a different pudding file?
---------- Post added at 09:35 PM ---------- Previous post was at 08:37 PM ----------
WOW! After a week of getting owned by this disappearing widget issue and going back to the stock kernel, it seems this might be the solution.
The only thing is I did it the opposite from what you did. I originally unlocked with the zomgunlock-lite.sbf. I'm currently on the unlocked and pre-rooted gb SBF.
So I went to the pudding thread and downloaded the newer pudding sbf from that thread (4547-fix-try2.sbf), flashed it, and after about 10 battery pulls, I still have my widgets!
I didn't even have to oem unlock again, I was expecting to be soft bricked, but to my surprise the phone booted up normally, and everything worked correctly!
Click to expand...
Click to collapse
This method apparently does not work for my T-Mobile UK Atrix. Any other fixes ?
Apparently it didn't work for me either.... Try the 0.1.7
Sent from my MB860 using Tapatalk
This has been also happening to me. I am on stock 2.3.4 with Faux's Enhanced stock kernel 2.0. I have tried fixing permissions, but it only worked with the first reboot after that
Try 0.1.7..... It's been a bit more stable for me.
Sent from my MB860 using Tapatalk
This will keep happening no matter how many fixes you try unless you:
1) Use stock kernel
or
2) Use CM7
Just trust me, I know you think the fix permission thing fixes it, but it will come back eventually, just a matter of time.
Sent from my MB860 using xda premium
Swiftks said:
This will keep happening no matter how many fixes you try unless you:
1) Use stock kernel
or
2) Use CM7
Just trust me, I know you think the fix permission thing fixes it, but it will come back eventually, just a matter of time.
Click to expand...
Click to collapse
Fingers crossed...I tried everything and never could get the Faux kernels to work with various roms and not with stock, either. Tried everything. (fix permissions CWM/Rom Manager/fastboot -w, fastboot erase everything, etc.)
Decided to give it a go a day and a half ago and tried the reunlock with the newer pudding unlocker (4547-fix-try2.sbf). Like the gent said didn't have to fastboot unlock, just rebooted. Then installed the Faux optimized 1.0 (not overclocked kernel).
Been running since with some reboots for good measure and the widgets are still there. We will see.
I was finally of the opinion that it was some problem between the kernel and setcpu..a month or so ago when I was running faux kernels. (I am not running setcpu at the moment)
We will see...
ps I intend to try CM7 but I am waiting for the lapdock to be functional. I use it everday
If you were successful -- were you completely stock, or some GB upgrade (like LEEDROID), or some HC upgrade? At this point, it sounds like the third option is not possible, but I am wondering about the other two.
Thanks!
First post!
I am a US Best Buy WiFi owner.
I previously upgraded to Honeycomb using the first leaked release using the standard procedure.
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
My guess is that if I flash the new radio image, then I will get Wifi Back. This would have to be done later because I have no access to a command line terminal here at work. I think we can probably skip the hboot and boot images.
Overall, the UI seems a little faster and there are some new transition animations.
Maybe someone can try to follow this procedure and see if it is successful.
What do you think?
I reverted back to the original HC release.
I'll update the radio image and then install the new HC sytem image again.
I had some funkiness (forced closes) when I went back. I had to wipe my user data but everything was fine after that. It is best to start everything with a blank slate.
lawguy said:
I reverted back to the original HC release.
I'll update the radio image and then install the new HC sytem image again.
I had some funkiness (forced closes) when I went back. I had to wipe my user data but everything was fine after that. It is best to start everything with a blank slate.
Click to expand...
Click to collapse
You'll have to keep us posted on this, as I too have a US WiFi only BB Flyer running HC (1st leak), so I'd like to see if this works too. However, I read another thread in the Dev forum from Globatron about fastboot flashing every item individually:
http://forum.xda-developers.com/showpost.php?p=18991623&postcount=497
EDIT: I assume this is due to S-ON...
That was my original thought - flashing each component just as you would in the original instructions. I would guess that this was tried and it did not work? Why else would we be instructed to go back to GB and start over? So I am hoping that just doing the radio image works and avoids whatever problems were encountered. I am thinking that since everything seems to work other than Wifi that it may only be necessary to flash the radio.
We'll see.
I have a combination of little fear and little skill so there is a good chance that I will brick my flyer.
fwiw...i have started a donation pledge drive in globatron's "Revert from HC to GB" thread and am starting it off with a $200 PayPal donation if others jump on board to pay for globatron to get a US Best Buy WiFi Flyer so we can not stress ultimately getting to ICS let alone a leaked HC.
http://forum.xda-developers.com/showthread.php?t=1307759
Maybe the boot.img and system image would work.
Sent from my ADR6400L using xda premium
I have a BB US Flyer that was running LEEDROID V2.2 and kernel 2.3 and I followed Paul's steps and successfully upgraded it to HC. All seems to be working at this point, except for that there was no English(USA) option so I chose UK for my language (bloody me, I have a strange accent now). Also, it thinks I have a phone capability, but I ignored those options. Step 17 I had to do manually by taking out the SD card, and step 7 I ignored because I already had the initial unlock.
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
lawguy said:
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
Click to expand...
Click to collapse
You might want to talk to PaulOBrian
http://forum.xda-developers.com/showthread.php?p=19012462
I don't have enough posts to do that yet!
lawguy said:
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
Click to expand...
Click to collapse
And what else did you do?
Wipe you any data, cache, Dalvik cache?
And how did you flash the image? In fastboot, with recovery or?
lawguy said:
Last night I tried totest my theory by flashing the radio image. No dice. I could not flash the Radio.
---------- Post added at 12:07 PM ---------- Previous post was at 11:59 AM ----------
Just a little more information: I think that the bootloader is locked and this is the reason that the radio cannot be flashed. Revolutionary does not support the Hboot version that is on the HC Flyers.
Click to expand...
Click to collapse
You should try to flash it using the app that does so from normal android mode (if that makes sense). It's over in the evo3d themes and apps section. I'm pretty sure it allows people to flash things like kernels and radios that have a HTC unlocked bootloader. It's worth a shot.
Edit : nevermind you can't flash radios :/
Sent from my PG86100 using Tapatalk
I did the whole process two times.
The second time, I wiped the data and caches. This was all done through recovery.
One other issue I noticed is that I had difficulty restarting the Flyer after flashign with the new HC version. After pressing the power button, the menu came up as usual. After pressing restart, it would not restart. Instead, I had to press and hold the buttons to manually restart the flyer. This suggests some issue other than just the radio.
---------- Post added at 01:49 PM ---------- Previous post was at 01:48 PM ----------
Gumby63 said:
You should try to flash it using the app that does so from normal android mode (if that makes sense). It's over in the evo3d themes and apps section. I'm pretty sure it allows people to flash things like kernels and radios that have a HTC unlocked bootloader. It's worth a shot.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I'll try it if you show me how to do it. I'm not sure what you mean.
Check the dev thread, we have working 3.2.1 wifi flyers going on there
Granted it's still in early stages, so there may be issues remaining to be worked out but things are looking good so far, I have this working on my US BB WiFi Flyer so far..
Cheers
BR
for those running HC, do you find it better in its current form than the gingerbread stock?
mcord11758 said:
for those running HC, do you find it better in its current form than the gingerbread stock?
Click to expand...
Click to collapse
Yes, If I had to define why all i could really say is that it just seems to fit running on a Tablet better than GB. Just my 2 cents tho.
Cheers
BR
For those that are flashing the new build you should follow the steps by Paul in the other thread http://forum.xda-developers.com/showthread.php?t=1330832 it is really very simple (it does involve using "ADB" tho, so if you are not familiar this may not be a good idea.
lawguy said:
First post!
I am a US Best Buy WiFi owner.
I previously upgraded to Honeycomb using the first leaked release using the standard procedure.
I took a little risk and just flashed the new Honeycomb system image zip file. It boots into HC 3.2.1 without any problem without flashing anythign else. Everything seems to be fine with one exception - No wifi. Under the Wifi setting it says "error."
My guess is that if I flash the new radio image, then I will get Wifi Back. This would have to be done later because I have no access to a command line terminal here at work. I think we can probably skip the hboot and boot images.
Overall, the UI seems a little faster and there are some new transition animations.
Maybe someone can try to follow this procedure and see if it is successful.
What do you think?
Click to expand...
Click to collapse
Hi, I think I was in the same situation when my flyer was on HC. I followed exactly paul's guide, but just like your flyer, mine also says wifi "error" in settings, and I can't check wifi. I think that should be the radio problem. For now, I rolled back to GB and wifi working good nwo, but really miss scribe using when I was on HC.
There is a simple upgrade method now to install the 3rd HC leak. Look in the DEV section for [Guide][Flyer]Honeycomb S-OFF, Honeycomb Easy Install, Recovery and Root. by globatron
http://forum.xda-developers.com/showthread.php?t=1358758
I followed the instructions last night and it went really well.
NEW USERS, installing HC first time, please read
NEW USERS:
HC works great on the BB wifi only. It takes a few steps to get it loaded and working. do your homework before installing HC ROMS, or you will be sorry and coming back for help.
Start with this thread.
http://forum.xda-developers.com/showthread.php?t=1358758
Have fun!!
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
I have updated to 2.3.5.418.
I have a few question about it. So far, there is no way that I can go back to 2.3.4 or previous version via sbf, correct? So am I stuck with 2.3.5.418 and Eclipse 2.2?
I am asking this because my wifi on phone is connecting and disconnecting every 5 second.
I am on 2.3.5.418 as about phone tells me.
What fix can I do?
Also I have battery % problem... When I reboot, the battery percentage changes. What can I do for this problem? I can't download GB battery fix, and even if I could, it is not intended for 2.3.5...
I would like to get answer for both problem. Thank you.
#FF0000 said:
I have updated to 2.3.5.418.
I have a few question about it. So far, there is no way that I can go back to 2.3.4 or previous version via sbf, correct? So am I stuck with 2.3.5.418 and Eclipse 2.2?
I am asking this because my wifi on phone is connecting and disconnecting every 5 second.
I am on 2.3.5.418 as about phone tells me.
What fix can I do?
Also I have battery % problem... When I reboot, the battery percentage changes. What can I do for this problem? I can't download GB battery fix, and even if I could, it is not intended for 2.3.5...
I would like to get answer for both problem. Thank you.
Click to expand...
Click to collapse
No. For whatever reason, Motorola did not prevent SBFing back to previous releases with this soak test or the previous 2.3.5 leak. You can go back to 2.3.4 if you prefer.
The battery GB battery fix *does* work for 2.3.5, you just have to manually push it thru ADB. Check out the thread.
As far as the wifi issue, I'd recommend flashing 2.2 again. Wipe big 3, etc. I haven't seen any issues with wifi connectivity since I've been on 2.2. If it persists, you might want to start from a blank slate, going from a clean 2.3.4 sbf.
I thought the gb battery fix was already present in Eclipse? At least, at one point I thought it was, unless Motorola re-introduced it with this latest patch.
Grrrr Motorola!!!
Sent from my Eclipsed 2.2 phone.
I can't remember exactly, but I believe it was initially *suspected* the battery fix was in 2.3.5 and then after a few days it was confirmed so we had to re-apply the batt fix again. It's also probably compounded by the fact that people are coming from a fresh 2.3.4 sbf.
Skelente said:
I can't remember exactly, but I believe it was initially *suspected* the battery fix was in 2.3.5 and then after a few days it was confirmed so we had to re-apply the batt fix again. It's also probably compounded by the fact that people are coming from a fresh 2.3.4 sbf.
Click to expand...
Click to collapse
Well, I can attest to the fact that Motorola reintroduced the battery bug with this latest OTA. After flashing Eclipse 2.2, I used peppermints battery fix and all is right in the eclipse 2.2 world. I also let nitro know about it.
Sent from my Eclipsed 2.2 phone.
Thank you
Thank you for quick response.
After reboot, wifi became better, after reboot... No idea what happened, but it doesn't refresh every 5 second.
Now for the battery issue. I cannot acquire GB file, as megaupload is down. (RIP megaupload) And I have no idea what is ADB.
So is there anyone willing to guide me through the battery fix? Flashable zip file would be even better for me. (less likely that I will screw that one up)
Thanks once again.
P.S. I see there has been issue about zergrush root. I am eclipse 2.2 with zergrush root. Should I be worried?
iBolski said:
Well, I can attest to the fact that Motorola reintroduced the battery bug with this latest OTA.
Click to expand...
Click to collapse
that's wierd, I would have said it was fixed
#FF0000 said:
Thank you for quick response.
After reboot, wifi became better, after reboot... No idea what happened, but it doesn't refresh every 5 second.
Now for the battery issue. I cannot acquire GB file, as megaupload is down. (RIP megaupload) And I have no idea what is ADB.
So is there anyone willing to guide me through the battery fix? Flashable zip file would be even better for me. (less likely that I will screw that one up)
Thanks once again.
P.S. I see there has been issue about zergrush root. I am eclipse 2.2 with zergrush root. Should I be worried?
Click to expand...
Click to collapse
Yes. The update won't install because Zergrush moves some system files. You'll need to SBF back to 2.3.4 and root with Pete's Motorola tools, install voodoo root keeper, backup root, install the update and then run voodoo keeper to reenable root.
Sent from my Eclipsed 2.2 phone.
three west said:
that's wierd, I would have said it was fixed
Click to expand...
Click to collapse
It was with the leaked 2.3.5, but I and many others have seen the issue. Once I've applied peppermints battery bug fix, the issue goes away.
Nice going, Motorola. >
Sent from my Eclipsed 2.2 phone.
Eclipse 2.2 wifi not working
Ive tried a couple time doing the same steps that's instructed to do for installing eclipse 2.2 but wifi not working it just says Error don't know what to do.
Update: Nvm I feel so stupid i was using 2.3.5 412 build silly me.
iBolski said:
It was with the leaked 2.3.5, but I and many others have seen the issue. Once I've applied peppermints battery bug fix, the issue goes away.
Nice going, Motorola. >
Click to expand...
Click to collapse
bah, I was all ready to challenge you on this one, cause I had seen stability between boots, and even seen it go down. Today I thought I'd test again and it just went from 88 to 99 ;(
how the heck did they not bother to fix that? It was one of the bigger issues noted on the soak test boards for 2.3.4
I very thoroughly apologize if this has been asked and discussed before, but apparently my search skills aren't the best. Anywho, her's the issue.
I've used a number of different ROM's since I first got my DNA back in January. I've used older Tranquil releases. But anything after 2.1 I believe it was, I haven't had WiFi. I have it just fine with all other ROM's. But no matter what I do for Tranquil (even up to and including RLS 4.2), there's no WiFi connection. It says it's trying to find sources or something and eventually errors out. I have no idea what the problem is. If I go back to 2.1 or 2.0, WiFi works great. This kind of sucks as I really enjoyed the earlier Tranquil releases and would like to continue using them. I'm currently using NOS m7's latest release for 4.1.2 (couldn't get their 4.2.2 release to work for some reason, just sat at the HTC screen for over 30 minutes, even after wiping the entire phone and attempting to sideload).
Anyway, if someone can tell me how to get WiFi to work on Tranquil releases after 2.1, that would be awesome. And again, I apologize if this has been covered before. I tried posting in the official thread but my lack of post count keeps me from doing so.
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
thatotherguy.. said:
You need to update your firmware to 2.06
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Attempting to get the 2.06 update and then reunlock at the moment, but it's not recognizing the phone in Fastboot. Recognizes fine when it's on, but not Fastboot.
aweber1nj said:
Can I ask where it's failing? I'm running the 4.2 ROM, and WiFi seems to work fine.
Be happy to look at my settings for you if you need, but IIRC, it came up correctly the first time -- during initial setup.
-AJ
Click to expand...
Click to collapse
It does it right from the beginning. Any other ROM and my WiFi network shows immediately. Any release past 2.1 and no WiFi at all.
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
thatotherguy.. said:
Make sure your cord works fine
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've used this same cord to ADB push and sideload while in Recovery before. Plus it reads just fine when the phone is on as normal. Wouldn't that make it fine? (Note: Not being sarcastic or anything, genuine question. I know how things can be misinterpreted over the 'net so I kinda like to point out how I mean things.)
Edit: I got it to work so far. I'm reflashing back to complete stock now. Apparently a driver wasn't installed for it to be detected in Fastboot. I'll post back after I get back to stock, completely update to newest, and reflash Tranquil RLS4.2.
So I got everything installed, running again, latest updates, reunlocked, TWRP back on, flashed RLS 4.2... No WiFi still... What am I doing wrong here?
Edit: NOS M7 3.0.4 is doing the same thing it was before, also. It's not even getting passed the HTC screen, no matter how long I let it sit. This is quite frustrating. I put M7 2.0.3 back on and everything works as it should. Anyone have an possible solutions?
Do you upgrade your firmware?
Sent from my HTC6435LVW using Tapatalk 4 Beta
It was upgraded to 2.06 when everything was completely stock..
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
matthall9815 said:
are you s-off or s-on sounds like youi aren't getting the kernel. If you are s-on you have to extract it and push it seperately, or find one marked to be flashed seperately s-on. I didn't see where anyone posted this. Sorry if I missed it. Busy here at work but saw your thread.
Click to expand...
Click to collapse
Other than being rooted with the custom ROM, it's whatever the normal S is (can't remember off the top of my head). I rooted and tried the Moonshine thing but it never took (on stock 2.06) so I just went through and reunlocked with my original packet from the HTCDEV website and went about things that way.
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
matthall9815 said:
Ok, it's an easy fix. When you flash from recovery you are getting the rom, but not the kernel information. I assume you've probably been having bad battery life also. The only way to falsh a kernal s-on is with adb push, or with a hboot flashable where it goes all the way back to the white screen. if you download the all in one kit I think you can use that to push a kernel easily. I can never remember the adb commands. I think they suggest beaups kernel for that rom. Go ahead and download the two, and pm me if you need any more instruction.
http://forum.xda-developers.com/showthread.php?t=2343352
http://forum.xda-developers.com/showthread.php?t=2000896
Click to expand...
Click to collapse
You're right. My battery life has been absolutely terrible. I can get maybe 6-8 hours until I'm at 30% or under, and that's not doing anything. Much less if I actually want to do anything with the phone. I'll give those two links a look. Thanks. :good:
Edit: So, I've noticed it's now S-On and the kernel isn't showing on the device. I copied the .zip over to the main directory where I always do, and it's not showing on the phone. But it shows just fine in Windows.
Edit again: Got it to flash using Sideload. Before I do anything else, is it okay to now flash RLS4.2 and see if WiFi works? Now that that's on there, it should be good, right? Or do I need to flash RLS4.2 and then reflash this kernal?
Yet another Edit: It took me a while, but I noticed a LOT of things were missing on the phone after flashing the 2.06 kernel. The one that made me notice was FaceBook. And Google Play Store wasn't there anymore, either. I've reflashed to Digital Dream 2.2 and everything is back to normal. This is really frustrating.
Pm me when you're working on this again I think there are a couple things that are confusing.
Sent from my HTC6435LVW using Tapatalk 4
I finally got it to connect.
I was running DigitalDream 2.2 while trying to figure this all out. I ended up getting S-Off and reflashing. For me to S-Off while already on DigitalDream 2.2, I used the first part of the Mooshine Method (downloading their 2.06firmware zip file, flashing that, rebooting) then used the FacePalm method. That successfully got me S-Off. I noticed that even on DG2.2 after that, I had no WiFi. So I decided to try flashing Tranquil 4.2 and now I have WiFi working. Hope this helps anyone that has the same issue I did.