So I just got this phone, and I've been trying to get it up to ICS. I've gone through and was able to complete the ICS update the first time completely, installed Safestrap, etc. Now this is where the issues came in. I did a backup, and then I started restoring some apps from titanium, from an old phone. This is where I started getting constant force closes. Tried fix permissions, went through again, same issue. So I wiped the phone, and went to restore with safestrap - it failed. Now on bootup, it refuses to even boot into safestrap anymore. All I can get is either a blank screen, or motorola recovery menu. By the fact that I can get into the motorola recovery menu, I presume it's not fully bricked, but I know there can be issues with installing on top of Safestrap.
Long story short, my question: In this condition, will flashing the same file I did during the ICS leak installation through Moto Recovery allow the phone to boot? Or will that cause a brick like downgrading from ICS does?
So, just to be sure, you installed one of the ICS leaks correct? Then you installed safestrap 2.0?
Sent from my Droid 4
Yes, that's exactly what I did. Was able to boot up into Safestrap (2.0) and restore through Safestrap, but after wiping /data I got errors with restoring a backup, and after rebooting to attempt it again, Safestrap splash screen no longer appears for me. It has the initial splash, and where the Safestrap splash should be, it just stays blank screen.
Not sure what would have caused this. I don't think you'll be able to flash the zip again since it looks for a .219 system build. Might be worth a shot though. You could also try booting into recovery and doing a factory reset. If neither of those work, try following the instructions for upgrading from one leak build to another.
Sent from my Droid 4
Tried Factory reset already, and attempted just flashing the update anyways - got an error saying build.prop file was invalid/missing?
Now I'm going through the tool steps to swap between ICS builds. At least I'll hopefully get something working.
Though I did do a step I forgot to mention, if that explains why it happened. After the Safestrap restore failed, I tried to do a partial restore of /system and /data. /system restored fine, when I went to do /data it said it was restoring /system in the log - could that have been an issue? A possible mistake in safestrap that overwrote the wrong folder? Or just an issue with the menu?
Doing the ICS switch got it working for me. Now to attempt round 2 and see if I can get into CM9, and Safestrap works right.
More research, root cause : Forgot to install busy box when doing the initial root.
Glad you got it working!
Sent from my Droid 4
Related
TL;DR: "can't mount system" and "error mounting system" in Safestrap when trying to backup systemorig and when trying to mount system manually. Flashed ROMs fail to boot up successfully as well.
I don't believe this has to do with Safestrap or any ROMs I try to install, but probably an issue with my phone. That's why I'm posting here instead of in another thread. I'm hoping someone knows how to fix the issue I'm having, but I'm definitely not complaining—I love the Droid 3 and just want to get some new ROMs working!
So, I can't seem to flash any ROMs or backup my system in Safestrap. No errors come up when flashing a ROM, but when I go to reboot safe system (to boot up the new ROM), it stays in a black screen after the splash screen and dual core screens. No matter how long I wait, the screen stays black and I have to pull the battery to go back to Safestrap and switch back to nonsafe system. Everything works fine when I switch back.
The only error I get is when I go to backup my nonsafe system. It says "backing up systemorig," then "backing up system," then "cannot mount system!" When I go to mounts and storage, and select mount system, it gives me an "error mounting system."
This is all I have to go on. I really hope someone knows what this means and how to fix it any suggestions are welcome. I was using the xt883 radio.img and custom build.prop a while back to get service on T-Mobile (which worked great), and before that, when I bought the phone from craigslist, the guy had it running the xt883 ROM because he wanted it to work on T-Mobile and couldn't figure out the radio hack. I have sbf'd multiple times and have always been running rooted/debloated stock since I got it. I don't think the guy I bought it from used a custom recovery to flash the xt883 ROM, cuz he mentioned using RSD lite.
Thanks again for any help! Also, I have already searched all forums, posted comments to hash's blog, and asked for help here before. Just trying again to see if anyone is willing to tackle this with me
UNLOCKED BOOTLOADER REQUIRED
Here it is: TWRP 2.6.3.0
I've tested backing up / restore, wiping, and installing an old backup (from ver. 2.6.0.0) and all seem to work. I also included the flag "HAVE_SELINUX := true" so it should be compatible with the newer 4.3 based ROMs (needs tested).
To install:
Download and unzip file ("img" was a few bytes over the 8mb forum limit)
Code:
fastboot flash recovery XT901-XT907-TWRP-2.6.3.0-recovery.img
BUGS: I have had the screen start very dim. Sometimes restarting the recovery would fix it, otherwise go to settings / screen, and set the timeout short so it goes out. Press power to turn on and it is at full brightness.
Enjoy!!
Thanks to:
TeamWin for TWRP.
Hashcode and Dhacker for STS-Dev Team source.
Djrbliss for unlocking the bootloader & providing root in the first place.
and mattlgroff
Thank you! Just tested it briefly and it works great. Glad the recovery is finally fixed to be able to use ADB. Was unable to use any TWRPs from 2.5.0.0+ as ADB was broken in the recovery.
CM 10.2 Build removed due to errors.
jbaumert said:
OP updated with link for TWRP compiled with CM10.2 sources
Click to expand...
Click to collapse
The recovery built with the 10.2 sources seems to have an issue with mounting the internal storage and sdcard, but the 1st one built is running perfect. I made a flashable zip of the 2.6.3.0 recovery for anyone who wants to simply flash it in recovery.
@mic213, Thanks for the sanity check. Any chance you have tried backup / restore of a 4.3 build?
Sent from my XT901 using Tapatalk 4
I was able to backup with it. Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
netizenmt said:
Still hangs at reboot.
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
Do you mean when you reboot from TWRP? I noticed that on other builds, but didn't think much of it.
Recovery Tools is a free app on Google Play. Simply download the Recovery IMG. file from this post, and then open the Recovery Tools app. Grant it root, and now you can simply flash the img. file from the app without having to go into fastboot or compress the file into a flash able zip. Once recovery is flashed phone will reboot into whichever recovery is the most recently flashed. About as basic and straight forward as can be.
---------- Post added at 09:34 PM ---------- Previous post was at 09:22 PM ----------
The recovery file works great, only bug after about 4 days of use would be the dim menu screen in recovery. Still very readable even when bug pops up. Thanks for the great upload
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
scottocs said:
Thanks. I could never get 4.3 to reboot past the initial boot after install, and now it finally does.
Edit....ehh maybe. Still working on it.
Click to expand...
Click to collapse
just make sure everything is wiped and that you are using 4.3 Gapps, also look up the SuperSU 1.65 update, some people have had trouble keeping root when rebooting into 4.3. Flash 4.3 ROM then GAPPS followed by SuperSU update, I would suggest running 4.3 on TWRP 2.5 or 2,6 first. Once your able to run 4.3 on one of those, then good ahead and try flashing 2.6.3. If anything on your phone is 4.2 and trying to load onto 4.3 it will never make it far past the boot screen.
Edited because I started rambling and couldn't delete.
Long story short, I have been having issues wiping, installing, and recovering.
I was flashing from a 4.3 ROM to another 4.3 ROM and decided it would be a good idea to wipe internal. Messed me up good.
I went back to 4.2 finally fixed booting issue on getting stuck at boot image. (Wasn't even making it to the boot animation.) I'll wipe everything except internal like I did before and go from 4.2 to 4.3. Last time I did this I didn't have issues.
motoroid7 said:
I'm not sure what I did, but some ROMs suggest that you wipe internal memory. I did this but now I have the issue after installing a ROM and booting it up... playing with it, if I then go to reboot the phone at all I just get stuck on my boot image (not the animation.) This happens on regardless of what ROM I've installed.
I also now can't go back to my backups. They fail on restoring. [Most recent backup was made on 2.5.0.0, previous to that 2.3.2.3]
How do I fix my phone? I'm wondering if I need to fxz back to a rooted stock ROM to fix what's going on?
Click to expand...
Click to collapse
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
RikRong said:
This happened to me on TWRP too. When I went to restore, it say that it failed. However, I decided to boot into system anyway. TWRP gave me a warning that no OS was installed but I went ahead and rebooted. It booted into my backed up ROM just fine but it needed to be set up, like I just had flashed it. Basically, the restore process restored everything but my data. I did a barebones set up then booted back into recovery and went to restore the same exact ROM. This time, I got my complete ROM, just as I had saved it. This is kind of a long process, but it's better than having to FXZ or using a utility to go back to stock.
Click to expand...
Click to collapse
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
motoroid7 said:
It's too bad I can't seem to locate the delete button on these posts, I'll go ahead and edit it. I was finally able to flash LiquidSmooth v2.9 (Android 4.2). It finally booted up, I just went back in and flashed gapps. It restarted fine. The real test is going to see if I go to hit a regular reboot and it boots up normally again. If that's the case I'm fixed. I would like to flash back to SlimROM that I had, but it seems that's going to probably be difficult without it messing up again. Not sure what to do if it does again. I won't be wiping internal memory anymore. I didn't have issues going from 4.2 to 4.3 when I didn't do it.
Any idea why I get a funky e:error: unknown media 'datamedia' error all the time in TWRP? I've had that error since like v2.3.x.x
Click to expand...
Click to collapse
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Kyles1329 said:
Not 100% sure, but i believe that when you wiped your internal memory on 4.3 you deleted the ROOT. SuperSU seems to be having issues with
carrying over root on 4.3 to some peoples devices, Ive had to flash SuperSU update 1.65 from recovery otherwise when ROM boots up I get stuck in a cycle of SU Binary update/reboot. Also make sure that in Developer Options in your custom ROM, that Root Access is set to APPS and ADB and the same in SuperSU - APPS/ADB. Now to clarify I may be merging two unrelated issues together. If so, my bad lol.. But from my experience running PaCMan 4.3 since August, and now running TWRPS 2.6.3 since OP , 4.3 ROOT will not revert back to 4.2 unless Recovery is included in the backup. One final suggestion, try flashing the boot.img from 4.2 before flashing your 4.2 restore. I was able to revert back to 4.1 restores when I upgraded to 4.2 but while running 4.2 I deleted the Root Data from Internal Storage, I strongly suggest looking up arrrghhhs Sept. 15th Kernal for XT 926 which runs the same for XT 907. It damn near all the way current with CM 10.2 merges, should make running which ever 4.3 ROM you want much easier. If you want to run a 4.2 Rom , look up arrrghhhs 10.1 kernal version.
Arrrghhhs xt926/907 kernal
Click to expand...
Click to collapse
To piggy back on general advice: I found I was having all sorts of problems going from 4.2 to 4.3. What finally did the trick was I wiped Dalvik, System, Cache AND I formatted data. The formatting was what did the trick.
When you wipe in twrp 2.5+ the recovery does not delete data/cache from internal (system) unless user mounts system prior to wipe. Wiping system cache, data, and dalvik cache is a full system wipe. Recommended if switching ROM rather than flashing nightly. This way no files from a AOKP ROM stick around and try to associate with your new CM based ROM.
Sent from my XT907 using Tapatalk 2
Thanks for the advice guys.
I was finally able to successfully getting my phone to work again last night (very early in the AM). It's very strange. I actually had 0 issues going from LiquidSmooth v2.9 to LiquidSmooth v3.0 (4.2 to 4.3). Though it was from the same dev could be part of it. It wasn't until I tried flashing from SlimROM/4.3 to CM10.2 nightly (where I wiped internal memory requiring me to type "yes".) Another thing is strange is even though it was saying I lost root in TWRP, I'm not sure that I ever did, unless TWRP just re-installed it when I reboot recovery automatically... because I finally told it no when asked if I wanted to re-install root? Then I was finally able to get LiquidSmooth v2.9 bootable and stable.
Again, thanks for all the help guys. I just wish I had a little bit understanding what I all did to finally get it to boot up. It was pretty early in the morning... going on 5/6AM. So I was pretty tired doing all of this. I just knew I couldn't let my phone not be up and running by morning.
I did a backup last night, flashed a 4.3 ROM which had reboot issues, and then restored with this version. I had zero issues, unlike when I was trying to restore with the previous version. Thank-you for your work.
It works with the xt902 too. Thanks!
What's the difference between the link in the first post and the one in the fourth? One of the is broken? Which one has been built with the CM10.2 sources?
I'm using a CM10.2 ROM... Which one should I peek?
Thanks!
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
jahfry said:
I'm trying to resurrect my I897 Captivate. I put it in the drawer a couple of years ago with Glitch kernel and AOKP ICS on it. My wife destroyed her Skyrocket (S2) and she needs a phone to use as a stand-in for a couple of months.
I wiped it, no nandroid backup since I had no plans to use any of the data on it, and began trying to install Cyanogenmod. I was planning to use the recent M5 snapshot of CM11 but am ok with going to 10.2.1 stable if 11M5 doesn't work.
However, I just can't get it to boot. It will go into recovery mode fine (in fact, it boots to recovery even when no buttons are pressed).
I went back, wiped everything, formatted all partitions, and started with CM7, then CM9, then CM10.2.1 to get the partition scheme updated and just to be sure it wasn't CM11M5. However none of those change the issue. It just refuses to boot anything but recovery.
I've repeatedly done wipes and factory resets, including going back and formatting the partitions. I've tried the "install CM twice" trick. The phone just does not want to boot the images.
The install processes seem to go fine. No errors reported during .zip install.
I went through many different pages that are meant to break a recovery loop, most of which just have you do the basic reset and reboot, but so far have found no way to break the cycle.
Any ideas?
Click to expand...
Click to collapse
my advice is, go to stock GB, then flash ICS, flash a KitKat kernel, reboot recovery and then flash CM 11..
hope this works for you!
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Stock Rom
jahfry said:
Yeah that was my next plan, already have the stock ROM downloaded. Will report back. Was just hoping there was a known issue that I could fix without reverting. Not a big deal Thanks.
Click to expand...
Click to collapse
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
asianlight said:
Hello jahfry! Glad to hear you got the stock ROM. Would you mind telling me where you got it from? All the links I've found here are dead… I am in a similar situation as you - managed to get a custom rom going but have lost all trace of EFS folder/ nv_data.bin file…. Need to go back to stock to start again… Any help appreciated!
Click to expand...
Click to collapse
Stickied threads: http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Search goes a long way
I've been modding androids, iphones, and windows phones for years now but I somehow ended up to finally brick a phone.
So I was running stock 4.3 rooted on my N900A and decided to install SafeStrap 3.71 in order to upgrade to Knoxraid. I followed this guide (kind of):
http://galaxynote3root.com/att-galaxy-note-3-roms/knoxraid-kitkat-rom-for-att-galaxy-note-3/
Everything went well and I got SafeStrap but I installed the rom to Rom Slot 1 instead of the Stock Rom slot., I rebooted into the regular download mode. Everything went okay with the install but after flashing the ODIN files I noticed that SafeStrap no longer booted to the recovery menu (of course). Knoxraid installed just fine but after booting into the rom I noticed that it would soft-reboot every 20-30 seconds. I couldn't get into Settings>General>Security. I couldn't load any apps because it rebooted too fast. It was basically useless. I booted into recovery mode to try and reload the rom there. Now I just get a black screen on bootup.
I think my saving grace might be that I took a backup of my phone using SafeStrap before I made any changes. However, how can I apply that backup without SafeStrap?
HELP!!
I've done this before and I'm wondering if I can do it again
http://forum.xda-developers.com/showthread.php?t=2559715
Okay I've made some progress. After restoring the original MJ5 ODIN files in the above link, SafeStrap came up after the reboot!!!!!! Now I'm doing a restore.in SafeStrap. I should be all set but I'll update in case anyone else has the same issue in the future.
It worked flawlessly after that. I followed the instructions to the letter and now everything is working perfectly!
I have Safestrap 3.7.2 and Lollipop rooted installed. I've googled and googled and can't find an answer to this. I booted into Safestrap to try to figure out how to delete an old NC1 backup I made. I hit the reboot/recovery button once. What a mistake. The phone booted into stock recovery. Now when the phone boots, I get a message saying Safestrap is disabled with the options of recovery or continue. Continue does nothing but gives me a blank screen. Recovery takes me into Safestrap, and I can't get the phone to boot back into Lollipop. If I hit reboot/system, I get the same Safestrap disabled screen. If I hit reboot/recovery, I end up in the stock recovery. It says to wait 10 seconds and it will boot, but all I get is a blank screen. I have Lollipop in the stock ROM slot with no other ROMs loaded. HELP!
Well the only thing I could figure to do was to ODIN back to NC2, use Towelroot to get root, install Busybox and Safestrap 3.75, install the OC1 rooted ROM, and reinstall everything via Titanium Backup. This time once I get the phone set up the way I want I will make sure to make a Safestrap backup. What a pain.
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
voigts said:
Unbelievable. After restoring everything via Titanium Backup, and then booting back into Safestrap to make a backup, I decided to wait and the only thing I did was to power the phone off. I'm getting the same Safestrap disabled message again. I'm not even sure how this is possible.
Click to expand...
Click to collapse
Since you're on Lollipop did you flash the OC1 kernel before leaving Safestrap? http://forum.xda-developers.com/showpost.php?p=59666958&postcount=2
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
voigts said:
Yes. What I have been finding after flashing/reflashing about 10 times today is that if I boot into Safestrap (v. 3.75) even once after flashing the rooted Lollipop Zip (OC1 that you linked to), Safestrap gets disabled. As long as I do not boot into Safestrap, the phone boots fine. Once Safestrap disables, I am dead in the water and can't get back into Lollipop at all. I then have to ODIN back to NC2, root with Towelroot, install Busybox, and then Safestrap to flash back to OC1.
I spent all day on and off messing with this. I'd really be in a fix without Titanium Backup.
Click to expand...
Click to collapse
Only thing I can think of is something in your Titanium backup is messing things up. If you happen to flash all that again (not saying to do) but if you do, I would boot into Safestrap (once you install Lollipop) and flash the OC1 kernel to see if it boots ok. (Before you do the Titanium Backup).
Thank you for the replies. I failed to realize that I needed to extract the lollipop file and then flash the SM-N900A_OC1_Kernel_Safestrap_Installer.zip file contained within AFTER flashing the lollipop file. Yes, I get the stupid award for the day. Duh....
I extracted the file, copied to MicroSD card, and then booted into Safestrap and flashed it. Hopefully things will work correctly now. I feel pretty stupid.
I need help myself.. Every time I try to flash any type of zip I get stuck in safestrap disabled