Related
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
Hey guys, I flashed the mod located here:
http://forum.xda-developers.com/showthread.php?t=1692233&page=9
It mentioned that it would work on any Sense 4.0 Rom.
i'm running CleanROM 3.0 SE.
Since flashing, I'll get to the HTC boot logo, then the screen goes black. The backlight is on, and the softkeys vibrate when pressed, but the volume rocker doesn't work. The power button seems to turn the display on and off though.
I tried:
Wiping cache
Wiping dalvik
Fixing permissions
No luck.
Any ideas?
Can you get into recovery? It said to make a nandroid before flashing, i hope you did so you can restore.
Me being dumb, no I didn't make a nandroid backup. I got lost in the whole confidence thing.
I can access recovery though, it's all the screen will display other than the HTC logo.
I have a nandroid running now. I was thinking of making the backup, performing a factory reset, then installing TiBu and using the "Extract from Nandroid" function to get what I need out of it, unless you have any other ideas?
ADB isn't working for me, I read somewhere that CWM on the HOX had ADB working, so I can't do much on that end...
I used twrp. Mounted the sd to my pc. Then moved over a tomorrow and installed.
So delete the system and cache and dalvik cache and install the rom. Make sure you unmount the storage when you move the files
Sent from my HTC One X using xda premium
Heres my problem...
I don't have the CleanROM zip on my phone anymore. It left me with like 20mb of storage, so I had to get rid of it.
If I flashed twrp using fastboot, would it still allow me to access it and then mount USB?
Hi
Just signed up.
Bit of background.
I installed twrp it was successful.
After wiping the data, and rebooting my phones camera wasnt working and there I couldnt save any apn on the phone basically cant use the phone.
I connected it back to my computer, its shows it a nexus but it shows theres 0 files on it.
I tried using adb but it wont find any device.
Can anybody give me some advice please.
Thanks in advances.
globy
globy518 said:
Hi
Just signed up.
Bit of background.
I installed twrp it was successful.
After wiping the data, and rebooting my phones camera wasnt working and there I couldnt save any apn on the phone basically cant use the phone.
I connected it back to my computer, its shows it a nexus but it shows theres 0 files on it.
I tried using adb but it wont find any device.
Can anybody give me some advice please.
Thanks in advances.
globy
Click to expand...
Click to collapse
Why haven`t you made a nandroid backup first after you flashed TWRP? Have you cleared the cache after flashing TWRP: fastboot erase cache in adb? If nothing else works reflash the stock recovery and clear cache afterwards or reflash the factory image as a last resort.
gee2012 said:
Why haven`t you made a nandroid backup first after you flashed TWRP? Have you cleared the cache after flashing TWRP: fastboot erase cache in adb? If nothing else works reflash the stock recovery and clear cache afterwards or reflash the factory image as a last resort.
Click to expand...
Click to collapse
I am new to it all.
I found the device using adb, but yeah I dont have a back up of the rom.
I downloaded the stock rom in the rom section but adb gave
archive does not contain android-info.txt
archive does not contain android-product.txt
error: update package has no android-info.txt or product.txt
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
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
xsteven77x said:
Did you flash the recovery in the twrp app? Reason I asked is cause the app wanted to flash mine to the wrong partition.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did it through fastboot
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Rushing said:
Use fastboot erase and fastboot format <partition>
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not real familiar with using fastboot, when I put this recovery on and unlocked the phone was the first time I ever used it. So how would I go about doing that and what does it do
Clockworkmod
Clockworkmod recovery is available for the M8 but it is not the official version. Link: http://forum.xda-developers.com/showthread.php?t=2708520
reaper420 said:
I have recently been having problems with TWRP, when I factory reset to install a new rom it rests just fine then when I go to install the new rom the phone reboots and when it has restarted it hasn't actually wiped anything. Is there a better option for a recovery everyone would recommend?
Click to expand...
Click to collapse
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
berndblb said:
TWRP works just fine here. Which version do you have installed? Sure you flashed TWRP for the M8???
And what do you mean with "hasn't wiped anything"?
You do a factory wipe (default under Wipe menu) and when you boot your apps are still there, you don't have to go through setup?
After performing a factory wipe, go to Advanced and save the recovery log. Post it here.
Click to expand...
Click to collapse
Yeah it doesn't wipe anything the phone restarts and all my apps and their data is still intact. I just finished recovering from a bad situation. I flashed philz touch recovery using flashify and when I went to the recovey to do a backup the screen went black and booted staight into the hboot screen, every time I tried to reboot the phone it would send me to the hboot screen. I finally got twrp back by fasboot from my computer it was the newest twrp I got to flash I believe 2.7.1.0 I tried to restore a backup but all it would was restore the system and stop when it got to system data. I even tried flashing a new rom and that failed also. I then installed the other twrp 2.7.0.2 because I read most people are still ueing it because of problems with theother one. The phone still wouldn't boot or flash a rom but I got the restore to work by choosing not to restore data after rebooting two or three times the phone finally rebooted and all my apps and their data were still the even though I tried to install and new rom three or four times. Im a little worried now about trying to flash anything now. Im not new to android but my last phone was rock solid and I never had to deal with this many head aches. Thanks for any insite you can offer and sorry for such a long post
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
reaper420 said:
https://docs.google.com/file/d/0B620epsnenvUMlB4MkRiSUpFd2c/edit?usp=docslist_api
here is this recovery log from the last time I tried to do a factory reset.
Click to expand...
Click to collapse
That file downloads as 0 kb
QUOTE=berndblb;54407730]That file downloads as 0 kb [/QUOTE]
I tried a reset again (which didn't work) then I tried for a log and the phone just reboots the second I touch the slider to make a log
ok I can get a log if I dont do anything else so I have a log before the attempt to factory reset but I can't get one after I try to reset. Will that do any good
https://docs.google.com/file/d/0B620epsnenvUeER0aERrYlRSUUU/edit?usp=docslist_api
RUU back to stock using the thread in the development forum. At the end of following the RUU instructions it gives you the option you flash a recovery. Select yes and flash twrp