This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up
Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?
what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone
i cleared up the memory, internal and external. the stupid ROM is still broken
if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?
Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.
i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.
Redownload the Rom. Then follow THIS GUIDE when you flash.
VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine
Related
Ok, So i rooted my T-mobile G2x 2.3.3 and there were difficulties when i flashed the Cyanogen 7mod. The Rom worked but the only default was i didnt get data. Like i couldnt even get Edge. The only way to use internet and stuff was through wifi. SO then i reflashed it thinking it was a bad flash. But when i reflash through rom manager it gives me the option to downoad with google apps. so i clicked that option. It downloaded fine but on the reboot it stayed stuck on the 2nd LG screen. Am i bricked or if anyone can help id appreciate it alot.
U can't do it via rom manager. U have to flash recovery using nv flash, then u can try to flash custom rom. Remeber to wipe data and format system before flashing any rom.
U r not bricked yet
Check here to nv flash the cwm
http://forum.xda-developers.com/showthread.php?p=13330067
Sent from my LG-P999 using xda premium
Did you flash CWM via NV Flash. If not, do that. Then boot into recovery by holding down the power + volume down keys until you get the second boot logo. Then wipe the dalvik cache and the regular cache. That is usually why a phone refuses to boot.
Also, if your phone turns on it is not bricked. Bricked means when you press the power button nothing happens at all. You can be soft-bricked like you are, but it can be easily fixed. Nothing to panic about.
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
iSpooNz said:
I did all of that im sorry if i gave you info wrong. Like i cant do anything it turns on but goes to the first LG screen then goes to the new LG screen with the blue streaks and it stays there. Then when i try to go into CWR it shows the LG with a blue and black loading bar below then shows as if its loading something then it just goes back to the blue LG screen and im stuck there.
Click to expand...
Click to collapse
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
Ok so from CWM do i wipe everything?
jboxer said:
You have stock recovery on the recovery partition, not CWM. You MUST flash CWM onto the physical recovery partition using NVFlash with the One Click flasher. You used Rom Manager and that doesn't install CWM onto the recovery partition. Once you have CWM properly installed you can enter recovery and revive your phone.
Click to expand...
Click to collapse
@OP, this is is correct. Use tga gunmann's nvflash tool from the development section. The process is super easy. Just make sure to follow his instructions closely. Just fyi, most people get errors during the nvflash process because they don't install the apx drivers appropriately, so take your time and read the instructions carefully.
iSpooNz said:
Ok so from CWM do i wipe everything?
Click to expand...
Click to collapse
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
phburks said:
Start off by wiping cache and then go to Advanced and wipe dalvik cache. If you still can't boot after that then try a full factory reset.
Just remember the first boot after wiping dalvik cache can take several minutes as android rebuilds the dalvik cache. All subsequent reboots will be MUCH faster.
Click to expand...
Click to collapse
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
iSpooNz said:
Ok so i ended up having to do a factory reset yet im still getting the same results. Im still stuck on the 2nd lg screen when booting up
Click to expand...
Click to collapse
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
phburks said:
Boot back into cwm, go to Mounts and Storage, format /system and then reflash your rom.
Click to expand...
Click to collapse
Ok ill try that.
jboxer said:
Did you do as phburks said and go into advanced and wipe the Dalvik Cache. Most issues of not booting are related to the Dalvik Cache not being wiped after flashing a new rom. That is essential to getting your phone to boot again. A factory reset DOES NOT clear the Dalvik Cache.
Click to expand...
Click to collapse
Yea i wiped Dalvik cahce and the same result came up. So i factory resetted and same result. So im going to try what phburks said and see what happens.
Im still stuck in the second LG screen :/
iSpooNz said:
Im still stuck in the second LG screen :/
Click to expand...
Click to collapse
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
phburks said:
Could be a bad download. I'd try downloading again. Use your computer to download again and save it to your microsd card. Then reinsert the sdcard, boot back into cwm and try again.
Click to expand...
Click to collapse
download the rom right?
iSpooNz said:
download the rom right?
Click to expand...
Click to collapse
Yea the rom. Is it cm7 that you're wanting to flash?
phburks said:
Yea the rom. Is it cm7 that you're wanting to flash?
Click to expand...
Click to collapse
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
phburks said:
The reason I ask is that with cm7 you have to flash 2 separate zip files. First you flash the actual cm7 zip which installs the rom and then you flash the gapps zip which installs the Google apps (market, gmail, etc). Make sure you have both on your sdcard and then flash the rom first and gapps second.
Click to expand...
Click to collapse
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
iSpooNz said:
Im glad you brought that up because when i first flashed Cyanogen i did also flash gapps but after i flashed gapps thats when i wouldnt get data. Do you know the reason for this? or was it could have been another bad flash?
Click to expand...
Click to collapse
Not sure. I'd just play it safe, re-download both, wipe data, and reflash both. Sometimes its hard to determine which step went wrong and its best and quicker to just start with a clean slate and redo everything.
I wont be able to post for a while so good luck.
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
Click to expand...
Click to collapse
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
leblvin said:
There is no way you simply wiped cache and dalvik. That doesn't even come close to touching your IMEI.
Why did you go to clear your cache / dalvik in the first place? Describe anything you did in terms of installing apps, flashing, wiping, etc.
Click to expand...
Click to collapse
All I did was flash a zip to change the dpi of my navbar. I've flashed the same zip a couple times before. Wiped cache + dalvik and it hung up for a while, screen went black for 5 minutes then the phone rebooted into its current state. I realize that wiping the caches doesn't touch the IMEI or anything like that, but what if the version of TWRP I have is buggy?
So knowing that yes, that is all I did, is there any way to fix it?
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Always run the very recovery latest version.
a hammerhead wrote this.
Might be worth backing up your EFS partition to be on the safe side!
Nandroid backup is your best friend
beekay201 said:
Always run the very recovery latest version.
a hammerhead wrote this.
Click to expand...
Click to collapse
Yup, didnt bother to check before.
EddyOS said:
Might be worth backing up your EFS partition to be on the safe side!
Click to expand...
Click to collapse
Agreed. First thing I'm gonna do when I get home from work.
gd6noob said:
Nandroid backup is your best friend
Click to expand...
Click to collapse
I have a recent nandroid. What good is it though if recovery can't see my storage where the nandroid was saved?
Sent from my Moto X
_MetalHead_ said:
After a bit of googling I got it fixed.
Click to expand...
Click to collapse
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
GldRush98 said:
Well, whatever you do, don't share your find here in case someone else ever has the same problem.
Click to expand...
Click to collapse
I did share it. Read the rest of the post you quoted. Derp.
Sent from my Moto X
_MetalHead_ said:
lApparently sometimes TWRP will cause some havok with the partitions when wiping cache
Click to expand...
Click to collapse
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
rootSU said:
I don't know about you, but this is just what I look for in a recovery
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Click to expand...
Click to collapse
It's a TWRP exclusive feature.
_MetalHead_ said:
After a bit of googling I got it fixed. Apparently sometimes TWRP will cause some havok with the partitions when wiping cache. I just updated to the latest TWRP, wiped the cache again and everything came back up. Weird.
Click to expand...
Click to collapse
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
reynwrap582 said:
Big thank you for this, I thought I was boned. I was trying to flash 4.4.1 but forgot that I had modified the screen density in the build.prop and so I got an error, tried to wipe the cache, thought it had hung up, got impatient and VERY stupid and forced the phone to reboot. SDCard was entirely inaccessible, couldn't connect to AT&T, everything was screwed up and everything I could find told me that wiping everything back to stop and losing the data was my only option. I had a week-old TiBu on my dropbox, which isn't bad but not great either. Nandroid, of course, inaccessible along with the SDcard. Your trick of updating TWRP (I had 2.6.3.2, latest is 2.6.3.4) and then wiping the cache again worked perfectly.
To anyone who comes across this, here's a quick overview:
1. Download the latest TWRP at http://teamw.in/project/twrp2/205
2. Boot your phone into Fastboot mode (Vol Down + Power from off, I think...worked for me)
3. Make sure your phone is plugged in via USB.
4. Open a command prompt in the folder you put TWRP in (ADB needed, obviously), type:
fastboot flash recovery imagename.img
For example:
fastboot flash recovery openrecovery-twrp-2.6.3.4-hammerhead.img
5. Only took a couple seconds until it was finished. Used the volume buttons to highlight Restart Recovery, hit power to reboot into recovery.
Wipe > Advanced Wipe, wipe what you need to wipe, viola, it was working at this point for me. Rebooted the phone, everything's back to normal. (it went through the "Optimizing apps" things on boot-up which took a few minutes, but everything is where I left it).
Click to expand...
Click to collapse
Yeah man, I was certain I was gonna need a new phone. Glad this helped you. I'm going to update the OP with a link to your post so more inexperienced users can benefit. Thanks for typing it out.
_MetalHead_ said:
So I just wiped my cache and dalvik in TWRP and now I have no radio, no IMEI, no storage.. I think it borked my partitions. Tried flashing the factory image to no avail. It failed on the radio and I still have no storage.
Is there any way to recover from this?
EDIT: I was able to fix it as easily as I caused it. Check the 4th post. More detailed instructions on the 3rd post of page 2.
Click to expand...
Click to collapse
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
MrGriffdude said:
I remember you from the HTC one forums! Figures you already messed up your Nexus 5... Lol
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Hey now, it wasn't my fault! Lol
Sent from my Nexus 5 using XDA Premium 4 mobile app
So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?
CarsonM135 said:
So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?
Click to expand...
Click to collapse
You Should flash the stock firmware through Odin . Your data will not be erased .
Don't forget to press the thanks button :good::good::good:
Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.
Lol
wolfclan68 said:
Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.
Click to expand...
Click to collapse
Flashing to stock always fix bugs that wiping can't solve
Because flashing to stock will restores the original firmware :good:
Sent from Gallifrey using TARDIS
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.