Before this happened I was running CM11 on my Nexus just fine for a few weeks or so. It randomly rebooted, and then got stuck in a boot loop. Now, here's what's weird. When I booted into CWM, the only partitions I could mount were /system & /firmware. /data, /cache, & /persist all just give "Error mounting /partition!". Here's what I also get when navigating through CWM:
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
When I format the /cache partition it works just fine, but I still can't mount it and the issues above continue. When I try to wipe data/factory reset it just gives me an error mounting /data and skips it, along with /sdcard. This also means I can't install a zip from the device. I tried sideloading the stock ROM onto the device but it just prints this:
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Anyone who could point me in the right direction would be much appreciated. Flashing anything with fastboot doesn't seem to change anything either, by the way (including trying to change to TWRP) Thanks again.
Sent from my XT1034 using Tapatalk
I take it you've tried to flash the factory image with fastboot? Do you get anything if you type fastboot devices?
jd1639 said:
I take it you've tried to flash the factory image with fastboot? Do you get anything if you type fastboot devices?
Click to expand...
Click to collapse
I have indeed tried to flash the factory image. And the device status shows up in fastboot when I do fastboot devices.
Sent from my XT1034 using Tapatalk
try this
n1kolan said:
Before this happened I was running CM11 on my Nexus just fine for a few weeks or so. It randomly rebooted, and then got stuck in a boot loop. Now, here's what's weird. When I booted into CWM, the only partitions I could mount were /system & /firmware. /data, /cache, & /persist all just give "Error mounting /partition!". Here's what I also get when navigating through CWM:
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
When I format the /cache partition it works just fine, but I still can't mount it and the issues above continue. When I try to wipe data/factory reset it just gives me an error mounting /data and skips it, along with /sdcard. This also means I can't install a zip from the device. I tried sideloading the stock ROM onto the device but it just prints this:
symlink: some symlinks failed
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
Anyone who could point me in the right direction would be much appreciated. Flashing anything with fastboot doesn't seem to change anything either, by the way (including trying to change to TWRP) Thanks again.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I've had the same issue while using recovery mode with certain toms and I was also worried at first. It usually happens after a bootloop.
Try this:
1) If your device gets stuck during boots and it seems like its taking forever and just wont get past the boot phase then do this: boot up again and just wait for a while. Be more patient than last time let the process go on for five or so minutes THEN do a hard power off (gold down power button until it turns off). Then turn back on while holding volume to boot into recover. Now check to see if your partitions are back (THIS IS WHAT WORKED FIR ME). If still gone, try again but this time instead of waiting a while do the hard power off sooner in the boot process, maybe about 30s to a minute in or at about the time when it usually would have completed booting back when it was working. Boot back to recovery, check for partitions. If still not there repeat the steps a few more time doing the hard power off at different intervals (first try doing it almost immediately, then try waiting even longer than before, then try after 15s, ext...). My experience has been if u do the hard power off at the right point of timing during the bootloop you will have shut it off either before or after (not sure which) the point during the booting process where it is screwing up and making your partitions look like they are gone. They really are not and your data should still be there in SD area if u didn't delete it, cwm just isn't seeing the partition because of some error during boot process.
OR
2) If it continually resets try to time it then doing a hard power off (hold power button several seconds until your device shuts off) at the latest possible moment before when it normally resets. Then turn your device back on holding volume buttons to get to recovery mode and see if the partitions are back. If not, try a couple more times.
Anyway that's what worked for me. At first I was pissed and thought my data was gone to and I was gonna have to do full unbrick process but nope, after shutting off at the right point during the bootloop or indefinite boot process I found that when I went back into recovery mode cwm could see my partitions and all my data and all I had to do was reinstall a different kernel I had in the SD area of my memory and next time it booted right up. If installing or reinstalling a different kernel (one that worked before for u) doesn't fix it or isn't possible just while and reinstall any ROM or backup IMG u got stored in memory and install that then next boot will hopefully work fine.
If none of those steps restored your partitions or fixed it back so cwm or teamwin could see them then u will prolly have to USB to computer and go through unbrick process.
Hope this helps
---------- Post added at 10:32 PM ---------- Previous post was at 10:26 PM ----------
n1kolan said:
I have indeed tried to flash the factory image. And the device status shows up in fastboot when I do fastboot devices.[\QUOTE]
Depending on what u did it may be too late to try my suggestion I gave above but if u are still getting a bootloop and haven't figured it out yet then trying my above suggestion it is still worth a shot.
Click to expand...
Click to collapse
Thanks a ton for the help, but I'm afraid its too late. I've formatted the system & data partitions already. What's weird however is when I turn it on normally it still shows the CM splash screen.
Sent from my XT1034 using Tapatalk
Alright, I tried wiretaps suggestion but still nothing. I'm unable to mount anything except for system and firmware. Any other suggestions?
Sent from my XT1034 using Tapatalk
n1kolan said:
Alright, I tried wiretaps suggestion but still nothing. I'm unable to mount anything except for system and firmware. Any other suggestions?
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Flash twrp 2.6.3.4 and in wipe, format data.
jd1639 said:
Flash twrp 2.6.3.4 and in wipe, format data.
Click to expand...
Click to collapse
I've tried flashing TWRP, it sends and writes without an error. But when I boot into recovery CWM is still there :/
well if you've given up on recovering your partitions...
and all you want is to get your device working again you can always just follow the unbrick instructions. There us a guide posted on thus site somewhere I'm sure about how to do it using the android SDK but if you aren't very savvy with command line utilities there is an all in one program for windows with a darn good GUI (graphical interface) that works pretty damn well and will automate all the steps you need to return your Nexus 5 back to the way it came.
The software is called Nexus Root Toolkit and you can find it on Google or download it from this link: won't let me post just search for nexus root toolkit download on google
I have used it several times on my Nexus 4 and two different Nexus 5s without any problems or errors. Just install the application on a windows machine and follow instructions. Connect your device via USB and open it up. First it will either prompt u to download some files you will definitely need for it to work or it will ask you what device you are connecting then download all the necessary files. The windows drivers, factory images, android SDK ext. Everything u need, its completely automated all you gotta do is click yes read the instructions and follow the prompts.
Most people who download it do so because its an easy way to go through all the steps to unlock and root your nexus but it also has tons of other options including an option to completely "unbrick" your phone and return it to factory warranty condition just like the way it came. You will have to allow it to download the factory images for boot loader and the original OS but just follow the prompts it really is quite easy even for a newbie who is uninitiated with android development.
You might not need to do the full unroot relock process but if u just want to return the phone to factory condition then go for it. After you finish you can use the same app to unlockbit again and reroot it.
I'm sure there are plenty of Android developer SDK purists around here who would scoff at the idea of using the automated toolkit and say you should learn how to do it all by hand withe SDK command line way but u think that is over your head go on and use the toolkit there is no shame in it and it seems to work very well. I never encountered any problems with it.
1. DO NOT USE A TOOLKIT (as mentioned above)
2. Follow the factory reset thread to flash the factory image (you could try to leave out the userdata.img if you don't wanna lose your data)
3. Once confirmed working again, flash a recovery and a new ROM (and be careful in future )
EddyOS said:
1. DO NOT USE A TOOLKIT (as mentioned above)
2. Follow the factory reset thread to flash the factory image (you could try to leave out the userdata.img if you don't wanna lose your data)
3. Once confirmed working again, flash a recovery and a new ROM (and be careful in future )
Click to expand...
Click to collapse
+1.
And just to be picky, below the 3d link for factory reset:
http://forum.xda-developers.com/showthread.php?t=2513701
P.S. new to XDA, hi @ all
I've done it both ways. With the toolkit and without. Both ways worked fine. I really don't get all this anti-toolkit sentiment around here. Not everybody is as savvy at using SDKs and coomand line as many of you may be. For some people where the whole SDK command line instructions are truly over their abilities I see no reason why they shouldn't at least have the toolkit to use as a backup option.
wiretaps said:
I've done it both ways. With the toolkit and without. Both ways worked fine. I really don't get all this anti-toolkit sentiment around here. Not everybody is as savvy at using SDKs and coomand line as many of you may be. For some people where the whole SDK command line instructions are truly over their abilities I see no reason why they shouldn't at least have the toolkit to use as a backup option.
Click to expand...
Click to collapse
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.
jd1639 said:
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.
Click to expand...
Click to collapse
+1.
In Fastboot we trust!
n1kolan said:
I've tried flashing TWRP, it sends and writes without an error. But when I boot into recovery CWM is still there :/
Click to expand...
Click to collapse
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick
samersh72 said:
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick
Click to expand...
Click to collapse
uhm.. pretty logic.
nice information. Thanks you.
samersh72 said:
hmmm... i smell a fried emmc.(hope not)
try to lock bootloader with fastboot, then reboot-bootloader and see if it still unlocked.
if yes so there is a hardware problem.... nothing will stick
Click to expand...
Click to collapse
Will try this when I get home
Sent from my XT1034 using Tapatalk
Alright update: I tried what samersh72 said, and it said it was still unlocked. Looks like its a hardware problem... :/
Sent from my XT1034 using Tapatalk
jd1639 said:
How can one command be over anyone's abilities. Fastboot flash will cover 90% of anything you need to do.
Click to expand...
Click to collapse
You might be surprised. There are a lot of younguns out there who have never so much as even seen a command line. I'm sure your response will be that they have no business rooting or installing Roms on their phones in the first place but such is the way of the world.
n1kolan said:
Alright update: I tried what samersh72 said, and it said it was still unlocked. Looks like its a hardware problem... :/
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I had the same problem, and couldn't find a solution. No partitions could mount, couldn't write to them, flashing and erasing recovery didn't do anything as it'd still boot to the one I had before, and to top it off fastboot OEM lock wouldn't stick. I had to rma it, and hope that whoever gets it is extremely tired from a long day and just passes it through without any checks.
Related
I can boot with volume up and get to the recovery screen. I am combing threads and doing all I can now. Any help is greatly appreciated. Downloading the SDK on slow work internet now and attempting to get all files I think I might need as we speak.
give members more details [what did u flash etc], so they can help u.
No, if you have recovery mode available nothing is lost.
Just download a ROM you like, and try flashing it. If it doesn't work, try formatting and then flashing again.
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
In recovery you can still use adb to transfer files to the device.
Code:
adb push update.zip /sdcard
I am having trouble getting adb to work. I am following these instructions but something seems to be wonky?
http://androidadvices.com/how-to-install-set-up-and-use-adb-for-android-devices/#.UAWbt7Sm_Nk
can you point me in a better direction to get adb access
I just noticed at the bottom of my screen in slightly greyed out copy it reads: FASTBOOT STATUS - FAILINVALID COMMAND
magicwands said:
I flashed one click stock and I saw that SYSTEM failed while it was running. Now I get no boot but I can get to the stock recovery.
How do I get a rom onto the phone in its current state?
when I boot with the vol up / power combination I get a small menu for reboot bootloader, reboot, recovery or power off. If I select recovery I get the triangle icon with the ! and then after a minute or so I can get to what looks like a very small clockwork menu with: reboot system now, apply update from /sdcard, wipe data/factory reset or wipe cache partition. I have tried to apply a rom I had on in the list but it failed verification and the list is only partital it does not let me go all the way down.
Click to expand...
Click to collapse
That small menu as you called it is fastboot.
That recovery is stock recovery.
Connect to phone to computer and use fastboot to flash a custom recovery. Boot into said recovery. Mount usb storage. Transfer rom over to phone. factory reset/format system and flash new rom.
If you don't know how set up and use fastboot. Look it up.
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
magicwands said:
I got the bootloader unlocked and TWRP installed but whenever I try to flash a rom I get the error message " E:error in /tmp/sideload/package.zip (status 7)
Any thoughts?
Click to expand...
Click to collapse
Do a full wipe, re-download the rom ( make sure its the correct rom for your device) and try again.
If it still fails. Flash the official stock images and make sure that at least works
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
magicwands said:
I am fully wiped but I am going through the process again just to be sure, all I have on the device right now is TWRP its unlocked and boots into TWRP recovery fine. But everytime I flash, I have tried 3 roms and one was the NS4G_IMM76d_deodexed it hits me with the same error as before: e:error in /tmp/sideload/package.zip (status 7)
I am searching frantically for a fix, any help is appreciated.
Click to expand...
Click to collapse
Download the following files:
7-Zip from http://www.7-zip.org
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
http://android.kcomputerzone.com/stock/sojus-imm76d-factory_windows-scripts.zip
http://android.kcomputerzone.com/extras/crespo-drivers.zip (just in case you need them)
Install 7-Zip
Extract sojus-imm76d from sojus-imm76d-factory-10660f4c.tgz (You will need to go in multiple levels deep to get to folder) to your desktop.
Extract contents of sojus-imm76d-factory_windows-scripts.zip to the sojus-imm76d on your the desktop.
With phone in bootloader mode run flash-all.cmd in the sojus-imm76d folder.
If all worked it should be boot and be working.
That should restore yours to default firmware all using fastboot. Hope this helps.
This site (http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/) got me up and running with TWRP then I been having issues flashing roms, I am able to get a Peter Alfonso stock rom to boot but then if I try to flash I get the same error. I was able to ODIN the stock 4.0.4 but nothing seems willing to flash via clockwork or TWRP.
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
magicwands said:
Ok just to bring some closure to this, thanks for all the help. My problem with the status 7 error was that I was using the wrong clockwork recovery. It was bundled in a one click root for Nexus Galaxy and Nexus S, the Root worked great but the recovery was the incorrect version. In any event I am now 100% functional. Thanks to all that helped out.
Click to expand...
Click to collapse
That is the problem with One click root/unroot. I know the simplicity is awesome but the end user is learning nothing. Doing it the ol' fashion way teaches the user how to use SDK, ADB, and other important simple things. I always say use the guide and do it yourself. Problems happen and instead of having to start a new thread you can trouble shoot it yourself. :good:
So I unlocked this without much trouble, and then when I was attemoting to use adb to flash images to recovery partition, one would just not work, and I stupidly tried to force it, and now it boots and just sits there.
I've seen a different website saying the Q can run Jellybean, and it also has info on getting the stock rom back .. but NO files. I know how to use the damn recovery tools once theyre booted up - those articles were completely useless. I don;t know what else to do. I tried to get the files that argghhhh jad posted to dropbox but they are not available anymore.
Stuck and been trying to fix this for the last 12 hours
EDIT:
Found stock recovery stuff, but I dont think it's going to help any...
Nevermind I suppose
I see that I can try the stock rar file posted for someone else in here to put into recovery, hope it works, I just dont know if the nernel is ok, but I would think so. It stops at the "unlocked"notificaton screen. anyay, yeah. If I get jellybean on instead ill share the info,
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
tetrabyt said:
I believe you need to fastboot your recovery, not adb. Then you may be able to flash something back on there.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks for the repl! S I actually have been using fastboot because adb for some reason just will not see the device (I checked the version and its correct supposedly). So what I did was take the WWRP rar, pull the contants out and make them into a .zip.and instaled with fastboot flash. The output looked ok:
sending 'userdata' (319120 KB)... OKAY [ 29.814s]
writing 'userdata'... OKAY [ 92.421s]
finished. total time: 122.235s
but what about all the other partitions? I jad done system earlier frok out of the stock zipfile. i think i may just try the entire Stock file insead, or maybe I am missing the fact that I beed to install the kernek into /boot, Any thoughts Thanks much!
EDIT: first im going to fastboot the recovery wit tue TWRP zip file, and try to install it from
I am a little confused, did you manage to get the recovery working? Looks like you were trying to flash the recovery img to your user data partition... Am I misreading your post.
-Saint
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
tetrabyt said:
Whoaa just saw that. should have unzipped the recovery image and flashed it to the recovery partition with
Fastboot flash recovery recoveryfile.img
Then you can boot into recovery and flash one of the system dumps that these devs have generously posted for when we mess up like this...
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
is this the basic method at present for a stock restore? i was looking at the thread with the files for RSD lite, but i was confused as to whether that was working. thx!
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Herby6262 said:
ok so I messed up what to flash from recovery. I had grabbed copies of the system, data, boot, etc for all the partitions thinking i needed to do them all from outside using fastboot,
Click to expand...
Click to collapse
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Herby6262 said:
i must be retardedly doing this the wrong way, i quickly get twrp into recovery and can get in there, and I have the stock photon .zip in 1 big zip and in separate pieces, but how do you get them to the external card.. windows 7 fails to recognize the phone with some message MTP device unknown so I can't transfer it that way ... I dont know. Im about to chuck this thing out the window and be done with it. The whole purpose was to be able to install apps to the sdcard, originally. Only fastboot works from a command prompt, adb doesnt do a damn thing, trying multiple versions of it. I give up
Click to expand...
Click to collapse
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
fallnSaint said:
Do you have an sd adapter or another device you can plug the sd into to transfer from your pc? Does adb fail when booted into TWRP also? Tried uninstalling/re-installing drivers?
Might be able to make a data img you could flash through fastboot, so long as the folder structure was correct... then use recovery from internal storage. Not certain on this: /data/media/sdcard/TWRP/BACKUP/"serial#"/
Maybe someone else can jump in here, this would be my last resort. Use any way possible to get it on external sd first.
-Saint
Click to expand...
Click to collapse
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
tetrabyt said:
I believe there is a system.img floating around here somewhere.
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1894575
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Herby6262 said:
Thanks a ton for the help Saint, and others. I finally got it back in working order .. yay! Now to install that powermenu update someone made, and see about making android 4 opeate like the older versions, where you could install apps onto the external SD card. Am I correct in assuming they just F'ed it up by changing the /mnt names, while the software was not updated to accomodate those changes? Why the hell is internal memory now "sdcard" ... so odd. I have a friend whose internal storage is named "USB storage" on his phone. It's USB accessible .. but its a freakin flash card. So odd, and stupid. I really felt like 4.0 was a downgrade, personally. What improved? I see nothing, only things taken away (Im sure the underlying scheduler and thread management/memory mgmt is better, but you know what I mean .. anything visible?)
Click to expand...
Click to collapse
Good to hear, glad you got her working again. As for how she runs, definitely snappier than older versions of android. Maybe just hardware, but I still see improvements w the wifes epic running ics, guessing that we will see better results once CM is dropped for this phone.
-Saint
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
fallnSaint said:
Ok, the easiest way to get your phone up and running again is to push the newest TWRP from here, put it in your tools folder and push w fastboot:
fastboot flash recovery openrecovery-twrp-2.3.1.0-asanti_c.img
fastboot reboot recovery
Make a backup to your external sd card so that TWRP creates the directory needed to restore the stock system & boot. You should delete this first backup later since it will be broken.
Then download a system & boot image from here, unzip to the /TWRP/BACKUPS/"serial#"/ folder on your external sd. Do full wipes for system, dalvik, & factory reset; then restore Stock from within TWRP. Should be good to go.
:edit:
Just saw that tetrabyt already hit on this, consider this post a more detailed revision.
Click to expand...
Click to collapse
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Still stuck on Unlocked bootloader screen.
My emmc might be corrupted I think
I do have sprint insurance. Think they can reflash stock?
yogi2010 said:
After RSD Lite, it might not have booted up because the system image was removed from the file to make it work. Probably if you flash TWRP after doing the RSD file, and restore Rangerbry's system backup, you might be good..
Click to expand...
Click to collapse
coolroman123 said:
No Luck.
Just tried this.
Got the following Errors during only system restore:
E:Unable to mount '/cache'
E:unable to mount '/data'
Click to expand...
Click to collapse
Was that in CWM or TWRP recovery? Just trying to make sure the process was correct, haha. I have only started using TWRP on this device, but i think the 2 recoveries use different backup formats?
coolroman123 said:
Tried this, still stuck on Bootloader Unlocked Screen. TWRP restores don't seem to work right. I tried restoring an old backup I had of the boot/recovery/system with no luck. Everytime I wiped system/dalvik/cache/factory reset before restore. No errors show up.
So, I can go into fastboot, and I can flash files.
I tried RSD Lite 5.7 with this Zip
It flashes everything until RSD wants me to reboot. Then it reboots and gets stuck on the bootloader unlocked screen.
Any ideas?
[Edit] I flash CWM and found out that I can't mound /sdcard which doesn't seem right...
Click to expand...
Click to collapse
Can you boot to bootloader or just to fastboot? There are two control files in that RSD zip, one doesn't flash bootloader, try removing that one and forcing the reflashed bootloader. Then try restoring again. About all I can think of if it successfully flashes the other components... Maybe just restore system and not boot or data?
-Saint
Everything you need is here to return to stock WITH ota update.
http://forum.xda-developers.com/showthread.php?t=2001226
The only thing simple is the belief in simplicity.
Hi all,
So, last night I successfully rooted and unlocked my One X on AT&T. Today, I tried putting a ROM on it. I flashed the boot.img first, then tried to install the ROM (Jelly Bean Sense). It failed for some reason, so I wiped and rebooted my phone.
Instead of going back to the stock ROM, the phone now will not turn on, is not recognized on both laptops I tried, and does not recognize even being charged. The only thing that happens is when I press down the power button, all of the soft keys illuminate and flash until I stop holding it. I've managed to get into the bootloader screen once, but the phone reset itself before I could do anything.
The only screen I can get to with the Vol Down+Power combo is the HTC Screen, but it's the one that shows before my custom recovery, with some warning from HTC in red letters at the bottom.
At this point, I just want a phone that works. This is a lot more complex [for me] than rooting and flashing a ROM to the Inspire I had for some reason. I fly out for vacation in two days for a few weeks, so I'd like to be able to avoid having to send this thing back to HTC or AT&T if possible.
ANY help is greatly appreciated.
If it's easier, feel free to Skype chat me.
Thanks!
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can get it to boot into the Bootloader screen and the TWRP now just fine, but that's as far as it will go. The internal SD will not mount with TWRP either now.
Here's the ROM I tried to flash: http://forum.xda-developers.com/showthread.php?t=2055490
I put it on my SD card, then extracted the boot.img to the folder I have my dab/fastboot files in, then flashed the boot.img, then tried to flash the ROM.
If I can get it working again, I'll try to do it in reverse order next time and see if that works. Still trying to find a way to get a ROM on here with my Mac, and to make my SD card work again. Everything on it is backed up so it's ok if I need to wipe it.
If you can get to bootloader, you're not bricked. It's just a matter of flashing the right stuff in the right order.
It could be that your sdcard is corrupted. Factory reset from bootloader will do it, but fixing it just a matter of formatting it again. Can you mount it on your computer? What happens when you plug into your PC?
Your sdcard is corrupt. No big deal but you'll lose everything. Plug it in into computer and locate the storage and try to find a way to format it. Sorry, I have no clue with a mac I swore off apple products :thumbup:
Anyway, you seem to know the ropes for the most part. If you can format, drag Rom onto SD. Wipe everything in twrp. Cache, dalvick, factory reset, system. Flash Rom.. immediately boot into bootloader and fastboot the boot.img. choose reboot from bootloader. Good luck!
Sent from my HTC One XL using Tapatalk 2
Yep, I also suggest doing a factory reset from the bootloader ( which will erase your internal storage) but at least you'll be able to mount your SD card, put a ROM on it and flash it. I would highly recommended you to flash viper 3.0.0, you don't need to flash the boot.img and its pretty much stock JB with some tweaks.
Sent from my HTC One XL using Tapatalk 2
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
That's good news!
I tried doing a factory reset from bootloader, but nothing happened. Maybe because the SD card won't mount?
I only have a Mac, with no PC in sight. It doesn't show up at all on here. Fastboot USB, or when I mount it as USB in TWRP. It does however show up as a device in recovery in terminal. But nothing on the desktop. Apple+Android do not mix well!
I'm ok with losing my data, what I'm not OK with is having to use this pink Razr while my nice phone is broken :'(
Thanks for all the help so far!
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
elijahpr said:
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
Click to expand...
Click to collapse
Format your sd..drag Rom..wipe..flash..enjoy
omario8484 said:
Format your sd..drag Rom..wipe..flash..enjoy
Click to expand...
Click to collapse
I can't format because it doesn't show up on my computer, and doing so in bootloader takes me to TWRP.
emylibef said:
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
Click to expand...
Click to collapse
Hey dude, I followed their advice (dug out my XP machine) and now my SD card is re-formatted.
Get into the bootloader screen, hit factory reset. (When I did this on mine, it took me right to TWRP)
From there, I mounted as USB and it showed up as needing to be reformatted on my XP machine. Took a few minutes to do on this dinosaur, but it worked, cause everything is gone!
Right now I'm in the process of zipping up the Viper XL ROM (thanks for the recommendation barondebxl, it looks awesome!), which I'll put onto my SD card and wipe/flash from there. (on my Mac now).
Hopefully it works!
I'm unable to flash ROMs for some reason. It doesn't give an error, just says that it failed. Any ideas?
elijahpr said:
Get into the bootloader screen, hit factory reset.
Click to expand...
Click to collapse
No no no. This is what is corrupting your sdcard. Only do a factory reset in TWRP or once booted up. Start over and format again. Then copy over your rom.
When you and a few others mentioned doing it, what were you referring to?
I've tried three different ROMs now, and each fails without saying why in TWRP.
Problem solved! Got the stock RUU back on there and it works perfectly. Just re-rooted and unlocked again. Round two..
Hey everyone,
Yesterday i tried flashing the latest CM12 nightly straight onto my Moto G over stock KitKat. After i flashed the ROM, i tried booting and noticed it was taking a lot longer than normal to boot. Ten minutes had gone past so i tried rebooting it again and the same thing happened, just got stuck booting for ages.
So i decided to boot into recovery and do a factory reset to see if this would make any difference. But even after doing this the phone still wouldn't boot, so i decided to just flash the stock KitKat ROM back onto the phone and forget about all the Lollipop stuff.
The KitKat ROM wasn't on my phones storage so i downloaded it from the internet and flashed it via fastboot using and included Windows batch file. I've used this method numerous times to get me out of situations like this and it's always worked, but this time no!
Tried booting after flashing the new stock ROM and now it just keeps going to the 'Warning, bootloader unlocked' screen and then booting back in a loop.
When i boot into ClockworkMod recovery it gives me these errors:
Can't mount /cache/recovery/log
Can't open /cache/recovery/log
Can't mount /cache/recovery/last_log
Can't open /cache/recovery/last_log
Can't mount /cache/recovery/last_install
Can't open /cache/recovery/last_install
And if i attempt to format /data, it says this:
Error mounting /data
Error formatting /data
I hate asking for help like this but unfortunately i don't have much option this time, no idea what to do despite searching forums for many hours.
Please help, any advice would be greatly appreciated!
Bump
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Pursain said:
You can try getting into fastboot and run commands fastboot erase userdata and fastboot erase cache from your computer to pretty much factory reset the phone.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
V3-571G said:
Thanks for the response. I tried entering the commands you suggested but the problem is still the same, phone stuck in the 'Warning, bootloader unlocked' loop. Does anyone have any other ideas? Really need some help with this, my little Moto has been dead for days!
And just an update on the situation, i noticed that if i go into CWM and select 'Wipe and Format Options' then 'Custom Format Options', choosing to format the cache and /data/media (/sdcard) options will stop the errors stated in the original post, but when i try flashing the ROM again the errors come straight back!
Click to expand...
Click to collapse
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Pursain said:
So sad to hear your Moto dead for the last days. Could you tell me more about your Moto? Can it turn off? Get into fastboot? Do you have recovery (stock or custom? Etc.
Sent from my Moto X 2014 Pure Edition
Click to expand...
Click to collapse
Yeah it sucks having a pretty much lifeless Moto, kinda scary as well not knowing if i'll be able to get it working again! But in response to your questions, i can turn it off and get into fastboot, i'm also able to boot into my recovery which is Philz Touch (ClockworkMod). If you take a quick look at the original post, i updated it a short while ago to show more details about the errors which are displayed.
Bump, still dead!
V3-571G said:
Bump, still dead!
Click to expand...
Click to collapse
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
classic757 said:
If you can get into fastboot you can flash the stock firmware (not backup) back onto your phone that way. I have used fastboot many times to restore my xt1028 Moto G many times after seemingly bricking it. You will need the stock firmware for your phone to do this.
Here is a tutorial:
http://forum.xda-developers.com/showthread.php?t=2542219
and here is a link to moto firmwares:
http://motofirmware.com/
Hope this helps.
Click to expand...
Click to collapse
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
V3-571G said:
Thanks for taking the time to respond to my request for help. I have already tried flashing the stock ROM via fastboot mode but it makes no difference to the situation, even though the new ROM flashes perfectly without error, when i try to boot it just gets stuck in the reboot loop on the 'Warning, bootloader unlocked' screen. I have no idea what to do now!
Click to expand...
Click to collapse
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
classic757 said:
I would suggest you try to install a custom recovery through fastboot (I use TWRP 2.7.1.0)
Just replace the stock recovery with TWRP in the fastboot file and use the command "flash recovery recovery.img" then reboot into recovery(hold power and volume down button down together for about ten seconds, release and you should see the fastboot screen. Then press recovery and then wipe>advanced>wipe ONLY cache and dalvik and then reboot)
See if that does the trick.
Click to expand...
Click to collapse
lost101 said:
Try this: http://forum.xda-developers.com/showpost.php?p=58116154&postcount=14
You have not stated your model. Don't use batch files to fastboot flash the firmware. Make sure the image is 4.4.4.
Click to expand...
Click to collapse
Thanks very much for the responses. Unfortunately i already had Philz ClockwordMod recovery installed on the phone and had attempted the various wipe options a number of times without any success. However, i thought that as i'd only tried flashing the UK ROM to the device, i would attempt flashing a different ROM just to ensure there wasn't an issue here somewhere. I downloaded the stock US ROM and after extracting the archive i ran the Windows batch file to flash the files onto the phone. After the process had completed i rebooted the phone (Didn't bother going into recovery and wiping/formatting cache) and to my surprise the phone booted up completely fine! So weirdly it seems that just flashing a different ROM did the trick. But anyway, my Moto is alive again now, i'm very pleased to say the least!
I know there is another very similar thread that was just opened(http://forum.xda-developers.com/oneplus-one/help/completely-stock-oneplus-one-stuck-t3396207), but his solution didn't help me so I'm making this thread.
I really need to save my internal data, so only as a last resort will I wipe userdata to save my phone.
First of all my phone is completely stock. Locked bootloader, unrooted, stock recovery, and stock rom. Last thursday(June 9th), I got the CM13.1 OTA update which I installed and everything went normal. It finished installing, restarted and booted up, optimized apps, rebooted, but then optimized apps again and again. I thought it might help to just reboot my phone, but it didn't. So I immediately started looking around for solutions.
I can boot into recovery and fastboot mode and since I can boot into recovery I started with wiping cache(Stock Recovery>>Factory reset>>Wipe cache partition). It took ~20mins which seemed like an unusually long time, then I rebooted and it still got stuck in the "optimizing apps/reboot loop". Next, I set up USB drivers, ADB, and fastboot since it seems to be very important to have those set up. I used a few guides to get them properly set up and I checked that they were correct by checking that the cmds "adb devices" and "fastboot devices" returned my device, which they did. I saw someone saying he saved his friends OPO by just ADB sideloading a CM zip file, so it looked hopeful in my case. I downloaded cm 13.0 and 13.1 zip files and tried sideloading them with the cmd "adb sideload cm13.zip". I tried both and they both got to around 50% complete and the install failed. Some of the red text said, "Package expects build fingerprint of oneplus/bacon/A0001:5.1:6.0.1..... & E:Failed to install /sideload/packages.zip ". Next I tried installing TWRP, which looks like it requires an unlocked bootloader to flash it(even to to just boot into it). From all my research it looks like there's no way to unlock the bootloader without wiping data. Even the OPO toolkit says you need to wipe data to unlock your bootloader.
One thing I haven't looked too much into is using fastboot to save my device. This guide http://www.technobuzz.net/fix-bricked-dead-oneplus-one-easily/ shows to flash userdata userdata_64g.img, which I assume wipes userdata.
Maybe I'm just overlooking some simple fix, but if anyone can help me I would be eternally grateful.
Edit: I need my phone working and I'm tired of waiting for help, so I just did a factory rest. Also I've been getting tons of conflicting advice. Thanks everyone for the help anyways
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
mastersen901 said:
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
Click to expand...
Click to collapse
download and install the 15 second adb/fastboot installer (http://forum.xda-developers.com/showthread.php?t=2588979)
It'll create a folder: C:/adb, In that folder you can open a cmd prompt window to send cmds to your device through adb/fastboot. that folder is also where you place files that you want to flash or boot into.
Also for the USB drivers just download the oneplus one toolkit, or use this guide: http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
the opo toolkit is in the 2nd method
Still looking for help. Phone status: After sideloading cm 12.1 it boots up but I get tons of errors saying com.android.phone failed/ android.system.acore failed which make my phone inoperable, also my phone usually reboots after ~10 seconds after booting up and getting errors.
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
itechy said:
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
Click to expand...
Click to collapse
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
woodhaus said:
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...e76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
Click to expand...
Click to collapse
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
itechy said:
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
woodhaus said:
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
Click to expand...
Click to collapse
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
itechy said:
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
Ohh! thanks! I was looking for this!
I just got around to sideloading the cm 13.1 zip. I'm still getting a bootloop /:
Edit: My phone reboots and optimizes apps after getting hung up on the cyanogen boot screen for a while.
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
hibernick said:
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
Click to expand...
Click to collapse
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
saurav007 said:
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
Click to expand...
Click to collapse
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
hibernick said:
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
Click to expand...
Click to collapse
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
woodhaus said:
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
Click to expand...
Click to collapse
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
hibernick said:
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
Click to expand...
Click to collapse
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
woodhaus said:
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
Click to expand...
Click to collapse
Oh, thanks. I didn't even go there.