Related
I have Iced 1.1.4, by accident I wiped all my apps and data when upgrading to it so I wanna go back to my backup of nandroid before to get all my stuff back.
I wiped cache and data and tried to restore the backup, but when I reboot it stays stuck on the MyTouch 4G splash screen. I've searched the forums and haven't found much of a solution for this. Any help would be great, thanks.
BTW battery is at 100%
try giving it a few minutes to load up
yes, I would recommend giving it a few minutes before loading up. Typcially on first boot it can take a few minutes. Only issue I have ever ran into with nandroid is when I renamed it and left a space, had to rename it again and was fine.
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
VillaCastana321 said:
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
Maybe it all started w/ a bad Valhalla Final or Lightning Zap download, check the md5, also if u r trying to flash ics I would recommend using a one-click first (It just seems like it always works better for me when I do that)... and I assume u know about the kernel version b4 flashing ics, right?
Yeah. Seems like I do have to do a one click. Everytime I go to make a call on pics it just ring once and then automatically hangs up
Sent from my SGH-T959V using xda premium
ya I would try that 1st
(Just wrote a detailed post and when I went to post, it said I wasn't logged in and erased it...will give a quick run down and can supply more detail where needed as I work through fixing my phone)
Stuck on the white htc splash screen is my most recent problem. Sometimes it gets by that but then boots into recovery. I think bananagranola has the solution in their sig to flash a boot.img. and think I'm comfortable with how to do that, just need to find that file (in the ROM zip?)
What led up to this.
Successfully unlocked and flashed to CM7 back in late Jan/early Feb.
Started experiencing random freezing about two weeks ago.
A week later (last weekend) flashed Jellybean (R10). Worked great for a couple hours then started having the same random freezes.
If things froze I'd have to remove the battery and reboot. After a day or two of this though it'd get to the point that even that would leave me on a frozen jellybean boot animation. So I'd go and factory/data reset in CWM Recovery, wipe cache, wipe Dalvik then reflash the ROM. and I'd be good for a little while more.
Tried flashing back to CM7 but Recovery didn't like the file (it has a good MD5 when checked) Had tried my restore point from early Feb before to no avail, so decided this morning to try other restore points from the last few weeks, right before and after switching to JellyBean. They got further, the first step is something with boot then something with system. It failed on the system part. OK...so I wiped and reflashed jellybean again, and now I am to my splash screen freezes.
I should have asked for help much earlier (lesson learned!) but here I am asking now...what's the first step.
Do I test out and see if I hang on the splash screen again. I haven't turned the phone on in about an hour. Worried of screwing it up more.
Thanks all.
TL;DR Believe I'm stuck on splash screen and know solution to that. Have had phone flashed with new ROM with no prob for months, recently freezing, regardless of ROM. Hoping for advice on getting things working again, starting with whether fixing the splash screen thing first is where to start
splash screen issue seems fixed
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
irishpanther said:
Seems I fixed the issue with the splash screen. Booted into recovery and reflashed the Jellytime ROM.
Got all the way into Android. after a few minutes I rebooted into recovery and loaded the gapps. Rebooted, it updated apps (not downloading, the popup that says it updates) and was setting up my account when it froze again as I entered a wifi password. Pulled the battery and tried again, got through that and all the way to the lock screen. froze shortly after that.
Now when I reboot, it locks on the boot animation. The Jellytime screen flashes the brightness as few times as things are loading. after the 5th or 6th flash it just sits there frozen.
a new SD card is in the mail, so I may post again when that arrives to see what I can do with an almost clean slate.
Click to expand...
Click to collapse
That doesn't sound like an sdcard problem. Are you full wiping?
bananagranola said:
That doesn't sound like an sdcard problem. Are you full wiping?
Click to expand...
Click to collapse
I'm wiping data/factory reset and cache as well as the dalvik cache.
The steps to flashing a ROM by sashank at link mention to format /boot and /system. I didn't specifically do those...but don't see the option for /boot in any menus I've checked.
A week or so ago I was beginning to suspect there was an issue with the memory but I never found the right search terms to find out how to do a memtest if that's what would have found any problems. Yesterday I did come across some discussion of a corrupt partition/bad chips in some HTC devices. I followed the directions there and through adb ran dmesg | grep mmc0 and the output was similar to the 'normal' one given and showed none of the messages they claimed to indicate a bad chip.
I'm not too concerned with any data from the phone...I backed all that up long ago and the rest restores from my google account. So if I getting things running would normally raise concerns of lost data, that's not an issue for me.
Thanks for taking the time to read. I try to be brief...but don't want to leave anything out.
Wanted to update here before trying to start a new thread and clogging up the board. The title of this thread is not up to date though.
I can hboot just fine and boot into recovery just fine. My phone is unlocked and rooted, ENG S-OFF from when I used AAHK quite a while ago.
When trying to navigate from menu to menu in Recovery I will get the following error messages (best I remember from last time I was in there, I've let the phone be for the last 2-3 days now)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
This doesn't show up at first though, only after I do a Wipe Data/Factory Reset. And if I understand correctly, that wipes /cache so maybe that's causing these errors?
Anyway, after wiping the dalvik cache I can flash a ROM, I've been using Jellytime, I haven't been able to rollback to CM7, not sure why not.
Jellytime will run though...at first! the first couple of boots I can get in and get through registering my google account and have it begin restoring apps if i make that selection. The time I have to work on the phone before it freezes gets shorter and shorter though. I have to remove the battery to get it to reboot. Eventually I am left with the phone hung during the boot animation. I've left it for over an hour before...it's definitely hung there.
So my reading leads me to believe corrupt partitions. I'm not finding a lot on what I should do to reformat and maybe repartition or whatever I may need to do to recover a functioning phone. I don't care about any data on the phone. I just want to get things working again. I ended up getting a new SD card during all this that arrived earlier. If I can get my phone working, I'd prefer to use that from here on out too. I can use the adb in recovery mode just fine if that's necessary to rejigger things to work.
Can anyone help reset my partitions, if that's what this issue seems to be? If not...any ideas?
Thanks.
Recovery and version?
bananagranola said:
Recovery and version?
Click to expand...
Click to collapse
ClockworkMod Recovery v5.0.2.0
Full wipe?
bananagranola said:
Full wipe?
Click to expand...
Click to collapse
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
irishpanther said:
Yes. Everytime I've flashed, I've followed:
wipe data/factory resent
wipe cache
wipe dalvik cache
unless there's more I can do.
Click to expand...
Click to collapse
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
OK, I'll give this a try. The issue with the freezing is why I moved from CM7 though (which had been stable for four months) so it's reproduced itself in different ROMS. I'll post back once I give this a try. Thanks.
bananagranola said:
Maybe try a different ROM, preferably a stock-ish ARHD or similar ROM?
Click to expand...
Click to collapse
I gave Android Revolution a shot. During the flash it gave a message which might also be why I wasn't able to flash back to CM7. The MD5 did verify.
Code:
assert failed:write_raw_image("/tmp/boot.img","boot")
When I went to reboot, I ended up in Jellytime. Of course I had to sign back in to google apps and those things were reset from the dalvik wipe. Shortly there after the phone froze.
On reboot I tried a logcat. Didn't get it right from the start (you can send the command during the boot animation if I read correctly) but captured the failure of things. It's back around the 09:02 portion of the log. To my eyes it looks similar to others I've collected. Especially the message
Code:
Fatal signal 7 (SIGBUS)
though I haven't been able to figure out much about that, or identify what it is before that that could give another clue as to what is screwy since that's maybe (Probably?) related to the flashing issues.
Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
I downloaded TWRP 2.8.6.0 and installed it. Then I downloaded cm-12.1-20150405-UNOFFICIAL-xt897.zip ...put both on the SD card...went into TWRP, wiped the system, installed CM12.1 and it stayed at the boot logo for about 20 minutes. I rebooted, wiped again, and now I am stuck at the warning screen about the bootloader being unlocked....can't get into the phone OS at all....
Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).
arrrghhh said:
Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).
Click to expand...
Click to collapse
I didn't do a backup due to lack of space available.....plus i've had plenty of experience with flashing phones/ROMS....this one was supposed to be so easy.....but its proven to be very difficult.....I did flash another ROM on it and its at the loading screen......never seen a phone take so long to load.....sadly, I was wanting Lollipop and this one that I'm loading up now is KitKat......been loading for over 10 minutes now.......I have two of these phones, I guess I could do a backup of the other one and restore onto this phone....not sure if that will work......
Same problem here and I did restore a backup and it wouldn't boot either anymore
4218kris said:
Same problem here and I did restore a backup and it wouldn't boot either anymore
Click to expand...
Click to collapse
There's always RSDLite as a last resort.
My cousin flashed a nightly early this week and now it's stuck in a bootloop. I tried flashing latest recovery en formatting /repairing data and internal storage. But I always get an error on format DATA and trying to repair Internal Storage is not even an option.
Next I tried CM recovery. Nada, same effect. Flashing is possible, it even boots, but then it also loops.
Just flashed using RSD LITE 6.1.5 icw asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip. Still, this baby won't boot!
So unless someone comes with a fix... This baby is dead. Something very wrong with internal memory I guess.
I finally got it to boot, I do get the error on formatting data too but try a couple times and it seems to work. It always has an error the first try. I also flash the ROM with data and cache on ext4 then changed it after flash and after first boot it will factory reset the phone when changing from ext4 to f2fs. That's what I did and it worked for me.
Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.
Die Bruine said:
Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.
Click to expand...
Click to collapse
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.
Die Bruine said:
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.
Click to expand...
Click to collapse
Ok, just checking. Did you wipe data and cache when doing that?
Sent from my SM-T320 using XDA Free mobile app
Yes I did. I would like to try 4218kris' suggestion. But without touch input that's not an option. Switched fronts to be sure, digitizer is ok. I'll leave this one for what it is. Still two users left in te family with XT897. When those break down I won't be replacig them.