Related
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Try doing full wipe and reinstall CM 10 as you did previously
Sent from my Xperia S using xda app-developers app
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
dumbl3 said:
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I have the same problem My phone not boot in just freexperia logo and cwm5.5.0.4. My /data partition can't mount and format I can't install any rom:crying: Heeeeeelp:crying:
All will be fixed
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
Follow this thread for Kernel and Rom installation; http://forum.xda-developers.com/showthread.php?t=1879982
Follow this other to select your Rom; http://forum.xda-developers.com/showthread.php?t=1642480
And take that cm-10-20130110-UNOFFICIAL is CM 10.2 for such reason look for JB Gapps For Android version 4.1.2
I flashed the Rom very well, also the kernel. my problem were the Gapps. I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Regards,
apsanchezs said:
I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Click to expand...
Click to collapse
I do have the correct gapps. This CM is android version 4.1.2. Here I downloaded the latest for CyanogenMod 10.0.x which is for android versions 4.1.x.
Anyway after a whole evening/night of flashing I finally managed to get it working via hei1125 cm10 version:
http://goo.im/devs/hei1125/nozomi
I dont know what I did to make it working again, but it does.. CM10 does look a lot nicer then CM9. Although I heard it has some bugs, which yet I still have to encounter..
FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip fails
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
I'm on the same problem. Use FXP201 instead or wait until 203... The cm10-fxp202 doesn't work on my device too. Same procedure as Yours or update from 201 to 202 - all will fail on (my) nozomi.
Hello!
Hello! orange fix for this rom?if so, I would like to link to it? thank you very much :fingers-crossed:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel nozimi and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
funky0308 said:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel hikari and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
i got same plobrem with You.
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Enable signaturecheck in recovery before install. It worked for me.
Gesendet von meinem Xperia S mit Tapatalk 2
Make sure you flash the good .img before flashing the ROM !
alexdan2302 said:
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Click to expand...
Click to collapse
It's always recommend to wipe all (cache, davlink even system) then flash.
Be sure to mount system and then try.
And of course, check is you zip file o.k (maybe download again)
Even if you updating cm to new version it's best if you wipe.
I know that's lot of work, but only then you'll have good battery life, smooth and fast ROM and stability.
Sent from my LT26i using Tapatalk 2
Reinstalled apps and Data from googleserver after a datawiped update shoudn't be a Problem, or?
Gesendet von meinem Xperia S mit Tapatalk 2
I had just the same problem today. I installed cm10 from recovery and did everything you did!!!!
What i did to solve this prblem is:
- Went into recovery.
- wiped cache and dalvik.
- flashed the latest CM10 (FXP215 to be precise) again!!
- flashed gapps again!!
- after flashing both zips I wiped dalvik and cache again.
- Than reboot.
If you keep getting into bootloops, keep doing these steps. Beliefe me man I had the exect same problam today and this solved it . Just dont panic or do something stupid and have alot of patients! :good:
But this is not a so called clean install. I use factory reset to have a clean install or just wipe data partition. After 1st boot I restore only some of my saved data with titanium backup.
Gesendet von meinem Xperia S mit Tapatalk 2
Hey there, I just flashed my DHD with CM11, but I have a small problem. CM11 works fine, but everytime when I install GAPPS (Tried many versions for CM11) The phone just boots, I insert PIN and there it starts. It starts flooding me with messages what crashed. Almost everything crashes and when i close it, it appears again (especially keyboard, com.google.process.gapps). Can someone help me? Thanks for all answers
kosil said:
Hey there, I just flashed my DHD with CM11, but I have a small problem. CM11 works fine, but everytime when I install GAPPS (Tried many versions for CM11) The phone just boots, I insert PIN and there it starts. It starts flooding me with messages what crashed. Almost everything crashes and when i close it, it appears again (especially keyboard, com.google.process.gapps). Can someone help me? Thanks for all answers
I solved this myself, I just formatted /system , Installed CM11 and GAPPS 20131107
Click to expand...
Click to collapse
try the GAPPS here.
if that does not work, do a clean flash of rom and boot into phone witout GAPPS, then go back into recovery and flash GAPPS , clear cache, and reboot. After that you should be good to go. :good:
Thanks
TheJokah said:
try the GAPPS
if that does not work, do a clean flash of rom and boot into phone witout GAPPS, then go back into recovery and flash GAPPS , clear cache, and reboot. After that you should be good to go. :good:
Click to expand...
Click to collapse
Yeah, I did this... some things still crash, but it wasnt so big flood so I clicked into Apps and disabled that apps what made problems. Solved
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.
Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )
LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !
LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.
I've tried to flash my Samsung galaxy note 2 (N7105) with the latest Cm (12.1). The phone starts up with no issues, and is working as a charm.
But when i add gapps. They go in to crash loop from the first second i start the phone. I've cleared dalvik and cache. I've tried several types of the CORRECT gapps.zip (stock, nano, pico). But the issue persist.
I've tried googeling for several hours now. You guys are my last resort :/ all info is much appreciated
stick to rom installation guide.
flash rom and gapps without rebooting, do not restore anything at the first boot, add account later, it should work
yaro666 said:
stick to rom installation guide.
flash rom and gapps without rebooting, do not restore anything at the first boot, add account later, it should work
Click to expand...
Click to collapse
Thank you for replying. I tried doing it like you said, but still no luck. -.-