Database Info

[Q] I messed up

i was installing one one of the kernel and i freezes at the gx2 logo, so tried recovery and it just sits at the gx2 screen. how bad did i mess it up?

blitzs13 said:
i was installing one one of the kernel and i freezes at the gx2 logo, so tried recovery and it just sits at the gx2 screen. how bad did i mess it up?
Click to expand...
Click to collapse
Did you NVFlash CWM recovery on it?

yes i did and it keeps freezing at the same gx2 logo, is there any way to bring it back to factory to start over

blitzs13 said:
yes i did and it keeps freezing at the same gx2 logo, is there any way to bring it back to factory to start over
Click to expand...
Click to collapse
After you flash a kernel the first boot does take a couple minutes, but flashing another rom should do it

cool ill try that, thanks
reflashed a new rom it boots up but i have no service and it starts restarting itself, i went back to recovery and did a factory reset and nothing, do i now need to get a new phone.

blitzs13 said:
cool ill try that, thanks
reflashed a new rom it boots up but i have no service and it starts restarting itself, i went back to recovery and did a factory reset and nothing, do i now need to get a new phone.
Click to expand...
Click to collapse
Just boot into recovery, factory reset it, clear the Dalvik cache, format the system and install the stock GB rom or another rom. If you don't clear the Dalvik cache and wipe the system before installing roms or kernels you get bootloop problems such as this. Your phone is okay. The G2X is virtually unbrickable. It just gets indigestion form operator error when flashing roms.

ok so i factory reseted, cleared the cache and the dalvic. my phone wont read the gb stock rom, i dl unto my external card

blitzs13 said:
ok so i factory reseted, cleared the cache and the dalvic. my phone wont read the gb stock rom, i dl unto my external card
Click to expand...
Click to collapse
Did you do a Nand Backup with CWM before flashing the kernel? If so, restore the phone how it was before you mucked it up.

Pressed factory reset by accident

Now it's my turn. Pressed factory reset by accident in boot loader. Can get to TWRP but it says E: Unable to mount storage
e:Unable to mount /sdcard/TWRP/twps. when trying to read settings file. etc...
Advanced File manager in TWRP shows /sdcard/TWRP
Any ideas???? If I try to mount data in TWRP my Mac wants to initialize.
Thanks
TWRP shows internal storage 0 mb

I flashed the stock recovery, then ran it and somehow it booted right into CM11. Everything was lost, but it's working again.

Factory reset wipe everything! Including SD card.

null0seven said:
Factory reset wipe everything! Including SD card.
Click to expand...
Click to collapse
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.

808phone said:
Possibly, but how come CM11 was still on there? I think that the Boot Loader in Moonshine's factory reset is not compatible with CM11. Luckily the stock recovery fixed things for me.
Click to expand...
Click to collapse
I had the same issue, pressed by mistake factory reset in bootloader some time ago. I was pressing vol down to reach recovery, there was a slight lag and I pressed it a second time the immediately I've pressed power...so cursor has jumped 2 rows then executed. I've solved it only by flashing stock recovery and resetting to factory settings again, then flashed TWRP.
Now why you still had CM11...well not 100% sure but in TWRP when you wipe to factory the system partition is not formatted. I've paid attention once to the messages during a wipe and it was formatting data, cache, dalvik and android secure but not system. A reason can be that while flashing any ROM, the install script formats system at the beginning so theres no need to do that with factory reset.
Now I can only think that the factory reset from bootloader does the same and system is not wiped. Theoretically it is correct...system is read only especially on a stock non rooted device and resetting it to factory practically means that any trace of personal settings/aps and so on should be erased. And those are not stored on the system partition. There is also no hidden place on the phone where a recovery image of the original android OS is kept so this is not like on the laptops where you reset to factory and Windows is reinstalled from the recovery partition. My guess is that the factory reset just wipes all partitions that contain personal data and settings and leave system intact. So after a wipe and reboot is like you first start it.
You still had CM11 cause the wipe didn't format system...If anyone has a better explanation I would be glad to hear it. So From my point of view nothing went wrong and has nothing to do with the Maximus recovery or it's compatibility with CM11. It would have happen the same if you have used any other stock recovery

Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.

null0seven said:
Factory reset, resets youre phone to original settings.
Anyway, its good that the phone works.
Click to expand...
Click to collapse
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...

Rapier said:
Yes. And it is not formatting system when doing this. So any os is installed will be kept
Sent from nowhere over the air...
Click to expand...
Click to collapse
I don't want to try it again but I wonder if moonshine's factory reset is incompatible with cm11?

