So I am trying to install the Stock Deodexed ROM and i've wiped and all but when I got to install the zip, it aborts. It says failure at line 7. I have backups of Stock 2.3.4 i can restore to, so I can get to my goal of being at 2.3.5 for the Eclipse update tonight, but I'd rather a clean install. Why is the install aborting?
UbuntuBrandon said:
So I am trying to install the Stock Deodexed ROM and i've wiped and all but when I got to install the zip, it aborts. It says failure at line 7. I have backups of Stock 2.3.4 i can restore to, so I can get to my goal of being at 2.3.5 for the Eclipse update tonight, but I'd rather a clean install. Why is the install aborting?
Click to expand...
Click to collapse
This has happen to me before. I had to sbf and then it was fine for a while. But recently I had the same iussue again but I had already made a back up of eclipse 1.3 so I am also hoping eclipse 2.0 goes ok for me as well.
Finishing up a restore of my stock, then to update. The only reason I am is because i installed the mash up rom and my signal was amazing for a day, and then today, it has picked up miniscule 3g, dropped it, and remained on low 1x.
Flashing the deodexed rom is unnecessary, all you have to do is sbf to 2.3.4, root, use rootkeeper (if you want), update, and flash eclipse when released.
Sent from my DROID X2 using xda premium
Related
Guys I'm new to the forum but have been messing around with custom pseudo-roms for the Atrix for a little while now. I was running Adeo, then Gingerblur, then Greyblur all without a hitch when I heard about the new OTA update coming to the phone and Gingerbread coming up, so I wanted to go back to any build that would allow me to get the HSUPA update as well as the gingerbread update, but when I went to flash my phone to sbf using rsdlite, it said internal programming fail and nothing else happened. I installed gingerblur over greyblur in an attempt to see if it would flash, but nothing. Have done a factory data wipe, still can't flash. I can't even get into the stock Android Recovery, all that comes up is a triangle and exclamation point. Could someone please help me out here, I'm running gingerblur on a rooted Atrix on 1.5.7 and cannot get it to flash sbf, all I want to do is go back to stock att rom for the coming updates.
Thanks,
BK
Hey,
I have the same exact set up as you. It seems vague in your post if you re-flashed back to 1.26, and that may be why you're getting errors? Every time I update roms, I re-flash to 1.26 using the method in the link below.
http://forum.xda-developers.com/showthread.php?t=991072
Then I ran Gladroot to unlock, enable sideloading, etc.
http://forum.xda-developers.com/showthread.php?t=1016060
Downloaded and install the 1.83 update online (not on-air because I didn't get prompted)
http://www.motorola.com/consumers/v/index.jsp?vgnextoid=9098bc50a569f210VgnVCM10000081bbb00aRCRD
I ran the 'afterupdate.bat' on Gladroot after installing the update.
And I now have 2.2.2 / 1.8.3
Thanks bud, what I ended up doing was trying to manually uninstall gingerblur and greyblur and the adeo rom by using scripts etc but it never worked. My phone started acting weird, the home button stopped working, no 3g connectivity, it would say I have superuser but it wouldn't be rooted... something was seriously messed up. I tried to get into the stock android recovery but it wouldn't boot, I think something was corrupted. I knew sbf files rewrite system and boot data, so I went into tenfar's custom recovery (after rooting for the 10th time) and deleted system and boot data, system data was deleted, but boot data had an error. I wiped the caches and all and I tried to sbf flash to 1.8.3 but nothing and the phone bricked. I then tried it on another computer with more memory than mine (mine was running kind of low because of a linux partition) and the flash worked and I'm on 1.8.3. I think I'll wait for official gingerbread and unlocked bootloader in July before I mess with my phone again.
I was trying about 10 days to install any 2.3.4 based rom on my AT&T atrix!
Everytime i trying to flash some rom (mostly i've tried Alien's and Cherry) i see bootloop: red circle with "M" >at&t logo >"M">"M">"M"... I have an unlocked bootloader, can see the sign "Unlocked" ot top of the screen, Rooted And CWM Recovery by tefnar installed, BUT EVERY TIME i flashing some rom i stucking on that bootloop. I was trying to search on xda a lot of time, still cannot find the answer. That makes me real sick of it, i'm not sleeping at nights, pleeeaseeee heeeelp!!!
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
First install rom racers recovery. Two. Make sure youre wiping everything before and after you flash, unless youre upgrading the same rom, you dont have to but still recommended. Three, be patient on initial boot of a fresh flash. Sometimes it can take awhile and might reboot still.
I voided my warranty.
lemortede said:
How long are you waiting for your phone to boot. It can take a while. 10+ minutes.
I waited until yesterday to update to 2.3.4 because I was on call.
Things I did.
1) Made sure that I had the lastest CWM.
2) Made sure I had the latest pudding.
3) I installed 2.3.4 pudding first. Note: I had to re-install CWM after this. Not a huge deal since it installed from fast boot.
4) Followed the ROM install steps here
5) Installed the recommended radio.
6) After that it should work. I had to install the webtop and the ad block but have had no problems since.
I am now trying to decide what Kernel to mess with.
Click to expand...
Click to collapse
I was waiting approx. 5 minutes, but is that suppose to be like that? I mean flashing screen on a bootloop? Because fading screen, when reboot looks like if i take battery out everytime. Besides, i've installed any of gingerblur or greyblur easily, but when trying to install 2.3.4, see that crap again.
I'm using all latest (CWM, Divers, RSD...)
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
iRobby said:
Are you wiping both the system cache and dalvik cache before you flash the rom?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I Do. Maybe here some thing i've missed before. Now I have 4.1.83 on board, and can install any of 2.2.x, but NOT 2.3.4 Why?
Is the OTA update only wayout??
thread still actual. UP
Hi,
i just flashed CM7 pre beta 3 after flashing almost every rom in the forum available and not satisfied by the GB ROMs i want to go back to stock froyo.
I have already downloaded Bell Froyo 2.2.2 gobstopper file,
tried to flashed it over CM7 and unable to complete the process
"Process aborted" for some unknown reason.
Can any one guide me to how to go back to stock.
xateeq said:
Hi,
i just flashed CM7 pre beta 3 after flashing almost every rom in the forum available and not satisfied by the GB ROMs i want to go back to stock froyo.
I have already downloaded Bell Froyo 2.2.2 gobstopper file,
tried to flashed it over CM7 and unable to complete the process
"Process aborted" for some unknown reason.
Can any one guide me to how to go back to stock.
Click to expand...
Click to collapse
Use tenfar's unlocked CWM.
Cheers!
Testing rit now, report with results as soon as i get the stock love
Flashed without any problem,
factory reset, wiped cashe
installed unlocked bell zip
after reboot red led shows up and phone reboots.
I think i am stuck in boot loop
Now what to do ?
I have managed to get back to Aura ROM
now will try to go back to stock.
Booting Aura rit now (y it is taking forever to boot )
Finally out of CM7
Now trying to go back to stock
Well, not sure what happened there, you can apply the ihop_bell again to see if that fixes it.
Cheers!
I managed to get back to Aura ROM and tried to flash bell 2.2.2 zip and process aborted i think that zip only works with tenfar's unlocked CWM only that managed to fully flash the rom but stucked with boot loop.
Now going to flash Alien rom (personally Aura removes blot and adds his own crap)
Nop bell stock 2.2.2 is giving error in all 3 recoveries
What to do ?
Have you tried fruitcaking?
iRobby said:
Have you tried fruitcaking?
Click to expand...
Click to collapse
Nop not yet, i want to go back to stock Bell
is it any good ?
Hi,
If you backed up your pds partition, try restoring that. Probably some sbf you tried modified it, changing the signature maybe.
Cheers!
I didn't backed-up any thing (no need of backup)
if u have any then let me have it
Nop dont have any backup, didnt bothered to keep any backup. now i am thinking i was so wrong
Hi,
I just threw that out there, it's the only partition that I don't touch, but sbf files can modify it, since I got my replacement phone I have never used a French/Orange/ATT whatever sbf, so that's probably the difference. My backup is the 2.2.2 Gobstopper really, I also have a pds backup but it's useless for other phones.
Only other idea would be to change the radio first, there are radio only sbfs out there, go for the .15P one for Bell. Once on my previous phone when going from Telstra and French there were issues due to the radio if I recall correctly.
Cheers!
Nitro suggested I update to 2.3.5 before I go about installing the Eclipse 2.0 update this evening. Well whenever I try and flash a zip from SD card, it aborts and gives an error. It happens with the Update, and installing ROMS. I fear that I won't be able to update to 2.0 this evening because of this error. Any ideas to fix it?
Try and sbf and get a clean start. If you heave not done that then do that first. Which update did you use? .412 or. 413
Which recovery are you flashing the update from? I flash it from my external. See if that makes a difference. And as said you have to be bone stock 2.3.4 for the update to work
Sent from my DROID X2 using xda premium
CadenH said:
Which recovery are you flashing the update from? I flash it from my external. See if that makes a difference. And as said you have to be bone stock 2.3.4 for the update to work
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Updated with android recovery. The last time I tried to flash molten it aborted but I did not care since I already had backup of eclipse 1.3 I just updated to 2.3.5 with android recovery and restored root with rootkeeper app.
The best I have done is sbf the leak then flash the 213 ota from folder "1 235" in my fake mp3 http://www.mediafire.com/file/4loqisamcd4y8ya/1_to_4_235isAzip.mp3 just change it to .zip.
Ah this sucks. I flashed eclipse 2.0 and it aborted line 294 permission error crap again. So I sbf back to 2.3.4 and re rooted. Re did the update and then tried again. Same error. Man I dont understand it will flash everything else except on the roms. When I went to 2.3.5 I flashed the drop down toggles and battery fix. This only happens when I flash roms. I have work tomorrow so i guess I will sbf one more time and re root so I can get back to my back up of eclipse 1.3 and mess with this again on my next day off on Sunday. Maybe I will try to go back to 2.3.3 and do OTA updates? I am at a lost and have not heard of any fixes for this out there yet!!!
Still having the same problem here, too. I just sbf'ed to 2.2.2 instead of 2.3.4 and took all OTA's. Did a NAND on 2.3.4. Getting ready to update to 2.3.5 via stock recovery.
Well that was a fail, too. Currently on stock 2.3.5 rooted. Guess I'm not sure what to do now. I still have my nand of Eclipse 1.3 but would have to sbf back to 2.3.4 again and go through it all just to restore it. This sucks!
Just got 2.0.1 Eclipse running this morning no issues.
UbuntuBrandon said:
Just got 2.0.1 Eclipse running this morning no issues.
Click to expand...
Click to collapse
What did you do it get it to work? Did it fail last night for you also or was this your first time trying?
Well I SBF'd and factory reset from stock recovery. Then I updated to 2.3.5 from stock recovery. Then I rooted with ZergRush, and then I flashed 2.0.1 Eclipse with x2 Bootstrap.
There have been issues with Root Keeper. So if any of you are using that, dont. Follow these instructions and use these files:
http://forum.xda-developers.com/showthread.php?t=1391824
I finally got it working, too. Root keeper is the issue. Now on 2.0.1. Will be on 2.0.2 later tonight!
Sent from my DROID X2 on Eclipse 2.0.1.
Agreed. 2.0.2 will be on mine too. I vote, though, that these minor updates chill xD
When I received my phone, it was on GB 2.3.3. I got the OTA for 2.3.4. I am now rooted, and running Eclipse 1.3, with Speedy 7. I was trying to follow the steps to flash Eclipse 2.0.3, but when I tried to SBF to 2.3.4, it hangs on applying update in bootstrap. It just stays there, and never progresses to install. Is it supposed to take a long time to apply the update since my device was originally 2.3.3? I really want to update to the newest Eclipse, but this troubles me. It is possible I'm doing something wrong, but it does seem straight forward. Any help would be appreciated.
It hangs om applying update in recovery, just to clarify.
Lord Nykon said:
When I received my phone, it was on GB 2.3.3. I got the OTA for 2.3.4. I am now rooted, and running Eclipse 1.3, with Speedy 7. I was trying to follow the steps to flash Eclipse 2.0.3, but when I tried to SBF to 2.3.4, it hangs on applying update in bootstrap. It just stays there, and never progresses to install. Is it supposed to take a long time to apply the update since my device was originally 2.3.3? I really want to update to the newest Eclipse, but this troubles me. It is possible I'm doing something wrong, but it does seem straight forward. Any help would be appreciated.
Click to expand...
Click to collapse
Make sure to apply update to 2.3.5 (.412 build) is applied using stock recovery not bootstrap. Phone off. Power and volume down button at same time. Volume down until you see stock recovery then volume up. When you see the triangle hit both volume buttons at same time. From stock recovery you install your update zip. Make sure to rename zip file to update first. Good luck.
Am I flashing 2.3.4 through bootstrap recovery, or stock? That's my issue, I do it through BSR, and it never applies the flash.
I know I need to SBF, but it never works.
To SBF, you need to use RSD Lite in Windows to flash 2.3.4. Once you've done that, apply the 2.3.5 update in android recovery. No need to to root until you've updated to 2.3.5. After you've applied the 2.3.5 update, root, install BSR and then install Eclipse using BSR.
Have a look at the first post in this thread. It looks like a lot but it's not as big a deal as it looks. You can just download the 2.3.4 file and use that. There's no need to do 2.3.3 first.
Lord Nykon said:
I know I need to SBF, but it never works.
Click to expand...
Click to collapse
What does not work? Are you turning your phone off and powering it up and volume up at the same time to start your phone up in rsd mode. If not rsd it will not recognize your phone.
Also, before you SBF, boot into stock recovery and do a factory reset/data wipe.
After that, reboot and using RSD lite to SBF back to 2.3.4.
If you're new to SBFing, here's a link to a great tutorial to help you out:
http://forum.xda-developers.com/showthread.php?t=1317707
Followed the directions, and I'm proud to say I am now running Eclipse 2.0.3! Thanks so much for your help!
Congratulations and enjoy. Dont forget to do a nano backup now and then you can play with some themes
Also i would highly recommend v6 supercharger. Moon shadow wrote up a good tutorial on how to install with 2.02 but it is the same for 2.03. If you are interested i can find you the link.
I have Speedy 7 installed, can I put in supercharger as well?
Lord Nykon said:
I have Speedy 7 installed, can I put in supercharger as well?
Click to expand...
Click to collapse
You would need to remove the 97 memory charger script from speedy 7.
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Look at this thread here at the end. http://forum.xda-developers.com/showthread.php?t=1412729&page=5
This is what i am running now but to be honest i think 2.03 did better with just v6 supercharger. I am going to run this way for another day or so.