i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Does adb work?
Wipe cache?
If you would have read through the thread, you would have seen that the ROM doesn't boot past the Google logo. The ROM doesn't work.
Sent from my Nexus 4 using xda premium
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Roshi69 said:
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try configuring the drivers from here. Can you mount USB Storage? Does your computer recognize fastboot?
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Roshi69 said:
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Click to expand...
Click to collapse
Can you get into fastboot?
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Roshi69 said:
i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Click to expand...
Click to collapse
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-It will ask u where to push ur file to.. just type /system/
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Roshi69 said:
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Click to expand...
Click to collapse
I think I was wrong. You can't push/flash a ROM through fastboot. Are you absolutely sure that you can't mount your SD card to your PC in TWRP recovery? I can't mount my SD using CWM but I can using TWRP.
enyceckk said:
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Click to expand...
Click to collapse
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Roshi69 said:
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Click to expand...
Click to collapse
Do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " ADB mode List of devices attached" If you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. it's the #1 option
When pushing the file, u should be in TWRP (where u see install.. wipe etc..) and mount /system/ should have an X on it.
enyceckk said:
do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " adb mode list of devices attached" if you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. It's the #1 option
when pushing the file, u should be in twrp (where u see install.. Wipe etc..) and mount /system/ should have an x on it.
Click to expand...
Click to collapse
it worked!!! Thank you so much!!!
Hey Xda, so I ran into a little problem earlier today.
After creating a backup on my PC with the nexus 4 root toolkit and rotting and flashing TWRP I attempted to install a rom but since it was my first time using TWRP (Im used to CWM) i accedently wiped my internal storage and my OS and now im stuck in TWRP since i have no OS to boot to.
Is there anything I can do or is all hope lost?
Thanks in advance
Gabrielvbrz said:
Hey Xda, so I ran into a little problem earlier today.
After creating a backup on my PC with the nexus 4 root toolkit and rotting and flashing TWRP I attempted to install a rom but since it was my first time using TWRP (Im used to CWM) i accedently wiped my internal storage and my OS and now im stuck in TWRP since i have no OS to boot to.
Is there anything I can do or is all hope lost?
Thanks in advance
Click to expand...
Click to collapse
Yes, install adb platform-tools and push a rom to the sdcard: adb push namerom.zip /sdcard/. Or try TWRP sideload http://teamw.in/ADBSideload.
Gabrielvbrz said:
Hey Xda, so I ran into a little problem earlier today.
After creating a backup on my PC with the nexus 4 root toolkit and rotting and flashing TWRP I attempted to install a rom but since it was my first time using TWRP (Im used to CWM) i accedently wiped my internal storage and my OS and now im stuck in TWRP since i have no OS to boot to.
Is there anything I can do or is all hope lost?
Thanks in advance
Click to expand...
Click to collapse
Dude the same thing happened to me the very first time but here's what I did I hooked up my phone to the PC and ran wug nexus tool kit and performed back to stock. And it worked like a charm hope that helps if you're still stuck there:thumbup:
Sent from my Nexus 4 using Tapatalk 2
Just posted a good reply from someone on the Nexus 10 forums who did the same thing:
espionage724 said:
I tend to take a FAT32-formatted flash drive, USB OTG cable, throw a custom ROM, Kernel, and Gapps onto the flash drive's root, reboot the tablet to TWRP, wipe everything (except USB OTG) and format data, reboot back to recovery, and then install ROM, Gapps, and Kernel (in that order).
In other words, if you have a flash drive and OTG cable, you can recover your device pretty easily If you don't have these though, you can adb push the zip's over to /sdcard I believe; it's been awhile since I've done this.
If you want to go back to factory stock, you can grab the latest factory image from the link shimp208 provided, and should be able to run the flash-all.bat included (may have to have platform-tools in PATH if running Windows, or cd into the folder).
Click to expand...
Click to collapse
Edit: I'm not entirely sure how USB OTG is on the N4 though. If it doesn't work, then adb push should be fine.
espionage724 said:
Just posted a good reply from someone on the Nexus 10 forums who did the same thing:
Edit: I'm not entirely sure how USB OTG is on the N4 though. If it doesn't work, then adb push should be fine.
Click to expand...
Click to collapse
Interesting, This is indeed a truly "clean install". Any idea if this method would this work in CWM. Sorry to OP for jacking your thread.
I myself have done this before, I hope you get through it. Goodluck
i deleted my rom so my nexus 4 just boots up and google image loads how do i install back my stock rom and also usb connection is also not possible as it does load any rom please help me
Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4
spaceman860 said:
Use adb to push a ROM to your phone and flash it or use fastboot and flash the system.img
Sent from my Nexus 4
Click to expand...
Click to collapse
can you explain indetail since im just a beginner
How did you root your phone did you install the drivers on your computer or did you use a toolkit
Sent from my Nexus 4
sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
Do you have a computer? You said something about usb support. You need to plug your usb cord into the computer and connect your nexus 4. It gets a lot more complicated in the next few steps so let me know if you can plug in your nexus 4.
sum93 said:
can you explain indetail since im just a beginner
Click to expand...
Click to collapse
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).
Read this thread - http://forum.xda-developers.com/showthread.php?t=2010312
how to push rom file inside the intenal momery
kbeezie said:
There's 3 main components.
1) Bootloader
2) Recovery
3) System
If you have previous rooted your rom, then you most likely have a custom recovery, such as TWRP or CWM.
If you can get into recovery, then you can mount your data partition, and do something like
adb push name-of-rom-file.zip /sdcard
and any other zips you need.
From there for clean-measure you can format /system , /cache and dalvik-cache, then go to "Install" and choose the rom zip you wish to install (though if you plan on using a rom different than your original you may wish to do a 'factory reset' in recovery to clean the main /data area to avoid settings conflicts).
Once you've installed the roms + addons you want, you should be able to reboot into it.
If you did not root your rom, and likely do not have a custom recovery, that's something that can be installed via fastboot from the bootloader, so let us know which options you have available to you.
This can go easy or hard depending on how much knowledge you have of ADB and Fastboot, or if you instead used a toolkit to do it for you (meaning you wouldn't easily know where to run adb/fastboot).
Click to expand...
Click to collapse
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive
sum93 said:
i did the root through nexus tool kit so how do i copy rom files inside internal memory and also how do i mount the drive
Click to expand...
Click to collapse
This is why you shouldn't use toolkits without knowing the process behind it read this guide it will show you how to fix it
http://forum.xda-developers.com/showthread.php?t=2010312
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
Sent from my Nexus 4
This is the first time I'm using a device that doesn't have an external SD card, but I've all along understood that the internal SD card does not get wiped when you do a factory reset, and I'm sure I read that again on another thread just the other day.
My N7 is rooted using Wug's toolkit, with CM10.2 and Bulletproof kernel.
Yesterday I decided to do a factory reset (under Settings, Backup & Reset, Factory Data Reset), but after I did it, all the stuff I had on the internal SD was gone, including my backup files, the ROMs I had transferred there, etc.
Surely this is not meant to be the case, is it??
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
sfhub said:
internal sdcard used to be a different partition.
Now it is just a directory in your /data and the "sdcard" is an emulated sdcard.
I know stock ROM and stock recovery wipes /data and everything in it including the virtual sdcard.
TWRP recovery will only remove the /data user stuff, leaving the virtual sdcard alone.
Which recovery are you running?
Click to expand...
Click to collapse
Thanks for that! (Thanks coming your way). Well, better to know now than later! The down side is that I lost my CWM backups and my Titanium Backup files, but the good thing is that I think I have a TWRP backup that's on my computer.
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
oohyeah said:
I'm using TWRP, but not really liking it, cos I cannot boot into recovery from the phone and have to keep relying on the Wug Toolkit. I've just downloaded CWM and will be switching to that.
Click to expand...
Click to collapse
I am not sure what issue you are having with TWRP, but you can flash it to the recovery partition and boot to it automatically. If that's the only reason you don't like it, I'd work on fixing the install rather than jumping to another recovery.
oohyeah said:
So the moral of this story is that if we are to do a factory reset, we should do it via recovery, correct? I'm presuming CWM will also leave the virtual sd card alone, yeah?
Click to expand...
Click to collapse
I would probably do it from recovery. I don't know what CWM does on this platform as I've only used it on other platforms.
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Sent from my Nexus 7 using xda app-developers app
geckocavemen said:
What do you mean you can't boot into recovery with twrp? I'm using twrp and have no problem booting into recovery.
Click to expand...
Click to collapse
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign. I remember doing some searches and it seemed like this was normal. I remember the reason was that the N7 would always rewrite the recovery or something. From your responses, I'm guessing it's not normal?
The only way I could get into recovery was using the Wug toolkit using USB debugging/ADB, which really sucked, cos if it bootlooped and I can't get into the system to turn on USB debugging, then I'm not sure what I would do (though I read there's some way around it or something). I had never encountered any such thing with all my many other devices which all run CWM.
So what's up with all that?
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
User_99 said:
"su" enter' next line "reboot recovery" in the Android Terminal window should also boot your device into recovery
Click to expand...
Click to collapse
This will work fine. If you have no aversion to installing apps, Rom Toolbox Lite gives you power widgets you can put on your desktop then go to recovery with one touch. I use Quick Boot PRO, although the free version of that all may do recovery also. One might work for you until you want to play with mods.
Sent from my Nexus 7 using Tapatalk 4
oohyeah said:
When I try to boot into recovery, it ends up showing a dead android with the red triangle "!" sign.
Click to expand...
Click to collapse
That is stock recovery.
You need to get rid of /system/etc/install-recovery.sh
You can get rid of it by hand, or just install SuperSU from TWRP. Then flash TWRP to the recovery partition.
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
oohyeah said:
Thank you everyone for your input!
I'm happily back on CWM right now. If I revert back to TWRP next time at least I'll know what to do!
Click to expand...
Click to collapse
None of your blunders has anything to do with TWRP.
khaytsus said:
None of your blunders has anything to do with TWRP.
Click to expand...
Click to collapse
OK let me get something straight.
Obviously, the factory resetting that wiped out all internal storage (the original point of the thread) has nothing to do with TWRP, and I never said it did. On this point though, I'm surprised that it doesn't seem to be more well known that a factory reset would do wipe out all your data (did several searches and only found 'confirmations' that your internal SD data would be left untouched), though I'm glad that I know it now.
The suggestions on different ways to boot into recovery were helpful, though I believe that I would still have encountered the dead android, or would I not have?
What's certainly still not clear to me though is regarding the problem of not being able to boot into recovery and getting the dead android with the exclamation/triangle. After the first few replies, I expected to hear that this was NOT meant to be the case and that I did something wrong in the process or whatever.
However, what I seemed to get was that this is the expected behavior, and what I needed to have done was to "get rid of /system/etc/install-recovery.sh".
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
oohyeah said:
So let me ask these questions for clarification:
1. Is the dead android normal, given what I did/didn't do?
2. Is deleting /system/etc/install-recovery.sh part of the process of installing TWRP in order to be able to boot into recovery?
3. Would I also need to get rid of /system/etc/install-recovery.sh if using CWM?
(so far it doesn't seem to. After installing CWM I'm not getting the dead android and I didn't delete the install-recovery.sh).
Thanks. And just to be clear, I hope no one takes it the wrong way that I'm bashing TWRP or anything, because I"m not. Just been a long time user of CWM and this is the first time using TWRP and encountering the dead android.
Click to expand...
Click to collapse
Dead android = stock recovery, so normal there.
When you flash a custom recovery on a stock ROM, there is a file, /system/etc/install-recovery.sh, or I actually prefer just renaming /system/recovery-from-boot.p, which will automatically verify your recovery image and restore it to stock if it doesn't match. So you must always remove this file, or the ROM will restore the stock recovery on boot.
TWRP makes it easy to remove either file by mounting /system in read-write mode and using its built-in file manager to remove it. You can do the same in CWM using adb.
As for point 3, yes, try to reboot into recovery again. If you didn't remove (either file), you'll find stock recovery again.
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
oohyeah said:
Thanks, Khaytsus. I booted into recovery (long press power button, reboot menu, recovery), and it booted straight into CWM, like it always has with my other devices. (And to confirm, I have not even looked for the install-recovery.sh file, let alone removed or renamed it.)
So far it seems to me that TWRP requires removal of install-recovery.sh, whereas CWM does not, but this doesn't seem to be what you guys are telling me is supposed to be the case.
Click to expand...
Click to collapse
It really depends on what ordering you do your actions in.
/system/etc/install-recovery.sh doesn't exist on a stock factory shipped system.
It only gets put in place after you install an OTA. If you do all your upgrades using the factory images, you'll never encounter it.
What it does is during your boot process, it will check to see if your recovery is different than what it expects (ie stock). If so, it will install stock recovery by taking the stock kernel and patching it.
If any of the following are true, it will not overwrite your recovery:
/system/etc/install-recovery.sh is missing (or modified to not run as the original file)
/system/recovery-from-boot.p is missing
you are not running the stock kernel
The most common way for install-recovery.sh to be missing is you always used factory images.
The most common way for install-recovery.sh to be modified to not do the original function is if you installed SuperSU. It will overwrite install-recovery.sh with its own.
So in all the back and forth, it is quite possible you got rid of install-recovery.sh or had it modified simply by installing root.
If you then subsequently installed custom recovery, it would stay in place.
Previously you were installing TWRP and flashing it onto the tablet, but upon booting into android, install-recovery.sh realized it wasn't stock recovery, and overwrote TWRP with stock recovery.
That is why whenever you rebooted, you got fallen android (which is stock recovery)
If the way you installed cwm is to use "fastboot flash recovery cwm.img" then the only reason it is around is because something else you did got rid of or modified install-recovery.sh. cwm would be no more immune to install-recovery.sh than twrp was.
oohyeah said:
Oh one more thing, I think I lost root after the factory reset!!
I checked my All Apps and SuperSu wasn't there anymore. Just rooted it again using Wug kit.
Click to expand...
Click to collapse
Just to clarify, you didn't lose root. You just lost the supersu app, a root permission manager, because it was installed to your /data partition. The su binary was still in /system, all you would have had to do was install supersu from the market.
I'm not sure what else you were expecting from a "factory reset"
creaturemachine said:
I'm not sure what else you were expecting from a "factory reset"
Click to expand...
Click to collapse
Did you read the thread? He explained his reason for expectation quite well.
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Skaziwu said:
I just started up on a Nexus 4, and was also surprised to see this. Coming from a Galaxy S2, the "sdcard" being left intact was pretty convenient when flashing from ROM to ROM. Albeit, leading to some messiness. When did Nexus change to this behavior?
Click to expand...
Click to collapse
Depending on which level you are looking at, it didn't really change the behavior, but rather how your data is organized.
Factory reset has always wiped out /data.
On older devices, they put the /sdcard in a separate partition and formatted fat32.
These are the ones that were surviving a factory reset.
On newer devices, the internal /sdcard is starting to migrate onto a directory in /data and the "sdard" you see is "virtual". Since it is on /data, when you wipe data, the virtual sdcard is also wiped.
Some recoveries try to simulate the previous behavior by doing a "rm" of every directory except the virtual sdard when you choose to wipe, instead of the erase/format that Android is doing.
The advantage of keeping the sdcard as a directory under /data is you don't need to decide how much space to split between the sdcard and your /data. Also permissions on files are more flexible being in an ext4 filesystem. Finally since everything is emulated and accessed via MTP, you don't need to unmount the filesystem, so your PC can access it.
There are also cons with this approach, but that is what Google is going with.