I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Zerox12 said:
I went ahead and flashed XTRSense 4.6 today after backing up my previous install from 4.0.6 (Or 4.1, can't remember) and after starting the process of restoring everything (And running the cache2cache script) I decided to restore my previous version because my texts didn't transfer over even though I used titanium backup on seemingly every messaging component. Every time I try to restore any nandroid backup or flash 4.6 again it fails on the writing boot - "Error while flashing boot image". So now every time I try to reboot it gets stuck on the androids, but I can still access recovery thank god.
How do I go about fixing this? I assume that since I can still access recovery that I'm not totally screwed, but I'm at a loss on how to fix this. Also, I am on ClockworkMod Recovery v2.5.0.1. I really should have restored Amon_RA when I had a chance.
Click to expand...
Click to collapse
Clockwork
10 chars
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Zerox12 said:
If you're implying 10 character limit, I tried renaming it and still no dice.
The error when installing a new ROM is :
E:Can't symlink /system/bin/bugreport
E: Failure at line 22:
symlink dumpstate SYSTEM:bin/bugreport
Installation aborted
Click to expand...
Click to collapse
He is saying to install the Clockwork recovery in place of Amon Ra.
The 10 character thing is a limit to this forum - each post has to be at least 10 characters long. "clockwork" has only 9...
Well then that made no sense because I said in my first post that I am running clockwork recovery.
he us saying clockwork is the problem. many eris users have had many issues with clockwork.
amons ra FTW
Same problem except...
I have an EVO and tried to return it to stock condition prior to return. I can not get off of the Hboot screen, except into recovery. I have several "nandroid copies" on my SD card but none of them will load. I an getting the same "error while writing boot image" can you tell me step by step what to do?
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Zerox12 said:
Well the Verizon RUU finally killed the damn thing. Won't turn on, no charging light. Hopefully my insurance plan through best buy will cover it.
Click to expand...
Click to collapse
Repeat after me:
"I don't know what happened. I was charging it while I slept overnight, when I woke up the charge LED was off and the phone will not turn on. Yes, I tried charging it through both the charger and just the usb connected to a computer. No it hasn't worked at all since."
Also clockwork for Eris bricks phones. People need to stop friggin using it.
Related
Something went wrong during an ODIN revert to stock, and now when I plug in the phone to the computer or wall it shows the battery charge image for a few seconds, then it says the "Samsung Vibrant" splash and goes straight into recovery mode. I've tried holding down the volume keys, adb doesn't recognize the device. IDK wtf to do. Any help would be so appreciated I'll paypal the person a six pack that can help me fix this.
When it goes into recovery mode it says...
Movi_check Start...!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed!!...
Movi_checking done!..
E:Can't mount /dev/block/stl11
(invalid argument)
E:Can't mount /dev/block/stl11
(invalid argument)
did you try holding down volume up/down, and just plugging it into your computer?( so you can get into download mode)
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
red96turbols said:
So I just got off the phone with Tech Support, luckily I'm still under warranty and my recovery screen says "Android System Recovery" and not ClockworkMod Recovery. They went through the "Master Reset" and that didn't work, obviously, because I tried that. I also tried every other thread to get into download mode and Odin the original rom/kernel/recovery to no avail. They agreed to send me a new phone free of charge, added on the insurance and shipping is now free. Luckily my girlfriend didn't tell them what really went down haha. "Oh well he rooted his phone and then tried to un-root it and ended up turning it into a paper weight." So now I just sit and wait. Next time I'm not using any other outside write ups to try and reflash a recovery on the vibrant. After I get the OTA (if it ever comes) I'll root it again just to remove the bloatware like I did the first time. But with Clockwork you can't get the OTA, or so it said, so I'll just be patient and wait it out. To anyone else who is stuck in recovery and can't get it into download mode, or flashed the euro version, just call T-Mo tech support and say you downloaded an app and rebooted and voila stuck in recovery. On the downside, I have to wait 5-7 business days (not including weekends or holidays though) for my new one in the mail. So let this be a lesson learned to everyone, read read read and if all else fails, lie.
Its not as easy doing things on the Vibrant as it was with the good old Gangster 1 (G1).
Also, I only tried this because Rom Manager said I still had ClockworkMod Recovery instead of the stock recovery after I did the proper forum.xda-developers.com/showthread.php?t=734475, You don't need to flash the root update as the CSC, I guess there could be a non-root update.zip to use, but There was a guide I followed the first time that only used the PIT and PDA files, which put it back to stock but still had ClockworkMod Recovery on it. If it didn't, Rom Manager was lying to me.
Click to expand...
Click to collapse
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
wildklymr said:
Rom manager doesnt replace samsungs recovery. There is an update.zip that is placed in your root that allows you to get to clockwork recovery by simply reinstalling packages in samsung recovery. Clockwork recovery may still be flashed, but if you remove or replace that update.zip, the only way otherwise to get to it would be through rom manager. Which obviously isnt an option for you.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Did you try to flash 2.2 by any chance? Easy way to fox your problem is just adb reboot. It will boot up your phone past the recovery screen, and then you can use odin to get back to stock.
Sent from my Samsung Vibrant
red96turbols said:
Dang. Because when I opened CW it said "Current Recovery: ClockworkMod Recover 4.x.x.x, last version: ClockworkMod Recovery x.x.x." So I guess CW wasn't even on there, so I bricked it for no reason. If I just removed the update.zip it would have just been fine? Because it kept saying "You can't receive the OTA with your current ROM, please contact ROM author." Which is why I decided to reflash to stock un-rooted rom. I had also had a 6 pack and 2 jager bombs so hahaha fsck it. I'm getting a new one and will read when I'm un-ability impaired. Thanks for the note though.... but I also renamed the update.zip to 2.1rootupdate.zip, would that matter to CW or not? Because it kept saying no matter how I reflashed that CWR was still on there...
Click to expand...
Click to collapse
There is no updated rom available. That function of rom manager is currently unused by vibrant devs. It allows them to make updates to roms and streamline the process, but they simply move on to the next rom. Renaming the update.zip that is used to root to whatever it is is ok for cw recovery, but once you have clockwork recovery flashed since it doesnt replace samsung recovery. When something goes wrong you need its update.zip it puts in root to stay right where it is. By reinstalling packages in samsung recovery is the only way to get to clockwork recovery when you cant load up the phone. If that update.zip is gone or renamed, you're s.o.l.
Sent from my SGH-T959 using XDA App
So if I had kept that update.zip file that CW put on, chances are I could have fixed it? Since I clicked the "Repartition" check box on Odin, would it have even mattered? I used the 512.pit file and the Phone file from the "Unroot" thread by Koush I believe. That worked wonderful, and then I did it a second time and I think something went wrong.
Okay so I recently got this phone more or less as a toy and have been playing with its hardware and software to get it up to par and usable. I've been very impressed by this thing. I ended up with Trackball optional recovery and CM7 Condemned running very well. I seen Gin-sen-tazz and decided to give it a whirl.
Booted into recovery, did a nandroid then wiped data cache and dalvik and then went to flash the rom. It wouldn't go, told me to do something via adb. So I went to restore the backup of cm7 and get a new download ( didnt verify any md5's )
The back up restore gave me the same sort of error, then told me to do something else via adb. I was pretty peved off at this point and went into rom manager and flashed cwr and made a back up of the fresh cm7 install via cwr, and then tried to install the rom via rom manager and then manually in cwr and it still failed.
I'm still downloading my second copy of the rom and I'll be reporting back, but is there any harm in having both recovery's? I really would prefer to run cwr but I have heard of a few bricks, how wide spread is the epidemic? Boot loader still pushes me into trackball optional recovery when selected.
Just kinda sucks that I have two recoveries and neither will work. I am not very new at the whole rom flashing thing but I am not an expert by any means, and have not yet taken the time to learn my adb skills which I know I should
Alright downloaded and put the new rom on the sd card, booted into trackball optional and it flashed just fine.
I also used cwr to back up cm7 and then restore cm7 just to see if that backup indeed worked, and it did. Now I'm concerned that I don't have a stock back up, I made one in trackball recovery but it wont restore... The only back up I have that's working is the cm7 one via cwr... what would you guys recommend i do?
If you decide you want to flash back to stock 2.1 at some point, there's a couple simple options.
Flashback21 will get you back to the latest OTA(March 2011)...unrooted completely stock 2.1.
http://forum.xda-developers.com/showthread.php?t=792026
This other also gives you the latest March 2011 unrooted stock OTA but leaves your custom recovery.
http://forum.xda-developers.com/showthread.php?t=984274
Dunno if this is what was going on, but the Nandroid restore in Amon_RA for the Eris (and derivatives including the trackball-free recovery, I presume) have a 30% battery charge requirement.
If your battery isn't charged above that level, you'll just get a cryptic message about running nandroid-mobile.sh from adb; it won't say "charge your battery, please".
It pays to read Amon_RA's original post, where he points out that you should always check the recovery log file - the exact reason that you could not run the restore operation is reported in that log file. Rather than complaining about an unknown problem on a forum, you would instead know exactly what the problem was.
You can get at the file ( /cache/recovery/log ) via adb while the same recovery session is running, or you can use the Amon_RA menus to copy it to your SD card for later review. It's just a plain text file. Every time you boot the recovery, it gets overwritten - so you need to either review it right away after a problem occurs, or save it to the SD card.
bftb0
Here's what's happenning.
- Device was rooted using HTC unlock method with HB00t 1.5
- Was running Synergy Rom
- Wanted to get latest OTA from Sprint so I followed the steps from another thread :
http://forum.xda-developers.com/showthread.php?t=1447839&page=2- Went through steps and unlocked my device again
Used file from post #16
- Did my updates, unlocked device, booted back into HBoot
- Decided I would try the Infected Eternity Rom this time so I followed those steps as stated in their thread. Did a clean flash. Flashed Superwipe, flashed data ext optimizer tool, flashed eternity rom w/ 3.5 sense
- after message said installation was complete, i got error message when i went back to main menu in recovery:
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
- device wouldn't boot once I rebooted from CWM. It would hang a the HTC white screen, then reboot again, keeps repeatedly doing this.
- Then I rebooted back in HBoot by pressing Vol Down and Power buttons. Went to recovery, flashed Synergy rom. Install was fine, still can't boot up device. Having the same issue. Device would hang at HTC white screen and continue to cycle on and off trying to reboot.
- Rebooted back to HBoot by pressing Vol Down and Power buttons. Went into recovery with CWM, restored my back up. Everything went fine except I got message:
sd-ext.img not found. Skipping restore /sd-ext.
As of right now, I can still boot into HBoot. I've tried reflashing Synergy rom again, but still nothing.
From my search, it says that based on my error message:
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
It could be a HW or SW issue.
Phone is still under HTC warranty, if I need to return it, what do you say to support department?
Thank you.
Have you tried flashing through fast boot through a usb connection? I know the h boot 1.5 are tough to do when you need to change kernals which is what happens when you got to a 3.5 Rom. I had some trouble too if you open recovery through fast boot and do everything that way all should be good.
Edit: as long as you can get into recovery I think you'll be okay.
I can definitely still get into recovery and HBoot. So I would assume those are good things.
Read another thread suggesting to use TWRP instead of CWM.
Will try both flashing with fastboot from usb and twrp and see if that helps.....
If anyone else have other suggestions,
fastbook using android sdk...
it's never bricked unless it won't turn on.
next time, don't try to fix it if it aint broken.
Unlocking via htc will require you to follow the following. The kernel can't be written unless you follow the directions below which can cause the issue you stated.
http://forum.xda-developers.com/showthread.php?t=1239821
Just let us know what happens it is most likely just a kernal problem. Look up how to do the fast boot to make sure it works right. Fingers crossed.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
That's not a brick a brick is where you can't even get into hboot tho if your slick enough you could still fix a bricked phone lol
cobraboy85 said:
next time, don't try to fix it if it aint broken.
Click to expand...
Click to collapse
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
kyaj9 said:
Actually, the reason for wanting to switch over to a different ROM was because with the Synergy rom, I was getting random reboots. Sometimes as much as 3 times a day. Other times, once or twice a week only. It seemed to be an issue that was never really addressed as it's still being asked in their thread now a days. So wanted to see if the Eternity Rom was more stable.
Back to the OP, just wanted to be clear that when I refer to rebooting back into recovery, I am not simply booting into HBoot and then selecting the "recovery" option on the menu. I am aware that I cannot use this method as I have Hboot 1.5. I am using a CMD window to fastboot the recovery program (either TWRP and CWM).
In my cmd window, I change into the propper directory with all my files. Then use commands:
adb reboot bootloader
fastboot boot recovery.img (used: fastboot flash recovery "FILE" to flash onto device)
And then I flash the zip files from there on.
In any matter, was able to get Synergy up and running again. For some reason, I couldn't get it working with CWM but was able to do so with TWRP.
Still getting the occasional random reboot. Have had it up and running for a day now and already one random reboot just a couple hours ago.
Still can't get Eternity w/3.5 Sense running though. So I have a quick question in regards to that. In following the steps on their thread:
http://forum.xda-developers.com/showthread.php?t=1277431
step 5 indicates that I need to copy over the boot.img file once I extract the rom.zip file to the same folder I used to unlock. However, I found two boot.img files under the Kernel folder. Which one do I use? Actually tried both and both gave me the same results (hangs at the HTC white screen and cycles on/off).
Note: the boot.img were found under sub folders "Shooter" and "Shooteru" in the kernel folder.
Click to expand...
Click to collapse
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
you should give that set up a shot man. most reliable rom in my opinion.
k2buckley said:
I had an error like that once before. I believe I had to format my sd card. I also formatted my sd-ext partition. Hopefully you have a backup of your sd card so you can try doing that. Of course you'd need to take your sd card out, and use a card reader to format it using your computer.
Sent from my HTC Evo 3D using Tapatalk
Click to expand...
Click to collapse
The only back ups I have when I first rooted the device.
As long as formatting the SD card doesn't mean I am losing anything vital to the operation of the device, I would have no issues with having to put everything back on manually.
cobraboy85 said:
gotcha. and is it eternity 3.0?
I have been running 1.4.2 with absolutely no issues now for 4 weeks. running Chad's RLS09 kernel that was pulled at the beginning of this month
Click to expand...
Click to collapse
No it's the 3.5. I wanted to try the one with Sense 3.5.
For the good news!!! Finally got it to work. Backing up my apps with Ti Back up as I am writing this.
The only difference I did this time around was that after flashing Superwipe, I DID NOT flash the optimizer tool.
In all my other attempts, whether with TWRP or CWM, I was also flashing the optimizer after flashing Superwipe. Don't know if that was the actual cause or not with the install, but that was the ONLY step I did not do this time around.
From what I read, the optimizer is suppose to make the rom run faster because of the ext 4 partition. So my question now that I have up and running is will NOT having it flashed have any significant results?
On another thought, I did flash the optimzer as needed when I re-flashed Synergy. Does this carry over to the new rom or was I suppose to do again also for Eternity?
In any matter, thank you to all who helped. I will run Eternity for a week or so and see how stable it is first before trying anything else.
EDITED NOTE: Perhaps it should also be noted that I did download the latest build of Eternity also beforing getting it flashed and finally getting it running. Build 180. The file I couldn't get running was build 155.
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
kyaj9 said:
OK...less than an hour into the rom and already experiencing some issues. It could be my flashing...but anyways.
When I try to run apps that require SU, it's saying that I the device is not rooted.
Could this simply be a case of a bad flash or am I missing something? Again, this is only apps that generally, would ask for super user permission. All other apps (games, etc) works fine.
Also, I do have the SU app updated to the latest version and it's visible in the APPS drawer.
To be specific, when I run the Adfree Android app, I get: "Fatal Error: Unable to get root"
Also, when I run MSL Reader, I get error: Couldn't find the superuser binary in any known path. Are you sure you are rooted?
Click to expand...
Click to collapse
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
cobraboy85 said:
k I'm gonna help you out a little bit here...
re-download rom.
before you flash, wipe data twice, and cache twice.
under recovery settings, format system.
flash superwipe.
flash rom.
don't use titanium backup.
don't use ext4 data optimization tool.
you still have problems after that, then use a different rom.
Click to expand...
Click to collapse
cobraboy85 said:
and if you get the SU error, reboot to recovery and under advanced options or whatever, select "fix permissions"
Click to expand...
Click to collapse
Making sure I wiped out everything was the first priority I took. I did re-download the rom just to be sure it was a good download also.
Can't seem to get 3.5 version working propperly, but I did get 3.0 version up and running. Have had it for a couple days now with no issues so just gonna stick with that. Wanted to try out the sense 3.5 first, but the fact that there's no 4g support for it yet means I am probably better off with just using the 3.0 Sense.
Thanks for your help....
mahmutmuratdemir said:
It seems like you have a partitition issue on your internal or external memory in your case i think your internal memory is having trouble try black rose and associated partition tool to fix your partition schema
Click to expand...
Click to collapse
Not familar with Black Rose....but if I am not mistaken, isn't that just a HBoot for the Nexus 1?
yes it is made for nexus one to flash higher andrid versions but i think it can be used in some other models for partitioning internal memory
Sent from my Nexus One using XDA App
Hey guys,
I am a noob. I admit it. LoL.
My device is the Samsung Fascinate, on Verizon. I'm running (or was trying to run) HellyBean (Android 4.2.2), and I have ClockworkMod v4.0.1.0.
I had quite a bit of trouble getting the device rooted in the first place. Many of the common rooting guides had links to files that were corrupted, or the links just led nowhere at all. I found the thread here on XDA that actually provided the name of the file as well as the link, and I was able to get the files from other sources, and finally complete the root.
The hellybean flash was a different story. I read the whole guide through, and missed the note at the bottom about GAPPS. So it got complicated, and I nearly bricked the device. So anyways, I got HellyBean and Gapps flashed successfully, and am approximately two months into getting my phone back into a usable state. (The Titanium Backup of my contacts was apparently incompatible with 4.2.2, and plain-text restore made no changes, so I've been restoring it manually person by person. LoL.)
Last week I went out of town for a few days, where power was limited, and so I devised a system where I brought an extra battery, and I would power off the phone and switch the old battery out with the newly charged one each evening. So on Sunday, I did the normal; powered off the phone, replaced the battery, and powered the phone back on. Cyanogenmod animated logo comes up, and stays up for 10 minutes. So I jerk the battery and try again. Same problem. I booted into CWM, and I get several errors, as well as "Error mounting /System!". I'm seriously disappointed. LoL. I thought for sure that this time, I would have a ROM I enjoyed using, and was stable. I guess I was wrong.
Symptons:
Cyanogenmod Logo Stuck on Loop
CWM displays these errors:
E: Can't mount /cache/recovery/command
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
Also, under "mounts and storage" when I try to mount my system, it gives me this error:
Error mounting /System!
Noticed that phone was extremely sluggish after previous reboot. Phone recovered with the help of Go Task Manager Pro (Advanced Kill), and I thought nothing more of it.
Just before re-boot, noticed that Go Task Manager Pro had reverted to Go Task Manager, and was asking me to re-buy the Pro version. (Odd, since I've never had troubles with the Go apps before.) This was another factor that prompted the re-boot, besides the battery being low.
Changes made directly before last re-boot:
Installed Google Goggles. Had an error signing in.
Needs:
Regain information such as contacts, notes, texts, and app data.
I neglected to make a Nandroid backup, since I was trying to wait until I'd gotten the phone into a state where I could use it after a restore. (Obviously a mistake, and one I won't make again.)
I have not made another Titanium backup for the same reason.
My question is: Is there a way to regain the information? If not, is there some reason why my phone would do this, and if so, how can I resolve it? Do I need to simply re-flash HellyBean and Gapps, or do I need to return to the stock (groan) ROM first?
If you all need any more information, please don't hesitate to ask. I'm doing the best I can, but this is my first time.
Thank you all for your help!
You need to flash back to stock and start over and FYI titanium is fully compatibly with 4.2.2 so just restore from that and your Google account should automatically restore everything else
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
You need to flash back to stock and start over and FYI titanium is fully compatibly with 4.2.2 so just restore from that and your Google account should automatically restore everything else
Click to expand...
Click to collapse
Thank you! Could you, however, tell me what went wrong? There was no apparent reason for this. If I don't know what went wrong, there's no way to guarantee that it won't happen again.
NafetsaDroid said:
Thank you! Could you, however, tell me what went wrong? There was no apparent reason for this. If I don't know what went wrong, there's no way to guarantee that it won't happen again.
Click to expand...
Click to collapse
More than likely it was a issue that has been fixed you mentioned the cuanogenmod logo in hellybelly that was from a older build the new 4.2.2 hellybellys has a custom boot animation I suggest downloading the latest 4.2.2 hellybelly and see if it happens again and if not it was probably fixed
Sent from my SCH-I500 using Tapatalk 2
That would do it. Should I just download hellybean from their website like I did the last time, or is there a specific link that I should go to? Thank you so much for your help!
NafetsaDroid said:
That would do it. Should I just download hellybean from their website like I did the last time, or is there a specific link that I should go to? Thank you so much for your help!
Click to expand...
Click to collapse
Nope just go to the website and download the latest version which I believe is 04_05
Sent from my SCH-I500 using Tapatalk 2
What happened is your system partition got corrupted. The main evidence is the thing with go task manager. Apps like that rely on your device's Android ID to recognize you've bought the pro version. If your system partition was corrupted, then when go task manager tried to read your Android ID, it errored and thought it was running on a different device. Probably, at its root, a serious kernel error that happened before you rebooted the phone.
Posted from my Galaxy Tab 2 with CM10.1
---------- Post added at 07:23 AM ---------- Previous post was at 07:05 AM ----------
WAIT!!!!! Don't wipe and start over! The data partition of your phone is still intact. The errors you saw that involved /cache are known issues with CWM4. Just follow the instructions in here: http://forum.xda-developers.com/showthread.php?t=1694984 and reflash HB.
Posted from my Galaxy Tab 2 with CM10.1
Yea I forgot to mention NEVER EVER EVER EVER EVER USE A TASK KILLER IT CAUSES SLOW DOWNS A D SOMETIMES BRICK THE PHONE but your system patricians WAS messed up or you wouldn't have got them errors even in cm7forcwm
Sent from my SCH-I500 using Tapatalk 2
I am getting the "Magic Value Mismatch" like the threads created by anosis, offload, and Fabodabo31. All the threads answers point to NVFlash being the fix. However the link to the download is broken with the following message:
Access to this link has been disabled. Please ask the owner of the shared link to send a new link to access the file or the folder.
Click to expand...
Click to collapse
I was going to ask for a new link on the thread, but it's locked. So where do I get it now? Heck I don't even know if it will be the solution. I really don't care as long as I get it working. I flashed an unstable ROM running JB 4.1 and things were crashing every 5-10 minutes, so I wiped and tried the step down, ICS, with the same results. So I wiped and I went to go install the previous ROM I had (CM 7.2). However when it booted, it wouldn't get past the CM boot animation. I left it for 12 hours before I finally rebooted to recovery to re-flash it. I wiped like usual, and used install from zip - but the CM installer aborted with errors. I tried re-wiping 17 times without luck. Finally I wiped EVERYTHING under mounts and storage. Then it began an oh, so lovely boot loop. I could get into recovery by turning it off while it was on so it didn't just continue the power cycle and then use the recovery key combo. Once in recovery I managed to get it to stop the boot loop, but I don't remember how. It then would just give something like could not boot or no bootable media or something along that line, I don't remember it exactly. I got frustrated with it and put it down for like 8 months, now it's a necessity that I get it working. So, I tried putting the CM installer on my sdcard and using the install zip from sd. It said it could not find anything. So I renamed it to update.zip and used install update.zip from sdcard. Not found. So I tried rebooting with it in the device. It gave me the "Magic Value Mismatch" error. I was scratching my head in confusion over this one. I figured it was like a bad sha sum or something so I tried to reboot to recovery. It gave me the same error. So I pulled the sd and tried again. No change. I was beginning to panic at this point so I took a deep breath and searched it. I found anosis's post and the answers referred to NVFlash. From there the rest just fell in line to now.
Bump
Sincerely,
Patrick Thomas (Timberwolf)
Timberwolf Programmers Owner & Founder
---- Sent from Tapatalk ----