Related
Hi guys. I am having a bit of an issue here.
I just got my DX a couple days ago. I have a buddy that has been into modding with his D1 for a while, and he recently got a Fascinate. He convinced me to try doing some stuff with my phone...
I rooted my phone successfully. I then wanted to install the DX Invertnito theme. It said I needed to Deadex my phone. I got the xultimate 2.2.2 deodex pack and successfully deodexed my phone. I then downloaded the zip file for the Invertnito theme. I put the zip file on my phones sd card as stated in the instructions. I then downloaded Koush's DX Bootstrapper from the market and Clockwork Rom manager. Installing the theme automatically through the rom manager didnt work, but the phone did boot normally nonetheless. I then decided to go directly through the Bootstrapper app [clicked the recovery mode right on the menu out of two options]. The phone instantly shut down, then booted into the clockworkmod recovery menu. I followed the instructions given to install the Invertnito from the .zip file on the zd card. I clicked install on that file. Everything seemed to work fine to this point. Installation successful.
Unfortunately, now the phone will not boot at all.... It loads the Motorola M logo and stays there. I've tried waiting for 30 min on the logo and it just doesn't move. If I remove/replace the battery, the phone will then load the clockworkmod recovery menu again just like it did after it shutdown from running the first time. I've tried clearing cache, restarting the phone, replacing the battery 20 times. Always stuck on boot M screen. Sometimes it will go the the Motorola bootloader screen, but when i click reboot system, it just gets stuck on the M logo.
Any help would be appreciated here. I'm hoping I haven't bricked my phone somehow. I didn't expect this as I can't find anyone else who installed this same theme have the same problem. Is there something I can do to get it back to normal? Is it possible to somehow get my OS back to clean stock and go from there?
Thanks
Did you do a nandroid backup before loading the theme?
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Retriraver said:
Unfortunately, no. I just read of someone having a similar issue though. Said he used RSD Lite 4.8 and an SBF and he was able to get back into his phone. Not sure how to dgo about any of that though.
Click to expand...
Click to collapse
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
rcerulli said:
go over to mydroidworld and look in the droid x mods section. It has rdslite and sbf for froyo
Click to expand...
Click to collapse
Thanks, I will go check that out and see if I can get this fixed.
be carefull i am in the same situation like you and flash the sbf file from THB team i now i think my phone is reall ****ed up bricke nooooooo
trying the 2.1 sbf file i hope its works
well first time failed and then was stuck in bootloader saying code corrupt damn i was so mad... so i tried again the 2.1 sbf adn voila droid x alive again ufffff
i will keep the ota version **** the custom rom relly i dont need it hehehehehe
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Retriraver said:
Also, how can i run the RSDlite and connect it to my phone while my phone is stuck on the M screen?
Click to expand...
Click to collapse
hold volume down and camera button while you press power button it will then say ready to program.
if you did the OTA 2.2 DO NOT USE THE 2.1 SBF!!!!
if your on the leaked 2.2 and you try the 2.2 sbf but get errors due the 2.1, if you get a boot loop after that you need to go into the stock recovery and factory reset, hold home button and
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
djtoonjr said:
ive been there as well. pull out an adapter for ur memory card or get another phone and pop ur memorycard in it and dl the file inside this link.
http://forum.xda-developers.com/showthread.php?t=794007
scroll down to option "2"
2. Update.zip - File
1.Wipe and reboot.
the "File" will be clickable and will send u to a link to dl. place it on the root of memory card(doesnt really matter where as long as its on the memory card) and click
install update.zip(if its in root and named update.zip) or u can go click choose .zip file or whatever and go look for it. hope it works for u. let us know. ill be waiting to hear ur respnse.
Click to expand...
Click to collapse
This worked for me...thanks mate!!!!
This may "wreak of non-search" and I am sorry if it does. While I have searched, the overall panic that one experiences when you suspect a brick and cannot afford to have a brick.... (that, plus a friend purchased this Glacier for me to help me get back on my feet with respect to career/employment, etc., so a good amount of guilt is thrown into this mix)... all prevents me from rationally and methodically searching thread after thread to figure out why I am having the problem I am having.
I will be as precise as possible.
1. Back in Feb., I perm rooted with visionary... then about 2 weeks later, I read that this root was not true radio s=off perm root, so I used adb and the scripts to perm root again--using the wiki as a guide. Saved a copy of the partition 7 bin on my laptop as an added precaution. Also, BTW, I never flashed the engineering HBOOT. It didn't seem essential to do so... PLUS, in almost every guide it warned that this was the most likely chance for one to f*ck up and brick, so in the interest of erring on the side of caution, I skipped that.
2. I kept stock ROM for several weeks after that... just enjoying root and freezing bloatware with Ti, and doing other root-enabled mods... nothing too involved.
3. About 1 week ago, I finally decided to flash my ROM. I had Rom Manager (paid version), and had flashed ClockworkMod Recovery 3.0.0.5. Further, as an FYI, I had/have numerous nandroid backups on the SD, plus several Ti backups of apps/data... even sync'd this with dropbox, so I can access those now (which are not of any help obviously).
4. I first flashed a CM7 nightly build--wiped data and cache, and as far as I know followed the guides precisely. All was well...new ROM worked alright... some bugs, but it was nice to have the new features, etc.. And of course the mental gratification of having 2.3.3 (GB) instead of 2.2.1 (boring old froyo). I updated the nightly maybe 2 times... in each case, I simply flashed without backing up those ROMS or wiping data/cache as they didn't seem necessary, plus I still had all my stock rom nandroid backups on the SD.
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Since I cannot get into the phone... I am of course panicked... I have ADB on my laptop if needed, but I really am at a loss as to why this happened, and what I can do at this point....
Please, please advise. My utmost appreciation and sincerest gratitude in advance for any assistance.
Thank you!!!
syntropic
syntropic said:
5. Then Last night, RC4 came out. I flashed this the same way... no wipe. This morning... after using it for awhile, I started to get forced close problems on numerous apps... and the one that was most bothersome was my Market app... So after trying to Fix Permissions using RM to no avail.... I decided to restore the last nandroid backup of my stock (rooted) ROM. All seemed well while the restore was progressing... I was powered by AC (as always). But when the phone rebooted at the end of the restore, it stayed at the MyTouch splash for a long time... longer than I thought was appropriate (~20 minutes). So, I took out the battery since nothing else responded, and tried to boot into recovery. WHen I tried this, I got 3 quick vibrate alerts, and a blank screen, with the LED flashing every second in an ominous disconcerting way. (!!) Again, I removed battery, then tried to start phone again normally. Same problem.... It won't go past the MyTouch splash.
Click to expand...
Click to collapse
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
should come up to a white screen.
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Sent from my HTC Glacier using XDA App
Can you boot in to the bootloader?pull the battery put it in then hold the power button down and the volume rocker down?
Click to expand...
Click to collapse
No... that is what I meant when I said tried to "boot into recovery". And I got the 3 vibrate alerts and a blank screen, and nothing........
take the battery out and let the phone sit a little bit. this has worked for others to get into hboot then recovery. Also if you get it going INSTALL THE ENG HBOOT! Can really help you with soft brick among other things.
Click to expand...
Click to collapse
Will do... Thank you. DO you have any idea of where I f*cked up here??
Could be a number of things. Like wipe didn't go through completely , bad download, or just random crap out like a few others. Even flashing with the wrong cwr version can less to your issues. Lol like I said could be a number of things. Sorry I couldn't be more helpful.
Sent from my HTC Glacier using XDA App
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Sent from my HTC Glacier using XDA App
syntropic said:
OK... Good news. I am in now in CWR. BTW, this may have been something that was my mistake to begin with. When I originally tried to boot into Bootloader, I held the volume button UP. I just tried both up and down volume hold while powering on. When I hold volume up, I get 3 vibrate alerts and nothing. When I hold volume down, I go straight into the bootloader/HBOOT.
OK.. So as said, I am now in CWR. What is the best course of action here...?? Can I try to restore my nandroid backup (maybe a different one) of my old rooted stock ROM? Should I do a factory reset (prefer not to, but I submit to the advice of my more skilled android fans)?
Just a point in the right direction, and I think we can put this thread to bed. Thanks a million just for holding my hand while I fixed this....
Click to expand...
Click to collapse
What recovery are you using? 3.0.0.5? and you're trying to flash a 2.2 ROM. Thats where the problem lies. See my post regarding this. It's in my signature, the green one.
I would wipe EVERYTHING but the sd card where your backup is, then attemp restoring whatever rom you had last. 2.2 and 2.3 use different versions of clock work and don't remember which 3.0.0.5 went with. So use that last one that booted and then updat clock work to 3.0.0.6 as it will flash both 2.2 and 2.3
Click to expand...
Click to collapse
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
EDIT: MUSTKll20... Well, you were right... This is not ROM specific. I tried Re-Flashing RC3, which previously worked fine. Now, since I have CWModRec 3.0.0.5, I need to use a 2.3 ROM.... So I thought I would start with this idea. So, I guess, I need to get whatever is corrupt deleted... So my only question thus remains: How do I wipe everything except the SD from within CWR?
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
syntropic said:
OK... and neidlinger... I think I read that post before and didn't quite get the full understanding of it.... I grasp now that you can only restore a 2.2 with a 3.0.0.4 CWR.
And now that there seems to be a 3.0.0.6 which solves this mismatch trap, why would it not be simpler just to reflash the CM7 RC4, then update CWMod, then just see if my original force close issue is even still occurring, and if so, then I would flash/install eng. HBOOT, "Wipe Everything except SD" (btw, does CW have a selection for that? Is that factory reset? Or will a factory reset wipe my SD.... because obviously that would be bad)
I don't really now how to wipe the internal... Except if I had a terminal and used dd, but as much as I am comfortable with Linux, I still do not understand how the SD and the ROM are separated and why, and how, and what shell commands do what to each....
AND THANKS AGAIN SO MUCH YOU GUYS FOR TAKING TIME TO ANSWER MY CRISIS-INFUSED QUESTIONS!
Click to expand...
Click to collapse
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
and android phone have a method of using a section of the SD card for their memory banks. I'm not really sure how it works either, but it does. You can wipe the internal w/o wiping the SDcard.
Wiping the phone from with in the recovery image will not touch the SDcard, it will only wipe the internal. You can format the SD card from the Recovery Image, but i'll leave that dog sleep so we do not it accidentally.
last little clean-up question.
Sorry to bump this... last LAST question...
Mustkll20: I realized that you were correct to suggest to wipe everything except the SD... Something is corrupt.
But I am not real sure exactly how to wipe EVERYTHING except the SD, from within CW recovery... Since that is the only mode I have available to me. Once I wipe, I will reinstall CM RC3, then update Clockworkmod Recovery to 3.0.0.6, and then try and download RC4 again using another method, and re-flashing.
I would trial and error this, but do not want to wipe the SD.
Thanks guys... seriously.
You can flash CM7RC4, and install 3.0.0.6. That's pretty much the only way you can fix it..
Click to expand...
Click to collapse
I didn't see your reply... ummm. and I do need to wipe.. Because I have tried to re-flash both RC3 and RC4, and I get what must be a "bootloop": During the CM splash, it stops and then reboots---over and over. It never did that before.... so my problem is something else...
I don't know what else there is besides the SD and the ROM, but whatever it is, I need to delete it. So should I do a factory reset???
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
lowandbehold said:
Also, are you sure you are holding the volume down and pressing power to boot into recovery? The result you described is what happens when you hold the volume up and press power.
Click to expand...
Click to collapse
Yep... I know the thread is not for thrillseekers (i.e., its boring), but I mention that I discovered this phenomenon... so I really wasn't in all that bad a spot to begin with.
I still need to figure out how to fix my current problem.... all CM RCs (I can only flash 2.3 ROMs because of CW 3.0.0.5) go into what I guess is a bootloop. In other words, they do not ever boot, just crash and restart. And the RC3 ROM I used worked fine before this... so something else is causing this problem. I need to wipe everything I guess, but I just don't know how... without touching the SD card and from within Clockwork Recovery.
Ok. Go into recovery.
1. Wipe data/factory reset
2. wipe cache partition
Both of these are on the main screen.
Go to advanced
3. Wipe Davlik Cache
Go back to main screen
Go into mounts and storage
4. format boot
5. format system
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
lowandbehold said:
Ok. Go into recovery.
{...}
Try all of that. It will not touch your sd card. After doing this flash the ROM again. Keep us updated and good luck.
Click to expand...
Click to collapse
Thank you for the concise and thorough response!!!!!!! Id thank you, but have used up my allotment. get ya tommorow!!
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
syntropic said:
And it worked! Thank you!
But.... ummm.... there is no market app. I would think the CM ROM would have this, but apparently it doesn't. I need to install Ti, etc. to restore all my apps.
Does anyone have a download link or at least a version # that is appropriate?
Click to expand...
Click to collapse
You can thank the Google c&d order for that. Go to cyanogenmod.com. there is a link there for the gapps zip.
Sent from my HTC Glacier using XDA App
OK... I thoght Gapps.zip was just Google Docs. Luckily, I had that on my SD card from one of my many ROM downloads. I see why they had to make it separate.
But I am installing it, and everything is great... And I learned a lot too... Which can only mean trouble.
Thanks!
I am having some serious issues with my evo. I have tried 10 different methods, googled 100 different help guides and still no fix.
I had originally rooted my phone using simple root and put the "fixed" froyo rom on there. Everything worked fine, but I was outdated and having some really slow issues so I wanted to try a new rom...Fresh.
Well I tried a few methods, but I somehow reverted my evo back to a nonroot of the original OS. Whenever i go into hboot, my recovery does not work. I push the PC36img and load it, then restart then I attempt to go to my recovery where it gives me the error picture with the yellow/red triangle. I then select recovery (after pressing UP volume and powerbutton) and try to load update from sd card. Everytime I do that I get a Failed error.
I've tried to reroot using several methods off this website, I've done everything I can to get it working but can't. Any help would be GREATLY appreciated!
Try reflashing your recovery image.
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
noweakness said:
BTW I have hboot 79.0 with S-ON, so it looks like I def became unrooted.
Click to expand...
Click to collapse
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Heaterz16 said:
Try reflashing your recovery image.
Click to expand...
Click to collapse
I have a recovery-ra.img, how do I tell it to flash it?
I pulled up this list of recovery files, is there a particular one I should use?
htt p://goo-inside.me/amon_ra/supersonic/
Heaterz16 said:
Not sure how it would have just unrooted itself. I would run an RUU from here: http://forum.xda-developers.com/showthread.php?t=884060
Then, I would re-root and start clean again.
Click to expand...
Click to collapse
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
noweakness said:
Ok I downloaded the top item:
RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed
Ran the exe, surprisingly picked up my phone and started the image update. My phone restarted and it forced closed the app on my computer. Now I have a new HTC logo for about 5 min on my phone not doing anything. Should I wait it out or restart my phone?
Click to expand...
Click to collapse
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Heaterz16 said:
I would have waited about ten minutes then restarted the phone. If the phone is stuck at the HTC logo, then I would go ahead and re-run the RUU.
Let me know how it turns out.
Click to expand...
Click to collapse
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
noweakness said:
ok, finally got it working. Had to restart the phone manually and try it on a different computer. It updated it to the newer version of android and hboot, thank goodness! That was the easiest and most productive thing I've been able to do so far, thanks!
Well now I try to boot into recovery and get the same error:
can't open /cache/recovery/command
Then I get :
E: signature verification failed
Installation aborted
When i try to load update from sdcard
Click to expand...
Click to collapse
Ok, so, I think you said you got the RUU working which would have completely restored the phone to unrooted and stock from factory.
Now, you need to re-root your phone using one of the methods on xda. I used the manual method here: http://forum.xda-developers.com/showthread.php?t=829045. However, many people have had success with the one-click methods.
After you re-root (which will likely included installing a recovery), select a rom you want to try, boot to recovery, wipe and flash it. A great starter ROM is MikFroyo 4.6 or 4.5.
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
ok thanks, i'll try it when I get back home
jesuspgt said:
Try downloading the PC36IMG.zip from here: http://forum.xda-developers.com/showthread.php?t=705026
put that on the root of your SD card, then boot into HBOOT and it should find that PC36IMG.zip after a few seconds and ask if you want to flash it. Choose yes and let it finish. Should then be able to reboot into recovery.
Click to expand...
Click to collapse
Ok, I tried this method...the filesize of pc36img.zip is only 3.5mb, but it didn't seem to work. It scanned the file then just went back to the hboot screen with my options never asking to flash.
I'm going to try to reroot using the other method now...
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
noweakness said:
So I clicked the link and he forwarded to the autoroot.bat page so I used his method. It worked well (the 2nd time around) all the way until it started to push amon_ra_1.8-mod.... then after that it says rebooting into the bootloader, and it reboots into it and just says waiting for phone...
It does appear that my phone is rooted now, but my recovery is still not working. If I use ROM manager will it work since my phone is rooted or do I need to have a rooted ROM to run it off of?
Click to expand...
Click to collapse
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
xHausx said:
Does your phone show s-off while in the bootloader? If so you should be able to run the FlashZip script and use that to flash the pc36img-sprintlovers zip. That one contains everything needed to bring your phone up to date and will leave you with a rooted rom and recovery.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
noweakness said:
FINALLY! Thanks a million! My recovery is now working and it installed the built in sprinter lovers rom, I guess the anti-virus was stopping it so I disabled it and ran the flash script. I was able to install Fresh on there, just to try it out. I do have a few questions though:
1. I noticed after going through many pages that to update to a newer ROM version you don't always have to wipe clean, you can just install (or flash) the new update? I noticed in Fresh there is a built in app that does that. Is this true for most ROMS or only certain ones?
2. I assume I am using the RA recovery. I noticed the backup/restore feature on there. What exactly does that backup and when should I use it?
3. I've noticed I've been very low with memory on my phone (not SD card), I have about 258MB free. How can I clear space and when I mount my phone what files are important to keep and can I get rid of, is it okay to get rid of my rom.zip's and radio.zip's?
Thanks again to everyone, autoroot was def the most painless root ever.
Click to expand...
Click to collapse
1) You'll want to always wipe your cache/dalvik (I do everytime I'm in the recovery) but the Data depends on the ROM. Usually if you are going from one sense rom to another you are ok and the same for AOSP to AOSP. Going from Sense to AOSP you'll need to wipe data though.
2) Autoroot comes with a modified version of AmonRA, they are mostly just speed tweaks. To make a complete backup of your ROM select Boot (kernel), System (ROM), Data (Apps & Settings) and .android (apps on SD card)
3) You can delete the zips from your sd card if you don't need them but that's about normal for free memory.
Hello, while I was testing 2.3.5 witch was great except that the mobile network was not woorking at all. So I decided that I needed too downgrade. And when I was browsing the phone I accidentally found this way.
This has not been proofed by anyone else I think.
Disclaimer: I do not take the resposibility for your device.
1. Put the dload on the root of SD-card (I used 138sp4)
2. Then go to storage in preferences. Head too the bottom then choose "upgrade SD-card". The phone blacked out, started up and installed 2.2
3. The phone boots up in recovery because of many errors. I choose wipe data/chache and wipe chache and reboot.
4. The phone rebooted and I am back to 2.2.2 from 2.3.5.
This method keeps the start-boot-picture (does not know if the other sulutions keeps it).
Sorry for my bad grammar on some of the words. I just wrote them down and did not have the time to fix them.
Hmmm...interesting....maybe I should try 2.3.5 even if I have the Atmel screen. :/
Sent from my IDEOS X5 using XDA App
UnknownAX said:
Hmmm...interesting....maybe I should try 2.3.5 even if I have the Atmel screen. :/
Sent from my IDEOS X5 using XDA App
Click to expand...
Click to collapse
I have atmel screen but I like it because i wear gloves and the screen is so sensitive that it responds thrugh them.
I was forced to downgrade from 3.2.5 to 2.2.2 for the exacly same reason and i tryied that same way you did and i couldnt do it, i got a message saying something like "there are no upgrade firmware inside the SD card". So i used the root & replace boot and recovery files to downgrade what was a sucess. Got the same issues as you with the boot but the "wipe data/chache" from recovery resolved it.
jopamasi said:
I was forced to downgrade from 3.2.5 to 2.2.2 for the exacly same reason and i tryied that same way you did and i couldnt do it, i got a message saying something like "there are no upgrade firmware inside the SD card". So i used the root & replace boot and recovery files to downgrade what was a sucess. Got the same issues as you with the boot but the "wipe data/chache" from recovery resolved it.
Click to expand...
Click to collapse
Ok, maybe it does not work for everyone but what 2.2 version did you use. For exampe I used the 138sp4(international (the last(I think) 2.2.2 from Huawei))
areedw said:
Ok, maybe it does not work for everyone but what 2.2 version did you use. For exampe I used the 138sp4(international (the last(I think) 2.2.2 from Huawei))
Click to expand...
Click to collapse
The version i used was/is U8800V100R001C00B138SP04, so as far i can see it's the same as yours correct me if i'm wrong. But as far i could read about good/bad reports for 3.2.5 and all the different problems different people having version and same phones making me belive what's possible for one's arent for others.
areedw said:
I have atmel screen but I like it because i wear gloves and the screen is so sensitive that it responds thrugh them.
Click to expand...
Click to collapse
THROUGH gloves? Omg xD
Sent from my IDEOS X5 using XDA App
that's very good!! thanks for info!
downgrade issue
hi, y just tried to upgrade my u8800 to 2.3 using the update from huawei but since the gps and de wifi didnt work I tried to downgrade back to 2.2, I dont really know if what I did was the right thing to do but I just copied the 2.2 dload folder to my sd card and tried to reinstall by presing the vol+vol-power keys and it seemed to work just fine, after it completed I just started the phone and it never woke up again it just vibrates a bit but nothing....does anyone know how can i fix it??it wont let me do anything the computer wont recognice it and there is no image at all....anyone please help me!!!
fermon797 said:
I just started the phone and it never woke up again it just vibrates a bit but nothing....does anyone know how can i fix it??it wont let me do anything the computer wont recognice it and there is no image at all....anyone please help me!!!
Click to expand...
Click to collapse
The decision to distort the battery. Insert, connect the USB to the phone (on the other end connected to a computer), press and hold keys + - food, and wait a few seconds, as soon as you see a red flashing light, unplug the data cable, you can start sewn.
Tnks!!
Igory0k said:
The decision to distort the battery. Insert, connect the USB to the phone (on the other end connected to a computer), press and hold keys + - food, and wait a few seconds, as soon as you see a red flashing light, unplug the data cable, you can start sewn.
Click to expand...
Click to collapse
Tnks!! im gonna try that but after doing that what should i do?? do i have to install 2.2 again??if so do i have to do this procedure with the sd card connected?? and also which rom would you recommend?? thank you so much for your answer!!!
fermon797 said:
Tnks!! im gonna try that but after doing that what should i do?? do i have to install 2.2 again??if so do i have to do this procedure with the sd card connected?? and also which rom would you recommend?? thank you so much for your answer!!!
Click to expand...
Click to collapse
Downgrade from 2.3.5 back to 2.2.2
U8800 V100R001C00B138SP04 (Overseas General) Android 2.2.2 from here
areedw said:
Hello, while I was testing 2.3.5 witch was great except that the mobile network was not woorking at all. So I decided that I needed too downgrade. And when I was browsing the phone I accidentally found this way.
This has not been proofed by anyone else I think.
Disclaimer: I do not take the resposibility for your device.
1. Put the dload on the root of SD-card (I used 138sp4)
2. Then go to storage in preferences. Head too the bottom then choose "upgrade SD-card". The phone blacked out, started up and installed 2.2
3. The phone boots up in recovery because of many errors. I choose wipe data/chache and wipe chache and reboot.
4. The phone rebooted and I am back to 2.2.2 from 2.3.5.
This method keeps the start-boot-picture (does not know if the other sulutions keeps it).
Sorry for my bad grammar on some of the words. I just wrote them down and did not have the time to fix them.
Click to expand...
Click to collapse
Yes its working great but if u have custom rom installed remember to factory reset, wipe cache and dalvik in recovery before downgrade, if u will not do this phone will stay at unpacking screen forever.
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
tmcookies said:
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
Click to expand...
Click to collapse
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Click to expand...
Click to collapse
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
tmcookies said:
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
Click to expand...
Click to collapse
Is RSD recognizing it?
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Is RSD recognizing it?
Click to expand...
Click to collapse
Who would have thunk? RSD Lite did recognize the phone and when it started flashing, the phone showed
"SW Update
In Progress.."
So, now what? Which sfb file should i flash?
Anyway, thank you so very much!
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Yes, root again if needed.
I saw your other post in the cm11 thread about how your phone died.
I remember reading somewhere in the forums that you should go to cm10.2 before installing the updated recovery, and then install cm11.
I'm not sure if that's 100% accurate, and I couldn't find the link (sorry).
Couldn't hurt, though, seeing as you'd just have to do a few extra ROM flashes.
Good luck!
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
after some effort - great on CM11!
leandrolutz said:
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
Click to expand...
Click to collapse
I had a simiilar problem - somehow after a similar failed CM11 install, I pressed that "reboot" button and my mb525 was dead. I did as suggested here, Except I happened to have CM10.1 not CM10 on the SD.
However I had a lot of trouble getting a successful boot after installing update-recovery.zip, and then also after installing CM11 with the updated recovery.
Now I have a great well-running defy on CM11. I don't exactly why it succeeded when it did - just repeatedly wipe and install and wipe until it worked.
The defy really runs well on CM11 - very responsive - it is robust both in HW and SW! - maybe I'll myke it my main phone again! (before the S3 or the xperia V) - Samy just ain't interested in my S3 - the community provides the same Android version for my defy as I have on my nexus 7 2013!!!
Many thanks to all who have contributed, especially quarx -
try this http://forum.xda-developers.com/showthread.php?p=48501247