Hi, I have two other threads on this problem but no answers yet - so sorry for cluttering up the forum. I moved one of my system files by accident and my phone will not start. I can access the bootloader and the recovery by using the hard keys.
It looks like I can do a factory reset thru recovery which will be my last resort. The recovery menu also has an option to "apply sdcard:update.zip". What does this do? Can I plop one of my recent backups into a folder on the sdcard and restore that way?
If I do need to reset is it better to do it through this Recovery utility or should I use RSD Lite? Which SBF is best for a US Defy that had the 2.2 OTA update?
I think I just need to push my original system file (I DO have the original on my PC) back to the phone. I have SDK and know how to do simple commands but I can not get SDK or ADB to recognize my device.
Many thanks in advance!
Wipe/Factory reset won't recover removed system files. It just clears the data partition.
Which system files had you removed? If you had removed anything in the pds folder, you probably have to send it back to factory. If not, just flash any compatibile 2.2 sbf (not China/Korea) with rsdlite should recover the phone.
Thanks. I messed up the build.prop file which sits in the system folder. I was trying to get Netflix to work. Well, I could not get Netflix to work and I also lost Swype so I tried to put my original build.prop file in the folder. Whatever I did, I did it wrong because the phone flashes the motorola logo then goes to a very dimly lit blank screen.
So perhaps the best solution is to flash a sbf then reinstall the clockwork recovery thing and then restore my backup (which had all my apps) etc.
Is there anyway to just push that one file back on to my phone?
Thanks for your fast reply!
If you've installed the bootmenu you can easily put that file back using ADB. However if you don't have access to bootmenu OR custom recovery you can't do that OR put it back via update.zip.
If you were on the US official 2.2 Just flash the 3.6.360 sbf from here http://sbf.droid-developers.org/umt...1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf.gz
then just do the official update OTA then root, install bootmenu, restore whatever backups you have
Thanks y'all. I ended up flashing a sbf via RSD Lite. At first, I was getting the message about flash fail... no initialization file... I was using version 4.5. I then saw a later version 4.9 and that worked. I was starting to sweat!
After the flash, I ran Superoneclick again. Then I installed the DefyRecovery and then I restored my backup (BTW is the backup that Defy Recovery does still called a nandroid?).
Phew! Everything is just fine. So, for the future, I should install the bootmenu?
I am not sure I will be so adventurous but this whole journey began with trying to get Netflix to work. *Sheepish smile*
Thanks so much!
I would HIGHLY recommend installing bootmenu. If you ever flash an SBF it wipes out the bootmenu but if you encounter disaster like you just did....... It's a life saver for sure!
Related
hi all,
so I saw that unrevoked3 is out and read that it makes installing other ROM's really easy.
so I installed the windows hboot driver and unrevoked3 automatically installed ClockworkMod 2.5.0.1
i didn't really know what todo next so I did a nandroid backup... that took a while, so I assumed it had backedup everything (old rom + apps + user settings etc)
anyways then I rebooted back into my stock ROM and copied opendesire 2.2 onto the SD.
then I rebooted into ClockworkMod and installed the opendesire2.2.zip
then I tried booting normally and it sort of sat on the initial screen for a long while, so I rebooted back into CWM and did a wipe/factory reset.
then rebooted again.
this time it loaded up opendesire fine.
after playing around for a bit I wanted to go back to my old rom.
so i rebooted into CWM and just did a nandroid restore...
now when I boot into my old ROM I am missing all my apps.
the home screens are blank
there is a new "super user privs" app
various other things are missing.
so what did I do wrong?
doesn't nandroid backup everything?
Cheers
D.
I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...
Hi, got my first andriod, the desire, only 6 weeks ago so still a n00b myself! Hopefully someone can answer better and correct my mistakes but here goes:
With Linux you have to be a root (or superuser) to access, modify, execute, etc any and all files. Our Desires, with stock ROMS, do not allow us to do these things - hence we need to 'root' our phones.
I think the internal memory of the phones has two parts - one holds the ROM (the operating system) and the other is a 'cache' which holds user/system info relevant to the ROM. The cache is specific to the ROM which is why if you change from say the stock ROM to opendesire you need to wipe the cache. However, if you upgrade the ROM, eg opendesire 2.1 to opendesire 2.2 you do not need to wipe the cache.
To be able to access the part of the phone which holds both the ROM and the cache you need to be root/superuser. If unrevoked worked without errors and you have been able to change ROMS (i recommend ROM manager) then you have 'rooted' your phone.
When ROM manager asks if you wish to back up your ROM I think it only backs up the cache, not the ROM itself, as that would already be on your SD card as a .zip file.
If you wish to go back to stock I think you need to download stock ROM, use ROM manager to install it, then go back to ROM manager and use the backup/restore option and restore your initial backed up cache.
Hope this helps a little!
tephra said:
I forgot to say, I havn't rooted the phone - I dont know if that makes a difference... I actually thought the unrevoked thing was going todo more that just install a different debug boot loader...
Click to expand...
Click to collapse
You rooted the phone when you ran Unrevoked3, that's why you have superuser permissions.
It doesn't install a different boot loader, it installs a new recovery which allows you to easily flash custom roms without having to use fake-flash.
Something must have gone wrong during your nandroid backup.
ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...
tephra said:
ok i understand about the root bit and also the recovery bit now - thanks
my nandriod backup folder has:
boot.img
cache.img
data.img
nandroid.md5
recovery.img
system.img
one thing, is this desire is a telstra branded phone. Now i have read that i might require a goldcard.
could this be causing the problems I am seeing?
last night I loaded the original RUU on, now I will see if the nandroid restore fixes my apps and stuff...
edit - hrmm the original RUU has removed CWM recovery... i will load up unrevoked3 again...
Click to expand...
Click to collapse
You shouldn't need a goldcard with ClockworkMod, I didn't need one for my branded Desire.
Alright, I may have a brick on my hands but after playing with Android for two years I've found that's pretty tough to actually do so I'm still hopeful. Using Clockwork recovery, I did a factory reset and flashed the cm vision full 5 nightly build onto my G2/Vision. It gave me a boot loop so I went into hboot and tried to flash the PC10IMG. I'm getting a "Main version is older! Update fail!" message and have no idea what to do. Somehow I'm back to S-ON so I can't even try to flash a different update. If anyone has any ideas I will try anything. I love my phone and would hate to lose it three days after root happened.
I hate to be the one to say this, but didn't the thread say not to not to try it yet?
ruleftbehind said:
I hate to be the one to say this, but didn't the thread say not to not to try it yet?
Click to expand...
Click to collapse
If you hate to say it and it doesn't help then why say it? And no it does not say that anywhere in the thread. Others have tried and had success.
You didn't make a nandroid backup?
No offense, but you said you've been playing with Android for 2 years. You should've known that the first rule is to backup what you already have!
Have you tried installing the stock ROM pre OTA in the "Downgrading ROM" thread?
tazz9690 said:
You didn't make a nandroid backup?
No offense, but you said you've been playing with Android for 2 years. You should've known that the first rule is to backup what you already have!
Have you tried installing the stock ROM pre OTA in the "Downgrading ROM" thread?
Click to expand...
Click to collapse
I'm attempting it but adb won't copy my misc.img to my SD card, nor will it detect the miscnew.img I've made from someone else's misc.img.
Edit: Oh, and I WAS using the first release of the Clockwork mod for the G2 and I did not see a nandroid option there or I would have made a backup. I guess I shouldn't have tried it without a backup. Is there any way to use nandroid to flash someone else's backup?
What you need to do is mount your phone to your PC using Clockwork Recovery and copy over the misc files that way.
I had to downgrade to the stock rom myself and I used the misc files located in the below file.
http://forum.xda-developers.com/attachment.php?attachmentid=437017&d=1289270330
Jigga0o7 said:
What you need to do is mount your phone to your PC using Clockwork Recovery and copy over the misc files that way.
I had to downgrade to the stock rom myself and I used the misc files located in the below file.
Click to expand...
Click to collapse
I already downloaded those files, and copied miscnew onto my sd. But when I try the
"dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17" command it says the file does not exist. It doesn't work with the card mounted or unmounted.
If you can get into clockwork you should be OK. i think your mistake was doing a full factory reset rather than install CM and then wiping data and cache. go into clockwork and wipe everything.
Find the official pre-ota zip, go into hboot, and flash. if this fails, go into clockwork, wipe everything, then go into fastboot, flash the original recovery, then go into hboot and flash the pre-ota zip.
Otherwise, find the thread when people had problems flashing the OTA after removing goggles and use that method to reflash the pre-ota.
So I've rooted my phone, got the latest defy clock work recovery thats in the clockwork thread, I've booted into recovery mode and made a backup.
Now I've downloaded a 3.4.3-11 zipped nandroid backup with the img files etc, but when I try installing from them it just sits there doing nothing.
The progress bar stops animating and it looks as if its hung, I left it for 15 minutes and nothing happened so I pulled the battery, phone restarts and boots fine.
I've tried multiple images and they all cause clockwork recovery to hang when attempting to install them.
Can anyone suggest what I might be doing wrong?
Using everything listed in this post:
http://forum.xda-developers.com/showpost.php?p=12122439&postcount=10
from this thread:
http://forum.xda-developers.com/showthread.php?t=993402
edit: If it toggle verification on it says this
E:signature verifications failed
installation aborted
what should I do?
no one ever had this issue before?
Found someone else who also has this problem.
can anyone out there help ?
kind of confused here... What's hanging, CWM? or RSD? You said that flashing SBF causes clockwork to hang.....Thing is..... clockwork don't flash SBF's.
You need RSD for SBF's, clockwork will restore nandroid or apply unsigned .zip updates among many other things but no SBF
zyxwvut said:
kind of confused here... What's hanging, CWM? or RSD? You said that flashing SBF causes clockwork to hang.....Thing is..... clockwork don't flash SBF's.
You need RSD for SBF's, clockwork will restore nandroid or apply unsigned .zip updates among many other things but no SBF
Click to expand...
Click to collapse
Sorry I meant nandroid zip files with the .img files inside of it, not sbf.
So yes clockwork hangs when trying to install zip file with img files in it.
What would cause this to happen and how should I rectify it? I would post in the clockwork thread but I dont have enough posts.
The issue was I was trying to apply an update.zip when what I wanted to do was restore a nandroid backup, being as it didn't give me the option to select any folder other than the clockwork folder I got confused.
Followed these instructions and all is well
the method i could understand:
maybe wrong, i'm warning you..
maybe you could ask someone who real capable of this.
i'm just trying to answer..
Preparing files needed, needed when you want to go back to 2.51
-download SBF of your stock (2.51)
-got root, install custom recovery, restart.
-when phone is ready go to custom recovery app, and install recovery then reboot.
-and then create nandroid backup from custom recovery.
Upgrading froyo with downgrade-ability
-download fixed SBF and nandroid backup of this froyo version.
-from custom recovery, wipe all cache.
-and then restore nandroid backup of the froyo rom
-restart and IMMEDIATELY go to bootloader. immediately press and hold VOL.UP+POWER after you press restart system on custom recovery
-on bootloader, flash the fixed SBF of that froyo rom with RSD Lite 4.9, and make sure you already download motorola driver...
Downgrading:
if you want to go back to 2.51,
-got root, install custom recovery, restart.
-go to custom recovery, and then RESTORE your 2.51 nandroid backup
-restart and IMMEDIATELY go to bootloader. immediately press and hold VOL.UP+POWER after you press restart system on custom recovery
-on bootloader, flash the fixed SBF of your stock 2.51.
Click to expand...
Click to collapse
maybe just another issue pertaining the restoring of nandroid backup. what is the issue if i get a md5 sum mismatch? i did all the thing, flashed sbf, root, wipe and when goes to restore, it just have the md5 sum mismatch. i'm using kb7sqi recovery
Have u checked if usb debugging is off? After rooting u should disable it.
Sent from my MB525 using Tapatalk
what are you doing to cause md5 mismatch??? You go into recovery and suddenly you are greeted with md5 mismatch or is it when you are trying to restore a nandroid? Or is it while applying an update?... Anyhow, if it's wile restoring a nandroid, be sure that a nandroid.MD5 file is included with the package you downloaded. If not you could try advanced restore or find a package with a md5 file or recalculate md5 yourself
roland_harrison said:
The issue was I was trying to apply an update.zip when what I wanted to do was restore a nandroid backup, being as it didn't give me the option to select any folder other than the clockwork folder I got confused.
Followed these instructions and all is well
Click to expand...
Click to collapse
Glad you got it sorted.... I have flashed almost every rom out there. Many many many sbf's. I have bootlooped a few times while experimenting, but always bring it back from the dead. These phones are honestly pretty resilient to user error. As long as the instructions for flashing a particular rom are followed exactly as instructed.. It ALWAYS works. When things go bad boot into stock recovery, wipe, pull battery, hold vol+ while inserting battery to get into bootloader then flash an appropriate sbf and youre back
Dear all,
I am new to Android root, but a very experienced PC user. I thought custom fw process to be easy but unfortunately bricked my defy. I need your assistance please. I define process I applied and problem in detail;
rooted my Defy
installed System Recovery (clockwork mod kind)
downloaded MotoGinger 2.3.4 and extracted it to clockwork mod/backup directory.
booted into recovery mode and wiped user data as suggested
went to advanced restore tab and selected system restore (img restore)
then went to boot restore (selected shadow4.5.1-134fixed.sbf)
then rebooted my phone
As a result it freezes in boot procedure (motorola logo hangs).
- The first question is what is wrong with the procedure I tried. Do I understand anything wrong? As the tutorial is not detailed enough I can't address it.
Then I've used RSD Lite and flashed my phone with shadow4.5.1-134fixed.sbf. No problem seems so far but I have some questions.
- May I use my Froyo application backup? (img backup obtained with recovery mode). Can I import it directly to my new 2.3.4 cfw?
- What is about MotoGinger img file? What is in it (complete backup?) and in which situation it is used. As I expect, it may be a backup of filesystem to make the flash procedure easier, faster and less risky. Am I right?
If you can explain these questions I will be appriciated. Here is the cfw I've used;
http://forum.xda-developers.com/showthread.php?t=1156855
Thanks and regards,
Sinan
Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.
Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.
In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0
It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.
Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.
I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.
I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)
I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.
Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it
Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.