Well somewhat long story to this. I purchased the Desire 816 (A5_CHL) through VM, received my phone, activated it, and immediately started modding it. I installed ClockworkMod and CM, everything went fairly smoothly minus some minor bugs in CM. I was starting to get frequent Google app crashes for some unknown reason, (seemed to get progressively worse). Notably I did install Xposed which I thought might be causing Kernel crashes and etc.
I went to go start fresh again however with a clean install of the latest CM and etc. however I was receiving errors within Clockwork that weren't there before:
Code:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log...
I attempted to restore from a clean backup of CM, now the phone is stuck at the HTC boot screen. At this point, I'm able to access the boot menu as well as the recovery module still. So I thought maybe re-installing the recovery would help, so I did so using Fastboot. Now when I select recovery from the boot menu, it just vibrates and returns to the main menu. Still confused, I reset once and nothing, screen is black. I assumed it was bricked so I RMA'ed for a new one.
Two days later, started the whole process over again with my new phone, this time I made thorough backups of the stock ROM as well as other settings. I unlocked the bootloader, and installed the same exact things. Now I'm receiving the same recovery errors, I was able to boot into the OS however it seemed to have lost it's service settings. I rebooted once more and restored from a clean backup, now it doesn't boot into the OS. (Backups are verified working prior to incident).
So at this point I'm unsure if I should flash another recovery, then try restoring from backups or how I should go about this. I'd rather not re-brick my phone again so I'm just seeking some guidance on this. Thanks in advanced for any help!
Edit: I recall the recovery issue occurring directly after wiping the cache, not sure if it's even related.
account2442 said:
Well somewhat long story to this. I purchased the Desire 816 (A5_CHL) through VM, received my phone, activated it, and immediately started modding it. I installed ClockworkMod and CM, everything went fairly smoothly minus some minor bugs in CM. I was starting to get frequent Google app crashes for some unknown reason, (seemed to get progressively worse). Notably I did install Xposed which I thought might be causing Kernel crashes and etc.
I went to go start fresh again however with a clean install of the latest CM and etc. however I was receiving errors within Clockwork that weren't there before:
Code:
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log...
I attempted to restore from a clean backup of CM, now the phone is stuck at the HTC boot screen. At this point, I'm able to access the boot menu as well as the recovery module still. So I thought maybe re-installing the recovery would help, so I did so using Fastboot. Now when I select recovery from the boot menu, it just vibrates and returns to the main menu. Still confused, I reset once and nothing, screen is black. I assumed it was bricked so I RMA'ed for a new one.
Two days later, started the whole process over again with my new phone, this time I made thorough backups of the stock ROM as well as other settings. I unlocked the bootloader, and installed the same exact things. Now I'm receiving the same recovery errors, I was able to boot into the OS however it seemed to have lost it's service settings. I rebooted once more and restored from a clean backup, now it doesn't boot into the OS. (Backups are verified working prior to incident).
So at this point I'm unsure if I should flash another recovery, then try restoring from backups or how I should go about this. I'd rather not re-brick my phone again so I'm just seeking some guidance on this. Thanks in advanced for any help!
Edit: I recall the recovery issue occurring directly after wiping the cache, not sure if it's even related.
Click to expand...
Click to collapse
I went ahead and RMA'ed the phone, you can go ahead and close this thread.
Related
This is as little long, but I wanted to be as thorough as possible. I have loaded custom ROMs successfully in the past and I beileve I followed all the directions in the FAQs. Nevertheless, I could have missed something.. so here you go.
I installed the cyanogen7 RC2 release today. I installed it on a freshly wiped phone. I updated the incredible to the latest official update from verizon, rooted it with Unrevoked3 and then did a nandroid backup.
I rebooted, opened recovery and wiped the cache and then the phone. I installed the rom update-cm-7.0.0-RC2-Inc-signed via SD card. It said it was successful. After I restarted, the phone worked.
Next, I went into the rom manager and downloaded gapps. it asked me to reboot I said yet but declined to backup prior (as I already had the fresh verizon backup). It said it installed successfully.
Upon rebooting I hit the cyanogen load screen which cycles ~4 times.. After that the "welcome to adr6300" screen pops up where it tells you to click the droid in the middle of the screen. The screen is almost unresponsive. If I can get it to click, i advance to the next screen where it becomes completely unresponsive. Regardless of where I get on the setup page, after ~3 seconds it takes me back to the cyanogen load screen and this continues in an endless loop.
I tried clearing the cache and wiping the drive in recovery and reinstalling the rom but I still get that screen (which leads me to believe its an issue with gapps??). So I went ahead and cleared the cache, dalvik cache, wipe, and then restored my original official vwz rom.
I downloaded gapps-hdpi-20101114-signed from the CM6 stick this time and put in on my sd card (root). I got the phone back into recovery mode, and cleared both cache's (realized I missed this the first time) as well as wiped the phone. The CM7RC2 rom installed successfully and once again I was able to get into the rom.
I restarted after that success, booted into recovery, and flashed the gapps-hdpi-20101114-signed.zip file. It said it was successful and I rebooted. However... the phone still will not get past the CM7RC2 screen...
Do you know what I'm missing? I've tried to be as thorough as possible. When I first boot up the CM7RC2 rom, do I need to do something else prior to installing GAPPS? Do i need to install GAPPS immediately after CM7RC2 prior to booting the phone up at all?
edit: With the fresh vwz rom install, I did install a few apps (about 10) prior to backup as well as remove about 15 bloatware apps so I wouldn't have to re download or delete them if I flash back to the regular rom (re installed beautiful widgets, astro, titanium backup, etc. Removed vm, vzwnav, etc). I didn't open or input preferences in any of them.. but could this be causing the conflict? Should I hard reset the phone, get the OTAs all over again, root etc w zero apps?
Just realized I had the wrong version of gapps and not to get the ones from the sticky under the Dinc rom section.
I got the latest (and correct one) here:
at goo-inside.me/google-apps/
Not sure how I missed this before but I now have the correct one and its working.
Thanks anyway!
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
WangLung said:
Unfortunately after doing a quick search it looks like many people who have a problem very similar to yours had to send the phone in for servicing.
Click to expand...
Click to collapse
yeah thats what it looks like. I guess my only question now would be is there any way to salvage the media thats on my internal sd? photos/music stuff like that?
MidwestEmo4Ever said:
BACK STORY: Im pretty noobish at this whole thing so thanx in advance to all for your help. So i was running the Official slim bean 3.1 rom for my sgh-t989 with no problems, after about a day and a half I would get a fc message saying whatever application for task i was doing (twitter, poweramp, etc) had stopped. after closing the app and trying to reopen it i would then get a fc message saying something to the affect of "process.gapps. has stopped working", at which point my screen was blank and nothing worked. so i opened up twrp 2.3.3 recovery and wiped my cache and dalvic, hoping to fix the issue. when done I would reboot and end up in a bootloop. I thought nothing of it (I planned to flash a new rom soon anyway) so i nandroid and then flash gsbean v11 and everything is fine. About a day and a half goes by and i start getting the same errors. At this point my noob angriness kicks in and i decide i should unroot back to stock ICS and start over. I unroot and the phone resets into a bootloop so i go into stock recovery and THIS IS WHERE MY PROBLEM BEGINS
PROBLEM: when im in stock recovery i try to data wipe/ factory reset to fix bootloop and i get the following error "E:failed to mount /efs (Invalid Argument) i get the same error when trying to wipe cache... is my phone bricked??
i appreciate all your help and support in this matter!
Click to expand...
Click to collapse
It's not bricked just reflash using odin or cwm back to stock
Sent from my SGH-T989 using Tapatalk
So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.
w0j07 said:
So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.
Click to expand...
Click to collapse
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?
cmlusco said:
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?
Click to expand...
Click to collapse
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.
w0j07 said:
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.
Click to expand...
Click to collapse
Well if you have a custom recovery and have flashed a rom, then you have to be unlocked. Use fastboot and type without quotes "fastboot erase recovery " and then " fastboot flash recovery recovery.img ".
Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.
This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.
I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good
Hi all. I've struck trouble and need help. While trying to make TWRP stick, I've caused my new Moto Z2 Play to get stuck on the unlocked bootloader warning.
I've tried to find the right kind of information for my problem, but it's a real battle as my Android knowledge is limited and my laptop is very slow.
Here's the order of things done;
I have XT1710-09 and it came with NPS26.118-19. I installed about seven OTA updates, and it ended up having OPSS27.76-12-25-3.
Unlocked the bootloader.
Installed twrp-3.2.3-0-albus.img, and it seemed to stay on after several reboots, but for an unknown reason, it then kept being overwritten by stock recovery. I had taken a backup of "System" and "System Image".
I tried a method of renaming/deleting the file that the system uses to restore the standard recovery, but that didn't work.
Now here is where I think I've caused it to stop booting. In TWRP I wiped "Internal Storage". Is my device recoverable from here? No I don't have a backup of it. Did I totally stuff it up?
Please help! Thank you.
try the way below to flash a new rom
https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153
Thanks Mark. Phone is back working, and now in use. There's a problem with default SIM for SMS, it ignores the setting... I will look into it and see if it's a known issue.
Regards