Related
Apologies for this stupid question resulting from a stupid mistake. Hoping somebody will be able to walk me through getting out of this.
I successfully rooted my sprint hero, then loaded modaco 3.0 (yes now I know that was bad). On reboot, the phone hangs on the black htc screen, and will respond to nothing.
The only thing I've been able to do is remove the battery, then turn it on in recovery mode. There, I did a wipe data/restore factory setting. Then I rebooted - and got the same boot screen, same problem.
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
When I try to restore, I get these:
(bart) error: run bart via adb
(nandroid) can't open file
Please help! I am out of ideas. Thanks very much in advance.
you'll probably have to take it back to the very beginning......
Get the Sprint RUU stock rom (a couple of posts below this one) and run that
then re-root your hero
Flash one of the roms ON THIS BOARD ONLY!!! Any other Hero rom is meant for the GSM version so it will give you the same headache again.
thanks
Thanks for the quick response! I'll try that.
Hmm, not looking good here. When I tried to install the stock hero RUU I got this error:
no signature
verification failed
which I presume is related to the htc sync requirement for that rom in the unrooting procedure that I did earlier.
Any idea for working around that?
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
david.danaan said:
Second try: wiped, toggled to usb, and replaced the 3.0 update.zip with the 1.1 for CDMA, tried to flash it, got this:
can't open /sdcard/update.zip (bad)
Click to expand...
Click to collapse
Don't use 1.1, grab a later one.
Which recovery? 1.5.x won't let you go back to the main menu without disabling USB-MS again... I don't remember what 1.2.3 did. If worse comes to worst, reboot the phone after copying the file.
gu1dry said:
So you used RUU_Hero_C_Sprint_1.29.651.1_signed_release.exe? If not, here is a link to it: link.
Click to expand...
Click to collapse
Yes, that's the one.
Using recovery 1.5.1. I can try a later rom, see if that works. I think I downloaded 1.3.
So first off yes, you aren't booting past the HTC screen because you flashed the wrong rom. However you aren't bricked. It's almost impossible to do once you're rooted and have RA's recovery installed unless you flash radios and stuff which you shouldn't.
Explanations for your other problems:
1. RUU doesn't work on the phones that are coming from the factory with 1.56. http://geekfor.me/news/sprint-ruu-fails/
There is a possible work-around but it's pretty detailed and I haven't gotten it to work. But you don't need to RUU if you can get in to RA.
2) (nandroid) can't open file is likely caused by RA 1.5.1. It had a bug that corrupted the backups. 1.5.2 is out. But for now don't worry about that cause your backup already sounds corrupted, nothing you can do.
3) can't open /sdcard/update.zip (bad). To me that sounds like your update was just corrupted.
How to fix it:
1. Boot in to recovery. With phone powered off hold your home button and then power.
2. Download fresh rom from http://geekfor.me/new-release/fresh-rom-1-0/ (what can I say... I'm partial. )
3. Within RA enable USB toggle and copy fresh rom to the root of your sdcard. Don't worry about renaming it to update.zip
4. Disable usb toggle. Go to flash zip from SD and choose fresh. That should be it. If you get the error saying the zip is bad then compare your downloaded copy with the md5 hash check on the download page (google it if you aren't sure how). If it matches then it's possible you have a bad sdcard. If it doesn't match then your downloads are crappy.
working!
Got it working by flashing the modaco v1.3a - must have been a bad update.zip before like you said. Thank you so much for the help and clear explanations, I was really worried I had bricked it.
David, now that it is working, I would recommend updating your recovery to 1.5.2.
I just want to thank everyone that posted to this reply I honestly thought that I bricked my phone and thank to you guys I was able to revive it. Thank you again.
I had rooted my evo with of course the unrevoked and my brother was playing around with my phone and did a format on the sdcard now i lost my backup and all data dose anyone know how to get back to stock or know of a stock rom any help i will take thanks...
You might give "Testdisc" or "Recuva" a try. I have used both to recover deleted and over-written files. Both are open source and surprisingly effective. I prefer Testdisc and always have it at the ready of my computers.
If you really want to get back to stock, find the post in the dev section called shipped roms. Download the 3.70.xxx .zip and make sure it is named PC36IMG.zip and not PC36IMG.zip.zip and put it on the root of your sdcard. Boot your phone into bootloader by holding down volume down and power buttons and it will scan the card and find the PC36IMG and ask if you want to update. Select yes and let it do it's thing until it asks you to reboot your phone. Reboot and you will be back to stock. Make sure your battery is charged before starting.
You know the guy I'm talking about: while he's sitting in the VD clinic with an itchy crotch, he's praying to God: "Oh God, please don't let it be herpes. If it's not herpes I swear I won't visit another whorehouse as long as I live."
Then, as soon as the doctor announces that he's just got a case of jock itch and he should put some anti-fungal on it, the guy runs to the whorehouse to celebrate....
Because, see, just a few days ago I semi-bricked my Evo running after a failed Unrevoked. Not sure why it failed, but the phone would lock up every 15 seconds. So I flashed a stock image to repair the damage, and then a newer one, and wound up with a phone that worked except it wouldn't read the SD card or USB port (charging would only occur if the phone was turned off).
So as I was working my way through the fix I kept promising myself that if I got it fixed I'd just keep it stock unrooted and be happy with it.
Then, thanks to the good fold here, I managed to get the device running again the way it should. Wheeew, I thought, I'm happy now.
But... of course... it only took a few hours before the "root" itch hit me again. Fixing the semi-brick issue required installing z4root, and that app gave me a taste of da root acces... and ooooh did it taste goooood! Problem with z4root, though is that you're still s-on, and it's my understanding that if you're s-on and take the new GB update, you're SOL (at least for the time being). And I wanted to be s-off for the peace of mind it offered.
So my desire for real permanent root got the better of me. I decided that the reason unrevoked had failed for me the first time probably had something to do with all the cr*p I had installed on my phone. So I used Titanium backup along with z4root to back up the stuff I'd installed since getting my phone back and re-flashed the stock 2.2 image that had worked for me, and started with afresh phone.
Tried unrevoked one more time and... viola! It worked!!!
I'm happy now... a happy, unrepentant sinner!
Anyway, if you've read through all this: bless you.
I do have a couple of questions:
1) Am I correct that being s-off means I can now install unsigned ROMs the same way I installed the stock image I am on? (basically, rename it PC36IMG.zip, put it on the root of the SD card and boot into the bootloader and let it install)?
2) do I need to run "unrevoked forever"? I'm not clear on this. Getting some conflicting information from searching. My best guess, from what I've read, is that the latest unrevoked includes all the stuff that unrevoked forever does.
-Is blessed-
1. You don't need to make a PC36IMG to flash a rom; just download the file, then backup your current rom, do a full wipe, then flash the rom zip
2. You don't need to flash the forever zip; it was used to give you nand unlock -s-off- in the older versions of unrevoked, and was incorporated into the new one.
And keep applying that jock itch.
And once you flash a couple roms, you will get the itch to start using the kitchen and playing with your own custom rom, its only a matter of time, lol
I probably try two a week now. Its amazing how much work these guys do.
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
RileyGrant said:
Unrevoked forever is incorporated in Unrevoked now. So need for that.
Also, you dont flash them in the bootloader. Boot into the bootloader, then use volume down to go down to the option that says "recovery" then use the power button to select. It will boot into recovery menu which should have a list of options, go down to flash zip from sdcard, then select zip from sdcard. It will show you a list of everything on your sdcard. Navigate to wherever your rom .zip file is that you downloaded and select it. It will ask you if you want to flash, select yes.
PS dont forget to wipe before you flash. ("Wipe all user data/factory reset" option when your in recovery.)
Click to expand...
Click to collapse
OK, so that's pretty much the same as with the Nook flashing Phiremod (a Cyanogenmod variant).
Ok hello all, I have a bricked atrix here (new user) and cannot restore the previous firmware I backed up.
What I did step by step is:
I followed this guide to unlock phone and install CWM recovery mod. ( I backed up my factory "firmware" )
After that I installed Neutrino ROM 2.2 from here but it was a bit buggy and I wanna revert to my factory settings.
When I try to restore the old firmware checking md5 and bootloader restore ok, system gives me a message: "Error while restoring /system"
At some point I also installed "recovery-en-goapk-0630-1029" which seems just another recovery tool (dont know if this caused the issue)
I also have RSD Lite and the original ATT's 4.5.91 .sbf file but that cant work as well. Once I hit RSD mode on my phone and hit start on pc, phone says after a couple of mins: sec_exception: febe, 35, 35 and then doesnt progress anymore.
By the way my phone is European and it came with 2.3.4 preinstalled out of the box, I just wanna revert it back! please help!
what's that "sec_exception" about? I always get this when I try to RSD-mount the .sbf from ATT 2.3.4 Pudding
RSD tells me a short after: Failed Flashing Process. Phone [0000] . Phone did not re-enumerate after RAM-downloader was sent (0x703E); phone connected (Result FAIL)
First of all, I don't think you should be using an ATT sbf file with your European Atrix. Not a good idea; they are not the same.
Secondly, using a sbf and RSD is tricky business and should be avoided if possible.
If you want to return to stock I suggest using the tool in this thread:
http://forum.xda-developers.com/showthread.php?t=1421522
It is dead simple to use.
since I'm new to this (got some good pc experience tho) I wanna keep things clean and organized, so what can I do to clean previous installations , zips , rsd sbf mounting etc. As I see this, the phone's memory has 2 partitions, 1 for system and 1 for apps? Correct me if I'm wrong I'm just starting to get familiar with all this thing
If you follow the link above it will wipe everything on the phone and return it to stock. You will need to wipe your SD card yourself however.
Sent from my MB860 using XDA App
I had this with all recovery iv try I found out its because the system.ext3.tar backup is over 300mb the only the only. Way back from this was to ever flash a European gingerbread sdf or use fruitcake
the way I got past this was to deodx my rom so it is under 300mb
following the above link is the best method. please do so.
the method is perfect indeed, my phone is back to normal except that AT&T submenus and logo. Is there any program to view root folders and clean previous installations / garbage files? Any guides on what should be left off - uninstalled? (Neutrino 2.2 custom ROM had a file explorer that could navigate between root folders and sd storage
thanks again
i got the same issue but my phone doesnt turn on at all, just the led light in green then it goes off
have you tried to pull the battery off? Do you see the Motorola logo or just black screen?
Hi guys, you are my last hope!
Bought my Defy early 2011 and regularily updated with custom ROMs, so you could say I know a thing about rooting, RSD Lite, fixed sbfs, ...
Or at least I though I knew, but I still managed to kill my phone I think.
Here's what happend:
I tried to install Epsylon3s nightly from may 8th (http://defy.wdscript.fr/defy-cm9/). Before that, I was on CM 7.1
After installing the zip and rebooting, I saw the bootlogo, then i was asked for my pin code. As soon as i entered it, again to the bootlogo, again the pin, and so on.
So i realized something was wrong.
Could not get into recovery, so I flashed
JORDN_U3_97.21.51.sbf
as this often helped me in the past.
I then tried this one:
http://forum.xda-developers.com/showthread.php?t=1498843
Also didn't start.
So back to
JORDN_U3_97.21.51.sbf
But here it might be, that I misclicked (I have quite some SBFs in that folder, cause I wanted to be prepared in case something went wrong), as after that, I never got my Defy to work again.
I was stuck at the Motorola M logo.
Coudln't get into recovery, so no zips for me anymore, only flashing of sfb.
That's basically when I entered panic mode. As I didn't know what I just flashed, I could only guess the problem. So I tried the Ginger2Froyo (http://forum.xda-developers.com/showthread.php?t=1486731) in case I went to BL6. Also tried http://forum.xda-developers.com/showthread.php?t=1552152
But in this process, my RSD Lite started to behave strange:
when flashing, it's building the image, uploads it, checks checksum. But once it says "rebooting" it immediately jumps to 100% and pass. Phone how ever stays black and white LED.
Of course I can still flash other SBFs, and I tried various (JRDNEM_U3_3.4.3-36-1.7. sbf for example). But I either get the instant PASS, which tells me something didn't work, or sometimes I get the neverending bootlogo and RSD telling me to start the phone manually.
So... that's my story.
I can't seem to find a single SBF that would work for me. I screwed up big time.
To make this clear: at this point I don't care about downgradeability or anything thelike. Whatever makes my Defy work again, is fine. Froyo, Ginger, ICS, or whatever.
So if anybody still has any advice for me, I'll love you forever! Promise!
Thanks a lot in advance for any help you sure will offer,
Clock
Try this if you haven't :
Go into stock recovery and make a factory reset
Sent from my MB526 using XDA App
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Have u tried this thread:
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade
Clock1999 said:
As I said, i cannot even enter recovery.
I'd be really happy to find an sbf, that at least lets me reset my phone.
Click to expand...
Click to collapse
Im sorry , thought you mean custom recovery when you say you can't enter recovery.
I was in the nearly same situation but i never changed my bootloader...., by me out works to power up my phone with pressed volume button down to enter stock recovery ...
So I'm sorry i couldn't help you
Sent from my MB526 using XDA App
You just like to play with your defy, don't ya
Have you tried the suggestions under Common problems/questions in this guide?
Thanks for all the responses.
However all the guides seem to point to two options only:
1) Flash this one Eclair (which I already mentioned that I did, that it used to work, but since the "instant 100% on rebooting" doesn't anymore.
2) Factory Reset/Wipe. Which I cannot, as I don't get into Recovery Mode. All I can do atm, is flash SBFs. Defy won't enter Recovery Mode (which I guess is a pretty bad sign)
But the way I always understood it, was that you only need to be careful what you install, so you don't lose downgradeability. And that, once lost, you wouldn't be able to flash "older" roms, but newer ones would always be possible.
So shouldn't there always be a rom, that saves me?
What about Defy+ roms? Any advice on that? Which best to try first? So far, I haven't touched Defy+ roms at all.
Thanks for the support!
Did you try this:
When Off, press Vol. down and power.
You'll get an exclamation mark inside a triangle.
Press both Vol. up and down at the same time.
Now you suppose to be in stock recovery and you can do factory reset.
Do the above after flashing stock SBF.
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Clock1999 said:
Hello again!
In the meantime, I flashed some 30 different SBFs, and at least I learned something:
when the bootloader verson is 6, I get stuck at Motorola Logo. I can enter bootloader mode, but not Stock Recovery.
When bootloader is below 6, RSD Lite doesn't get the Dey to reboot, but shows instant 100% PASS.
Okay, maybe this was to be expected, but I didn't realize how very similar sounding ROMs have very different bootloaders...
So: can anybody guide me on whether installing a BL7 ROM would repair my problem?
I read elsewhere, that my green lense definitely will not work. Is this true, or are there fixes? And if it's true: if I'm sure the rest will be working again, I'll take that. If I just rob myself of future chances, I'll pass.
And hints here?
Thanks in advance so much! One week without a phone is pure horror!
Clock
Click to expand...
Click to collapse
If you flash any of the defy+ roms, camera won't work..there isn't a fix or patch for that..
Doesn't matter from where I send it, what matters is written above
corrinti said:
If you haven't flashed BL7, then check this http://forum.xda-developers.com/showthread.php?t=1486731&highlight=bl6+downgrade&page=2
Click to expand...
Click to collapse
Hi,
as I mentioned above, I already tried this ROM but it gives me the same result as all the others: stuck at bootlogo.
Maybe there is a special trick on which ROM I should flash before flashing this one?
Sorry, I do not know how to help. Just no idea now, try to dig the forum.
Once I had very similar problem - whatever I flashed I was stuck at bootlogo. And in my case I found out that just before flash my internal memory had been filled with some mess, which was not removed by any wipes (cache, dalvik cache, cache partition) and after any flash memory was too filled to start the system.
But finally I could flash Chinese eclair (CG5), which at last started horribly laggy, and I could wipe private data from a system - it gave me more than 1GB of internal memory back (from 40MB after all wipes and clean system install) and a way to flash whatever I wanted without a problem.
So even if it is also your problem, my way is not available to you now. Maybe you can find as small sbf file as possible and try then.
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Clock1999 said:
I'm sorry, but I don't quite get, which ROM saved you, and why that is no option to me. Can you please clearify? Thanks a lot!
Click to expand...
Click to collapse
I could use CG5 full sbf which will not boot for you as you put BL6 and maybe BL7.
To boot from flashed sbf it cannot be lower BL version.
I suppose that now you have a memory problem - flashing sbf do not wipe the memory.
At first I would try getting into stock recovery (even several times, just pull battery out, wait a minute, power, vol -, battery in) - if successful then do a factory reset and reboot.
If not I would try to find out a smallest sbf with proper BL version - just to give it more chance to boot with small memory available, if not then again try to get into stock recovery.
I'm the happiest guy around, as I finally revitalized my Defy.
For all you guys, who already tried everything: here's what worked for me.
Just let it rest a few days.
After I hadn't touched my phone for a couple of days, I thought about giving it one last try. So I flashed the Defy+ SBF (4th in this list: http://sbf.droid-developers.org/umts_jordanplus/list.php), like I've done multiple times before.
But this time, when rebooting, I wasn't stuck at the M-logo, but in a bootloop. And that gave me the smiles as I knew, that now I should be able to enter Stock Recovery again. From there on, it was no problem to get to a stable base again. After flashing the BL6 Froyo, I'm now on CM9 and everything is fine.
Thanks for all you help.
Sometimes, you just have to give it a rest...
Clock
It is a next such case I see in moto forums ;-) but it is really hard to give a tip: leave it for few days and check again
Use the sbf_flash for Linux
Sent from my MB526 using Tapatalk 2