So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
I think so
LGG2 LS980 said:
So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
Click to expand...
Click to collapse
I think u also losses the root permission re-root ur phone install cwm and flash gapps
and
slogger001 said:
I think u also losses the root permission re-root ur phone install cwm and flash gapps
Click to expand...
Click to collapse
So I'm screwed?
NA
LGG2 LS980 said:
So I'm screwed?
Click to expand...
Click to collapse
not so just re-root ur phone from software which u used earlier and install cwm
Just because you can't get to recovery does not necessarily mean you lost root access. They are not one and the same. LGs are kind of finicky about recovery, If the built in reboot to recovery option from the Power menu is not working, you can try an app like QuickBoot or via adb commands from the computer, or via the hardware buttons like so: http://itechtriad.com/articles/2014/2/27/how-to-reboot-lg-g2-into-recovery-mode#.U14kH_ldWSo
If you actually have lost your recovery (which is unlikely because CM would not change that), and still have root access when booted up with CM - you should - then grab Flashify from the Play Store, put your favorite recovery img file on your storage of the phone, and use Flashify to install the recovery for you. Very easy.
Related
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Tell people who you fixed it FFS!
how did you fixed ?
radici said:
need some help please. just did something pretty dumb in a moment of not thinking. i went into rom manager and flashed cwm recovery (I'm using Hairy Bean 1.51 with TWRP) over the damn TWRP recovery, then did a system backup through rom manager. now I can boot into the rom, but no chance of recovery (as i'm guessing there is a twrp/cwm and possibly jb/ics conflict - if the rom manager flashed ics cwm recovery)
how do I get back my twrp recovery?
NB. Rom manager shows both TWRP recovery as well as CWM flashed and I can choose which i want to use... but when I pick TWRP, I still cannot access recovery. Is there an ADB command I can use to remove CWM and then reinstall TWRP? (I already tried installing the TWRP over it hoping to overwrite, but both recoveries still exist)
FIXED, NM.
Click to expand...
Click to collapse
Please help , I'm having exactly the same issue.
OS is booting correctly, but I'm not able to enter in any recovery mode, neither in CWM or TWRP..: confused:
radici said:
FIXED, NM.
Click to expand...
Click to collapse
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
sparkdroid said:
These forums become useless if the knowledge is not captured. It is awesome that you fixed it, but please let us know briefly HOW you fixed it!!
Click to expand...
Click to collapse
Same issue here too' please share how you fixed it.
Hello
Today I've tried to unlock my bootloader of LG Optimus L9 (P760) and install a custom ROM. I managed to unlock the bootloader after a few hours (Windows 8.1 sucks in this and do it on Windows 7 netbook is even more harder) and install the CWM. Then I wanted to install CM11, but the installation failed. I didn't realize that I need special version of CWM for this.
Well, I wanted to enter fastboot again a flash CWM again, but I couldn't boot, because the system was now erased. I couldn't install stock ROM, because phone wouldn't connect, so I grabbed older CM9 and succesfully installed it through CWM.
Problem is, that even from there, I can't flash CWM (flash_image recovery recovery.img in terminal doesn't work - shows error "error scanning partitions failed with error -1" - yet another problem no one can solve). And also, phone won't connect to my PC properly, because there is no LG Software mode in CM. Because of that, I don't see the device in adb and can't reboot it into fastboot. I tried to do it via wi-fi adb, which however only reboots phone and doesn't put it into fastboot mode.
What should I do? I can't install stock ROM, which would help (LG update tool doesn't recognize phone now and any driver I tried for "LGE U2 Device" didn't work... If it was available as a rar installer for CWM, everything would be OK again), I can't reboot it into fastmode, I can't flash CWM in any other way and I'm stuck with CM9, which I hate.
I don't understand why there is no other way, how to get to fastboot. Every other LG Optimus has a key shortcut (vol -, power), except L models and that sucks... I'm completly desperate.
RIPR said:
Hello
Today I've tried to unlock my bootloader of LG Optimus L9 (P760) and install a custom ROM. I managed to unlock the bootloader after a few hours (Windows 8.1 sucks in this and do it on Windows 7 netbook is even more harder) and install the CWM. Then I wanted to install CM11, but the installation failed. I didn't realize that I need special version of CWM for this.
Well, I wanted to enter fastboot again a flash CWM again, but I couldn't boot, because the system was now erased. I couldn't install stock ROM, because phone wouldn't connect, so I grabbed older CM9 and succesfully installed it through CWM.
Problem is, that even from there, I can't flash CWM (flash_image recovery recovery.img in terminal doesn't work - shows error "error scanning partitions failed with error -1" - yet another problem no one can solve). And also, phone won't connect to my PC properly, because there is no LG Software mode in CM. Because of that, I don't see the device in adb and can't reboot it into fastboot. I tried to do it via wi-fi adb, which however only reboots phone and doesn't put it into fastboot mode.
What should I do? I can't install stock ROM, which would help (LG update tool doesn't recognize phone now and any driver I tried for "LGE U2 Device" didn't work... If it was available as a rar installer for CWM, everything would be OK again), I can't reboot it into fastmode, I can't flash CWM in any other way and I'm stuck with CM9, which I hate.
I don't understand why there is no other way, how to get to fastboot. Every other LG Optimus has a key shortcut (vol -, power), except L models and that sucks... I'm completly desperate.
Click to expand...
Click to collapse
Fastboot on these devices is a pain... Make sure you have installed the fastboot drivers twice.
Try flashing the recovery.img with Flashify (root) app from the play store.
xdrc45 said:
Fastboot on these devices is a pain... Make sure you have installed the fastboot drivers twice.
Try flashing the recovery.img with Flashify (root) app from the play store.
Click to expand...
Click to collapse
Thank you for your answer I got into fastboot afterall by using app named "Rebooter (fast reboot)". It allows to reboot phone and make it go immidiately to fastboot. So great, now I could rewrite the CWM and install ROM.
Unfortunately other problems appeared. I'm using the right version of CWM for installing KitKat Android ROMs (and I've tried others), but I'm still unsuccesful in booting them. Instalation goes OK (ROM + gapps), but booting then is pain in the ***. I can wipe dalvik, cache, system... and return the phone to factory settings through CWM as I want, but every ROM gets stuck everytime on the boot.
At first, it takes at least 15 minutes, until LG logo disappears and the animation of booting starts. I left all ROMs to boot for an hour. But it seems I'm without a chance. Did anybode have the same problem as me?
BTW: This is my 6th smartphone into which I installed alternative ROM. I swear, that this is the hardest piece of crap for installing those, I have ever seen
Edit: I tried other kernels, also without success. It's strange, that I can install only CM9 and PACman ROMs. CM11, Miui, Mokee - no chance
RIPR said:
Thank you for your answer I got into fastboot afterall by using app named "Rebooter (fast reboot)". It allows to reboot phone and make it go immidiately to fastboot. So great, now I could rewrite the CWM and install ROM.
Unfortunately other problems appeared. I'm using the right version of CWM for installing KitKat Android ROMs (and I've tried others), but I'm still unsuccesful in booting them. Instalation goes OK (ROM + gapps), but booting then is pain in the ***. I can wipe dalvik, cache, system... and return the phone to factory settings through CWM as I want, but every ROM gets stuck everytime on the boot.
At first, it takes at least 15 minutes, until LG logo disappears and the animation of booting starts. I left all ROMs to boot for an hour. But it seems I'm without a chance. Did anybode have the same problem as me?
BTW: This is my 6th smartphone into which I installed alternative ROM. I swear, that this is the hardest piece of crap for installing those, I have ever seen
Edit: I tried other kernels, also without success. It's strange, that I can install only CM9 and PACman ROMs. CM11, Miui, Mokee - no chance
Click to expand...
Click to collapse
Hmm... That is strange. Are you getting any errors like "status 7 error" when you try to install any of the ROMs?
xdrc45 said:
Hmm... That is strange. Are you getting any errors like "status 7 error" when you try to install any of the ROMs?
Click to expand...
Click to collapse
Nope. That was back when I had bad CWM installed. This one is however OK and install goes absolutely right. Right now I'm pretty sure, that problem isn't in kernel, cause I tried every I could find...
RIPR said:
Nope. That was back when I had bad CWM installed. This one is however OK and install goes absolutely right. Right now I'm pretty sure, that problem isn't in kernel, cause I tried every I could find...
Click to expand...
Click to collapse
If I remember correctly I think the cwm for cm11 has a bug that doesn't wipe dalviks. So flash ROM with the cwm for cm11 then restore the other recovery to wipe data. Or use something like rm -rf /data/* through terminal adb and reboot.
Make sure you mount the data partition first if you use adb and terminal.
Sent from my LG-P769 using XDA Premium 4 mobile app
kuma82 said:
If I remember correctly I think the cwm for cm11 has a bug that doesn't wipe dalviks. So flash ROM with the cwm for cm11 then restore the other recovery to wipe data. Or use something like rm -rf /data/* through terminal adb and reboot.
Make sure you mount the data partition first if you use adb and terminal.
Sent from my LG-P769 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That was it! Thank you very much!
RIPR said:
I got into fastboot afterall by using app named "Rebooter (fast reboot)". It allows to reboot phone and make it go immidiately to fastboot.
Click to expand...
Click to collapse
Wait...what??? Did I just read that there's another way to get into fastboot???
Sent from my LG-P769 using XDA Premium 4 mobile app
So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
LGG2 LS980 said:
So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
Click to expand...
Click to collapse
go and post here instead.. http://forum.xda-developers.com/android/help
LGG2 LS980 said:
So I just flashed CyanogenMod 11 on LG G2 and forgotbto flash GApps on my phone and when I try folowwing CyanogenMod steps to booting into recovery mode it won't and it just boots back into the operating system. I think Clockworkmod got deleted when I flashed the operating system. So I can't install it without gapps and I need my apps! Please help me. You contact me from my email [email protected] or message me on here.
Click to expand...
Click to collapse
ROM manager at your disposal..
Install ROM manger after install it will ask to install Recovery if not present.. If you are not sure then check if you recovery or not.. by slecting the recovery version it asks after installing the app..
shubhojit89 said:
ROM manager at your disposal..
Install ROM manger after install it will ask to install Recovery if not present.. If you are not sure then check if you recovery or not.. by slecting the recovery version it asks after installing the app..
Click to expand...
Click to collapse
:good:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.