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
Related
1.83 is just a speed update right? Like network speed? I am running grey blur with the telstra or what ever radio for the higher upload speeds. ... with that said is there any reasons at all to update to 1.83 anymore? It is there more s
To the 183 update then just dl and up speeds. Right now I get 4-6 down usually like 5.3 down or so annd 1.1 1.4 upload with the 1.77 (telstra or w/e) I went through different fourms and didn't really find my answer so I decided to write the exact question which is it word upgrading ... my battery has gotten worse though . Thank u.
Sent from my MB860 using XDA Premium App
i highly recommend Going to 1.83. The 1.83 radio is different from the telstra, i had the hot phone and battery issue running it like everyone else. 1.83 Does fix bugs in the system with the screen and a few other tweaks to enhance interaction, I am on 1.83 OTA and phone is cold as ice and my battery last me almost a full day with normal use that is. Might as well get the legit update, an update in future may conflict with the telstra radio. Telstra 1.77.17, 1.83OTA & SBF radio- 1.77.15
Thank u so much I guess ill have to erase my phone all over again and go back to 1.26 and then 157 then 183 right?
Sent from my MB860 using XDA Premium App
Dirtburgler said:
i highly recommend Going to 1.83. The 1.83 radio is different from the telstra, i had the hot phone and battery issue running it like everyone else. 1.83 Does fix bugs in the system with the screen and a few other tweaks to enhance interaction, I am on 1.83 OTA and phone is cold as ice and my battery last me almost a full day with normal use that is. Might as well get the legit update, an update in future may conflict with the telstra radio. Telstra 1.77.17, 1.83OTA & SBF radio- 1.77.15
Click to expand...
Click to collapse
can this 1.83 OTA run over GreyBlur 2.1?
Thanks
Araf said:
can this 1.83 OTA run over GreyBlur 2.1?
Thanks
Click to expand...
Click to collapse
No
Sent from WinBorg 4G using XDA Premium App
Back to 1.26, then OTA back up to 1.83 then Gingerblur 3.1 if your looking for a pseudo rom. I haven't seen greyblur for 1.83 yet. Im sure its in the works though. ive used them both but i am getting tired of flashing back to 1.26 lol. I think ill wait for the door to the bootloader to be kicked in (if ever) before I put a Rom back on. Im going to give my Atrix Hardware a breather for a while I think.
Araf said:
can this 1.83 OTA run over GreyBlur 2.1?
Thanks
Click to expand...
Click to collapse
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update with RSD Lite on to your phone, this will reset your phone completely to stock.
2: Run GingerBreak to roots the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
IrateCustomer said:
Here are the steps I had to use being on 1.5.7 with GingerBlur:
Here is what you'll need after backing up your apps/files to the SD Card, in this order:
Download RSD Lite 5.0
Download 1.8.3 sbf
Gingerbreak
GladEnable
Tenwar's System Recovery
GreyBlur 2.X (Or insert custom ROM here)
1: Flash the 1.8.3 update with RSD Lite on to your phone, this will reset your phone completely to stock.
2: Run GingerBreak to roots the device.
3: At this point I was unable to install Tenwar's, so I used GladEnable to sideload it.
4: Installed Tenwar's and loaded up my custom ROM.
5: Restore your backup.
Click to expand...
Click to collapse
Thanks for sharing the steps...
Sent from my MB860 using XDA Premium App
I'm sorry if somebody already posted that, i swear I had a look
I have a SIM unlocked AT&T MB860 Atrix with gingerblur 4.5, and I would like to try some real gingerbread goods, which means bootloader unlock and 2.3.4 HKTW.
Do I have to flash back to 1.8.3 stock sbf before actually unlocking and installing gingerbread? I heard people saying is not safe to flash sbf for SIM-Unlocked Atrix because it can cause Wi-Fi problems, is it still the case?
Second problem: I had my phone rooted, but now I don't have an external micro SD card, so I wouldn't be able to root with gingerbreak-similar methods, is this a deal breaker or there is another way to complete the process all the way through?
Thanks a lot
As a general rule, it's best to flash back to stock before flashing anything else. Because Gingerblur requires Tenfar's recovery to run, I believe this will be the best way to do this. If someone else could chime in about the SIM-unlock/wifi issue, that would be great.
As for the rooting method on 2.3.4 HKTW, it works by installing a ZIP through recovery. In my own experience, it only seems to read external SD cards. If you can make it read the internal somehow, then you should be able to root.
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
dLo GSR said:
i was on GingerBlur 3.1 (rooted via GladRoot), and did the following over the weekend
- flashed the unlocker SBF (still on 1.8.3)
- flashed the new CWM onto the phone via fastboot
- flashed GingerBlur 4.5 using that CWM, just for a few days
- flashed the 2.3.4 IMG using the Windows x64 guide in the general forum.
ran into no problems, and the GB build was already rooted when it booted up.
Click to expand...
Click to collapse
Good to know, thanks!
Did you clear data or anything like that after flashing?
jwhited said:
Good to know, thanks!
Did you clear data or anything like that after flashing?
Click to expand...
Click to collapse
oh, right, forgot. i did do the fastboot -w beforehand.
i have simunlocked atrix as well, it makes no difference.
I went from Greyblur straight to GB with no issues.
Thanks guys
This is worth a try
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
kshiuan said:
If I wanted to return to the stock ROM after flashing 2.3.4, all I have to do is RSDLite flash 1.8.3 back correct and then restore using CWM?
Click to expand...
Click to collapse
I just did this tonight, and for some reason, I had some problems flashing the 1.8.3 SBF directly. So I downloaded the 1.2.6 (shipping) firmware and just did the updates.
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
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.
Guys,
What should my baseband read? I lost my 4g and I read somewhere that my baseband should indicate if it is 4g. Mine does not, it reads CMDA_N_04.07.01R.
Is that correct?
I use the ICS flashing utility 1.1, but I decided to go back to .173 to take the OTA to .181. After all of that, I have not so much as seen a glimpse of 4G....
I had the same issue but since you went to 181 I can't help. Use your utility and go back to 173. I used a bone stock 173 update zip which I flashed thru stock recovery. I didn't wipe anything and lost no data and it put my radios back in. If you can't find it I will be uploading to 4shared and drop you a link once it completes
Use this once you are back on 173. Just flash it on top of it. Don't use a custom recovery. Don't install one. Don't freeze any apps. Just be stock 173. Do exactly as this says and make sure you have 50% or better battery.http://www.droid-life.com/2012/01/2...ings-phone-to-android-2-3-6-no-root-required/
You sir are a hero. Back up and running!
Sent from my cm_tenderloin using xda premium
Glad it worked. I didn't have time when I found out about mine. No laptop handy and dropped that while at lunch. Really happy it worked on mine.