wolf v3.8 - XPERIA X10 Q&A, Help & Troubleshooting

i got some little problems after i flash to wolf v3.8 rom.
i cant access my phone, it said "google talk authentication failed"
how could i gonna solved this problem ?
thx...

I have many problems with V3.8, 3.7 I had problematic force close on some apps, however, 3.8 is worse...wonder??? should I go back and reinstall fresh 3.5, then 3.8? wiping, because I started from 2.1 SE with update, then, Generic XDA 2.3, then WB 3.0, with bndle, and other add=ons, then, 3.6, 3.7, and finally 3.8. I followed instructions exactly as specified.
Should I reboot a few times and let the system settle in for a few hours??
I would appreciate ANY help with this
I am also having problems with finding devices in bluetooth

i think if u flash everything correctly should be ok. i tried once. but then after i flashed bak to v3.5 again and wait for a moment then only updated to v3.8, the problem solved. the only problems remain for me now is the market problems... still cant solved it.. >_<
i like wolf's work.. he done his job very well... hopefully someone can help me solve the market problem..

I am a proudly very happy user of EWJET rom!
It's perfect, faster and smoother. It worths to give a try. Recommended!

Recommended removal of some
1.Wipe Cache
2.Wipe dalvik
3.fix permission
Should be able to re-brush into the solution
Wolf ROM is great

Gzrdon said:
Recommended removal of some
1.Wipe Cache
2.Wipe dalvik
3.fix permission
Should be able to re-brush into the solution
Wolf ROM is great
Click to expand...
Click to collapse
this method didnt work in v3.8 i tried it lot many times !!

gcopher said:
I have many problems with V3.8, 3.7 I had problematic force close on some apps, however, 3.8 is worse...wonder??? should I go back and reinstall fresh 3.5, then 3.8? wiping, because I started from 2.1 SE with update, then, Generic XDA 2.3, then WB 3.0, with bndle, and other add=ons, then, 3.6, 3.7, and finally 3.8. I followed instructions exactly as specified.
Should I reboot a few times and let the system settle in for a few hours??
I would appreciate ANY help with this
I am also having problems with finding devices in bluetooth
Click to expand...
Click to collapse
thats why m on v3.6 only ... its better than v3.7 and v3.8 so once he rolls out a new ROM with all the fixes installed better to swap at that time!!

Related

About > [ROM] [REL 02-05] TripNMiUI "IRIS" 0.1.5 Gingerbread!

Just to report that for me i couldn't get network(no service) signal for 1 or 2 minutes even after crashing the system server
http://forum.xda-developers.com/showthread.php?t=1037855
I can't post in there yet, if someone can do that for me, i appreciate that.
I don't if it is connected but the signal showed up when i went to the system update on settings.
Settings> System > About Phone > System updates> Then it crashes in here and FC
Once it gets back to the home everything gets alright.
The rom seems a bit laggy yet, but maybe is something configuration or procedure i did wrongly.
Also from time to time, the screen gets lighted (bright) and after that dark again when i am not using it, not even near.
Just flashed it 20min ago.
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
what I did and it worked for me was flash TripNMIUI_BTS_02.zip first, then I rooted it again and installed xRecovery. I then flashed bb.52, booted into xRecovery, cleaned the cache, dalvik, battery, etc. and then flashed this ROM. Do a system crash and once it reboots it should pick up a signal within 10 sec.
aval1392 said:
you should attempted to reflash the ROM. Make sure you are on basebrand.49 or .52. Wipe data, cache, dalvik cache, and battery stats, then flash the custom zip ROM. Crash system server like you said and you should have a clean ROM
Click to expand...
Click to collapse
As i said before, after the last FC in the settings, it did work normally i have the rom working perfectly fine, what i wanted was to someone that can post there to do this for me, or that trip could see this to add to the install steps so people can try also what worked for me may work for others.
ironjose said:
If you want a GB ROM you may try this one http://forum.xda-developers.com/showthread.php?t=911364
You're gonna get more suport from J with this ROM =)
Click to expand...
Click to collapse
I normally try every rom for one or two weeks at least so i can be sure which one is better, so far i've tried one based in this rom, but is wasn't faster than TripNMIUI version.
In TripNMIUI i got 36,5 in Linpack without using any APP2SD tool, also got in Quadrant from 1100 to 1200.
The other roms i tried hardly passed up than 32k in linpack and normally near 900 in quadrant.

