Hello!
I'm having a problems, when i'm trying to install iodak v5 and Werewolf v005 on my phone.
I have CM 10.1 Nightly (20120604) and CWM 6.0.3.1.
When i boot into recovery mode, im installing iodak v5 from internal sdcard, and after install i'm rebooting phone.
It stucks into logo lg, and i have to boot into recovery again and do a factory reset.
Another problem is when i'm trying to install Werewolf v005 instead of iodak v5.
I'm doing factory reset, cache partition reset, and installing CM 10.1, gapps, Werewolf v005_fixed.
When im rebooting phone, it stays in 'bootloop', so i have to re-insert my battery and do a factory reset again.
But when i install only CM 10.1 then Werewolf v005 - it works, but what can i do without google apps?
When i'm trying to install only play store, phone is turning off and again stuck in 'bootloop'.
Pls help me, i really want to have 1.7 ghz and 520-600 mhz.
mikollek said:
Hello!
I'm having a problems, when i'm trying to install iodak v5 and Werewolf v005 on my phone.
I have CM 10.1 Nightly (20120604) and CWM 6.0.3.1.
When i boot into recovery mode, im installing iodak v5 from internal sdcard, and after install i'm rebooting phone.
It stucks into logo lg, and i have to boot into recovery again and do a factory reset.
Another problem is when i'm trying to install Werewolf v005 instead of iodak v5.
I'm doing factory reset, cache partition reset, and installing CM 10.1, gapps, Werewolf v005_fixed.
When im rebooting phone, it stays in 'bootloop', so i have to re-insert my battery and do a factory reset again.
But when i install only CM 10.1 then Werewolf v005 - it works, but what can i do without google apps?
When i'm trying to install only play store, phone is turning off and again stuck in 'bootloop'.
Pls help me, i really want to have 1.7 ghz and 520-600 mhz.
Click to expand...
Click to collapse
hmm, your problem sounds interesting... what's your cpu variant?
also, have you tried: full wipe --> flash rom --> flash gapps --> wipe cache --> flash kernel --> reboot?
cause sometimes flashing gapps needs to wipe cache, too...
laufersteppenwolf said:
hmm, your problem sounds interesting... what's your cpu variant?
also, have you tried: full wipe --> flash rom --> flash gapps --> wipe cache --> flash kernel --> reboot?
cause sometimes flashing gapps needs to wipe cache, too...
Click to expand...
Click to collapse
Thanks for your post.
It's my first rooted phone and i have LG 4x HD from just one week.
How can i check my cpu variant?
PS. Yes, i've tried, and with Werewolf it works, but when i will open Play Store, phone is turning off and bootlooping again..
And with iodak it's still stuck in lg logo.
PS2. Sorry for my bad english! English isn't my main-language.
mikollek said:
Thanks for your post.
It's my first rooted phone and i have LG 4x HD from just one week.
How can i check my cpu variant?
PS. Yes, i've tried, and with Werewolf it works, but when i will open Play Store, phone is turning off and bootlooping again..
And with iodak it's still stuck in lg logo.
PS2. Sorry for my bad english! English isn't my main-language.
Click to expand...
Click to collapse
about CPU variant, @exFAT wrote a tut on how to find it out.
and about the bootloops:
flash it and let it boot. then run a logcat, recording the crash when attempting to open play store. when it is bootlooping then, please grab a dmesg (last_kmsg) and give me/us the two files. then we can see what's the problem
laufersteppenwolf said:
about CPU variant, @exFAT wrote a tut on how to find it out.
and about the bootloops:
flash it and let it boot. then run a logcat, recording the crash when attempting to open play store. when it is bootlooping then, please grab a dmesg (last_kmsg) and give me/us the two files. then we can see what's the problem
Click to expand...
Click to collapse
Now i have another problem.
I did like u said (full wipe -> flash rom -> flash gapps -> cache wipe -> flash werewolf)
I opened Play Store, and it worked.
I downloaded the game (Subway Surfers) and opened. I've started playin', and after about 10 seconds phone got fully lagged, i had to re-insert battery. Now when i'm trying to boot it up, it's coming to PIN, but i cant click numbers.
Are you sure you installed the right Kernel? There are two variants: for CM and Stock. If you flash the wrong one you'll get problems.
Sent from my LG-P880
mikollek said:
Now i have another problem.
I did like u said (full wipe -> flash rom -> flash gapps -> cache wipe -> flash werewolf)
I opened Play Store, and it worked.
I downloaded the game (Subway Surfers) and opened. I've started playin', and after about 10 seconds phone got fully lagged, i had to re-insert battery. Now when i'm trying to boot it up, it's coming to PIN, but i cant click numbers.
Click to expand...
Click to collapse
what do you mean with you can't click numbers?
Monskiller said:
Are you sure you installed the right Kernel? There are two variants: for CM and Stock. If you flash the wrong one you'll get problems.
Sent from my LG-P880
Click to expand...
Click to collapse
good point, but if he's flashed the stock version on CM, it shouldn't boot at all
laufersteppenwolf said:
what do you mean with you can't click numbers?
good point, but if he's flashed the stock version on CM, it shouldn't boot at all
Click to expand...
Click to collapse
Well.. he did get in a bootloop or stuck on boot logo didn't he?
Monskiller said:
Well.. he did get in a bootloop or stuck on boot logo didn't he?
Click to expand...
Click to collapse
yeah, he did, but:
mikollek said:
...
I did like u said (full wipe -> flash rom -> flash gapps -> cache wipe -> flash werewolf)
I opened Play Store, and it worked.
I downloaded the game (Subway Surfers) and opened....
Click to expand...
Click to collapse
and with the stock kernel he wouldn't be able to do all this
laufersteppenwolf said:
yeah, he did, but:
and with the stock kernel he wouldn't be able to do all this
Click to expand...
Click to collapse
Iodak kernel was the issue with boot logo, maybe that one was the mistake. As for the Werewolf one, could it be the ROM itself? Or wrong gapps version. Instead of 4.2.2 got 4.2.1
Monskiller said:
Iodak kernel was the issue with boot logo, maybe that one was the mistake. As for the Werewolf one, could it be the ROM itself? Or wrong gapps version. Instead of 4.2.2 got 4.2.1
Click to expand...
Click to collapse
well, of course it could be the rom having a bug. and about gapps, nope, i don't think so.
but for giving a proper answer, i'd need a dmesg
laufersteppenwolf said:
well, of course it could be the rom having a bug. and about gapps, nope, i don't think so.
but for giving a proper answer, i'd need a dmesg
Click to expand...
Click to collapse
Indeed. I'll leave it to you, My knowlege of Android isn't very high.,
@Monskiller
The first time that's true, i used variant for Stock, but i did wipe and installed the CM variant, and it's the same - stuck in lg logo.
@laufersteppenwolf
I will try to run 'logcat' when i will again flash werewolf [cuz sometimes when i flash it works, and sometimes i'm stuck in PIN and i can click anything (lagged)].
But i there i have Another problem... Im trying to check CPU variant as u said, but when i flash CM, adb says - 'error: device offline'.
@@EDIT
Help me pls, again i flashed werewolf. I downloaded and installed 'catlog' and started recording, then i wanted to download trickster, and in one moment, phone just turned off... im broke..... how to check file from catlog now? (phone is not bootloping, when im trying to boot up it's just turning off after CM logo)
When i will flash CM, i wont be able to check logs, cuz on CM my adb doesn't work (device offline)... what have i to do?
mikollek said:
@Monskiller
The first time that's true, i used variant for Stock, but i did wipe and installed the CM variant, and it's the same - stuck in lg logo.
@laufersteppenwolf
I will try to run 'logcat' when i will again flash werewolf [cuz sometimes when i flash it works, and sometimes i'm stuck in PIN and i can click anything (lagged)].
But i there i have Another problem... Im trying to check CPU variant as u said, but when i flash CM, adb says - 'error: device offline'.
@@EDIT
Help me pls, again i flashed werewolf. I downloaded and installed 'catlog' and started recording, then i wanted to download trickster, and in one moment, phone just turned off... im broke..... how to check file from catlog now? (phone is not bootloping, when im trying to boot up it's just turning off after CM logo)
When i will flash CM, i wont be able to check logs, cuz on CM my adb doesn't work (device offline)... what have i to do?
Click to expand...
Click to collapse
Did you do a full backup in CWM before trying to flash kernel/ROM or mess with anything like that? I've made and kept a full nandroid backup of mine just in case.
Your problem seems pretty serious.. I'm no expert. Try to use a different ROM maybe? just for now see if it behaves the same.
Also, did you try to whipe Dalvik cache? (Think that's how is called)
Monskiller said:
Did you do a full backup in CWM before trying to flash kernel/ROM or mess with anything like that? I've made and kept a full nandroid backup of mine just in case.
Your problem seems pretty serious.. I'm no expert. Try to use a different ROM maybe? just for now see if it behaves the same.
Also, did you try to whipe Dalvik cache? (Think that's how is called)
Click to expand...
Click to collapse
Ehh, so i won't check that dmesg?
Maybe i have to try Werewolf ROM? It looks really good too.
Try a different ROM, but if the problem still exsists then check dmesg, as laufersteppenwolf said. He'll know a better solution.
Monskiller said:
Try a different ROM, but if the problem still exsists then check dmesg, as laufersteppenwolf said. He'll know a better solution.
Click to expand...
Click to collapse
yeah, that'd be no bad idea. 'cause you've got problems with my kernel, try my rom (don't have to like/use it, just for testing). the v005 kernel is already included.
wipe everything (full wipe + format /system), flash rom, flash gapps, wipe cache ,boot and see what happens
and about adb, you need the latest adb version (.31) for android 4.2.2. then you also need to "register" your PC in your phone. simply just type adb devices --> look @ your phone and allow the access. now adb should work
Really thanks for help..
But i have another problem.. did i broke my usb cabel or what?
When im on CM 10.1 nightly, and connecting usb for try to put urs ROM into my internal sdcard, my PC says error.
Also when im trying to update to V20A through S/W Upgrade it says 'PHONE WAS NOT FOUND'.
So what should i do now.. ?
mikollek said:
Really thanks for help..
But i have another problem.. did i broke my usb cabel or what?
When im on CM 10.1 nightly, and connecting usb for try to put urs ROM into my internal sdcard, my PC says error.
Also when im trying to update to V20A through S/W Upgrade it says 'PHONE WAS NOT FOUND'.
So what should i do now.. ?
Click to expand...
Click to collapse
try to re-install your drivers
laufersteppenwolf said:
try to re-install your drivers
Click to expand...
Click to collapse
Sorry for me but.. which drivers, and how?
@@EDIT
I've installed the newest LG MOBILE UNITED Drivers, and it's still the same...
'can't copy files - device stopped working or has been disconnected' (or something like that, cuz it's in polish and i don't know how is it in english properly).
@@EDIT2
I've tried to connect my phone to other PC, and on other pc everything works fine... where's problem?
@@EDIT3
I connected via WiFi file transfer pro, and downloaded your rom on it, but now CWM says when i'm trying to flash 'Can't open ..... .zip (bad) installation aborted'
Related
I got some problem with installing a Custom rom...
I allready got root from superone Click, got Titanium Backup working...
then i installed The clockworkmod (external sd) from the tread in the forum.
then i moved the Custom rom MODACO FR17 Fear edition to my external sd..
booted into CMW by holding VOL DOWN + POWER
backup with nand
then wiped data and Cache
then installed the Custom rom and it went fine it took 3-4 min and then it said ok
I rebooted and i just hanged on the LG LOGO for 10-15 min.
removed the battery and still the same hangs on the LG LOGO
tried flashing it all over but still the same...
i was so lucky that i could restore my backup and now it up running...
can somebody please help me what could have gone Wrong ??
should i try another CWM ??
dk_iceman said:
I got some problem with installing a Custom rom...
I allready got root from superone Click, got Titanium Backup working...
then i installed The clockworkmod (external sd) from the tread in the forum.
then i moved the Custom rom MODACO FR17 Fear edition to my external sd..
booted into CMW by holding VOL DOWN + POWER
backup with nand
then wiped data and Cache
then installed the Custom rom and it went fine it took 3-4 min and then it said ok
I rebooted and i just hanged on the LG LOGO for 10-15 min.
removed the battery and still the same hangs on the LG LOGO
tried flashing it all over but still the same...
i was so lucky that i could restore my backup and now it up running...
can somebody please help me what could have gone Wrong ??
should i try another CWM ??
Click to expand...
Click to collapse
newest CWM is here : http://forum.xda-developers.com/showthread.php?t=1098001
generally, you did everything right, wipe data / cache FIRST in recovery, THEN apply custom ROM
superone Click is not really needed before, but it doesn´t matter ...
you could update baseband first : http://android.modaco.com/content/l...lash-stock-baseband-release-1035-21-20110502/
use Baseband 1035.21_20110405 , Baseband 1035.21_20110502 is buggy !
75markus said:
newest CWM is here : http://forum.xda-developers.com/showthread.php?t=1098001
generally, you did everything right, wipe data / cache FIRST in recovery, THEN apply custom ROM
superone Click is not really needed before, but it doesn´t matter ...
you could update baseband first : http://android.modaco.com/content/l...lash-stock-baseband-release-1035-21-20110502/
use Baseband 1035.21_20110405 , Baseband 1035.21_20110502 is buggy !
Click to expand...
Click to collapse
The CWM your refering to is the one i used ? should i try the one useing INTERNAL SD ?
does it matter that before i used the mentioned CWM above i tried to use the CWM ROM MANAGER from Marked, but it did'nt work, then i installede the other CWM ??
I Allready got the baseband 405 installed
can it have something to do with the custom rom change the fileformat to EXT4 ??
I really dont undestand what went wrong ?? I have been flashing rom since HTC HERO, never had problems not even with SGS
had the same problem that it hange at the LG log, i searched for a recovery solution and i found one in this forum and found a soltution to restore the phone with NVFlash
here is the link :http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
all you have to do is download the 2 files from there, take the battery out of your device, connect it to the computer. hold up and down and power and a device will be recognized by your system (the device disp;lay will stay black)
install the downloaded driver (the device should be recognized by your windows)
then run the bat file from the 2nd download and the device should be restored.
after that it will go into boot loop and you have to insert the battery.
then it should start up like a new device. hope that helps
grognaz said:
had the same problem that it hange at the LG log, i searched for a recovery solution and i found one in this forum and found a soltution to restore the phone with NVFlash
here is the link :http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
all you have to do is download the 2 files from there, take the battery out of your device, connect it to the computer. hold up and down and power and a device will be recognized by your system (the device disp;lay will stay black)
install the downloaded driver (the device should be recognized by your windows)
then run the bat file from the 2nd download and the device should be restored.
after that it will go into boot loop and you have to insert the battery.
then it should start up like a new device. hope that helps
Click to expand...
Click to collapse
I got it up running again by restoring my nand backup, and its working.
but what i would like to is installe a custom rom, would that your are saying help me ??
do i have to root it after doing the above ?
dk_iceman said:
The CWM your refering to is the one i used ? should i try the one useing INTERNAL SD ?
does it matter that before i used the mentioned CWM above i tried to use the CWM ROM MANAGER from Marked, but it did'nt work, then i installede the other CWM ??
I Allready got the baseband 405 installed
can it have something to do with the custom rom change the fileformat to EXT4 ??
I really dont undestand what went wrong ?? I have been flashing rom since HTC HERO, never had problems not even with SGS
Click to expand...
Click to collapse
you can try and download / install CWM 3028 with ROM Manger, it also used to work for me ...
perhaps the EXT4 conversion didin´t work, who knows ...
you didn´t do anything wrong yet, so keep trying
Just one question, did you wipe the dalvik cache ?
Mike_52 said:
Just one question, did you wipe the dalvik cache ?
Click to expand...
Click to collapse
yes i tried again now... and wiped dalvik cache in advanced. still the same stops on the LG LOGO
one question.. when entering CWM by holding VOL DOWN + Power i have read it should say ANDROID ?? but mine Dosen't say ANDROID , it just goes from LG LOGO into CWM
okay now Im starting all over i think...
I just flashed the O2X with NVflash and beging from scratch
make sure your CWM is updated the first CWM version had issues
Anyway you should post such threads in General, it has nothing to do with dev.
Sorry for placing this tread in the wrong place...
I finally got something working..
CyanogenMod 7 is running and BlazingDragon 1,7 works perfekt..
but still no matter what i do i can't get MoDaCo FR17 Fear Edition to work :-(
dk_iceman said:
Sorry for placing this tread in the wrong place...
I finally got something working..
CyanogenMod 7 is running and BlazingDragon 1,7 works perfekt..
but still no matter what i do i can't get MoDaCo FR17 Fear Edition to work :-(
Click to expand...
Click to collapse
you can try orig. FR17 prebake from Modaco, worked fine for me ... http://android.modaco.com/content/l...ptimus-2x-with-online-kitchen-now-with-oc-uv/
FR17 Fear is using my theme, you can apply afterwards if you like
find in my signature BGB Theme
Have you tried downloading the ROM one more time?
Maybe you got a bad download. you could do a MD5 check on the file to be sure.
cagra said:
Have you tried downloading the ROM one more time?
Maybe you got a bad download. you could do a MD5 check on the file to be sure.
Click to expand...
Click to collapse
Tried that also :-S
the only thing i haven't tryed is Checking the MD5, wich program do you use to check it with ?
Never done a MD5 check my self, but there should be plenty of freeware tools that can do it.
I had the same problem on fear edition. After i got stuck @ logo i just wiped dalvik and cache again 2x and then rebooted and started working fine.
Sent from my LG-P990 using XDA App
peacekeeper05 said:
I had the same problem on fear edition. After i got stuck @ logo i just wiped dalvik and cache again 2x and then rebooted and started working fine.
Sent from my LG-P990 using XDA App
Click to expand...
Click to collapse
still not working
Good afternoon,
I'm sorry i'm creating a new thread about an old subject, but i just can't get my X8 to work with custom kernel+rom. I've searched the forum for the same issue but none of the solutions described worked. Until this moment i had to use PCC to flash my smartphone back to normal about 10 times and it's starting to get very annoying. I've followed the devs instructions on all procedures thoroughly, rooting, bootlader unlock, flashing kernel and installing ROM, and it always gets stuck on the kernel logo wether is it before or after flashing the rom (unless i press the back button). To this moment, i've tried nAa-14 and alfs v09 kernel, GingerDX and Zaraki roms, followed guides step by step. I'm a newbie in the smartphones area but not when it comes to computers. Throughout my 'voyage' i had a number of bumps i had to overcome, like having the installation aborted (bad) error when trying to install a rom, which i solved by downloading the zip directly to the SDcard like described here in the forums. GGdrivers are installed, and so are the SE USB drivers, phone is recognized by PCC with no problems.
I honestly have no idea what might be wrong, and as i said, i've done a search before creating a new thread but nothing helped, or maybe i'm just missing a tiny detail. I would really like the help since this is my first smartphone and i would like to play with my new toy!
Thanks and sorry for any inconvenience.
EDIT: I forgot something. In the kernel installation guide is requested that after flashing it, to check in the phone settings if everything is ok. I can't even boot the phone after flashing the kernel (gets stuck on kernel logo) which means my problem is related to something previous to it? Maybe bootlock? I'm pretty sure i'm doing what's required.
Appreciate the fast answer.
I get stuck on the logo wether is it before or after flashing the rom. The only way i don't get stuck is to press the back button to boot into cwm.
Yes i've tried to wipe after and before, and it didn't work. And these were the only roms and kernels i've tried.
There's no problem with hardbricking my device by the way, 11w03.
I'll have to get out for a while, but i will come back later to check all the answers, this is a priority for me at the moment
emaz1ng said:
Appreciate the fast answer.
I get stuck on the logo wether is it before or after flashing the rom. The only way i don't get stuck is to press the back button to boot into cwm.
Yes i've tried to wipe after and before, and it didn't work. And these were the only roms and kernels i've tried.
There's no problem with hardbricking my device by the way, 11w03.
I'll have to get out for a while, but i will come back later to check all the answers, this is a priority for me at the moment
Click to expand...
Click to collapse
Don't full wipe two times,either before or after,you can see this at the rom thread.
One basic detail that many forget is that you must have baseband that lasts to 15,so it would be like this xxx015
Sent from my X8 using xda premium
I didnt full wipe when trying gingerdx, as you said its not requested, only wiped with zaraki. I can confirm my baseband is xxxx015.
Sent from my E15i using xda app-developers app
emaz1ng said:
I didnt full wipe when trying gingerdx, as you said its not requested, only wiped with zaraki. I can confirm my baseband is xxxx015.
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
You have to full wipe,don't full wipe two times,gingerdx needs full wipe before installing the rom....
Sent from my X8 using xda premium
I tried again using the correct wiping method for gingerdx and it still freezes on kernel logo. the weird thing is that it freezes the first time it boots after flashing the kernel, meaning it has nothing to do with the rom, right? and maybe even not related to the kernel itself. i'm completely clueless about this, i wish i had a friend who could do it for me, because i can't detect anything done wrong.
What version of cwm are you using?
Sent from my X8 using xda premium
i'm not quite sure what's the version of cwm since it installs itself along with nAa-14 kernel, but i think it was v5.0.2.8
IAmNice said:
I think its the cwm that comes with the kernel.
For the OP. No idea what to do. You have a weird problem
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
please don't destroy my hopes of having a working custom rom on my phone jokes aside, i get your point, but doesn't it seem not logical that i'm the only one who can't get it to work? it's weird enough i can't boot my phone after flashing the kernel....
i could post a video, sure, but it's pretty straightforward. after i flash the kernel, unplug the phone from PC and boot it up, IF i don't boot into cwm, it will freeze on the kernel logo, making it impossible to even check the phone settings as requested in gingerdx thread. AFTER i install the rom and reboot the phone, it will still show the kernel logo and freeze again (if i understand correctly this is not supposed to happen, what's supposed to show on the screen after the rom is installed are the normal SE logos.)
So, summing up. Flash kernel, turn phone on, freezes on kernel logo if i don't use back button to go into cwm. If i enter cwm, install rom from sdcard, reboot, it shows the kernel logo and freezes if i don't use back button again.
Don't know if it helps but the only way to turn the phone off when it freezes is removing the battery. Sometimes after placing the battery again it will automatically turn on.
Dunno what's wrong,why don't you try with stock kernel and gdx,or why don't you try different rom(yea neither gdx nor gzr)
Sent from my X8 using xda premium
you mean formatting partitions after flashing the kernel or before? i assume there's an option for it under cwm?
stamatis16 said:
Dunno what's wrong,why don't you try with stock kernel and gdx,or why don't you try different rom(yea neither gdx nor gzr)
Sent from my X8 using xda premium
Click to expand...
Click to collapse
sure i can try other roms, but the fact that it freezes before installing the rom seems to point towards another problem?
the phone was bought in 2nd hand by the way, maybe there's something that could have happen before it got to me?
You have to format the partitions after flashing the kernel. In CWM recovery, go to 'mounts and storage' and format all the partitions except /sdcard.
feherneoh said:
Try to format all of the partitions (yes, ALL of them), then install ROM again.
After installation turn off the phone, take out the card, then turn phone on.
I hope it will work.
Click to expand...
Click to collapse
Lajbymester said:
You have to format the partitions after flashing the kernel. In CWM recovery, go to 'mounts and storage' and format all the partitions except /sdcard.
Click to expand...
Click to collapse
Just did it and the same thing happened. Flashed nAa-14, booted into cwm, full wipe, full cache wipe, wiped all the partitions but sdcard, installed rom, rebooted and it froze on the logo. Tried again with removing the sdcard and turning the phone on, froze on logo. Flashing it back to stock using PCC atm
By the way, it didn't let me format sd/ext.
Have you tryed with older version of naa? Naa 14 is buggy, naa 11 is the best
Sent from my p970 using xda premium
emaz1ng said:
Just did it and the same thing happened. Flashed nAa-14, booted into cwm, full wipe, full cache wipe, wiped all the partitions but sdcard, installed rom, rebooted and it froze on the logo. Tried again with removing the sdcard and turning the phone on, froze on logo. Flashing it back to stock using PCC atm
By the way, it didn't let me format sd/ext.
Click to expand...
Click to collapse
Try some other roms like minicm7. Do it in this order
Flash the kernel
Boot to cwm
Format system,data,cache
Fullwipe/Factory reset
Install Rom
Reboot
....wait .....
I do this every time i install a new rom..
Make sure The rom you have downloaded belongs to x8..
ElmirBuljubasic said:
Have you tryed with older version of naa? Naa 14 is buggy, naa 11 is the best
Sent from my p970 using xda premium
Click to expand...
Click to collapse
I will do that right away. I will also download a few others roms (and respective kernels) and try them all out. Only one thing, I was going to download MiniCM10 and i saw this in its post: "MiniCM10 is an unofficial port of CyanogenMod 10 for the SEMC msm7x27 devices." What does it mean 'for the SEMC msm7x27 devices'? Is it related to bootload unlock? Because i get Setool2 Certificate instead of SEMC. Does this make my problem a little easier?
EDIT: Ok, i've just tried ICZaraki+nAa-04-ics, minicm10+nAa-jb, gingerdx/gingerzaraki+nAa 11, and guess what, none worked.... We have to start thinking this is not related with the kernel or rom maybe? Any suggestions? When i tried the nAa-11 kernel, when i booted up the phone a white led popped up instead of a green one. I'm not worried if this takes a whole month to fix, i'm up for any suggestions and ideas of any kind, just throw them at me.
emaz1ng said:
I will do that right away. I will also download a few others roms (and respective kernels) and try them all out. Only one thing, I was going to download MiniCM10 and i saw this in its post: "MiniCM10 is an unofficial port of CyanogenMod 10 for the SEMC msm7x27 devices." What does it mean 'for the SEMC msm7x27 devices'? Is it related to bootload unlock? Because i get Setool2 Certificate instead of SEMC. Does this make my problem a little easier?
EDIT: Ok, i've just tried ICZaraki+nAa-04-ics, minicm10+nAa-jb, gingerdx/gingerzaraki+nAa 11, and guess what, none worked.... We have to start thinking this is not related with the kernel or rom maybe? Any suggestions? When i tried the nAa-11 kernel, when i booted up the phone a white led popped up instead of a green one. I'm not worried if this takes a whole month to fix, i'm up for any suggestions and ideas of any kind, just throw them at me.
Click to expand...
Click to collapse
This happen with alfs too? Have you followed all istructions to unlock bootloader?
Ah please..provide logcat! Big devs like rohin,eet, etc maybe can help you with logcat
ElmirBuljubasic said:
This happen with alfs too? Have you followed all istructions to unlock bootloader?
Ah please..provide logcat! Big devs like rohin,eet, etc maybe can help you with logcat
Click to expand...
Click to collapse
Yep, happens with all the kernels i've used, nAa-11/14, nAa JB, ICS, etc....
Googled logcat, i understand its use, but how do you want me to use it?
Yes, bootload is unlocked, i have the "r". Or is there any chance that even with the "r" it's still locked? Anyway, i followed the guides with no problem.
emaz1ng said:
Yep, happens with all the kernels i've used, nAa-11/14, nAa JB, ICS, etc....
Googled logcat, i understand its use, but how do you want me to use it?
Yes, bootload is unlocked, i have the "r". Or is there any chance that even with the "r" it's still locked? Anyway, i followed the guides with no problem.
Click to expand...
Click to collapse
you can try to use my automated tool at my siggy. Just upload the logs at here and the devs will do their jobs
wcypierre said:
you can try to use my automated tool at my siggy. Just upload the logs at here and the devs will do their jobs
Click to expand...
Click to collapse
am i supposed to specify a device (device id?) or just log all and upload them here?
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason
knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?
No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.
tried without the external SD card inserted?
nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!
SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..
I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".
So...which Stock Rooted ROM using to flash?...
heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
HellRoot said:
if you are sure that you have an z1... then just remove the device check in the updater script (within the zip...) it is in the beginning... cant really remember how it looks but ... search google perhaps.. then it will flash weird enough ... my s also identifies as an sl... but that is from the build prop
Click to expand...
Click to collapse
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Sari95 said:
Haha, yes. I google for it and tried to simply delete the device check in update-script, but it didn't work for me. I believe the issue is in my recovery, which is not a 4.4 kitkat recovery. The CWM-recovery I have at the moment is 6.0.3.6 and I believe that is the reason for my issues. I have had no luck trying to find a 4.4 kitkat recovery... any tips here?
Click to expand...
Click to collapse
well..i have never had problems with it being the recovery... what error does it make now?
HellRoot said:
well..i have never had problems with it being the recovery... what error does it make now?
Click to expand...
Click to collapse
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
[/COLOR]
Sari95 said:
I tried this recovery too, without any luck: http://forum.xda-developers.com/showthread.php?p=49966299
To begin with I got Status 7 error, which is now gone.. I found a tutorial to flash SlimRom for Z1, which is android 4.4.2: http://www.ibtimes.co.uk/android-4-4-2-kitkat-sony-xperia-z1-available-via-slimkat-rom-1432702
However, I was only able to make emergency calls, no cellular at all. I flashed CM through the same method and everything I tried worked, except cellular. Thus, I had to wipe it and install stock Sony firmware.
After that I tried flashing CM the "normal" way through recovery and everything installed as usual, but when I push reboot to reboot the system, the phone simply shuts off. Even if I press the powerbutton to turn it on, it only vibrates and nothing else happens. Again, I flashed stock firmware to be able to use the phone again...
I am very confused about this, because it does not give any errors. It simply does not work :l
Click to expand...
Click to collapse
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
HellRoot said:
[/COLOR]
just copied from the CM11 dev fora...
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
Click to expand...
Click to collapse
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Sari95 said:
Hmm... seems reasonable. Could you give me the link to the fora, so I can try this method out too ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Sari95 said:
As the title suggests, I rooted my phone, unlocked BL and was about to flash CM for Honami, which is Z1, but the flashing of the ROM was stopped because it recognizes my device, a Z1, as a "togari", a Z Ultra. I find this quite odd as I have practically no idea why it does that.
I also tried flashing "togari" CM ROM, but that also fails.
Any fixes for this?
Click to expand...
Click to collapse
I had this problem when I try to flash with LB.
HellRoot said:
http://forum.xda-developers.com/showthread.php?t=2540650
there it is.... hope you figure it out.
Click to expand...
Click to collapse
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Sari95 said:
Thank you I kind of figured it out... but I am not sure why/ how xD I wiped everything, flashed stock firmware "a.136", rooted, installed recovery and flashed CM. After that, it worked as it is supposed to, so problem solved
Thanks for your help
Click to expand...
Click to collapse
good to hear hope you enjoy the CM.... if you want then please tell me how it is running.. performance, battery, camera etc
have a good day
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
panamera2011 said:
Download Odin, using 3.04 or 3.07 for win 7,8,10
http://www74.zippyshare.com/v/18196321/file.html
Put the devices in download mode (Press volume Up + home + power) and install a stock firmware
http://www.sammobile.com/firmwares/database/GT-N7000/
Guide Odin n7000
http://forum.xda-developers.com/showthread.php?t=1424997
If you want to install a custom rom type CM11, CM12 or CM13 you have to install a kernel compatible with recovery
Install PhilZ recovery, then from recovery install a compatible kernel
Kernel CM11
https://www.androidfilehost.com/?fid=24052804347829437
Kernel CM12
http://forum.xda-developers.com/devdb/project/dl/?id=16862
After flashing the kernel do a
Data factory reset
Wipe cache
Wipe Dalvik/ART
Install ROM, install gapps
If it does not work
Data factory reset
Wipe cache
Wipe Dalvik/ART
Format system
Format cache
Format data
Install ROM, install gapps
Click to expand...
Click to collapse
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
bfürbanane said:
I did everything you said. Unfortunately, my device is still stuck at the boot screen. There were no error messages while flashing the roms and no other unusual events.
Click to expand...
Click to collapse
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
panamera2011 said:
This is really strange, try to redo the procedure without installing SuperSU
Sent from my H60-L02 using Tapatalk
Click to expand...
Click to collapse
Where does it say to install SuperSU? How would that be possible when Android is not booting.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
I'm sorry but it's really strange, never had installation issues with any version of this rom
Have you tried this kernel to install the rom?
https://www.androidfilehost.com/?fid=24052804347829437
Sent from my H60-L02 using Tapatalk
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
bfürbanane said:
Where does it say to install SuperSU? How would that be possible when Android is not booting.
Click to expand...
Click to collapse
Sorry but I confused the message with the MIUI 6.2.12 thread [emoji16]
Sent from my H60-L02 using Tapatalk
AutumQueen92 said:
Alternatively, Odin a stock rom and look for a philz.zip with compatible baseband. You can enter stock recovery and then flash the philz.zip via update option. This is essentially replacing stock recovery with the custom version. I did this on a naturally occurring bootloop phone and it seems to work, this method also bypasses the yellow triangle warning on boot.
From there, if you want to use other custom roms just remember to wipe /data and /system before installing the kernel, followed by rom itself after a reboot to recovery.
Click to expand...
Click to collapse
I tried that. I went to samsung-updates.com and downloaded a version that I believe is compatible with my baseband version. Is there any way to check what baseband version my phone has? Then I flashed with odin and was stuck in a bootloop. I then flashed PhilZ recovery and the boot hangs at the samsung logo.
bfürbanane said:
Is there any way to check what baseband version my phone has?
Click to expand...
Click to collapse
Settings>about phone>
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
The phone is not booting.
IronRoo said:
Settings>about phone>
Click to expand...
Click to collapse
Doh! sorry not reading what's in front of me. I did once read that you can get phone number via ADB, maybe the same will work for baseband?
bfürbanane said:
This phone was not rooted prior to being stuck at the boot screen. Actually, it wasn't event stuck at the boot screen. Instead, it turned on and off. I installed PhilZ recovery and was able to backup all files. Then I tried to flash different versions of CM without success. They all get stuck at the boot screen now. No more turning on and off. I also tried to clear cache, wipe dalvik something and reset to factory. Is there something else that can be done? What would be the most likely cause for the failure?
Click to expand...
Click to collapse
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
N00b... said:
Have you tried a clean install ? Wiping /system and /data partitions then installing a custom ROM .. This option can be found in philz under install a new ROM ..
Click to expand...
Click to collapse
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
bfürbanane said:
Yes, I tried that. I also tried installing a ROM with a custom kernel that works on my other N7000, but it is still stuck at the boot screen.
Click to expand...
Click to collapse
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Condox18 said:
I think i got same problem as you do. Im digging on internet , if i get something ill write here.
Click to expand...
Click to collapse
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
same problem
bfürbanane said:
Good to know that I am not alone with my problem. Right now, I am out of ideas. I tried everything I could think of. I hope you have more luck than me.
Click to expand...
Click to collapse
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Condox18 said:
Check this thread, post 3207 http://forum.xda-developers.com/showthread.php?t=1774208&page=321, u may have eactly same problem as me.
Click to expand...
Click to collapse
Thanks for the pointer. I subscribed myself to that thread.