Hello all
Today, after quite a long time, I unlocked my bootloader and installed CWM recovery, but I'm still with 4.1.83.
I have some questions:
1) If I want to flash a custom 2.3.4 rom do I need to flash the 2.3.4 update first usind RSD, or can I flash it right away from the CWM? (After a full wipe of course)
2) Do I need to flash a 2.3.4 radio prior to flashing this rom? Can I use the flasheble radio from here: http://forum.xda-developers.com/show....php?t=1163009 ?
3) What should be the size of an average 2.3.4 rom? because I downloader both the full Alien #2 rom and the CherryBlur 1.4b, is it possible that the Alien is 163MB while the CherryBlur is 553MB?
Thanks for the responses
alien blur is smaller because not cooked all the way its in beta testing and needs work....and yes you can flash to a rom if you wipe everything....
Moonshield said:
Hello all
Today, after quite a long time, I unlocked my bootloader and installed CWM recovery, but I'm still with 4.1.83.
I have some questions:
1) If I want to flash a custom 2.3.4 rom do I need to flash the 2.3.4 update first usind RSD, or can I flash it right away from the CWM? (After a full wipe of course)
2) Do I need to flash a 2.3.4 radio prior to flashing this rom? Can I use the flasheble radio from here: http://forum.xda-developers.com/show....php?t=1163009 ?
3) What should be the size of an average 2.3.4 rom? because I downloader both the full Alien #2 rom and the CherryBlur 1.4b, is it possible that the Alien is 163MB while the CherryBlur is 553MB?
Thanks for the responses
Click to expand...
Click to collapse
You should never have to use rsd ever again after unlocking bl. Stay away... use fruit cakes in the dev section. Use fastboot and img files this applies to radios as well. All it takes is a power failure or your computer to lock up in the middle of rsd flashing and its game over.
Radios can be flashed at any time.
Those are both normal. Depends on the rom. 200-300 mb average
Sent from my MB860 using Tapatalk
Thank you both for these answers, I flashed already the gb beta 4 of kenneth,without the radio for now, and I must say that the new blur looks really nice
an other thing is that I personally don't think that wiping the device via 'wipe data/factory reset' from the recovery is wise, since it wipes also the internal and external memory cards, which is not required to flash a rom, just format the data, cache, system from 'mounts'the should be enough.
good night
Related
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.
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
Welcome to the EternityProject...!
What do we have here?
Android....
.....Ice Cream Sandwich for Motorola RAZR XT910 (GSM/UMTS)!
This is a PREROOTED ICS ROM to be flashed with the BOOTSTRAP RECOVERY. It does contain everything you need. It is intended for developers and people who wants to enjoy the light performance & stability modifications in this ROM.
It actually doesn't work on BR devices because of different signatures
Requirements:
1. Root
2. Bootstrap Recovery
3. Official ICS OTA already installed
Flash How-To:
1. Download the file
2. Place it on the root of your external SDCard
3. Go into Bootstrap recovery
4. Go! Go! Go!
Making it to be fast & stabler:
Settings -> Developer Options -> Force GPU Rendering
Enable it. :°)
Why flash this or use this as Base ROM for Development?
The vm heapsize is increased here so with this ROM there's some performance more than the official Moto one.
Oh, and this is prerooted, so you don't have to provoke you headaches on rooting your ICS system.
For developers, this is an already build ZIP file, easy to deodex and reimplement the changes.
Download:
EternityProject Website
The EternityProject Team Manager & Main Developer,
--kholk
Is there anything else modded, or is it just a flashable, rooted version of the leaked update?
WooHoo ! Downloading now !
It is only a flashable rooted ICS update.
This will make you able to install ICS without going through OTAs and various reflashes.
just to make sure.. after i flash this, will i be able to boot cwm and restore my backed up rom?
Well, there's a problem for that.
This package will also flash the ICS kernel on which Gingerbread can't run.
If you want to come back to Gingerbread, you'll have to flash the Gingerbread kernel through fastboot after restoring your Gingerbread ROM from CWM.
Flashing a Gingerbread ROM via Fla**** or RSD Lite won't give you this problem.
Master kholk
Just want to ask before i try this ICS, and i know its out of this topic, do u think i can flash the Chinese ROM and its 2.3.7 OTA? Seems newer though, any changelogs?
Thanks for all the projects you have, i am from the Philippines and i am encouraging my fellow RAZORIANS here in my country to check out this FORUM in XDA and ETERNITY PROJECT...
You are doing a great job for our RAZR...
Keep it up
doesnt work for me. "E:cant't open ..." error message during installation
kholk said:
Well, there's a problem for that.
This package will also flash the ICS kernel on which Gingerbread can't run.
If you want to come back to Gingerbread, you'll have to flash the Gingerbread kernel through fastboot after restoring your Gingerbread ROM from CWM.
Flashing a Gingerbread ROM via Fla**** or RSD Lite won't give you this problem.
Click to expand...
Click to collapse
EDIT: explanation in the next post.
Nope, you have to flash ONLY the kernel, not the whole image, otherwise you'll automatically discard your recovered system on CWM.
You can do that with EternityProject Fla**** placing ONLY boot_signed into the Fla**** directory. You'll see a LOT of errors: that's because it won't find any other file than boot_signed, the only one you want to flash in THIS CASE.
So, if you want to restore your previous ROM:
1. CWM
2. Fla**** (only boot_signed).
doesnt work for me! im on BR stock rom and it just stays in the M logo doing nothing! tried twice in two different razrs, same result. had to fastboot back to stock!! b;( any sugestions? also i wipe data cache everything before flashing
Sent from my GT-I9100 using xda premium
I was on Eternitys Deodexed Stock Rom - Flash via Bootstrap and now am stuck at Motoroal Logo " M logo ".
Having to RSD back to stock to get my phone back operational. Any suggestions ..
At the current.. DO NOT FLASH THIS lol.
yeah, i'm stuck at M logo too.. i was on 651.150.1 OTA, didn't wipe anything and just flashed the zip. now i'm stuck.
EDIT: Factory reset is not the solution if it makes any difference.
Me too ... the same probleme, please, foun solution.
Thanks
Do you recommend a factory reset after flashing or is everything working fine without fr?
Gesendet von meinem XT910 mit Tapatalk
Unless ICS looks just like the Motorola Logo it's not working for me either.
kholk said:
Welcome to the EternityProject...!
What do we have here?
Android....
.....Ice Cream Sandwich for Motorola RAZR XT910 (GSM/UMTS)!
This is a PREROOTED ICS ROM to be flashed with the BOOTSTRAP RECOVERY. It does contain everything you need.
It should work on BR devices, too!
The EternityProject Team Manager & Main Developer,
--kholk
Click to expand...
Click to collapse
you are Masterpiece kholk, do we have to full wipe or not?
A full wipe is highly recommended. However, I can't really know why you're having those "M Freeze" problems.
Can you post the exact version of your previous software (and your ability/unability to flash en.EU Fastboot ROMs), so that we can fix everything?
Thanks.
I don't think anyone reads through posts.. only the first and maybe the last. But Quit asking what to do, READ..
This does not work currently as reported by mutliple people on this site as well as his Home Site - Eternity Project .
I done a full Wipe - Dalvik / Data / Cache - and atempted to flash - got stuck at the M logo - My battery got too low while at work waiting to get home, and well now waiting on Phone to charge enough to Fastboot lol.
kholk said:
A full wipe is highly recommended. However, I can't really know why you're having those "M Freeze" problems.
Can you post the exact version of your previous software (and your ability/unability to flash en.EU Fastboot ROMs), so that we can fix everything?
Thanks.
Click to expand...
Click to collapse
I was/am running the BR Fastboot Rom, and could not install the EN.EU, so I was waiting on this one.
Everything installed correctly, it just hangs on reboot with the big red M. I had to RSD the Stock ROM again - but I will give it another go.
Hi guys,
This is my first post(go easy on me) also english is my second language.
Anyway, i've had my ATT-i777 GS2 since launch & been keeping tabs on its development & such. I stayed on stock experience due to not having any issues at all. I think i waited long enough that i should try the ICS experience, ive' red quite a bit about it & learned of its huge improvement for Android.
So my question is what's the easiest way to get stock rooted ICS?
I have these options in mind:
1. update thru Kies & then use creepyncrawly guide UCLE5 Stock ICS with Root
- to me its risky because this have the brick bug
2. root GB with a custom kernel with CWM so then i be able to flash a CWM stock ICS rooted rom
- this one sounds more tedious to me but with this i can avoid KIES update(i think)
Keep in mind my phone is still bone stock GB 2.3.4 & this is my first attempt in flashing.
any more suggestions pls.
Whatever path you choose will be a little tedious. If you plan to flash a custom rom rather than stock ICS, then I would suggest that you root Gingerbread and install a custom Gingerbread kernel containing ClockworkMod Recovery, and then flash ICS from there. I suggest my guide for installing firmware without incrementing the flash counter. If it were my phone running 2.3.4, I would use zergrush toolkit to root, and mobile odin to install the kernel.
creepyncrawly said:
Whatever path you choose will be a little tedious. If you plan to flash a custom rom rather than stock ICS, then I would suggest that you root Gingerbread and install a custom Gingerbread kernel containing ClockworkMod Recovery, and then flash ICS from there. I suggest my guide for installing firmware without incrementing the flash counter. If it were my phone running 2.3.4, I would use zergrush toolkit to root, and mobile odin to install the kernel.
Click to expand...
Click to collapse
if i use the zergrush toolkit route is there any wipe/reset involve or necessary prior to doing so?
lvlark02 said:
if i use the zergrush toolkit route is there any wipe/reset involve or necessary prior to doing so?
Click to expand...
Click to collapse
No. Just root it and then flash a Gingerbread kernel. You'll still be on the same base, 2.3.4.
Then, when you are ready to flash a custom rom, which will obviously be another base, especially if it is an ICS rom, then you should do a wipe data/factory reset before you flash the rom.
creepyncrawly said:
No. Just root it and then flash a Gingerbread kernel. You'll still be on the same base, 2.3.4.
Then, when you are ready to flash a custom rom, which will obviously be another base, especially if it is an ICS rom, then you should do a wipe data/factory reset before you flash the rom.
Click to expand...
Click to collapse
sorry didnt got to reply soon enough, i got busy a bit. anyhow i think follow yer instructions & hope for best & ill let u knw bout the results.
I have a vibrant with Asgard Version 3.1.2 installed. How do I upgrade that to a jellybean rom? The problem is changing the partition from bml to mtd and I haven't done this for a long while and I only did it on a Galaxy S 4g, not a Vibrant. I remember I had to get version 3 or above of CWM for the 4g when I upgraded it to jb long ago. I never got the Vibrant past Asgard because the phone belongs to an ex-girlfriend and I haven't worked on her phone for over a year.
I tried flashing a kernel that had version 5 something of CWM on it (99 problems) but although I was able to flash it and the jb roms seemed to be loading, every time I rebooted it would only go to recovery and the new rom would never boot up. Reflashing Asgard with Odin didn't work, I kept getting the lady Sandra saying there was not enough space on the card to convert it to lagfix and it has been a long time since I ever had to deal with her at all. I was able to Odin a stock Froyo rom and it now boots up to the old grassy screen with the bloatware.
I suppose if a Vibrant works like a 4g I'll now be able to reflash Asgard but maybe that is not what I am supposed to do. You guys have so many roms and kernels compared to the 4g forum that I'm kind of lost trying to deal with this phone. I have not had to convert from bml to mtd for a long time. The phone I have came with an odin version of jb that got around all of that crazy stuff.
I remember using the Vibrant toolbox a long time ago as part of the upgrade, but the link now points to a page that isn't there any more.
Go here http://forum.xda-developers.com/showthread.php?t=849028 and use Odin to flash back to stock JFD, which is 2.1 not 2.2. After you flash to stock, use update.zip B from the link above to get CWM (clockwork mod recovery), you have you reinstall packages twice for it to work FYI. To flash to Jellybean from stock you must flash the ROM twice as well (important), the first flash just upgrades your CWM recovery. It will reboot to Jellybean CWM (blue), just flash the ROM again and you will be good to go. Remember to follow the devs install instructions, it's usually wipe data/factory reset, wipe cache and dalvik cache then flash the ROM and fix permissions. My favorite Jellybean ROM is Avatar in case you want a suggestion, tons of themes and very stable, I prefer Semaphore kernel as well, both can be found here http://forum.xda-developers.com/showthread.php?t=1982728.
Sent from my SGH-T959 using Tapatalk