Sd card/rom issues

Hello,
I was wondering if someone could help me out. I checked the forums although I cannot find an answer.
Been trying to switch roms and get this issue with every rom, that my phone won't find the baseband. So I crash the server and it works, but I get the error phone stopped working unexpectedly. So I found that this problem only occurs when my sd card is inserted. If I remove it the rom picks up signal.and no crashes.
So I tried a different card, same issue, I format the card, same issue, etc...
Is there any fix? any help would be much appreciated
Thank you.
Sent from my X10a using XDA App
Try a clean flash and install. Reflash the latest FW, root and install XRecovery. Then make sure you do a full wipe, wipe cache, dalvik and battery stats before installing the ROM. That usually gets rid of all those odd little bugs. You can also unmount your SD card without physically removing it but hopefully the clean install will clear up your troubles.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Ok, I got that before going straight to a Froyo custom rom, try a EWJET 2.1 custom ROM first and see if you still have that problem. I did that and didnt have problem moving up but I went back again to 2.1 for other reasons.
CMoney87 said:
Try a clean flash and install. Reflash the latest FW, root and install XRecovery. Then make sure you do a full wipe, wipe cache, dalvik and battery stats before installing the ROM. That usually gets rid of all those odd little bugs. You can also unmount your SD card without physically removing it but hopefully the clean install will clear up your troubles.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!
Click to expand...
Click to collapse
Thank you for responding. I gave that a shot, well i tried in two methods.. i downloaded for xrecovery a clean rooted, xrecovery installed of the stock rom.. then followed the steps and got the same issue.. so i thought to do a full factory wipe using sony's tool, went back to stock rom, rooted, xrecovery installed, etc.. flashed the rom, same issue.. i tried this with several roms and cannot seem to bypass this error.. it almost seems like its just me due to limited info in the forums...
i guess i'll keep trying, thank you for your help.
sasukewa said:
Ok, I got that before going straight to a Froyo custom rom, try a EWJET 2.1 custom ROM first and see if you still have that problem. I did that and didnt have problem moving up but I went back again to 2.1 for other reasons.
Click to expand...
Click to collapse
I gave this a try, downloaded the latest EWJET 2.1, everything worked fine on that rom, no crashes, etc.. so i tried flashing several roms thereafter, without success..
could it have anything to do with being on a locked bootloader?

[Q] Systemtray not working

Hello,
I switched from WanamLite for Foxhound and I must say everything is working great. No more freezes, crashes and my geolocation ifnally is accurate again.
I followed all installation instructions, format /system, factory reset wipe cache and dalvik and installed.
The only problem Im having is that some of the systemtray icons arent working. The ones that are working is random. So im able to toggle GPS but not to toggel wifi, an hour later wifi is working but data is disabled. etc.
Anyone has any idea what this could be?
sometimes the package dosnt open fully so if ur facing prblm then its better to hav a fresh installation,,an also many will carry tb backup all the way frm stock to custom roms so even tht gives a prblm to many out here......cheeeeerz
rocky23 said:
sometimes the package dosnt open fully so if ur facing prblm then its better to hav a fresh installation,,an also many will carry tb backup all the way frm stock to custom roms so even tht gives a prblm to many out here......cheeeeerz
Click to expand...
Click to collapse
I never restore anything else but applications when I'm switching roms, not systemdata whatsoever. Would it be possible to flash a different systemui instead of reinstalling the rom? Or could I just reinstall the rom without resetting the system all over again, spent hours to rebuild my settings etc ><
Why don't you redo the procedure once again, wipe cache then dalvik, format system then flash the package via recovery.
Errors could happen, so no harm if you try it again.
If not try the latest wanam 10.6 version it is almost perfect or you can always go back to a stock ROM and use Siyah kernels, I'm on XXLPQ with Siyah b6, very stable tremendous battery life. (you should test different kernels though and stick to the best)
maf23 said:
Why don't you redo the procedure once again, wipe cache then dalvik, format system then flash the package via recovery.
Errors could happen, so no harm if you try it again.
If not try the latest wanam 10.6 version it is almost perfect or you can always go back to a stock ROM and use Siyah kernels, I'm on XXLPQ with Siyah b6, very stable tremendous battery life. (you should test different kernels though and stick to the best)
Click to expand...
Click to collapse
For some reason I always have troubles with my geolocation and gps working very slow or not at all on different kernels then stock. Thats why I switched to foxhound. Ill redo the complete procedure tonight to see if it helps.
Thanks for the info so far.