Dont understand what do you mean by "incompatible". The factory reset from bootloader is not the same thing as the one from a custom recovery. You shouldn't do a factory reset from bootloader regardless of the ROM you're using
Moonshine is an S-Off method, I didn't used it myself so I don't know what factory reset option is in there
Sent from nowhere over the air...

I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.

808phone said:
I never said anything about the custom recovery. If you should never use it, why is it there and why does it make the SD card not available?
Wow, HTC says you can use it here:
http://www.htc.com/us/support/htc-one-x-att/howto/313779.html
I'm sure you know something others like me don't, but I when I mean "incompatible" I mean that I don't believe that it should make the sdcard unavailable and make the phone think it has zero MB. I think what you might have missed is that I used factory reset from the custom boot loader from moonshine. I was wondering if that factory reset was compatible - that's all.
Again, it was a mistake - it's not like I chose it on purpose. Thank you for the help.
Click to expand...
Click to collapse
The reset to factory from bootloader exists because on stock ROM there's no custom recovery that has that option....so it's in bootloader. For it to work properly though, you must have the stock recovery also. If you have a custom recovery like twrp/cwm and use the wipe from bootloader it'll mess your sd cause phone is not able to perform the wipe properly with that custom recovery. That's why, in order to get back to normal you should flash back stock recovery and perform the wipe from bootloader again.
Sent from nowhere over the air...

Thank you for the clarification. It makes sense. Too bad that reset is so close to the recovery command. It's pretty weird that I didn't have to run the wipe from the stock boot loader again. It ran and rebooted the phone into CM11. Anyway, I am glad I am back to running. Thanks.

[Q] Random Reboots

No matter what rom i'm running I get random reboots. I even took the update from Verizon to 4.4.3 and still recived random reboots. Is this just me? I have also ran safe mode and get them.

Have you tried a factory reset?. If not try that. Don't do it from security settings though. Do it through fasboot. Just be sire to save anything you don't want to lose.

Yes and have tried multiple roms. IT does it not matter what rom or what settings I have.

Sounds like a complete wipe via fastboot may be your only fix. Just be sure to back up all the stuff youbwanna save cause it gonna wipe it clean. I am stock and was having same issue did the reset and everything fine now. I however forgot to make a back up lol

How do I do that? I tried the factory reset option and it took me back to TWRP

Make sure quick boot is turned off in battery settings. Then power down device. Power back on holding down volume and power. Your phone will boot to a white screen. Then use volume down to cycle to factory reset. Only thing is I'm not entirely sure what it will do to s-off and unlocked bootloader. You may want to Google that and see what it says

I've had my m8 for several weeks and never had a random reboot, that's on both stock and custom Rom. If the factory reset doesn't fix it, you may have a hardware issue

Factory reset doesn't work on a custom recovery

tjamscad said:
Factory reset doesn't work on a custom recovery
Click to expand...
Click to collapse
Better: You should not try a factory reset from settings if you have a custom recovery installed. It can lead to unintended consequences......
And why would you? That's what a recovery is for! TWRP and CWM both have the factory reset option, which basically just wipes /data (without /data/media), cache and Dalvik. And that's what you need 95% of the time. For the rest format data.

A factory reset doesnt clear everything. I have done a few and nothing ever seems to be reset. When I did it from hboot I was required to set up phone again as if it had just been powered on for the first time.

berndblb said:
Better: You should not try a factory reset from settings if you have a custom recovery installed. It can lead to unintended consequences......
And why would you? That's what a recovery is for! TWRP and CWM both have the factory reset option, which basically just wipes /data (without /data/media), cache and Dalvik. And that's what you need 95% of the time. For the rest format data.
Click to expand...
Click to collapse
For the record,twrp wipe was what I was referring to when I said factory reset. I thought about saying wipe, but was afraid of how that might be interpreted.

mdorrett said:
A factory reset doesnt clear everything. I have done a few and nothing ever seems to be reset. When I did it from hboot I was required to set up phone again as if it had just been powered on for the first time.
Click to expand...
Click to collapse
A factory reset in TWRP (at least on every version I've used) wipes /data without wiping /data/media, cache and Dalvik.
Meaning it wipes all your apps and settings without wiping your personal files, but rquiring ou to go through setup again. Just did exactly that before installing CleanROM 2.0. If you had a different result I don't know which option in TWRP you chose.....

[SOLVED] Google Apps Not Working And Recovery Refusing To Open

About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat

Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.

acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.

NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.

acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please

First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?

leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.

Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.