Hello everyone, I'm new to the Photon Q area. But anyways I flashed TWRP successfully, then SU. I then made a backup and booted to system. It worked fine. The I flashed the power menu mod. Now my phone just boots to the "Sprint logo" (yellow background) and stays there. I then recovered from my backup and it still does the same thing. I've cleared dalvik and cache. Any ideas....
kevinrocksman said:
Hello everyone, I'm new to the Photon Q area. But anyways I flashed TWRP successfully, then SU. I then made a backup and booted to system. It worked fine. The I flashed the power menu mod. Now my phone just boots to the "Sprint logo" (yellow background) and stays there. I then recovered from my backup and it still does the same thing. I've cleared dalvik and cache. Any ideas....
Click to expand...
Click to collapse
nvm, turns out my system backup was corrupt. Got it fixed. Now if I just figure a few things out I've got a few treats for you all.
Ive got the same problem but i used CWM and i tried reflashing extended power menu as well as flashing the stock power menu. I also tried flashing the stock recovery to see if i could get the phone to master reset but it says it cant find the file when i hit enter. I also have tried doing a factory data reset in CWM.
oldskoolerhatch said:
Ive got the same problem but i used CWM and i tried reflashing extended power menu as well as flashing the stock power menu. I also tried flashing the stock recovery to see if i could get the phone to master reset but it says it cant find the file when i hit enter. I also have tried doing a factory data reset in CWM.
Click to expand...
Click to collapse
Why not just restore the backup you took from before you made the power menu changes...?
You did take a backup before making those changes, yes?
arrrghhh said:
Why not just restore the backup you took from before you made the power menu changes...?
You did take a backup before making those changes, yes?
Click to expand...
Click to collapse
no i was a complete dumb *** and didnt think to back up before i started
oldskoolerhatch said:
no i was a complete dumb *** and didnt think to back up before i started
Click to expand...
Click to collapse
Do you have _any_ backups to restore?
If not, you'll probably have to find the stock stuff floating around here somewheres. I posted a system image backup from TWRP, that wasn't quite stock. I think some others posted bone stock backups.
Edit - looks like you got help in another thread... That you created... In the future, try to keep the exact same question isolated to one thread. It dilutes the community effort if you post the same question across multiple forums/threads.
Related
flashed a rom Eaglesblood 1.7, wiped cache/data, and now stuck on android bootup animation. tried to enter clockwork recovery with power+volumedown and it only goes to a "stock" android reboot if even that. Need a way to get into clockwork any way to help?
i still have the backup i made from my previous stock rooted rom in clockwork on my sd card is there a way to access that from adb or some program to flash it back on my phone?
Get into clockwordmod, goto backup and restore. Hit backup, choose your backup. Voila. Reboot.
Mister Hat said:
Get into clockwordmod, goto backup and restore. Hit backup, choose your backup. Voila. Reboot.
Click to expand...
Click to collapse
I've been trying to do that. Power+volume down. however there is no menu for clockwork mod. it just goes into a box with a arrow and the android logo. and then goes back into infinite loop. I need to get into clockwork mod is the problem. How can i do that? Is it possible with adb?
deathbyloki said:
flashed a rom Eaglesblood 1.7, wiped cache/data, and now stuck on android bootup animation. tried to enter clockwork recovery with power+volumedown and it only goes to a "stock" android reboot if even that. Need a way to get into clockwork any way to help?
Click to expand...
Click to collapse
Assuming you did nvflash recovery you should be able to get into it. If not I don't know if it will work but try to do the nvflash recovery. And if you did maybe try redoing the nvflash. MYte be worth a shot to try
How did you do that first recovery image? Maybe you "faked flashed"
Sent from my LG-P999 using XDA App
Relash the recovery with nv flash again. Boot into recovery and restore your back up. Heres the nvflash instructions and downloads if u need it http://forum.xda-developers.com/showthread.php?t=1056847 also you typed flashed eagleblood wiped cache/data. You need to wipe data wipe cache partition wipe davlik cache 3 times then flash the rom . U need too wipe before installing the rom not after. Not sure if thats what u typed ment u did
Hey I think they are right reflash CWM see if that works and silver03wrx is right you have to make sure you do all of the wiping before installing any ROM. Just like you **** first then wipe. Or at least I do. silver03wrx I have a question you said 3 times does that mean we have to wipe each one 3 times? I have only been doing it once.
Charllie
mojorisin7178 said:
Hey I think they are right reflash CWM see if that works and silver03wrx is right you have to make sure you do all of the wiping before installing any ROM. Just like you **** first then wipe. Or at least I do. silver03wrx I have a question you said 3 times does that mean we have to wipe each one 3 times? I have only been doing it once.
Charllie
Click to expand...
Click to collapse
LMFAO
Sent from my LG-P999 using xda premium
deathbyloki said:
I've been trying to do that. Power+volume down. however there is no menu for clockwork mod. it just goes into a box with a arrow and the android logo. and then goes back into infinite loop. I need to get into clockwork mod is the problem. How can i do that? Is it possible with adb?
Click to expand...
Click to collapse
You need to use nvflash to install clockworkmod recovery the proper way to this phone. This issue has been asked and answered multiple multiple multiple times.
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 a Samsung Conquer 4g and I have ran into a huge problem as the title tells itself. I tried flashing the new FC17 2.3.6 update for it and now the phone shows the first start up screen than immediately goes to clockworkmod recovery. I tried restoring a backup of the whole phone I made a couple of days ago and that still doesn't work. Than I also tried extracting the .img files from the backup and tried pushing those folders into the phone but it still doesnt work. Any help? I will also provide with any other information needed. Thanks.
itzdarockz said:
I have a Samsung Conquer 4g and I have ran into a huge problem as the title tells itself. I tried flashing the new FC17 2.3.6 update for it and now the phone shows the first start up screen than immediately goes to clockworkmod recovery. I tried restoring a backup of the whole phone I made a couple of days ago and that still doesn't work. Than I also tried extracting the .img files from the backup and tried pushing those folders into the phone but it still doesnt work. Any help? I will also provide with any other information needed. Thanks.
Click to expand...
Click to collapse
check the kernal first...is it the correct kernal for that?
do one think...got cwm
wipe data/factory reset
wipe cache
goto advanced>>wipe dalvic cache
wipe battery status...!!
I tried that but still no luck this is very odd maybe there is a file doing this?
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
please help!!!!!
hi am using a gionee e3. i changed my phone font last night using the "my font" app (not the first time), i was prompted to reboot my device, the device comes on displaying the gionee smartphone screen but doesn't boot any further than this.help needed
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Gilbert_vanguard said:
did you make a cwm backup? if yes, then go to recovery and restore. if no, then m sorry my friend you have flash stock, or another ROM through cwm
Click to expand...
Click to collapse
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
mcgrabowski said:
Sometimes if you get stuck on the boot logo and it never fully boots, simply clearing the cache and dalvik cache in CWM or TWRP can fix it. (Might throw in fixing permissions as well.)
Click to expand...
Click to collapse
yup that's one possible solution. but usually bootloop spells doom
thanks guys
thanks guys, apparently it was doom afterall, nothing worked. had to reinstall the os. lost everything