I've noticed that both the built-in android recovery and Clockwork Recovery allow a user to flash just about any zip they want. Is there a functional difference between the two?
tech.kyle said:
I've noticed that both the built-in android recovery and Clockwork Recovery allow a user to flash just about any zip they want. Is there a functional difference between the two?
Click to expand...
Click to collapse
First off, the clockwork recovery doesn't work for x2. You have to use bsr recovery. As for applying updates, the stock recovery will do official motorola ota updates (like the 2.3.5 update), but it won't install custom ROMs. BSR will do ROMs and one time I did apply an OTA update with it, but your mileage may vary.
Sent from my CM7ed X2 using Tapatalk.
Stock recovery u can ONLY flash Motorola signed zips
Our cwr will do any thing the stock will. I always use the install zip>choose zip rather than the apply update... You don't have to rename it to update... And do not be alarmed when it just shuts down. It looses root perms and system closes it or so I assume. Be sure to use voodoo root keeper . It gets bad rap here but just use my rerecovery and if eclipse bombs delete suback up and eclipse latest will work with rk. Enough?
skwoodwiva said:
Our cwr will do any thing the stock will. I always use the install zip>choose zip rather than the apply update... You don't have to rename it to update... And do not be alarmed when it just shuts down. It looses root perms and system closes it or so I assume. Be sure to use voodoo root keeper . It gets bad rap here but just use my rerecovery and if eclipse bombs delete suback up and eclipse latest will work with rk. Enough?
Click to expand...
Click to collapse
Im sorry but this process is way more complicated than just flashing 2.3.5 , root zergrush, install BSR, install eclipse
Ash... I have never gotten ZR to work. I have issues w/ my old laptop. Others too have ZR troubles. You do not need a pc with voodoo rk. It IS different but not more complicated if ZR don't work.b
I still use Petes.
skwoodwiva said:
Ash... I have never gotten ZR to work. I have issues w/ my old laptop. Others too have ZR troubles. You do not need a pc with voodoo rk. It IS different but not more complicated if ZR don't work.b
I still use Petes.
Click to expand...
Click to collapse
True
I don't even have a working computer but I refuse to use rootkeeper unless I absolutely have to.
Last time I used root keeper I had a paperweight in my pocket for 36 hrs until I could get to a computer lol....that's why I recommend (like others) to stay away from it unless u REALLY need to use it.
You were overzel'ed cuz of yo predictiment. Fess up man. Give po voodoo a chance.
iBolski said:
First off, the clockwork recovery doesn't work for x2. You have to use bsr recovery. As for applying updates, the stock recovery will do official motorola ota updates (like the 2.3.5 update), but it won't install custom ROMs. BSR will do ROMs and one time I did apply an OTA update with it, but your mileage may vary.
Click to expand...
Click to collapse
BSR is what I meant. (I thought it was based off CWR?)
Either way, thanks! Now that you mention it, I think I remember hearing that somewhere.
Well we have a lame version of cwr, very old and adb will not work but the every day: BU, restore and flashing work fine, bsr = system recovery = cwr = (the new rerecovery) . See my thread in the dev sec. And how rerecovery solves the "data wipe dilemma". Btw it is rom manager and the newest CWR that do not work on our retard phone. RM will not tell you it does not work it will DL the latest 2025 ver and not do a thing.
Related
Okay, so I see there are many people that have the same questions I had yesterday trying to apply this update with a custom ROM already on my phone. Here is what you'll need and how to get your phone updated. This isn't the only way to do it, but it's what I did and it was pretty easy. It was harder finding out how to do all of this, and in what order than actually doing the process.
It will take a little while to do this, roughly 30-45 minutes.
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 on to your phone using RSD Lite, this will reset your phone completely to stock.
2: Run GingerBreak to root 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.
This should get you all updated and with your custom ROM installed.
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Thanks a lot for this....
spitefulcheerio said:
Awesome! Thanks man
quick question: how do we make a backup (Ti Backup?) on our current setups? And will restoring the backup we make bring back all apps and settings and everything?
Click to expand...
Click to collapse
Yes, use Titanium Backup to backup your User Apps and Data, not the system apps or data. And make sure to backup to your SD Card as the flash with wipe your internal memory and your backup will be lost. I had that issue and had to reinstall all of my apps. It's minor, but still a pain in the ass.
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
IrateCustomer said:
When I flashed 1.8.3 through RSD Lite, it completely put everything back to bone stock. It wiped the entire internal memory. So I'm not sure if it should or shouldn't, but it did. I know it wasn't GingerBreak because you flash the update before installing GB.
Click to expand...
Click to collapse
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Swiftks said:
that's weird, b/c when I flashed it, it didn't wipe anything just added the bloat ware back and changed the radio, etc. still had homescreen the same with all my apps, etc.... oh well
Click to expand...
Click to collapse
Maybe because I was on 1.5.7, and flashed 1.8.3 instead of going back and OTAing the phone. That would make sense because the OTA process probably does a backup/restore during the process. As mentioned in the OP, it's only one way to do it, but there are other options.
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Datblkbro said:
the sbf download is sending me to Motorola site,, dont I need the sbf not the exe??
Click to expand...
Click to collapse
I've updated the link in the OP so you can download the correct file. My apologies.
Regarding 1.8.3 sbf, which of the sfb files from the link you provided is it? They vary in size. Thanks.
You want the one with the most hits and the ridiculously long filename.
It actually has 1.8.3 buried in the name of the file. It's a few from the top.
THANK YOU this has been a big question mark for me ever since 1.83 came out. Fantastic guide.
Swiftks said:
Flashing 1.83 should not wipe anything; as far as apps or info. goes. Some people have had a problem with gingerbreak wiping some things though. I flashed 1.83 and ran ginerbreak with no problems, except for having the bloatware re-installed and loosing my root, but that's to be expected.
Click to expand...
Click to collapse
Did the GingerBlur 3.1 get fixed when it comes to the Webtop mod? Cuz I read something about it having a problem with actually working on this Rom? Maybe that was on the 3.0, so I figure 3.1 fixed it?
PLease just a simple "yes it works" or "No, it doesn't" will suffice
Thanks
Just wanted to post my initial experience with using RSDlite to update afterting and gingerblurring it.
I followed your how to as much as I could (You should provide a link to RSDlite instructions, I had to search for it because I didn't know how to do it exactly... not a big deal but it would make it easier/idiot proof)
When I first updated via RSDlite, something must hve went wrong. At first, A triangle and lil android was haunting me on my screen... so I went to reboot.. **** [I thought I bricked it]... Then I restarted it again... DOUBLE ****... Couldn't load into recovery... I restarted a third time and it loaded up(**** YES). But for some odd reason, it said I still had to update (even though it said the firmware was @ 1.8.3.)
Everything seemed to work fine, and was able too root and ginger blur it. About a few hours later, wifi seemed wonky (kept randomly disconnecting and the update dialog came up every 15 minutes).
I ended up reflashing to 1.2.8 and OTA's all the way up to 1.8.3 and then re-rooted and blurred it. No problems since the full refresh
Hopefully everybody elses experience goes better than mine!
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
winky! said:
Also, Random question. How do you remove Tenwars System Recovery app after using it to load up a rom?
Click to expand...
Click to collapse
You can use Uninstaller for Root (I found it on the Market), and you can uninstall from there if you wish. Personally I see no real reason to remove it, but you can if you need to with the above referenced Uninstaller. There are a few others that can do it, but UfR is free, which is clearly a win.
564mb for the sfb??? Thats freaking huge
GreyBlur on 1.8.3
After following the steps I still show
"System Version 4.1.57MB860.ATT.us"
rooted and sideloading enabled by gladroot then flashed greyblur 2.1....little help for the n00b?
I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Jubakuba said:
I'm not an android noob...
But just curiously browsing this forum because my sister is getting an Eris as a semi-permanent replacement for her crapberry that she lost.
I can't stand to see her stuck on cupcake...and she's given me the go-ahead to get her up to speed.
I plan on putting CM7 on there for her...
But I have a few questions.
Rooting:
Should I just use this application?
https://market.android.com/details?...1bGwsMSwyLDEsIm5ldC5hbmRpcmMuZXJpc3Jvb3RlciJd
Click to expand...
Click to collapse
Yes. Install the app. Run the app. It will tell you to restart the phone - so, that means shut down the phone. Start it back up again. That will have installed Amon_RA recovery, which will allow you to Nandroid backup, install a custom ROM, etc.
(So, after that restart, you can shut the phone down, hold VolUp while powering on to get to Amon_RA recovery. You sound experienced enough to know what to do from there.)
By the way, the Eris by now should have Eclair (2.1), not cupcake (1.5). There should have been three OTAs that brought cupcake up to 2.1.
And then to get CWM...
Rom Manager?
I see that CWM is bricking phones...why is that and how common is it?
Are there alternatives I should use instead (RZrecovery or similar?)
Click to expand...
Click to collapse
As you have seen, many people running Clockwork Recovery as the default recovery have bricked their Erises. ROM Manager comes with almost all of the CM7 ROMs, but you can install it. From within ROM Manager you can have it flash Clockwork, which puts an update.zip file on the SD Card. Go into Amon_RA Recovery, Flash a zip from SD card, choose update.zip, and it will start Clockwork, if you prefer using that. (I actually always do this, as I prefer the Nandroid backup and wipe functions in Clockwork over Amon_RA.) Running Clockwork in this way is safe, as Amon_RA remains as the default recovery.
And as far as returning to stock...
We use SBF's with Motorola.
What is the alternative here?
Do I have to rely on Nandroids?
Can I restore a stock nandroid from CM7?
Click to expand...
Click to collapse
No SBF files for the Eris; however, user bftb0 created a ROM that you can flash that reinstalls stock Recovery and the stock 2.1 ROM. It's called Flashback_21v2, located here: http://forum.xda-developers.com/showthread.php?t=792026
The no radio version should be fine for this purpose.
Perfect.
And I even meant to ask if there was a way to boot into the custom recovery from a power-off state...which you already covered!
That's all I needed.
I appreciate the time you put into answering every question...most people tend to pick one and then the thread dies.
Thanks!
Edit:
Oh, and ya her phone hasn't arrived yet...
The HTC official website said Cupcake...wow that would have been out-of-date!
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
I am working with a company phone at my bosses request..what he really wants is a rooted phone on Froyo with Clockwork recovery.
This proved to be more of a challenge than I thought (Froyo). I did try to get around the signed update problem in the E3 recovery but wasn't successful.
Finally, I odin'd back to Eclair and installed CWM. It is weird in that I have to reinstall the update package each time to get CWM.
My questions:
1) anyway to get it into CWM directly (each time?; so it defaults to the CWM)
2) re Froyo, I guess the only way is to use CWM to install a Froyo based ROM?
a) If so, any recommends on an almost stock rooted ROM with Exchange email? (would prefer one that had the bloat removed, however; prefer stability to speed)
b) If I flash a Froyo ROM, am I ok in that I don't have to mess with the new bootloader business?
Thanks for the help!
(an Atrix owner out of his element and nervous about the bootloader biz after having previously dealt with the Moto locked bl problems )
You don't need to mess with bootloaders in order to install froyo. If you're on eclair then just put the attached update.zip posted by s15274n on root of your internal sdcard. Do not rename it or anything. Get into recovery, reinstall packages TWICE and you'll have your recovery then flash any froyo rom you want. Yes, it is that simple. There are few latest ones posted by Jellette and fishman0919 in development section. For example this one ...
http://forum.xda-developers.com/showthread.php?t=1586472
OR this one...
http://forum.xda-developers.com/showthread.php?t=1565768
Or this one...
http://forum.xda-developers.com/showthread.php?t=1589429
PS Is it hot in valley already? lol
Alex9090 said:
You don't need to mess with bootloaders in order to install froyo. If you're on eclair then just put the attached update.zip posted by s15274n on root of your internal sdcard. Do not rename it or anything. Get into recovery, reinstall packages TWICE and you'll have your recovery then flash any froyo rom you want. Yes, it is that simple. There are few latest ones posted by Jellette and fishman0919 in development section. For example this one ...
http://forum.xda-developers.com/showthread.php?t=1586472
OR this one...
http://forum.xda-developers.com/showthread.php?t=1565768
Or this one...
http://forum.xda-developers.com/showthread.php?t=1589429
PS Is it hot in valley already? lol
Click to expand...
Click to collapse
Thank you, sir!
It is always hot here....
Okay I have done with process with 2.2 eclipse as well and it didn't work either so I figured I would try it with 2.3
I do every single little thing in this list.
1. sbf to 234
2. Root using MotorolaOneclick
3. Install Voodoo OTA rootkeeper and protect root but temp unroot
4. Apply 235 update in stock recovery
5. Restore root in Voodoo rootkeeper and delete backup (make sure root is restored before deleting!)
6. Install bootstrap
7. Reboot into bootstrap recovery
8. Wipe data
9. Flash eclipse
10. Profit from its beauty
After its all done and flashed and loaded the wifi ALWAYS says error. Now if their is a patch or zip out there that I need to install I am all for that but there just has to be a reason after trying this ten time that it fails every single time. I love how stable this rom is OS wise, but this wifi deal has got to stop. Someone let me know if they find out anything please.
I realize this is a few months old, but just out of common courtesy, here's the solution I used.
I was have the same frustration and finally found what the problem was after a good amount of hunting.
When you apply the 2.3.5 update make sure its 2.3.5-418. I kept applying the wrong 2.3.5 and wifi never worked.
Finally just got It working using the correct update with same process. DL available here http://forum.xda-developers.com/showthread.php?t=1703640 It'll be this one "2.3.4-380 to 2.3.5-418 (official OTA)"
Try to reflash the firmware or try some apps like wifi fixer.
DONT FORGET TO HIT THANKS.......