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.
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
its been said before that once you're unlocked, you're always unlocked. Flash a fruitcake for a stock setting.
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
xploited said:
If you haven't updated to OTA 2.3.4, you can SBF flash 2.2.2 and it will restore your phone to default.
Note: It will remain unlocked, but it won't show the "Unlocked" text during boot.
This way you might get lucky and they fix it without noticing that it's unlocked.
Good luck.
Click to expand...
Click to collapse
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Pizzaapu said:
the SBF file, is that the Pudding one? (sorry didnt mean to hijack just have the same problem)
Click to expand...
Click to collapse
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
xploited said:
Not pudding, I meant SBF flash full stock 2.2.2 rom.
BUT YOU CAN ONLY DO IT IF YOU HAVEN"T UPGRADED TO OFFICIAL OTA 2.3.4!
Or you will HARD BRICK! LOL.
Click to expand...
Click to collapse
Lol hes returning back to Moto anyways ha ha! I'll try it out, I fastbooted to Gingerbread (via Kenn) So I never did the OTA.... so I guess I am safe.
Per this post, you can tell if you've flashed OTA 2.3.4. If it has been flashed already, then DO NOT downgrade to a official 2.2.2 build.
mysticdrew said:
guess that's a little moot in this case since he's sending it back to motorola anyways lol
The other suggestion is to sbf flash the 2.3.4 sbf, still may risk hard bricking since it's not really confirmed if it's safe since most of the hard bricks have from sbfing backwards.
Click to expand...
Click to collapse
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Sass86 said:
Its safe. I have done it. U can sbf the 2.3.4 (4.5.91) over 2.3.4 (4.5.91) even after ota. I used the pudding sbf and did not brick my phone. Even still, same rules apply, your risk.
My overclocked alien atrix
Click to expand...
Click to collapse
Yeah but doesn't using the pudding 2.3.4 (4.5.91) still makes you have the "Unlocked" thing on the boot setting? which is what the OP wants to avoid so if he takes it to like AT&T if they see it and see Unlocked they will void the warranty, I am pretty sure the retail story wont extract his phone to see if the fuse it sparked and unlocked.
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
I am not sure about the sbf, but I can tell you for sure fruitcake will not get rid of the unlock logo, flashing a fruitcake is only a stock ROM.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
No. Only if you haven't upgraded via ota update. If you did, then there is no way of removing "unlocked" yet.
My overclocked alien atrix
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Just a thought... did you ever back up your PDS partition?
Touchscreen issues sometimes are due to pds issues. If you have made a backup, wouldn't be a bad idea to try restoring it to see if that fixes your issue.
If you didn't back it up, take a look at this thread with a pds file that helped others.
http://forum.xda-developers.com/showthread.php?t=1131649
RampageRR said:
Hi guys, posting for my wife here. She has an Atrix, running Cherry Pi 0.7 currently (unlocked bootloader, romracer recovery, etc). The touchscreen is completely borked, doing all kinds of weird things. I know it's a hardware issue, i have tried flashing 3 different roms, 4 different keyboards, and multiple wipe/reinstalls of roms. Always does the same stuff with the touchscreen - not responding to input, random multiple presses of qqqqqqqq when trying to type, soft buttons not working, etc.
i want to return the phone to complete stock so i can send it in to Motorola to be either repaired or exchanged. I cannot find any insrructions for this for an AT&T Atrix. How can i get back to stock os, factory recovery, and locked bootloader like when it was new? I tried search, but cant find exactly what im looking for. Can someone help me out, please? Thanks.
Click to expand...
Click to collapse
Probably a long shot but, I used to have very similar issues with other phones in the past when I've had a screen protector on for awhile and it gets scratched up. Maybe try remove the screen protector if there is one and see what happens.
If it is going back for repair. why not intentionally hard brick it? The first thing they will do is the full blown factory flash, erasing all evidence.
If you do this, make certain you give them a story that somehow describes both the actual problem and the bricked condition (else they might think the un-bricking fixed it and not catch the other issue.
EDIT: Maybe not all evidence, the fuse that was blown when you unlocked a 2.3.4 might be a real hardware type fuse and never be cleared. Don't know.
My device is doing this exact same thing and I'm in the same position you are in. I never backed up the PDS partition, but a backup using the image in the linked thread did not solve the problem. Nor did flashing multiple new ROMs.
I'm not sure if this is a hardware or software problem. It problem seems to go away if you lock the screen a few times, but then later reapers.
Sorry to hijack this thread, but does anyone know if replacing the digitizer will fix this problem? Since I'm in New Zealand this would be an economic solution as shipping to and from the US is pricey.
RampageRR said:
Thanks for the replies, guys. I basically need to get back to 2.3.4 with no "unlocked" logo on boot. I'm pretty sure they won't go and check bootloader status for touchscreen issues (I hope).
If I sbf the factory 4.5.91 will it remove the unlock logo and restore webtop, etc?
If I flash the fruitcake version, does that get rid of the unlock logo?
I guess that's my main concern so I can return for repair, just getting it back to appear normal. Thanks again.
Click to expand...
Click to collapse
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Pizzaapu said:
Ok, I have the same issue as you, I was able to fix the "unlocked" logo ( I havn't taken it back to AT&T yet for warranty, but I will update when I do). So this is what I did, when I upgraded to 4.5.91 I fastbooted it instead of OTA or flashing it, I also unlocked my bootloader by using pudding. Assuming if you did the same, then will be able to flash the official 4.5.91 via SBF ( I wasnt going to try 1.8.3 because I didn't want to risk the brick). I got the 4.5.91 sbf from this link: http://forum.xda-developers.com/showthread.php?t=1125944 ... My phone is still rooted, but the "unlocked" logo is now gone and I flashed fruitcakes so It looks completly stocked now! I hope this helps, I dont think you will fool motorola if you send it in for repairs, but I am pretty sure you can get by with that if you have to return it to the store for warranty reasons! Good luck : )
Click to expand...
Click to collapse
I just saw this. I ended up using the stock 2.3.4 sbf, and then doing a factory reset in the privacy menu. Now has all the stock info in the "about phone" section. I'll let you all know how it goes. Thanks for the suggestions.
Just got back from AT&T! they said it was a software issue! They gave me the warranty and gave me a refurbished Atrix with 1.8.3, stock froyo on it! I'll stay OTA until CM7 comes out of pre-beta then see how to root it after OTA : )
I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
custom bootloader?
avoid flashing bootloaders whenever possible. If your phone is working okay right now, leave it.
hottpockets said:
I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
Click to expand...
Click to collapse
There are no custom bootloaders. Since you flashed the one click ics leak you now have the secondary bootloader that came with that package. codworxx kernel and tasks' ics leak have no bootloaders and will not change them in any way.
As long as the secondary bootloader does not suffer from any corruption during the flash process and your phone boots up normally after flashing it, it will not cause you any problems (other than resetting the custom binary counter if that ever becomes an issue for you).
The danger of flashing packages with bootloaders is if something happens during the flash process to corrupt the bootloader it will hard brick your phone, as in dead paper weight brick.
So don't ever flash any package with bootloaders unless you are absolutely sure want too flash them and are aware of the risk.
Sent from my SGH-I777 using XDA Premium HD app
hi,
I am sorry if this is a dumb question. But i have failed several attempts while shifting to ICS (RC 5 by team-nyx). Every time when i install ROM & kernel via CWM and boot the device (vibrant t959) it freezes on the screen with VIBRANT and SAMSUNG displaying WHITE on BLACK back ground.
i have gone back to JFD and tried several times BUT same result.
I was on froyo 2.2 (build UVKB5) updated via kies and did it but no luck. I followed wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and did starting from No. 03 --
downloaded Cmenard's Kernel with the ClockworkMod Recovery 2.5
Heimdall Suite 1.3.2 for windows
AND upto No. 9 under Windows ONLY: section
the CWM installs as it says (A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically. )
after that i cleared factory, cache and dalvik cache.
then I select install Zip from SD card and chose the ROM (which is from team-nyx.com/index.php/releases).
after 3% it says rebooting and vibrant shuts down and reboots.. when after I clicked the combo (vol+vol-power) to enter the CWM its not there.. so I reinstall using [heimdall flash --kernel zImage] command in PC's cmd. then after i redid the same to select from SD and then ROM installed ok.
then I selected the kerenel which was taken by same source and installation went normal..
after I select reboot from CWM it reboots and hangs on vibrant screen.
I cannot figure OUT WHAT IM doing WRONG..
Please HELP ME..!!!
thank you for your time
I am moving to 2.2 via kies after going back to stock JFD. then i will root my vibrant. after that i will install ROM manager from market. THEN i will try to FLASH to ICS RC 5 + kernel from nyx TEAM.
I dont know what is wrong.. please HELP
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
iwillkillyou said:
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi,
thank you for the reply. No i havent tried a different ROM. yes I checked repartiton when ODin Y this is happening.. I have Flashed this ROM once.. but then when someone calls me they cudnt hear me clearly.. when i initiate the call its ok.. so I moved back to JFD..:/
kaiser_bun said:
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
Click to expand...
Click to collapse
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
haarsh said:
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
Click to expand...
Click to collapse
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Woodrube said:
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Click to expand...
Click to collapse
Thank you for the links.. I downloaded and place CWR inside SD. Without kies can we install official releases via Odin.. is there any way.. im sorry if that is a stupid question
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Woodrube said:
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Click to expand...
Click to collapse
thank you. btw can we Flash to 2.2 via CWM .. directly selecting the ROM from SD .. without Odin
If you can find it, you should be able to. Just put on your card and flash away, taking care to wipe accordingly.
A note on flow though:
2.1, 2.2 -can go into and out of any 2.2 there is laterally.
2.3-4.0 -will need to Odin to stock before going back to a 2.2 ROM. Can move laterally from 4.0 to 4.0 though.
(i.e DO NOT try to restore a 2.2 nandroid or flash a 2.2 ROM when you are on an ICS variant. the /system is completely changed and reformatted. You need to Odin to get it back.)
Moped Ryder uploaded a semi tweaked version of the stock 2.2 build. It's a zip that you can just flash using CWR:
http://forum.xda-developers.com/showthread.php?t=1674519
It comes rooted with busybox and some other goodies, but it's the stock kernel and whatnot. I'd highly recommend Fishman's Bionix-V Mod or Moped Ryder's Slim_Ryder ROMs if you're going to be on Froyo though. They're both great, but I went with Fishman's latest Bionix Mod since I couldn't get bluetooth to work on Moped Ryder's ROM. Which is really unfortunate because I loved Moped Ryder's otherwise.
And you don't have to Odin back to stock if you're just bouncing around Froyo or Eclair builds; only if you're coming from Gingerbread or ICS (2.3 or 4.0).
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Is your Samsung Vibrant (T959) Rooted.?
iwillkillyou said:
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi.. I tried again with flashing semaphore kernel through Odin installed CWM version higher than 2.5 to install ICS RC5 by nyx --sorry i need that soo badly so didnt checked anything else ..
@that time I was on vibrant 2.2 UVKB5 (stock)
NOT rooted
I didnt had so called
bootloaders
Click to expand...
Click to collapse
(i dunno what it means though--have to search )
BUT it didnt worked for me instead freezes at Vibrant start-up screen. So i Couldnt switch back to CWM. I Odin back to JFD with repartition clicked and my vibrant was locked (network lock). Finally, I got it cleared by application named Galaxy_S Unlock by Helroz from the market.
Now I am at the very beginning again. I am now on 2.1 JFD. I dont know WHY this happening to me .. :crying:
gonna try again with GB bootloaders.. BUT Im sick of failing and going back to 2.1 (my friends who are having captivate had no problem)
Speedy5150 said:
Is your Samsung Vibrant (T959) Rooted.?
Click to expand...
Click to collapse
At the time i was trying it was NOT rooted.. But now i have it rooted because i needed to unlock the network . which happened me for the very first time after flashing back to JFD using Odin..
Thank you guys for the links and thoughts on 2.2 ROMs.. I am not that expert . Thats why i was updating to 2.2 via KIES -- which is not a good idea as it seems with the ability 2 brick the device. I am going to get Bionix-V FishmanMod V4 FULL and install as http://forum.xda-developers.com/showthread.php?t=1441976 says..
It says Boot into clockwork recovery and i think i found something to do that in this thread http://forum.xda-developers.com/showthread.php?t=734164
I have to get ROM manager from market and go through it..
BUT Im damn upset with the RC5 ICS update by nyx being unable to installed into my device.. I will try with GB bootloaders flashed ..
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Woodrube said:
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Click to expand...
Click to collapse
thanks alot for the info brother.. some guys told me STUPID.. but YOU guys are awesome.. I am a newbie to this flashing and stuff.. but learned a lot from XDA . Thanks again for the reply. now I have stock 2.1 with ROOT . (rooted cuz i had to unlock the vibrant). I will flash to Fish's 2.2 ROM soon. BTW may i ask you after moving to Fish's ROM and later if i need to move to ICS still can I do it without messing with Bootloaders..
Thank you
That is what we are here for in the Q&A/General sections.
Regaring your question about Gingerbread bootloaders being needed:::Yes and No.
Gingerbread bootloaders were required in the infancy of ICS ROMs bc they prevented what is called "Rainbows" in your clockwork where you couldn't see anything. The options were there but you just couldn't see them. Then as ICS evolved, the need for GB bl's lessened and now you don't need them at all.
But...There's always a but...Gingerbread bl's are recommended by most of the devs for ICS builds because they seem to work better with the custom recoveries that come with some of the kernels. There is more to it but in short, GB bl's are not required but recommended.
If you go to my ICS install guide, in the middle pages and more again at the end, Yosup (highly respected user) and I have a detailed conversation about bootloaders and their installation. Once he got over the fear and did it, he was hooked and flashing ICS ROMs weekly if not more. It is a very informative section of that thread.
Hi all,
I have a friend with an AT&T Atrix 4G. I've had a Droid X and current have a Galaxy Nexus & Nexus 7. I did everything you could do to the X and know my way around the Nexus very well; the atrix is a little confusing to me. moto-fastboot and the idea that SBFing is bad are new concepts to me. On the Droid X, if you were in trouble, you just SBF'd.
My friend had some trouble with his Atrix the other day, he was stuck at the splash screen, we got it half way fixed and he was in a bootloop, and eventually we got a version of CM9 on there: 9.0.0-rco-atrix-kang. The phone is running now but the ROM is unstable. I'd like to know how to safely downgrade to a CM7 ROM. Is it as simple as booting into recovery, wiping, and flashing the earlier rom? Something blur based would be ideal at this point as he's just looking to have a stable phone back. He got into rooting/ roming on his own so I'm not sure what updates, if any, were on there before he started. Is there an easy way to check and see which bootloader version he's on, find out which SBF we can safely use, etc? He does have it unlocked, so that should make things easier (or maybe harder, this Atrix really is a mystery to me...).
TL;DR - How do you safely downgrade an Atrix 4G from CM9 to CM7 and which recovery is the best to be using?
I used to switch between CM10 and CM7 all the time, if the phone is rooted and bootloader is unlocked, it's as simple as wiping data/cache, wiping dalvik, format system, install ROM, boot, reboot, install gapps.
Did your friend follow directions and make a nandroid of original before wiping? That would be the simplest way.
エイトリックス から 送ります
He said he had a backup but that when he restored it it was bootlooping. I'm assuming it was some kind of issue with switching recoveries or something like that. With the Droid X there was a recovery for 2nd-init roms and a recovery for blur roms. With the Nexuses it's mostly TWRP or CWM but as long as you're on the latest you can flash anything. Is there any reason to downgrade recoveries on the Atrix? Is there one "up to date" recovery? I see a lot of posts that point to a 2011 thread with the "latest CWM based recovery" but that seems kind of old...
Alright so I think I have this sorted out for the most part, and my understanding is that RomRacer made a version of CWM that we should be using on the Atrix. I just can't find a link to download the thing, is there a thread in development? When I search all I find is a ton of threads telling me to use it and no one linking it.
Edit: http://forum.xda-developers.com/showthread.php?t=1204500 Right?
Or is TWRP better?
http://teamw.in/project/twrp2/72
Lot of people love TWRP, but I'm one of the few that still uses RomRacers CWM 5.0.2.7 (I think) and no issues flashing CM10.1 (android 4.2.1) Had it for over a year, and works great every time. If it's not broken, don't fix it.
As for the boot loop, those are usually fixed with a wipe. Try wiping everything and restoring.
Edit: Yeah, that seems like the proper thread. Sorry, haven't looked at it since I first rooted my phone. Try TWRP, most people swear by it. The touch does add a nice feature, but I'm too lazy to make the switch.
エイトリックス から 送ります
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
You can flash to stock rom and then install CM7 :laugh:
ravilov said:
Once you have an unlocked BL and a custom recovery, switching between pretty much all ROMs is safe so long as you stay away from SBFs.
Click to expand...
Click to collapse
Thanks for the help, I'm glad I checked in. On the Droid X whenever anything went wrong and someone posted a thread like this the first ten replies were "Just SBF" - that used to be safe, until they rolled out .621, but that was end-of-life anyway.
I digress; next time I see him we'll iron this out and he'll be off to the races. Thanks again.