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
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.
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
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
Hi folks.
I'm facing a really weird problem. My friend's N5 doesn't want to boot with Lollipop, it shows the boot animation, but nothing happens, more than an hour and nothing.
I tried to flash back to kit kat. It indeed booted, but just to say that the camera and gallery has stopped, and gallery couldn't find any storage. When I go to the storage section in the settings, it doesn't show the pictures, music and other sources, just available space, cache and apps.
I tried to flash a custom rom to, but they all give me bootloops.
I never had this problems with my n4, so i don't know what to do anymore.
Any solutions?
Flash lollipop with fastboot. Then boot into the stock recovery and do a factory reset. Everything will be fine.
Sent from my Nexus 9 using XDA Free mobile app
I've already tried that, didn't work :crying:
Floydroider said:
I've already tried that, didn't work :crying:
Click to expand...
Click to collapse
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
_MetalHead_ said:
You flashed the factory image with FASTBOOT and still had this problem? You sure?
Click to expand...
Click to collapse
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Floydroider said:
Yes, i'm absolutely sure. I'm used to use fastboot to flash my Nexus 4. I downloaded the proper factory image from Google and flashed it using both flash-all.bat and manual input in the cmd.
I tried to erase the partitions, format using TWRP, and install a custom ROM.
With twrp I can see the the internal storage partition, and even mount it to access by computer. But when the device boots, it just can't see the partition.
I put a song in the internal storage with twrp just to test, and when the device booted it didnt recognize the song, but when I got back to recovery, it was still there.
It seens that the problem is in the internal storage, but I don't know how to fix, and what could have caused it.
* Sorry, my english is bad :/
Click to expand...
Click to collapse
Try wiping cache in TWRP.
Wakamatsu said:
Hmm. Try fastboot formatting all the partitions and then flashing the image again. Can't hurt.
Click to expand...
Click to collapse
Tried that. I first used fastboot erase, didn't work, and then I use twrp to format to another fs. After that, I flashed the image again. Still nothing.
_MetalHead_ said:
Try wiping cache in TWRP.
Click to expand...
Click to collapse
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Now I flashed kitkat image again. It booted but with the storage problem. Then I update via notification, and it stuck in lollipop boot animation.
I will let it booting through the night. Or it boots after a couple of hours or the battery dies.
Floydroider said:
I have wiped everything lots of times.
It's the first time I have a hard time trying to fix an android phone...
Click to expand...
Click to collapse
Yeah this seems kinda crazy. Usually when stuff gets messed up like this a factory image clears it up. In your case, I honestly don't know what else to recommend. Sorry I can't be of more help.
Replace internal storage, nothing else you can do
Nothing worked in the end. My friend will send the phone to tech support.
Thank you guys for the help.
:good:
So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)
Hello,
Yes, if you made a nandroid backup in recovery then restoring that nandroid should fix you.
To better assist you, your thread will be moved to your device forum linked below.
http://forum.xda-developers.com/blaze-4g/general
The experts there may be able to help you with any other questions you have. Good luck.
digfive3 said:
So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)
Click to expand...
Click to collapse
No, you are not bricked. If you are able to access recovery, think of it as a second chance . Since you have recovery available, have you tried transferring a ROM to it? If that is what you were aiming for, I recommend transferring TWRP onto it, flashing it, reboot to recovery, and proceed to flashing a ROM.
xWolf13 said:
No, you are not bricked. If you are able to access recovery, think of it as a second chance . Since you have recovery available, have you tried transferring a ROM to it? If that is what you were aiming for, I recommend transferring TWRP onto it, flashing it, reboot to recovery, and proceed to flashing a ROM.
Click to expand...
Click to collapse
Can I just use an SD card to do that or will I need to find a way to get into download mode?
digfive3 said:
Can I just use an SD card to do that or will I need to find a way to get into download mode?
Click to expand...
Click to collapse
That works also.
digfive3 said:
Can I just use an SD card to do that or will I need to find a way to get into download mode?
Click to expand...
Click to collapse
Yes, download your ROM and Gapps package, place the zips on your external sdcard, boot to recovery, flash the ROM zip then flash the Gapps zip, do the wipes(factory reset, wipe cache, wipe dalvik cache), reboot.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Yes, download your ROM and Gapps package, place the zips on your external sdcard, boot to recovery, flash the ROM zip then flash the Gapps zip, do the wipes(factory reset, wipe cache, wipe dalvik cache), reboot.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Could you link me to a rom for my device? I'm having a hard time finding an actual ZIP file, just a bunch of .IMG files.
digfive3 said:
Could you link me to a rom for my device? I'm having a hard time finding an actual ZIP file, just a bunch of .IMG files.
Click to expand...
Click to collapse
Do a Google search for "custom ROMs for SGH-T769" that should give some results if anything exists.
Sent from my SCH-I535 using Tapatalk
digfive3 said:
So I believe I've bricked my SGH-T769, at least, whenever I attempt to turn it on, I am greeted with the standard Samsung splash-screen and can never proceed past it. I can still boot into recovery mode and i wanted to know if I could use the "restore from sdcard01" option to fix this. I have a removable SDCard and the ability to add files to it via- cardreader. Can I even get system restore files?
P.S. I cleared EVERYTHING... not JUST the harddrive, dalvik, and caches, i mean... i cleared EVERYTHING which was obviously a mistake because that's when the problems came. I believe I may have actually cleared the system files themselves...
:silly:
Oddly enough, CWM Recovery is still alive and well, but I cannot access DOWNLOAD MODE
(I KNOW HOW TO ACCESS DOWNLOAD MODE BUT IT IS JUST BROKEN WITH THIS PHONE)
Click to expand...
Click to collapse
By the way, there is a device called a USB jig that is used to force a device into download mode, you can get one for $4-5 on eBay or you can make your own by cutting the end off of an old micro USB cord and using a 300k resistor(or any combination of resistors that equal but do not exceed 300k), there are videos on YouTube that show how to do that. That should boot you to download mode so you can restore the device to stock.
Sent from my SCH-I535 using Tapatalk