[Q] Apex Launcher error in Shostock and ultimatum rom

hello,
i have samsung sghi777. i have flashed shostock2 v3 but after flashing i m regularly getting error "unfortunately apex launcher stopped unexpectedly". i have tried go launcher instead but . Same problem i m facing after flashing ultimatum 2.1 with apex launcher.
can somebody help?????
Do a full wipe and install and try again.... I had the same issue. Do you happen to have SetCpu installed? What are your settings...
But yeah start off will a full wipe and then install. Don't forget to reset the ExTweak. Not sure if that has anything to do with it but just do that.
i have never installed/used setcpu. i didnt get u, settings??????? actually i just play with flashing ROMS nothing else (never overclocked, never flashed custom kernel......). i already did a full wipe before installing, well will try again and see. anywayz thanx for the reply. kindly inform me if u found some another solution that can help me as shostock is a great rom and now i dont want to do further experiments.
Yeah, try to install one more time.... if you have a Kernel Cleaner run it before install.
ShoStock just released a new Update.... Try installing that. If you continue to have issues I don't know what to say to be honest.

[Q] Phone Issues with Viper 2.0.0

Hello, I've been lurking on XDA for some time now since I first rooted my OG Dinc and I just recently got the Dinc 4g LTE running on the 2.17.605 version with sense 4.1. I have also rooted it and installed TWRP recovery after following the fakecid guide. On the stock rooted Rom, I have no usability issues, but when I tried to use the Viper 2.0.0 Rom, I was unable to dial out, the people app wasn't syncing with my google account and was generally quite glitchy. I would like to use this Rom to take advantage of the features, but I can't use it as a daily driver with these conditions.
What have I missed and what should I do to fix this?
Thanks for hearing me out,
Raven744
Raven744 said:
Hello, I've been lurking on XDA for some time now since I first rooted my OG Dinc and I just recently got the Dinc 4g LTE running on the 2.17.605 version with sense 4.1. I have also rooted it and installed TWRP recovery after following the fakecid guide. On the stock rooted Rom, I have no usability issues, but when I tried to use the Viper 2.0.0 Rom, I was unable to dial out, the people app wasn't syncing with my google account and was generally quite glitchy. I would like to use this Rom to take advantage of the features, but I can't use it as a daily driver with these conditions.
What have I missed and what should I do to fix this?
Thanks for hearing me out,
Raven744
Click to expand...
Click to collapse
Boot into twrp and fix permissions. That will fix the sync issue. Generally glitchy it's a little broad, off you post specific issues we can probably help.
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
I've had the Google account sync issue on two consecutive installs of v2. Both times I've booted to TWRP and wiped cache & dalvik. Fixed it both times. Other than that, this ROM has been rock solid for me. No dialing issues.
same here, wipe cache and dalvic and all is ok. did this on viper1 and viper2, worked both times
I did the fix perms and wipes pre flash to no effect. I still don't have the people app syncing. Did you guys do this post-flash? Also dialer still doesn't work.
Thanks guys! Doing what you recommended post-flash helped clear up the issues.
i just previously ran the vipers 2.0 rom because i didnt knotice the 2.1.1 patch for sence 4.1 andnow i still have no problems.....
did you flash it right
1. boot into recover> wipe> factory data reset
2. wipe> cache
3. wipe> dalvik cache
4. install zip> your rom ( viper 2.0.0)> and use there full wipe script and install
5 install zip > your rom ( viper 2.1.1)
6. reboot, problems should be fixed

Categories

Resources