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
Related
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
lexx210 said:
I'm on Gobstopper 2.3.4 and I've recently been modding my phone with faux123's OC kernel, juwe11's ram optimizer, the Webtop hdmi hack and so on, but I recently ran into a problem. Whenever I reboot my phone the widgets don't load and just display as "Problem Loading Widget" in LaucherPro. It might not be because of any of the mods, but it only started happening after I installed them so it's lead me to believe it might be one of them. Please help!!
Click to expand...
Click to collapse
Fix permissions with Rom Manager, or in CWM under advanced, then set up your widgets again. You shouldn't have problems after doing that.
I Also noticed in ADW if I installed a backup configuration within ADW I ran into this problem. If I loaded my widgets after re-loading ADW I did not run into this problem. Caelan's post is also spot on!
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
lexx210 said:
I just tried doing that and it came back up as "Problem Loading Widget". I'm using romracer's CWM. Would that make a difference? Should I flash tenfar's? Also, when it boots it seems to almost freeze for a second as my internal storage and sd card are being mounted and then I can slide the bar to unlock.
Click to expand...
Click to collapse
Fix permissions, reboot, then set up widgets again if you lose them. You shouldn't have any more problems unless you flash another ROM, and possibly another kernel.
Then just do the same thing again if you happen to do that.
This is probably stupid, but you don't have the Widgets installed on the sdcard do ya?
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
lexx210 said:
No I have nothing installed to SD. I just tried to fix my permissions and it didn't work CaelanT. They still don't show on a reboot. If I reflash my Gobstopper or another ROM would that work? Should I try fixing the permissions with tenfar's CWM instead of romracer's? Oh and there's a little vibration I feel when the phone boots up right before it displays the lockscreen. Is that normal?
UPDATE: I just noticed that every time I reboot my appwidgets.xml file gets reset!! Please someone help, nothing seems to be working...
Click to expand...
Click to collapse
Same problem here and only after faux's kernel...I tried all the fixes (fix permissions, wipe cache first before flashing kernel) and the only the thing that worked is to go back to the stock kernel.
Oh man, you may be on to something because EVERYTHING was working fine before last night when I flashed faux123's OC kernel. I'm gonna try and go back to stock and see. Thanks man!
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Swiftks said:
Last couple of posts on his thread already mention it.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Ok perfect then I'll just wait for his next version and hope that fixes the problem. I need his kernel to flash ROM's since I'm on a international phone. It's weird saying that since I'm just in Canada...
lexx210 said:
Holy hell that worked!! Back on stock kernel and they are loading fine! I knew it had to be one of the modifications I recently did to my phone and it was the kernel after all. Thanks again!!
P.S. Show we contact faux123 and let him know that his kernel causes widget loading on boot issues?
Click to expand...
Click to collapse
No problem man....yeah I've made some comments on the the kernel thread about the issue. Hopefully it gets fixed in an updated version.
in the kernel thread (dev) faux is asking INTL users about this issue, for INTL users on his 1.6 unified kernel. some report the widget issue, others do not. its the kernel causing. I am using unified OC 1.6 kernel and am lucky enough to have no issues, and WAY better batter life then stock kernel.
I also encountered this issue, however I don't have an international version of the Atrix.
Using 2.3.4 (pudding version for AT&T) with Alien ROM #4 and faux123's 1.6unified kernel.
Also using Launcher Pro.... I just reinstalled everything after doing a hard reset to try and isolate the problem, and it did occur after the kernel flash.
Same problem here, luckily I just reboot my phone few time a month..(why do I need a reboot, anyways?)
The widget is left blank white with Problem loading widget warning..
I'm not using an INT Atrix, only AT&T (I don't know if there's any other Atrix version) using faux123 1.6, piecrust, romracer cwm ..
any luck, guys?
would there be an update of 1.8 of faux?
I think I'm going partially nuts over this problem. I have tried every thing mentioned in any post. Fix permissions with different CWM's.
I thought was going to win today today when I formatted everything, installed gobstopper 2.3.4 w/ deodex update then setting up my screens with ADW it glitched and would go to the screen preview whenever I touched the screen. a reboot and those damn black boxes are all over the place.
Order of operations:
- format internal/external
- factory reset
- fastboot flashed tenfars CWM which wouldn't mount the internal sd so I couldn't flash
- fastboot erase/flash romracers CWM
- installed Gobstopper 2.3.4
- reboot and used it for an hour or so to let it level out
- installed the deodex update
- reboot and another hour of use with a bunch of reboots to make sure everything was cool (it was)
- used Diviances EXT4 User Journal script
- used it for a few more hours without issue
- installed ADW Ex and while setting up my screens it glitches and goes to the screen preview with every touch.
- reboot... no widgets with a string of expletives
so now what...
Same problem here. I am using latest Aura Rom with latest faux Kernel for International users.
I did everything: Wiped cache, reseted factory, installed rom again, changed kernel to older versions, stock versions, fixed permissions and always lose my widgets configs after a reboot.
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 just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
I SBF'd to 2.3.4, then installed the 2.3.5 update via the stock recovery. Then I flashed Eclipse V2.3 with no issues. Problem.. The wifi will not turn on. It says error in the box and won't check on when I click it.
I read that it could be because 2.3.5 (Build418) isn't installed but it is on mine, that's where I'm at a loss... Anyone know what is causing this issue?
Btw, I did run the Gingerbread Phone 7 rom and the wifi worked on it. But I like Eclipse more and would like to run it instead if I could get wifi working. Would appreciate any help.
And yes... It is rooted.
i would try a re-download and reflash. might be a bad download. other than that, you seem to have read up and know what youre doing, sounds like you took the right steps, especially if peppermints win7 rom worked for you. if after redownloading it still doesnt work, only other solution would be to try an sbf.
---------- Post added at 05:55 AM ---------- Previous post was at 05:52 AM ----------
by the way cm10 is way more stable than people make it seem. perhaps not as stable as eclipse, but i say its worth trying atleast. if you sbf to 2.3.4, make a nandroid, you can try it, restore nandroid, voodoo ota and get back to eclipse. just sayin. she is one spicy meatball.
That's what I was afraid of... I already reflashed it twice and it still didn't fix the issue. Guess I'll redo for a third time tomorrow! I'll let you know if it works
maybe just use 2.3.5 sbf and root with magic md5
Sent from my XT862 using xda premium
Think I figured it out! I overlooked it and didn't realize, but I was on the 412 build instead of 418... So after setting back to stock 5 times and rerooting and flashing Elclipse, it finally works! Wifi is on
ramthis9501 said:
Think I figured it out! I overlooked it and didn't realize, but I was on the 412 build instead of 418... So after setting back to stock 5 times and rerooting and flashing Elclipse, it finally works! Wifi is on
Click to expand...
Click to collapse
you stated specifically in the first post that you were on 418.
I know... And I thought I was. The file I downloaded said it was 418 but who knows I got the real 418 file off of here and it worked flawlessly
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.