Hi guys,
I went to update my ROM to the latest PA, which meant wiping the whole phone etc.
I downloaded the files etc to the phones storage and started wiping the phone. For some daft reason I wiped the SD storage as well, Duh!
So now I've got nothing on here to install
Is there anyway I can sort this out? or is it as the saying goes "you've got an expensive paper weight"
Any help is greatly appreciated.
Cheers
You could use adb sideload to get a ROM back on the phone, or use the factory image from Google to go back to stock. Plenty of threads on here on how to do both
EddyOS said:
You could use adb sideload to get a ROM back on the phone, or use the factory image from Google to go back to stock. Plenty of threads on here on how to do both
Click to expand...
Click to collapse
I managed to push a few files back onto my SD card to install them, but when i went through the recovery to do so, it kept saying the files where not existent?
Cheers
You're better off using adb sideload when in CWM to flash a new ROM. Get the ROM.zip in your adb folder (if you don't have adb/fastboot in your system path), boot the phone into CWM, select install using 'install zip using adb sideload' and then type:
adb sideload ROM.zip
It will then flash the ROM and should get you running again
EddyOS said:
You're better off using adb sideload when in CWM to flash a new ROM. Get the ROM.zip in your adb folder (if you don't have adb/fastboot in your system path), boot the phone into CWM, select install using 'install zip using adb sideload' and then type:
adb sideload ROM.zip
It will then flash the ROM and should get you running again
Click to expand...
Click to collapse
Just finished the sideload with the factory image and it came back with this error - E: Can't open /tmp/update.zip (bad)
Any ideas,
Thank you
You don't sideload the factory images, you run them as a standalone script. You can follow the full guide here:
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
You don't sideload the factory images, you run them as a standalone script. You can follow the full guide here:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Ended up sussing it in the end.
Really appreciate your help mate, cheers!
jayclarke94 said:
Ended up sussing it in the end.
Really appreciate your help mate, cheers!
Click to expand...
Click to collapse
No worries, It's easy once you know!
Related
I managed to wipe data/factory reset but on dalvik-cache and SD: ext partition, it says theres an error and I have to run both of them via adb. This is my first time actually wiping and the only video I could find was for a mytouch3g. Any help would be grateful.
Does anyone know? Im trying to get his wiped and install a custom ROM asap because Ive already had my phone out of commission for a few hours now.
a bidet may help.
actually I read on these forums that even though you get the error on dalvik that it wiped successfully completed. don't know about the other.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
flash a new recovery image
works everytime
PawkChop said:
Having trouble wiping
Click to expand...
Click to collapse
Sounds like a personal problem.
Just kidding, try flashing another one like was already suggested.
Im currently on version 1.5.2 and I got it from a guide I followed earlier to root my phone. I dont know where I'd get another one from though
The guide for rooting in the sticky is the exact one I followed and that brings the version I have. Unless Im not looking in the right place. Im sorry that Im a total noob at this, just trying to finally use some custom stuff on my phone.
http://rapidshare.com/files/360288584/recovery-RA-heroc-v1.6.2.img
Thank you very much. Now this is where its get even noobier. Where exactly do I put the file. Ive never flashed a ROM or a recovery image unless that guide involved it so Im kinda at a loss here.
I sent you a PM
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
PawkChop said:
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
Click to expand...
Click to collapse
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
HeroMeng said:
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
Click to expand...
Click to collapse
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
PawkChop said:
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
Click to expand...
Click to collapse
In ADB. If it shows a $ sign after you type adb shell, then type su. That might be your problem.
I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
z1gackly said:
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
Click to expand...
Click to collapse
what ive been doing is not making any backups (nothing important to save) and just using nexus toolkit to flash back stock and starting over and trying new way every time
still nothing though after about the 20th time
No idea then sorry. Stick with rooted stock?
z1gackly said:
No idea then sorry. Stick with rooted stock?
Click to expand...
Click to collapse
i think I might have to, ive never had any issues with custom roms (to speak of)
oh well, at least im happy with stock, i just love miui.
anyone else have answers please chip in, i give thanks!
harecurtis said:
I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
Click to expand...
Click to collapse
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
give me 5 minutes, while i try your method.
harecurtis said:
give me 5 minutes, while i try your method.
Click to expand...
Click to collapse
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
its a no go
anyone else wanna help me?
ive tried almost everything:/
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
harecurtis said:
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
Click to expand...
Click to collapse
If you're going that route.. you might as well just use fastboot to reflash recovery instead of the app.
Download the same image i linked to earily. While in the bootloader issue this command
Code:
fastboot flash recovery name-of-recovery.img
Make sure you have the Command Prompt in the same directory as the recovery image.
So say its in your downloads folder on your computer open CMD and cd to that directory.
Code:
cd C:\Users\Name\Downloads
Or just open yoru downloads folder and Shift + Right click and select "open command window here" then issue the fastboot command.
ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
didnt work(
harecurtis said:
didnt work(
Click to expand...
Click to collapse
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
ÜBER™ said:
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
Click to expand...
Click to collapse
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
harecurtis said:
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
Click to expand...
Click to collapse
Stop... dont use that.. -_-. Do it manually..
ÜBER™ said:
Stop... dont use that.. -_-. Do it manually..
Click to expand...
Click to collapse
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
harecurtis said:
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
Click to expand...
Click to collapse
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
ÜBER™ said:
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
Click to expand...
Click to collapse
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
harecurtis said:
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
Click to expand...
Click to collapse
Keep it unlocked.... otherwise you'll have to re unlock it...
So I downloaded new kernels and CM10 for my newly rooted N4. I did a backup before flashing the kernel and didn't pay attention to the error message saying cache was not found or whatever. But the kernel flashed fine and it booted up, nothing out of the whack. When I went back to flash CM10 it said the MD5 sum didn't match so the flashing processes didn't finish. Since my backup was ****ed up and the MD5 didn't match I couldn't restore the system either. Device will boot and will go into fastboot and recovery. Currently using CWM. If I turn on the device normally it will stay on the GOOGLE screen and it will not go into the boot screen. What do?
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
El Daddy said:
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
Click to expand...
Click to collapse
The CM10 zip itself is bad. How can I get another one on the phone? Or can I flash the CM zip without the file being on the phone? Thanks
Also, the error message popped up when flashing the CM zip was set_perm: some changes failed
E: Error in /sdcard/0/cmblahblahc zip
(status 7)
installation aborted
Should I turn off the signature verification anyway?
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
El Daddy said:
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
3 years of rooting and flashing stuff on 3 of my previous phones, there wasn't a time when I had to do this, or had to ask for help. Damn it.
Could you be a little more detailed in how do I go about doing so? As you can see my post count I am a bit of a noob Despite those 3 years. I just don't wanna mess up again, you know?
Thanks for everything dude
What screen should my phone be on? Just type that into the command prompt and it should work?
_thunderchild_ said:
What screen should my phone be on? Just type that into the command prompt and it should work?
Click to expand...
Click to collapse
Sorry I was out and about the past few hours.
You want to be in recovery. Custom recoveries allow you to use adb.
Rename the ROM something easy like CMrom.zip
Then put the CMrom.zip in the same location as adb on your computer.
Open the command window from that directory. (hold shift and right click; then choose open command window here)
Type the command: adb push CMrom.zip /sdcard/
It will push the file to the root of /sdcard/
Then you can flash it.
If that fails, use toolkit to download factory image and flash it through fastboot.
Oh man you guys saved my life. I cannot thank you guys enough. You won't believe how happy I was when I saw the bootscreen. Glad that was dealt with. Again thanks guys
Hey everyone I don't know if this is the right place to be posting this but I had the same problem as OP a few hours ago. I flashed LiquidROM and it got stuck on a boot loop. Needless to say, I panicked and used the adb push method since I decided to delete my AOKP ROM from my folder. Anyway, while panicking what I did was is before flashing, I backed up my entire SD card onto my laptop as ADB backup wasn't working and I pushed the entire folder using "adb push sdcard /sdcard/. Next thing I'm in recovery (CWM) and when I go through the flash from sdcard option, usually there were 3 options name 0/ and 2 others, however since I pushed the sdcard folder to /sdcard/ I get a 0/ at the top of the list which is where I would usually go but then underneath that I get all the folders I pushed! Is there any way to sort this out? I could attach pictures at some point for those of you who find it hard to picture what I'm describing Thanks in advance for any help!
Edit: just to add a couple of other things, my NANdroid had a checksum error so I cannot revert to stock without having to manually flash it which I cannot do at the moment due to a lack of WiFi, is there any way to sort this out? And the other thing was that for some reason sdcard cannot be unmounted at all in cwm, is it meant to be like that or am I missing something? Afaik its supposed to toggle.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Rizy7 said:
I tried to update a rom by dirty flashing but there was a problem when I tried to install the zip, now I cant get past the google logo. I have TWRP recovery and I can get into that.. What shall I do? I have a nandroid from back when I first rooted the device. Whats the best way to get everything working again while still keeping all my recent sd card data the same.
Click to expand...
Click to collapse
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Rizy7 said:
I wish I didnt delete the last working one when downloading the new one.. So do I just push the rom by adb? Any guides?
Click to expand...
Click to collapse
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
I used adb to push a file but I cant see it
thank god it worked
simms22 said:
if you have the previous working rom in your storage, just flash it. if not, you can push it to your device via the adb push option in twrp. you should always keep the last working rom zip in your storage just in case.
Click to expand...
Click to collapse
gee2012 said:
Try a data factory reset/wipe cache in recovery and reboot. You should be able to get into recovery.
Click to expand...
Click to collapse
username8611 said:
type this when you are in twrp and have the fastboot cmd window open
adb push "filename.extension" /sdcard/"filename.extension"
then flash the rom
alternatively, you can use sideload.
Click to expand...
Click to collapse
Thanks for your help guys
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Any help? Please
Goto cmw and install your ROM via adb.
Under option install zip there will be a choice for flashing zip via adb. Just select that in cmw and connect your phone to laptop.
Now in laptop you should have adb files in a folder and paste your ROM in that adb folder.
Next do as it is written in cmw and it will be flashed
Sent from my Nexus 4 using xda app-developers app
suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
You cant brick your phone as long as fastboot and recovery works.
boot into fastboot.
if your recovery is not working : reflash your recovery
Then boot into recovery and install rom via sideload;
From your pcadb sideload):
http://teamw.in/ADBSideload
Try wugfresh tool kit from here: http://www.wugfresh.com/nrt/
suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:
playya said:
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:
Click to expand...
Click to collapse
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes... sorry I forgot to add sideload and if you not sure what that is please use Google
Edit; My bad I see instructions and website for sideloading were posted area in here