Hi guys,
Long time reader, and great help to be found I hope!
I just bought a Z1C, followed successfully the full DRM backup, full root process and bootloader unlocked, from the guide posted : http://forum.xda-developers.com/showthread.php?t=2642081
I took a full backup of DRM keys and Nandroid.
I then went to load the Resurrection Remix ROM. I booted in to PhilZ recovery and did a full wipe and factory reset - "Ready for ROM". This completed successfully.
I then realized I forgot to copy the Resurrection ROM files onto my external SD and cancelled/exit out of PhilZ Recovery.
Now when I power up, all I get is SONY logo. I assume this is because the phone has no operating system due to the ROM being wiped and nothing being installed in it's place.
I can confirm I can get into Fastboot mode (Blue LED, but connecting USB and holding UP volume button) but nothing else!!!
If anyone has any ideas, I would really really appreciate it!
thanks in advance!
... ok, so I found a quick fix, sorry for the alarm. I just used ADB to flashboot a version of CWM6 and made it boot into recovery, copied the Resurrection ROM onto my external SD with a card-reader (seperate) then installed the ROM ... hooray! Now I can sleep.
Thanks to anyone who started reading...
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Rekoil said:
For future reference, just using fastboot to install a boot partition with a recovery on it is sufficient to fix these kinds of issues.
fastboot boot path/to/boot.img
or
fastboot flash boot path/to/boot.img
And for the record, with most recoveries you can mount your SDcard on your computer via USB, in CWM it is available in the mounts menu as "Mount USB storage"
Click to expand...
Click to collapse
Thanks for the tips. I'm a bit new to this thing ... I assume your commands above will create a separate partition for booting, but how do I get to that recovery screen? ... and I assume boot.img is a recovery boot file? Renamed from CWM?
My issue above was I couldn't load up anything (Sony logo appears, and nothing else, couldn't proceed to recovery screen by pressing UP volume) ... I only could connect to my computer in flash mode for Flashtools to read, and had to start the whole "root my phone" process again.
I am playing around with the stock Sony UK ROM, but I am keen to flash Aura's AURom or maybe another one ... is there a way that I can basically create a "rollback point" so that if I don't like the new ROM I can re-instate what I am playing with now? I really don't want to have to go through the whole root process again if I semi-brick again! Just want to do an easy "undo" ...
Many thanks for putting up with the noob-ness.
boot.img is an image of the kernel. Note that this command is only for unlocked bootloader.
Seems you are using dualrecovery (which resides inside /system) and since you wiped /system you couldn't get into recovery anymore. If you have unlocked bootloader you should use a custom kernel. You can use the one of [NUT] (same functionality as dualrecovery) or the one from Doomlord.
I really don't want to have to go through the whole root process again
Click to expand...
Click to collapse
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
zxz0O0 said:
You do realize that the root process with unlocked bootloader is as followed:
1. Flash custom kernel
2. Go to recovery and flash SuperSU zip
Click to expand...
Click to collapse
Exactly, and if you have saved your TA partition already, then you can always unlock the bootloader, root, and then relock bootloader by flashing your TA partition back.
Awesome, thanks guys for all the help. I will give the AURom a go and hopefully succeed this time.
One last question, what is contained in the TA backup, and what is in a Nandroid backup? From reading, TA is just a set of keys and Nandroid is a Rom backup?
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
zxz0O0 said:
TA backup is a backup of the Trim Area partition, inside of this partition there are DRM keys. Nandroid backup is a backup of various partitions (/system, /data/, etc.) but not TA partition.
Click to expand...
Click to collapse
Super thanks guys, much appreciated
Related
As simple as that
Another question: if I perform "format system" and then reboot, will I be left without recovery?
I bought my device already rooted, but I understand that there is some sort of stock recovery. Is it true, if yes, what does it do?
In case I reboot after formating system and there will not be recovery as I suspect, I will be able to flash recovery image via fastboot as usual, right?
thanks
Format system will format the system partition, not the recovery.
Recovery will remain intact.
Thank you, but I would really like to understand how it works:
I know that the Internal memory devides into 3 partitions: system ,cach, data.
Which are the ROM. (This "ROM" is actually just flash memory isn't it? and is rewritable)
Where is the partition of the recovery if so?
Are there more partitions than those 3 in there?
Now when I come to think about it, I still don't know where the radio partition is, and where the data of bootloader is located.
I would still like to know what happens if you perform "format boot". Is it the partition where recovery is sitting or it refers to the memory partitioning (aka Hboot).
and That too
I bought my device already rooted, but I understand that there is some sort of stock recovery. What does a stock recovery allow to do?
Click to expand...
Click to collapse
thanks
There are actually more than those 3 partitions =)
There is:-
HBOOT - This is the bootloader its-self and contains the partition table
Boot - Contains the Kernel and a ramdisk used during startup
Recovery - Contains the recovery image
System - Contains the ROM installed on the device
Data - The internal memory, apps etc stored here
Cache - Pretty self explanatory =D It hold the cache =P
Radio - (Not too sure if this is on the NAND or not) Tells the radio chip how to communicate with your carrier etc (as far as I'm aware, someone feel free to correct me)
If you format boot, the phone will just go right to the bootloader without actually loading Android, but with a custom recovery it can be fixed easily by reflashing the ROM, nandroid restore, or by using fastboot to flash an existing boot.img. (Just a note here, flashing a Kernel wont fix this as the scripts used try to extract some parts from the existing boot.img, which isn't there after a format =P)
Assuming that you have an S-OFF HBOOT (Alpharev) you can flash any of those partitions with an image, using Fastboot as you mentioned, however, if you don't have S-OFF, you would have to do it through the Recovery (and you can’t flash HBOOT through recovery).
The phone does come with a stock Recovery Image, but this is very limited, Can only flash update.zip signed by HTC (again, might be wrong here), factory reset (Wipe data), reboot the phone and possibly some others.
Using either ClockworkMod Recovery or Amon_RA's recovery will let you flash custom ROMs, perform nandroid backups + restore (Boot, system + data) and a few other fancy things like wiping individual partitions =)
Hope this helps!
Thanks alot! you've explained it very clearly.
I would like just correct a very tiny mistake, probably unintentional - Factory reset is "wipe data", not "format system + data".
I got the answers that I wanted and more.
thanks again
It was unintentional =P I corrected incase someone happens upon the post.
Glad I could Help
wrong thread
A phone being "bricked" means that there is no way in hell you can salvage it and you have a very expensive paperweight. Ok, so there's a 99% chance your phone is not bricked at all, but I hope this guide will help you figure that out. If you have any questions on terms, refer to the earlier Noob's Dictionary Guide in my sig. I am not responsible for anything you do to your phone.
PART ONE: Things You Should NEVER Do With Your Phone
Any of these things may cause your phone to be legitimately bricked.
1. Flash a radio for any other phone, even the IncS. Your phone will be bricked.
2. Pull the battery during a radio flash.
3. Flash a ROM for any other device.
4. Flash a kernel for any other device.
5. Do a Root/S-off method with no experience.
PART TWO: How To Tell If Your Phone is Actually Bricked
1. Does anything happen if you hold the power button down? If you even get to the splash screen, your phone can probably be salvaged.
2. Can you get into Hboot by holding Power and Vol Down? If yes, you can probably run a RUU and you'll be good.
3. Can you get into recovery? Then you are fine! Many newbies assume that "OMG mai fone wont turn on so its liek brik3d!!!111!"
4. Does your screen not turn on/ you get flashing LEDs? Your phone probably is bricked, with no way to salvage it.
5. Do partitions not mount? You probably have a hardware issue, so your phone needs to be replaced.
PART THREE: Fixing It (If Possible)
We will go from easiest fix to hardest.
1. If you can get into recovery, just restore a Nandroid and you're good.
2. If your phone is stuck at splash screen, just pull the battery, hold power + vol down until you are in Hboot. Then select recovery. Restore a Nandroid Backup. If it won't go into recovery, see Steps 3 and 4.
3. ***Especially for EXT4 Recovery Users*** If your boot image has been erased, recovery will not boot. Get the Android SDK working. Go to http://forum.xda-developers.com/showthread.php?t=1219246. Download the recovery image in the OP and put it in your android sdk tools folder. Hold Power and volume down until your phone is in Hboot. Plug your phone into your computer. Use this code:
Code:
cd C: \[insert path of android-sdk here]\tools
fastboot devices
fastboot flash recovery cwm-4.0.1.4-vivow.img
fastboot reboot recovery
Your phone should now be in CWM recovery. You can now restore a Nandroid. CWM will not restore any 4EXT backups, though, so be careful. You may also flash a zip.
4. If you can't get into recovery at all, follow these steps. http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/
If anyone has any corrections, suggestions, or comments, feel free to leave them!
Hi, I read this after trying to flash a firmware to in order to flash Android Revolution ROM. I made a NANDroid backup and I tried restore my phone back by with the back up I made and it says:
"Restoring Data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring Cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore Complete!"
I reboot my phone and it is stuck in bootloop. I can still boot into CWM Recovery so I am not exactly "bricked" am I? Is there a way to fix this? If so, how can I fix this?
LOL, there is no Android Revolution rom for the Inc2. And also, just download any rom, plug phone into computer, wipe in recovery, go to mounts and storage, mount USB storage, copy the rom to your sd, flash it, reboot.
myst3ry23 said:
Hi, I read this after trying to flash a firmware to in order to flash Android Revolution ROM. I made a NANDroid backup and I tried restore my phone back by with the back up I made and it says:
"Restoring Data...
.android_secure.img not found. Skipping restore of /sdcard/.android_secure.
Restoring Cache...
sd-ext.img not found. Skipping restore of /sd-ext.
Restore Complete!"
I reboot my phone and it is stuck in bootloop. I can still boot into CWM Recovery so I am not exactly "bricked" am I? Is there a way to fix this? If so, how can I fix this?
Click to expand...
Click to collapse
Did you try to restore a back up from a different phone? Or did you port arhd yourself?, if it's, just restoring data, it's not wonder you have a bootloops for a snack
Hello I'm new to the nexus line and recently upgraded form a SGS. my phone is Rooted, unlocked boot loader and running the most recent version of CWM 5.5.0.4. I'm running the GSM version of the Nexus.
My question is how do I flash the my first rom? When I boot into recovery and click install zip from SDcard i get "E: Can't mount /sdcard/" I am also unable to mound the data partition within. windows drivers are installed for both fastboot and adb so I can flash that way, i'm just wondering what the exact steps are and if that error mounting data is normal.
I also downloaded the most recent franco.Kernel as I want to run that, I know how to flash that with fastboot but wasnt' sure if that is how you would flash a rom with the nexus, on the SGS i used to use odin.
Thanks and sorry for the noobness.
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
yiannisthegreek said:
How did you "unlock fastboot" and "root" and "install CWM"? Did you use one of the "Tool Kits"?
Do you have ROM Manager installed on your device?
Click to expand...
Click to collapse
Sorry, Yes I have ROM Manager installed and its' paid for.
I unlocked my boot loader using fastboot oem unlock, I rooted by using an app because I couldn't mount the data partition in recovery so had to use some app some guy made that downloaded the su.zip from clockwork and flashed on it's own.
I installed CWM using fastboot.
fastboot flash recovery recovery.img
it's the dam data partition that i'm really having trouble with, i'm just wondering if this is normal, all the posts on the web say to flash a zip by choosing "choose zip from scard" but mine wont mount???
I should also mention that my entire device is encrypted.....that is whats causing it isn't it?
I'm not 100% sure but it could be that you flashed the wrong recovery.
According to this thread
http://forum.xda-developers.com/showthread.php?t=1357642
the recovery for the GSM version is 5.5.0.2 and not 0.4.
I would flash the correct recovery then try again.
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
P4p3r1n0 said:
You can not mount sdcard from CWM recovery (don't ask me why, I don't know.. maybe because it is not supported yet ..)
anyway, do like me, use CWM 5.5.0.2 and then try again toflash zip files .. It works for me
Click to expand...
Click to collapse
He posted it on his Google+ account here:
https://plus.google.com/112476065271141473049/posts
I'm starting to think it's my encrypted phone, technically when I boot I have to decrypt the device before it boots into android.
I'm going to factory reset and see if that helps. I have a feeling that is what my problem is
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
spectre85 said:
OK so that was the problem, the data partition was encrypted (now that I think of this it makes sense that it wouldn't mount) anyways, for whatever reason a factory reset from android wouldn't work. I removed the "recovery-from-boot.p" file from my system folder originally so the CWM image would remain in tact.
anyways, I flashed the original recovery over the CWM recovery, preformed a factory wipe (which is the only way to decrypt your phone) then flashed CWM back on and now I can mount the data partition
what a pain in the ass, guess I wont be encrypting the phone any time soon, I wish there was an option to decrypt the drive and then get into recovery....wouldn't have this issue.
Click to expand...
Click to collapse
It is possible now on 4.1.2 to decrypt the device. You must provide a password for dectypting (chane from unlock pin to passw).
Hi
Would it be possible for me to do the above without having to connect my phone to my laptop every time?
I know I have would have to load the boot.img first from a cmd window whenever i wanted to try a new rom, but was just wondering if I'd have to do that with it already on the internal sd card.
Any help would be appreciated.
Wiggo
Unless the backup you're restoring uses the same boot.img as the one you're using you will need to flash the one from your backup (using fastboot) when you restore it.
Recovery doesn't have permission to write to the boot partition; this means whether you're flashing a ROM or a backup from recovery the boot.img won't be written and you'll have to do it manually.
hopscotchjunkie said:
Unless the backup you're restoring uses the same boot.img as the one you're using you will need to flash the one from your backup (using fastboot) when you restore it.
Recovery doesn't have permission to write to the boot partition; this means whether you're flashing a ROM or a backup from recovery the boot.img won't be written and you'll have to do it manually.
Click to expand...
Click to collapse
That makes sense. Thanks very much for your help
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
nodnarb said:
Hello all, I've searched around and tried many different things to resolve my little problem. I'll try and list out all the details of what I've done and perhaps someone could help me find the error in my ways.
I've got a - VZW Droid Incredible - S-On - Unlocked. The H.boot Is 1.02.000 Radio is 2.15.10.07.07.
*History*
I started with a bootloader locked Droid that was stuck in a boot loop that started after a failed OTA update. The H.boot was lower too, I'm not sure what it was. The device would only boot into the stock recovery and factory reset wouldn't help. It just hung on the white HTC screen.
To fix that I tried to flash a variety of stock images from the SD but each time it failed with a versioning error. I assume that was due to the bootloader being locked and on an OLD h.boot After some troubleshooting I was able to issue a fastboot oem reset command and I was able to boot into the OS.
So then I began working with a factory default Droid running 2.2
Once I was in the OS I used the HTC Dev site to unlock the bootloader. That all went well. I was running Stock 2.2 with a unlocked bootloader. Next I flashed a custom recovery. copied a ROM to the SD and booted into recovery to flash CM 7.2. I began to run into problems at this point.
Then and Now when I boot into recovery (TWRP, or ClockworkMod) I'm unable to mount cache, internal SD, External Sd, nor can I toggle USB. I'm not really clear on what causes that. However because I can not mount the SD I can not flash a ROM, and my attempts to get back to a working phone have been unfruitful thus far.
I created a problem at this point when I wiped System. I ASSUMED that I could drop the stock image back onto the SD card and get back to factory but that doesn't work. Because I wiped system each time I reboot the phone I go directly into recovery.
( I really didn't think that it would mount system and wipe it because it wouldn't mount the other partitions... WRONG)
So now I have a inaccessible SD card while in recovery, a wiped system partition (and boot), and no clear way to get back to good.
I've downloaded numerous stock images, formatted two different SD cards FAT32 saved the stock image to the SD Card as PB31IMG.zip and booted to HBoot watched the progress bar load/complete then it stops and I'm left sitting at the bootloader screen. I can reboot expecting to boot into a stock system but each time I'm dropped back into recovery and recovery will tell me that I have no loaded OS, to me that means the PB31IMG didn't write to system, but IDK.
A RUU won't work because I can't boot into android.
I did extract the system.img and the boot.img from a stock image and used fastboot to write both of those partitions without error, but that didn't help either.
Does anyone have some Thoughts or advice on what to do next?
Many thanks,
Click to expand...
Click to collapse
Try this, reformat your sdcard fat32 with a pc. Then place only this file http://dinc.does-it.net/Stock_Images/4.08.605.15/PB31IMG.zip on the sd in no folders (Do not rename). Boot to hboot (vol down + power), it should find the file and prompt you to press vol up to install. I think your issue with the ruu before was that you were trying to flash an older version than you already have installed. If that dosent work try fastboot flashing cwm again, and see if it can mount the sd then.
Thread moved. Please post all questions here in the correct section of the forum.
Thanks
AvRS
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
shivaagarwal1 said:
Hi... Mine is incredible s unlocked bootloader... I have cwm installed but now I want to flash 4ext touch.. I tried flashing it from command but it failed.. Also I grief installing by 4ext updater, it did flashed 4ext but didn't overwrite cwm... And hence after pressing vol and power button only cwm comes... Pls help with this..
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
You'll probably get better help in the Incredible S section. This is for just the plain olé Incredible.