Database Develop

O2x bootloop after unlocking boot loader

Hello everyone
So I have fully rooted phone which I've been using for a long time with CM10.1, I just wanted to flash cwm from 6.0.3.1 to same version with cwm touch support but I couldn't because of many errors in ADB and other programs like All in one tool kit and others. So again, I got an error that I couldn't flash a new cwm, I don't know why but I thought of unlocking boot loader again.... that was really stupid, why I had to do that I don't know I thought the errors would go away... but now I have some crappy old lg logo which I had a year ago like I just bought a phone, now I cant get past or even see CM boot logo, just the red old lg logo. So I guess that's what is called boot loop? Its not first time I got this problem and fixed it somehow, but now I don't know what to do because I cant even get into cwm, the only way to get in there is to flash cwm again and if I power off my phone the combinations of cwm doesn't work, so that's why I need to flash again so that it could launch cwm automatically. Did I messed up my boot partitions or something ?
Things I have:
6.0.1.5 cwm from nv flasher
CM10.1 a new nightly in my phones internal memory (I install them like 2 times a week through cwm without problems) which I thought could fix everything by installing a rom with not messed up system files (I've put it into phone before this problem occurred)
but I cant install any zip from sdcard like I did every time before because it sais E:Cant mount /sdcard/ (WHAT???)
I don't have any backups -_-
internal and external memory which are both full and cant access in cwm by pressing mount usb storage, it doesn't work..... So it means I cant make a backup in cwm.
Things I want to do:
Get back to phones previous state. I think its possible because its not like I have erased the data, I just messed up boot partitions, yes ?
I also don't want to loose my data on sdcard/emmc or what ever its called. (on my phone both internal/external memories are called sdcard). Ofcourse if there is a way to somehow make a backup without cwm then Its okay if loose my data, then I can do a factory reset.
Maybe I cant install zip from sdcard because this cwm is bad? Will a newer version also say that I cant mount sdcard (I never had this problem in any cwm's that I have used).
I hope someone can suggest me something . If I wrote something not clear or haven't said some details, tell me I'll try to explain.
!EDIT: Ok I've managed to fix that lol.
Things that I've done:
used All in one kit option called "flash stock rom" (even if I have already a custom rom, not stock ) then installed older cwm, it was version 5 it had a good working "mount usb storage" so my pc recognized the phone and I placed new CM rom into my sdcard (external). So after I flashed the rom, installed cwm5, I fixed permissions just in case, then deleted cache partition and dalvik cache, then installed that CM rom, somehow it still had an old boot logo and was still stuck in boot loop, then again after I used All in one kit and flashed stock rom I saw my new lg logo (black and white, not the broken one with red lg circle) so I just normally booted up phone from cwm and I have everything back without any data loss.

Weird CWM behaviour

Hello!
Before I want to go on to CWM I want to tell you what happened before.
Yesterday I flashed TWRP recovery which resulted in a really bad situation. I was stuck in recovery. If I pressed reboot it went straigt to recovery again, even if I pulled out the battery. So flashed the stock firmware via the KDZ flashing method and everything worked again.
Then I rooted again, installed CWM, installed CM, installed all my apps (TB backup on PC was quite old),....
So all in all it was a big amount of work and it took me a few hours.
Then everything was working again as it should and I updated all my TB backups and then I wanted to make a Nandroid backup so that I wouldnt have to do all that flashing and installing again.
So I went to recovery--> backup and restore --> backup
But it didnt finish. It always stopped with this error: Error while meaking a backup image of /system!
So i thought maybe I should install everything again, which i did. (I had already made a TB backup of all my apps, so i thought this woulb be done fast)
Well, went to recovery again, did a factory reset, wiped dalvik cache and even formated /system. Then I installed the latest CM + GAPPS and rebooted.
And the first thing i recognized was that the screen popped where it says "android is upgrading". And I wondered even more when I realized that all my apps where stille there. So obviously the factory reset and also format /system didnt work properly.
If I format /system and dont install any ROM then the device doesnt boot (which i guess is the normal behaviour). But what I want to say is that the format works there but if I flash CM afterwards all my apps are still there (despite the fact that i also did a factory reset).
All in all the phone does work normal now, but I'm not able to make a Nandroid backup and I'm really wondering why.
(I also reflashed CWM recovery but that didnt change anything)
I would be glad if s1 could help me.
PS: Could the solution be to flash stock again via KDZ and then do everything from the beginning?

Never heard of anything like this before.
Did you flash the recovery as a .IMG or through Rom manager (I would suggest to flash it with Rom manager).
Try this and report back (maybe your recovery image is damaged or smth.)
Sent from my LG-P880

I have no idea what caused this crazy behavoiur of CWM, but I started over again with flashing kdz and now everything is fine

Maybe your SD card is full. Try deleting a few files from your SD and then do the backup.
Sent from my GT-I9070 using xda premium

I dont have any external sd card and on phone memory there were more than 10GB free space

Unable to install latest Mokee build properly

Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?

isketch93 said:
Today I tried to install the latest Mokee build on my phone, but I probably messed something up, as all I was left with upon reboot was a stuck boot screen and hardware keys making the phone vibrate when pressed.
I proceeded as follows:
first of all, I wiped cache and dalvik cache from recovery (I am currently using CWM r7). I did NOT wipe data, as I didn't want to lose any app/document/photo/etc. - I suspect this might be a major cause of failure, but I hope not, since I realy really really don't want to lose anything. Since I already had true dualboot enabled, I went as far as flashing it on system2, to avoid messing with my primary partition (MIUI v5 is mounted there). The procedure apparently completed fine, without errors or hiccups, then it asked me something about fixing root access on system2 and I selected to fix it since I need root access for several apps. I then rebooted the phone on system2, and I got stuck on the boot screen: a white MI logo in the middle and 'android' written on the bottom. The only sign of reactiveness the phone showed was some weird pattern of vibrations produced by the pressing of the hardware keys (volume up, down, and power).
Luckily I was able to reboot into system1 without any issue there, but still I can't use Mokee. Do you guys have any idea what I could have done wrong?
Click to expand...
Click to collapse
I had 70% similar scenario ,but different error. i could boot into mokkee rom but crashed during initial setup ,below were the steps i used to fix it
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
got perfectly working Mokee ROM in MI3

bluethilak said:
Take a nandroid backup of your miui using CWM recovery and apps backup(used EasyBackup ) as well contacts and other important datas for re-installing in mokkee.
saved the mokee zip in internal memory.
went back to CWM and disabled True boot.
formatted System 1 partition.
installed Mokkee zip latest
installed banks GAPPS latest
Click to expand...
Click to collapse
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?

A nandroid backup is to be used in case of failure (and as a backup... but you should have backups anyway so data loss isn't the end of the world) - an app backup is so you can reinstall the apps with settings in Mokee.

isketch93 said:
This step scares me. I am very afraid of data loss, so I'm not eager to try this without in depth explanation
Also, what's the exact purpose of the nandroid backup? Safety measure in case of failure? Or restoration of stuff into the new rom?
Click to expand...
Click to collapse
Nandroid backup is nothing but a complete backup of both Rom and Data.It will in a zip format ad gets saved in your internal memory
[Clockworkmod for CWM/TWRP for TWRP recovery]
http://www.makeuseof.com/tag/what-is-a-nandroid-backup-and-how-exactly-does-it-work/
Let me tell you How I handle my backup plans for my device because at least per week i will be changing the ROM.
1) I always save my contacts in Google contacts(So a normal sync will do)
2)I backup all app data and Message data using EasyBackup
:good::good:

I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?

bluethilak said:
...got perfectly working Mokee ROM in MI3
Click to expand...
Click to collapse
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps

isketch93 said:
Little update here!
I managed to install and boot into Mokee (yay!) without any major issue, but I get endlessly repeating "Google Play Services has stopped working" warnings as soon as it boots up. Seraching "banks gapps" I found and flashed the ones from the euroskank website, were they wrong?
EDIT: nevermind, I was able to solve this by myself flashing latest minimal gapps
Click to expand...
Click to collapse
Dude banks gapps latest is for 5.1.0 lolipop ,mokkee is still in 5.0.x try other gapps ,PA or MInimal or get old Bank Gapps of correct lolipop version.:good:
---------- Post added at 10:06 AM ---------- Previous post was at 09:59 AM ----------
isketch93 said:
I decided to give all this a go, but I encountered a problem right away: I cannot make a nandroid backup due to not having enough free space on my phone's memory.... How can I solve this problem?
Click to expand...
Click to collapse
Clear some space at least 2gb temporarily in you Internal Memory ,Since you will be backing up your App Data,it definitely requires a lot of space .

'do a wipe' ? not sure what this means exactly, maybe it is what i need to do?

I have a HTC ONE m7, rooted, I have been running CM11, flashing the nightlies with great success. When CM12 came out, it 'soft bricked' my phone, continuous reboots, failing android functions. was able to reinstall Titanium backup, then restore the phone to a previous point. back running, but not without bugs. after trying this 3 times, I have given up. but I read where people say, "do a wipe" then flash the ROM....... What, specifically does this mean?
yes I have rooted my phone, but I am just knowledgable to be dangerous. if It means back to factory specs, then how do I flash the rom? I think that my phone should run CM12, and maybe I need to wipe? wipe what? dalvic cache? is that a wipe?
Anybody have some ideas or can point me to some postings that may help me. Many Thanks, very tired of operating on the last build of CM11
blairan

Do a wipe typically means wipe the data, system, cache, and dalvik cache partitions. If you are using TWRP as your recovery (I do for this phone), boot into it and then press Wipe, then Advanced Wipe. Select those four (not internal storage or USB OTG) and then Swipe to Wipe. Of course, your phone won't boot at this point, so you'll need a new ROM waiting on internal storage to be flashed.

thankyou Coal, I have been trying to install a CM12 and/or a CM12.1 ROM I can get them to boot up, but play store is not present. I can access play store via themes, and it comes up as a web page rather than an app. (is this norm for CM12?)
once I sign in to play store, I try to install titanium backup to restore all my apps. it says it is installed, I press it anyway, and it says it will be installed soon, which never happens. CM12 and CM12.1 seem to be running fine, but I can't restore any of my old phone. I can recover to a CM11, but it is a little unstable, so I would like to upgrade the system and be flashing nightlies again. what do you think?

and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!

blairan said:
and after watching a few videos on you tube, I figured out that I was missing the Gapps file, and the supers file. enjoying lollipop success.
thanks coal!
Click to expand...
Click to collapse
I was going to suggest GAPPS, but I wasn't sure if you needed it for CM. Glad you figured it out!

Soft bricked my G2. Can enter TWRP but flashed ROMs won't boot up

I ran into a strange problem. I was experimenting between 2 ROMs (T-Mobile 30b Extreme and xdabbeb's VS980 3.12). I have TWRP installed and I had successfully tried both ROM (Stock 39A Rooted -> T-Mobile 30b Extreme -> xdabbed -> T-Mobile 30b Extreme).
But then, I went into TWRP recovery and decided to wipe it clean (Advanced, wiped all partitions including system and Internal Storage) and flash again, something bad happened. The phone will not finish booting.
The phone will boot up with the standard LG logo for about a minute. Then boot into an animated, bigger LG Logo. And then it will stuck there forever. Normally, it should go into something like "initializing... 1 out of 130".
I can still enter TWRP recovery and browse the file system and even flash another ROM from OTG-USB. But none of the ROM would boot beyond the initial boot screen. Any ideas?
Edit: It seems my issue is covered here:
https://www.reddit.com/r/lgg2/comments/1vtp6u/help_accidentally_wiped_internal_storage_in_twrp/
I had 39A and really don't want to go back to square one if I have a choice. What exactly is the Internal Storage and why even having TWRP cannot help me recover?

Answering my own question.
Yes, there is a better solution. The solution is even under the same page as "Wipe" of TWRP. It is called "Format Data". I suspect that either the entire partition for internal storage is removed or some important file is missing. "Format Data" restores it. I'm back to where I was. I can't believe no one from reddit mentioned this.