Related
All,
This rom is a rebuilt version of the latest Telstra AU ROM with GPS fix ( RUU_Bravo_Telstra_WWE_1.16.841.1_Radio_32.30.00.28U_4.05.00.11_release_126124_signed ).
I have removed all of the Telstra crap and added some useful apps. I have deployed it to my unbranded phone and it is working fine.
Changes from the standard ROM include:
- Removed all of the Telstra apps (except whereis... maybe next version )
- Added root access, of course
- Apps2SD included but not functional (you can get it to work by issuing adb commands)
- WiFi Tethering included. Will probably remove from the next version as it's a bit flaky.
- Changed the boot animation to the Nexus One anim
- Some additional apps such as:
3D Gallery
Car Home
Navigator
Voice Dialer
Others I inevitably forgot
To do:
- Figure out how to add APNs to the ROM
- Fix A2SD
Download link is in the next post.
Credit to:
Cyanogen for the Kitchen
Paul OBrien from MoDaCo for making the kitchen available
FeaRThiS for hosting the ROM
Enjoy!
IMPORTANT: READ FIRST
Flashing ROMs in general is a risky business. If you've never flashed a non-standard ROM before, I suggest you read about and understand the method before you even consider downloading this. I take no responsibility for any issues that may be caused by this ROM. Use it at your own risk.
I also suggest you read here and note any known issues and changes for new versions.
You must have a rooted handset to be able to flash this ROM. Head over to MoDaCo, or search XDA for guides on how to root your phone.
To flash this ROM to a rooted handset, follow these instructions:
BEFORE YOU START
Copy the zip file to the root of your SD card.
Method A:
1a) Power on your phone, holding the VOLUME-DOWN button until you see the HBOOT menu
2a) Use the VOLUME buttons to navigate to the "Recovery" option and select it using the POWER button
....continue from step 3 below.
Method B (quicker but requires SDK)
1b) Boot up your phone and connect it to your PC via Micro-USB cable
2b) Execute 'adb reboot recovery' form the tools directory of the Android SDK
....continue from step 3 below.
3) Once you see the red triangle (of death ) connect your phone to your PC using the micro-USB cable
4) Go to the 'pushfiles' folder that came with the root-kit from MoDaCo.
5) Execute ./recovery-linux.sh (Linux), ./recovery-mac.sh (OSX) or recovery-windows.bat (Windows) and wait for the recovery menu to load.
6) Use the TRACKBALL to navigate to the Wipe option. Select Wipe by clicking the optical trackball. Do a System wipe, followed by a cache wilpe and finally a dalvik-cache wipe (each of the first three options). Once complete, press the VOL-DOWN button to return to the main menu.
7) From the main menu select FLASH ZIP FROM SDCARD, select the ROM zip file, confirm flash.
8) Once flashing is complete, select REBOOT from the menu.
9) Enjoy your uncluttered handset
DOWNLOAD HERE:
http://79.170.44.128/r3volutionary....ra-free-skitzandroid-signed_050610_214824.zip
Thanks to FeaRThiS for hosting!
Alternative downloads:
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Thanks to lucus30
http://www.deswong.com/android/
Thanks to deswong
Changelog
=======================
Issues:
=======================
- Titanium Backup not working. Its not included in the ROM but just thought I'd mention it It complains about not being able to get root access whereas every other app that requires root access works fine so far. Downloading busybox through TB causes a FC.
- Some people are getting the A2SD infinite boot loop issue (next version will definitely not include A2SD as you can add it yourself if you want it).
You can get out of the loop by doing:
Code:
adb reboot recovery
from the SDK tools folder on your PC to get back to the recovery menu.
You can also do 'adb shell' and then issue the command 'a2sd' from the shell but I wouldn't advise it. It will boot up 'normally' but it's not a permanent fix.
==================
reserved for changelog
Uploading link
http://uploading.com/files/631d4617/hellstra-free-skitzandroid-signed_050610_214824.zip/
Nice one!!
I'm yet to root my phone and WILL get to it in good time.
When I do, I'll give this one a flash.
Thanks for your work.
Death to all the Hellstra visual bloatware scum that crapped up the original ROM (stupid splash screen Tel$tra ding noise especially)
new Link and I have PM'd you all of your FTP details
FeaRThiS said:
new Link and I have PM'd you all of your FTP details
Click to expand...
Click to collapse
Thanks FeaRThiS. Much appreciated!
I've also thrown it on my www as well.
http://www.deswong.com/android/
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
I am experiencing the pink AMOLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
qubit76 said:
I am experiencing the pink AMBLED problem at low brightness and may have to replace the phone with another one. If I root the phone and flash this ROM, can I flash back the original ROM that I downloaded recently from HTC to restore it to the state it was when I bought it?
Click to expand...
Click to collapse
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
negatron said:
Hey guys,
Correct me if I'm wrong but for anyone with a Telstra set the problem is 2 fold?
1) we need to be able to Root the phone, Paul's latest 0800 root method will hopefully fix this
2) we need a ROM that incorporates the Telstra GPS fix whilst debloating the phone.
Does that mean that if we want to use GPS we are restricted to ROMs cooked with the GPS fix? or will any generic ROM do the trick (i.e. those from MoDOCO?
Click to expand...
Click to collapse
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
mwong1980 said:
The GPS issue was a software related bug from the shipped ROM, I read somewhere on here someone mentioning that they flashed the generic ROM and had GPS working before HTC/Telstra released the update
Click to expand...
Click to collapse
yeah the new Telstra ROM had the exact same GPS config as my unbranded one so the prolem was caused by Telstra meddling with things.... surprise surprise!
bcmobile said:
I dont think so. You could flash the original Telstra one back again but the recovery partition is wiped/messed around with as part of the rooting process. Have a look around Modaco and you'll find your answer - you're definitely not the first to ask.
Click to expand...
Click to collapse
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
well tried yrs BC
and now it boots to the htc logo ..and stays there
i've tried twice now.
i can get to recovery mode tho, something wrong with yr image maybe?
note in recovery mode ..down the bottom, it says " Build: not set"
note that i tried yrs after succesffulyy rooting via the latest method from paul, and, applying the radio update. neither got my gps working so i've tried yrs ..
http://android.modaco.com/content-p...h-hboot-0-80-and-os-to-1-21-support/page/340/
qubit76 said:
Cheers bcmobile. So in your opinion am I correct in saying that it's better I wait until the screen problem is worked out (to return under warranty to Telstra from whom I bought it outright) before I go rooting the device?
Click to expand...
Click to collapse
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
ok, my phones working again, rerooted with pauls method.
but have no gps and i can't flash back to the telstra rom thanks to the radio updating my hboot to .80
same here guys. I rooted using Paul's latest method but gps stopped working. and when flashing this Rom it hangs at the white HTC screen. now back to Paul's rooted Rom. hope we fix the gps issue soon!
mitchello said:
I've used three Desires and they all show the pink on low brightness so returning it under warranty won't help you.
Click to expand...
Click to collapse
Thanks for your feed back. At the risk of hijacking this thread and double posting - My post on the AMOLED sticky.
In summary if you don't want to read my above post, I saw 2 phones 'in store' that did not have the pink issue.
Possibly it's better to split A510 and A511 stock rom firmware list?
Here's the list of A511 ROMs I have found (looks like just one downloadable so far):
Acer_AV041_A511_0.003.00_WW_GEN1
Acer_AV041_A511_0.008.00_WW_GEN1
Acer_AV041_A511_1.011.00_WW_GEN1 (download here) - translation
Acer_AV041_A511_1.028.00_EMEA_DE
Acer_AV041_A511_1.032.00_WW_GEN1 (available through FOTA on my device)
Acer_AV041_A511_1.035.03_WW_GEN1 (mentioned on benchmark website)
Regards,
Nika.
Added new version:
"Acer_AV041_A511_1.032.00_WW_GEN1 (available through FOTA on my device)"
3G version
Is the 3G version out?
Petya19 said:
Is the 3G version out?
Click to expand...
Click to collapse
Sure, that's the A511. Might depend on the region though...
Sent from my S300 using xda premium
Acer_AV041_A511_1.028.00_EMEA_DE
Hey, i have canceld my system. Now i look for this rom or a costum rom for my 511. Its functionally with adb or bootloader. Thanks
http://android.clients.google.com/p...511_AV041.RV35RC04_AV051.RV00RC06_EMEA_DE.zip
It's the direct link for the new JB 4.1.2 update for A511 EMEA_DE devices. :good:
Hi
Anyone know where to download Acer_AV041_A511_1.028.00_EMEA_DE
need it to get my a511 back to stock so that i can install 4.1.2
regards chris
Same over here.
I rooted my A511 and now I can't go back, already tried several things but everytime I install the OTA update I get a bootloader error. (Yes my bootloader is back to stock)
chris1005 said:
Hi
Anyone know where to download Acer_AV041_A511_1.028.00_EMEA_DE
need it to get my a511 back to stock so that i can install 4.1.2
regards chris
Click to expand...
Click to collapse
I'm in a similar boat (bricked my device and somehow need to flash something to have the tablet boot). Can't we just use the firmware linked in the OP? It might not be the german version but I suppose we could still flash it and just change the language or something? Anyway, that's what I'm gonna try as soon as my SD card arrives.
Is it possible, to install the english OS on a "german" tablet?
Or encounter some problems?
English itself, shouldn't be the problem.
I was wondering whether I might get some helpt flashing the "Acer_AV041_A511_1.011.00_WW_GEN1". My Tablet has been bricked for some time because I (stupid as I am) tried to do a factory reset using the recovery provided by nikagl even though he specifically said that we were not to do that (I did read that warning but after a few weeks I just forgot about it :/).
Anyway, I've installed the cmw recovery by nothrills and tried to flash aforementioned firmware. I put it on an external SD card which has been formatted to FAT32. I went to the recovery menu and tried to flash the zip file. However, I got a getprop(product.name) error and the installation was aborted. After browsing the board a bit I found out that I have to delete the line starting with 'assert(getprop("ro.product.name")' which is located in META-INF\com\google\android\. But still, the tablet won't flash the firmware. It simply says "Installation aborted. Status 5 [or 6]".
I've also tried flashing the firmware by going back to stock recovery, renaming the firmware to update.zip and starting the tablet by holding the power and the minus button which is supposed to start the flashing process automatically. However, that just results in a red " ! " and an Android lying on its back.
I'd really appreciate it if someone was able to help me. (I've already sent the tablet to the Acer customer service who said that the installation of cmw recovery has damaged the motherboard. They say they will replace it for ~250€.)
Thank you for trying to help, I really appreciate it .
You have to edit line 1 of the updater-script in META-INF\com\google\android\
Delete this: in assert(getprop("ro.product.name") == "a510_emea_de");
Click to expand...
Click to collapse
That is mostly what I did. Except I used winrar instead of 7zip. The first line of the updater-script was "assert(getprop("ro.product.name") == "a511_ww_gen1");" and I deleted it. When I then try to flash the file it says "E:Error in /external_sd/Acer_AV041_A511_1.011.00_WW_GEN1 - Copy.zip (Status 6)"
I also tried renaming the zip file first but the result was the same.
Edit:
As it turns out, the Status 6 error does only occur when I edit the updater-script file with wordpad. If I open it with the editor it works just fine. I was able to flash the firmware. However, the tablet then wouldn't do anything else then showing "Acer" on the screen for ever and ever and ever and ever :/.
In the case you installed a A510 ROM (without 3G) and can't flash back to the original A511 to be able to upgrade to JB and have a working 3G functionality, cause CWM vomits status 7 or 4 errors while flashing the offered .zip, try this way
Greetz
Pauli
I'm going to start collecting the various little tid-bits of information that we have scattered across the threads here to hopefully compensate without having a dedicated forum. Eventually I'll add some other guides and such from personal experience, if you know of any Relay related threads or other information located on the interwebs, please drop a link here!
Standard Disclaimer: I am not responsible for what you do to your phone. The information contained in this thread is here to help you do [anything] correctly. If you follow the instructions listed there-in you will be fine, and ask questions if you don't understand something. I am not responsible for what you do with and/or to your phone. If you are unsure about a procedure's outcome, do not proceed with the procedure.
(1)
How to Get Into Download Mode:
1. Hold Power, Vol Down, and Home button simultaneously
2. When "Samsung" appears on the screen let go of the power button but keep the other two pressed down
3. Voila!
Click to expand...
Click to collapse
ROMS:
[CM9][ALPHA]Galaxy S Relay 4G [12/8]
(Use the updated link below instead.) Stock + Odin Flash (+ Rooted System Img File)(Simplified Instructions)
Updated Stock ROM (Has LH1 flash-able via ODIN) Post + tested Tethering Fix(1)
How I reverted my phone to stock + root.
Update from LH1 to LMA2 On Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Update from LJ1 to LMA2 on Stock ROM w/ preserved root (doesn't remove if you have root, but doesn't give you root) (Untested)
Root:
[root]\{cm9} samsung galaxy relay 4g (updated 11/19)
General Discussion:
Galaxy S Relay 4G Development Thread
Miscellaneous Information:
Keyboard Customization:
Dillalade's Explanation on How To Set Custom Key Mapping(1)
jarrodlombardo's Key Mapping (Follow Dillalades's guide first)
orange808's Key Mapping
Unsorted, Need to Organize and Determine Relevance (If still applicable or OLD information) or Flesh out supporting information:
nopty's Hiemdal Method (Need to use Heimdal 1.41RC1 or Higher from This Post) (gee ones building heimdal for ubuntu 12.04)
AndriodForums Relay Forum
Sim Unlocking (Need to Verify - Unknown Method) (Sorta Verified)
Nardholio's Links to Create an Odin Flashable Image
NV Dump Backup (Important in case of corrupted IMEI)
Nardholio's Flash Counter Information
gee one dive's into nard's stock rooted img in response to Qualcomm secure boot
nopty's CWM recovery post (10-11-201) Odin Flashable of nopty's CWM Recovery
kornyone's introduction
How to change/remove startup/shutdown sounds
dillalade has issue with 64gb card w/ resolution to issue
fantomex's Andriod WPA2 PSK Authentication issue and resolution
Skinomi Skins for the Relay
gee one fixes his bootloop
gee one's list of bloatware Bloatware gee one was able to remove
Sim Unlocking for those who purchased Retail (no contract)
dillalade's guide to getting Google Now to work on the stock ICS Rom
Nardholio's Untested Tethering Fix
T-mobiles KIES LH1 Update Support Page
gee one investigates the efs partition on the relay Nardholio's response
CWM-Only Flash-able LJ1 Modem
Some changes from stock LH1 to LJ1
Reserved
Reserved 2
Just in Case
how about a link to the original factory rom to restore back to before CM9 ?
Kaczman said:
how about a link to the original factory rom to restore back to before CM9 ?
Click to expand...
Click to collapse
I found one that might work for you, update the OP with the info.
I've got to flash my relay to stock and when I do I'll create a small guide. For now I found an older flash that could be used then KIES could update this ROM to the current LH1 (Need to verify build number).
I need a stock rooted rom, while traveling through the mountains the switching in CM9 isn't working correctly (phone constantly looses service when switching from 4g>3g>Edge frequently).
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Spoxy said:
Here's another sim unlock. I can verify this one as working since I am now using my phone with Solavei. I purchased my phone directly from t-mobile (no contract). I used an AT&T sim to do this method.
http://forum.xda-developers.com/showpost.php?p=36400199&postcount=783
Sent from my SGH-T699 using Tapatalk
Click to expand...
Click to collapse
Thank you!
Update OP. It's still in the unorganized section, but it's there!
Thank you, is a very useful guide ! :good:
You should post your first post from this thread in the request thread to show everything going on. Should work better than just posting "Samsung Relay, please"
That's the plan after I get it organized. I'm also going to follow the instructions given by kinfauns.
It's a start.
Never really notice that many steps when you go through it quickly, but this is the process that I used to revert my CM9 + CWM recovery to Stock rom + Stock Recovery. I don't know if it was supposed to happen that way, but it did. After flashing the stock PDA file (via odin) I was able to flash the CWM recovery again while adding root to the stock rom.
All of the items talking about (roms, odin, root, ect) except a program to unzip the files can be found in links in the thread in my signature. For reference, I use 7zip and just rightclick>7zip>extract to folder.
How to go Back to stock w/root from CM9:
Download stock rom (newest is the LJ1 tar.rar).
Download Odin
Unzip LJ1 into it's own folder. Navigate to where you unzipped the file.
Rename unzipped file to remove .md5 so it ends in ".tar" instead of ".tar.md5"
Unzip Odin (into it's own folder, navigate to the folder)
Put phone in download mode (Instructions are quoted in the OP of the thread in my sig)
Start Odin (assuming that you have already plugged the usb cable into your computer)
Connect phone (that's in download mode) to computer via USB cable.
ODIN Will have blue "Added!" box after it's recognized the phone (2nd box from the top left)
In ODIN, click the "PDA" Box and select the .tar for LJ1 (the file you unzipped and renamed)
Uncheck the "auto-restart" radiobox under "Added!". Then Click Start.
Wait for odin to finish. Do not touch your phone or click any buttons in the odin program. After It's done, reboot the phone.
Go into recovery mode on the phone (Vol Up Instead of Vol Down)
Wipe SDCard and cache
Reboot phone. It may take a few minutes to pass the samsung screen. The phone will vibrate briefly as is finishes booting
Sign into the phone (google, facebook, ect...this is probably a skipable step).
Turn off phone. Reboot into download mode (Vol Down)
Download nopty's CWM recovery
Unzip file (into it's own folder, navigate to it), removing the .md5 like the file above
Connect phone to computer, after ODIN recognizes ("Added!") it click the PDA button
Navigate to the unzipped and renamed (".tar") CWM file and select it.
Unceck "Auto-Reboot". Click start
Wait to finish, then power off and reboot phone
After phone has re-booted connect to computer
After connected to computer, transfer SuperSU zip(CWM Flashable) to SD card (You'll need to download this too, can be found in the Updated Stock Roms link)
After that's transferred, reboot phone into recovery mode. (Vol Up)
Use CWM to flash the SuperSU zip
Reboot phone
Congrats, you now have a stock rooted phone!
Just the basic frame for the guide, will update with links and what little troubleshooting I know and add guide to OP after it's finished.
Working with you guys is awesome.
Anyways, you guys know the drill.
New Device Request Forum
I may be naive, but I would like to equivocate a thanks with a "signed" on the post above.
PM'd kinfauns, lets hope that he can help us get to the right people!
thanks
thanks
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
zakiancel said:
thanks
Click to expand...
Click to collapse
your welcome
mikeybot said:
So, has anyone else gotte the software update notification and felt brave enough to run it? I don't want to have what happened with the G2 with their first update and lose root.
Also, the damn notification icon won't go away despite postponing the update.
Click to expand...
Click to collapse
Not yet for me. I'm playing around with a stock rooted (debloated) rom that gee one made right now, I didn't get the OTA update message though. If you do "update" you should still be able to flash CWM and enable root/superuser again. Keep up updated!
Help
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken compass?
I remember seeing a few posts about it too, but I didn't flag them unfortunately. Post the question in the Development thread and we may be able to get you an answer quicker :good:.
tany.jags said:
I am thinking of buying this phone with such great hardware....but one important question....does this handset have a common 'broken compass' issue?!!!...came across a couple of post with such issues....btw why dont we have a dedicated forum for this famous device?
Click to expand...
Click to collapse
Broken? No, but on occasion, it does momentarily glitch up, but once you start moving it clears itself up. Nothing like what would happen with the G2. (I do also have GPS Status installed as well)
I did run the update after taking a look through the zips and deciding to take the plunge and see; and it does reflash the recovery, and while I do have Odin, I have as yet been unable to flash any CWM again. There are no errors, it just doesn't work. I am as yet hopeful though and will report my progress. I didn't see anywhere in the update where it updated the bootloader, so flashing should still work.
I have a very strange problem, and would require help. I had accidently flashed the Atnt ics version on my Asia (indian) version of atrix 2. These are the steps that i have followed.
Note: I appreciate Jimbridgman, for guiding me via pm to help me solve this.
1. Atrix 2 MB865 asia version. (non atnt) purchased and using in India.
2. Had SEARET rom ics.
3. After it came back from the service center (1 month and 7days, it was with them) everything was fine. But the camera app was not working. The moment i opened the camera app, screen flicked and stayed on the same screen. But the app was active as background app. Multitasking window showed it.
4. Thought of reflashing ics,hoping to fix the camera issue. But few months back, searched for official moto ics and never used it. Something as inline ics. So flashed without realising that it was atnt's ics. (using RSD)
5. Phone booted with atnt logo and i was dumbstruck. (i was aware that we should never flash international atrix 2 with atnt. (Hardware incompatibility.
6. Tried to reflash the SEARET rom but cdt.bin in step 7, failed every time. was using rsd lite 6.
7 tried other rom but same,
8 tried jim's script from ics ti gb. and got soft bricked.
9 was able to get fastboot and the screen to see "motorola dual core" (but it was stuck there).
10. Was reflashing atnt's ics again to atleast use the phone. But the battery just gave away it last breath at the climax.
Now cannot charge the battery and reflash. (will get an external charger and pump up some juice in the battery.
Now as i was being guided by Jim regarding the issue, im posting his reply
Jim : "Sorry to say but you are toast. If you have an international version, you can NOT flash the AT&T version, it will lock to the phone to AT&T harware ONLY, and if you try to flash any other versions it will brick.
If you can get the phone to boot and can get into it with adb you can wipe the CID partition and flash an international firmware, but if you are truly bricked and it will not power on, the only thing you can do is, buy an Atrix2 off of ebay or the like, that has a broken screen and replace the parts inside with the ones from the phone you buy that has a broken screen... That really is the ONLY way that I know of, sorry. "
Ebay doesn't have any broken international atrix 2 for sale. I reside in New Delhi, India. And would appreciate if any body can guide me get a new motherboard for my phone. Gaffar market (Indian will be aware of this market) just ignore a moto phone like a step son. And hardly anybody agrees to trouble shoot. And the person who was willing to reflash the ROM and just try to fix the phone quoted 2400/- (did not mention that he will change the motherboard or what.) even i was not aware of the motherboard replacement part (got to know from Jim)
Now can anyone try and help this poor soul :crying:
chayan18885 said:
I have a very strange problem, and would require help. I had accidently flashed the Atnt ics version on my Asia (indian) version of atrix 2. These are the steps that i have followed.
Note: I appreciate Jimbridgman, for guiding me via pm to help me solve this.
1. Atrix 2 MB865 asia version. (non atnt) purchased and using in India.
2. Had SEARET rom ics.
3. After it came back from the service center (1 month and 7days, it was with them) everything was fine. But the camera app was not working. The moment i opened the camera app, screen flicked and stayed on the same screen. But the app was active as background app. Multitasking window showed it.
4. Thought of reflashing ics,hoping to fix the camera issue. But few months back, searched for official moto ics and never used it. Something as inline ics. So flashed without realising that it was atnt's ics. (using RSD)
5. Phone booted with atnt logo and i was dumbstruck. (i was aware that we should never flash international atrix 2 with atnt. (Hardware incompatibility.
6. Tried to reflash the SEARET rom but cdt.bin in step 7, failed every time. was using rsd lite 6.
7 tried other rom but same,
8 tried jim's script from ics ti gb. and got soft bricked.
9 was able to get fastboot and the screen to see "motorola dual core" (but it was stuck there).
10. Was reflashing atnt's ics again to atleast use the phone. But the battery just gave away it last breath at the climax.
Now cannot charge the battery and reflash. (will get an external charger and pump up some juice in the battery.
Now as i was being guided by Jim regarding the issue, im posting his reply
Jim : "Sorry to say but you are toast. If you have an international version, you can NOT flash the AT&T version, it will lock to the phone to AT&T harware ONLY, and if you try to flash any other versions it will brick.
If you can get the phone to boot and can get into it with adb you can wipe the CID partition and flash an international firmware, but if you are truly bricked and it will not power on, the only thing you can do is, buy an Atrix2 off of ebay or the like, that has a broken screen and replace the parts inside with the ones from the phone you buy that has a broken screen... That really is the ONLY way that I know of, sorry. "
Ebay doesn't have any broken international atrix 2 for sale. I reside in New Delhi, India. And would appreciate if any body can guide me get a new motherboard for my phone. Gaffar market (Indian will be aware of this market) just ignore a moto phone like a step son. And hardly anybody agrees to trouble shoot. And the person who was willing to reflash the ROM and just try to fix the phone quoted 2400/- (did not mention that he will change the motherboard or what.) even i was not aware of the motherboard replacement part (got to know from Jim)
Now can anyone try and help this poor soul :crying:
Click to expand...
Click to collapse
well spending 2400 for atrix 2 is better than buying a new phone.if any one guarantees that he will repair your phone get it repaired for 2400.
Sent from my ME865 using xda premium
Of you're in warranty period, then give it to service station saying you just took an ICS OTA and now the phone wouldn't work! Or any better lie you could come up with
Even if it ain't in warranty, ask them how much it would cost to fix it. If it's lesser than 2k, then get it done by them.
- - - - - - - - - - - - - - - - - - - - - - - - - -
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
You could try using the fastboot commands to flash the SEARET ICS fxz. To do this you will need to get to get the moto-fastboot executable and the android SDK installed.
There is a thread in here I think it is in the General section, that explains how to flash the fxz with the fastboot commands. You will need to flash EVERY part of the SEARET firmware to be successfull and not skip any parts of it when using the fastboot commands.
I have seen others that were getting cdt.bin errors avoid it, by using the fastboot commands, but the only worry I would have is since it has the at&t firmware on it, if it will hard brick or not.
@shubham41230 well they cannot guarantee the fix and cannot be trusted to leave the phone for a day. but if nothing works. They will be the last resort.
@Lifehacker7 can a failed OTA update give the fastboot screen with ''flashing failed" message on top?
@jim the post you forwarded to help to charge the battery did not work. Or mayb i could not mix up the step efficiently to get the phone to charge. Cannot even try fastboot command (battery doesn't have charge) . Can you be kind enough to expalin why can it cause a hard brick if atnt Rom is there. And if gets hard bick. Will changing the motherboard revive it. Cause then i will first chk for availability of motherboard and try the commands (but after getting the damn battery charged). Else will reflash the atnt rom and try and use it. Atleast i will have my $ 400 phone and not a black expensive paper weight.
Regards to all helping and the advices...
Have the same problem as in the first post but my a2 is able to boot
I can flash ROMs with fastboot script.
Erased CID but still can't flash ROMs with RSD (cdt.bin error) and 4.1.2. leak3 Camera is unable to initialize.
Help please!
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
amritn said:
Hi, Is there any one suceeded to downgrade from leak Jb 4.1 to ICS 4.0.4??
If yes could some one make video or provide step by step procedure.
There is no thread related to downgrade from leak jb 4.1 to ICS 4.0.4
even though many claimed they suceeded to downgrade.
Thanks
Click to expand...
Click to collapse
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
I have. You will have to download the correct file from here . (if your phone is Asia retail like mine , download the 2nd one in the list)
Flashing is the same way you did the JB leak. It's via RSD, put the phone in fastboot and flash via RSD.
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
My second and last question is( bear with me it's some how long)
1 I was previously in gingerbread 2.3.6,( the phone was asia retail), I flashed directly from gingerbread to jb leak 4.1.
Everything seemed ok and it passed RSD and the phone booted but stuck in motrolla splash screen ( kinda soft brick),
There was error in my lappy running window 7 64bit , mtp usb drive failed to instal(In device manager when i tried to update mtp usb driver it said
newer version of driver already installed),
Now a second scenerio starts Being in softbrick I tried to downgrade from jb to ICS, every firmware except those written with fastboot p3( I guess only chinese version) can be flashed through RSD , otherwise if fimware like 6.7.2 ------mearet or 6.7.2 ------ searet when flashed failed with error in step 4 in rsd like it shows rebooting in bootloader and shows failed error. So my point is only chines firmware with fastboot p3 can be flashed easily. Now I flashed both chinese and hongkong ICS firmware with title fastboot p3-------, and they both flashed correctly and passed but same things happened as jb leak, stuck in M logo and mtp usb driver failed error in my lappy.
Now my last option to fully boot was to go to gingerbread , so I downloaded couple of stock rom like 5.5.1 edem-27searet, it didnot flashed and got error with rebooting bootloader in step 4 or 5. At last I tried fastboot-p3_edison-edison-user-4.0.4-6.7.2_GC-180-EDS-20-31-release-keys-ChinaRetail-CN_chn.tar and it booted properly.
Now again I tried two times to go to ICS or jb leak and samething happened, stuck in M logo. But gb firmware always booted properly.
Please read above scenario before replying, because I haven't seen such situation in the whole xda thread for atrix 2 and by googling, Everyone flashed the rom and they said booted properly
My questions are
1 I want to flash jb leak rom or otherwise ICS, what will be my step?? I'm desperate to try these roms. Please keep in mind about my above situation as i'm unable to flash like other people do.
2 Why the above situation happening like softbrick while upgrading and why other firmware file are not flashing except titled with fastboot? Is it related to kernel or bootloader. When I was in xperia S when I updated from gb to ics same scenario occured but i tackeled situation by flashing in kernel. When I was in AT&T Infuse 4g, I tacked the above situation by upgrading from froyo to gb by updating from froyo bootloader to gb one.
But situation about atrix 2 just blow my head, I'm trying from 4 days, read every thread of xda related to atrix 2 , atrix 4g, googled for solution, watched video from youtube, tried every firmware but none solved my problem .
So waiting for solution from my senior XDA's
Thanks
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
Thanks for ur fastest reply
1 True i know our bootloader is locked
2 If we aren't how we can flash chinese firmware on our set?
3 True
4 True At&T firmware can't be flashed on or model and vice versa
5 As per ur question gb version which i can boot is 2.3.6 and the firmware i Flashed is fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
6 Can I take OTA ICS even though my set was not previously in Chinese firmware out of box. By luck or unluck I'm now settled in chinese firmware
7 Now last question is can i go directly to Angeeks jb 4.1 firmware posted in the thread.
Once again thanks :good:
2 I
Lifehacker7 said:
1. we have a locked bootloader. ( no custom kernels/edits )
2. You aren't supposed to flash any other firmware files other than the correct one according to your phone region.
3.all the files from the thread i linked to are fastboot files ( correct me if i'm wrong) and are to be flashed via RSD while in fastboot mode ( turn off the phone, press power and volume down simultaneously to get there).
And by mistake of you flashed att firmware, then your phone will be completely screwed up. ( there are hardware and bootloader differences bw att and international versions )
Since you can successfully boot to gb, which firmware version does it state ?
Have you tried taking an OTA ICS? ( idk how well it might go).
I hope Jim comes across this thread
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Click to expand...
Click to collapse
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
A small correction.. If you have a retail phone, you can flash any region firmware as long as it is for this phone. Just don't flash att ones. The radio is different and your phones cdt security number will be increased if you do.
Regarding flashing jb leak, how long did you wait after flashing? First boot usually takes long..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
About 30 minutes after flashing
More update I Flashed ics hk firmware, and this time it showed android is upgrading 1of 30, then passed 30/30 and then freezed for 25 minutes.
So after waiting for 20 minutes and stuck in android is upgrading I took out the battery and entered into recovery and did factory reset and wipe cached.
Now this time no android is upgrading message came up and stuck in M logo
To try any of the ROMs available ( except the gb ones, official jb leak, and one or 2 ROMs based on that) you should be on an ICS base ( they are built based on the ics kernel).
And to try the angeeks jb ROM, you should be on the JB leak 1st.
ROMs like PA, CM10, 10.1, they all need ics as base.
If nothing is really working out, you should probably give the phone to service station.( tell some lie about how that happened )
--------------------------------------
LIFE!
IT'S WHAT YOU MAKE OUT OF IT!
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
jimbridgman said:
Ok, so... there is a major issue going on here.
You flashed the HK/TW firmware on an international MEARET or SEARET phone, the HK or TW firmware is very much like the AT&T versions and that they lock the bootloader version so that upgrading or downgrading and changing firmware regions are blocked for the most part. There is a file in all the firmware version that tells RSD and the phone if it can or can not flash things... the one everyone knows is the CDT.bin, and the one that not everyone knows about is the CID, and the CID can get you into BIG trouble if you do not know what it is, or why it is there, so DO NOT mess with it, unless you know what you are doing... The CDT.bin on the other hand is part of EVERY FXZ, it will tell RSD if you can flash something for the most part or not.
Your ONLY chance is to flash your PROPER version of ICS firmware through fastboot commands. I will not give directions again, they are posted in several threads in here, do a search in the general section for the commands.... you MUST flash all the same files that RSD lite would to make this work, and you can no skip any of them. I would look for the order and the files to flash in the .xml file that comes with the firmware so that you know the order and partition names and such.
You MUST have the following and at the latest versions, even if you have the drivers installed, uninstall them and reinstall them again.
1) A2 moto drivers
2) Android SDK
3) moto-fastboot command/utility for your operating system
4) The PROPER ICS FXZ file for your phone and region
5) understanding of the comand line and the commands that are needed to flash with the moto-fastboot utility
After you have done all of that flashing, you should be on the proper ICS for your region. If you want to try and do the JB leak again, then it MIGHT, work, but I am not sure if it will or not.
It is a real bad idea to flash other regions firmwares to your phone, unless they are leaks, and have been tested to work on your regions handset, just for future reference.
Click to expand...
Click to collapse
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
amritn said:
Thanks jim for the gr8 info,
Would you recommend me for OTA update to Ics from here? It's saying update available
Do my mobile boot in this scenario?
Any consequences taking OTA.
Thanks again for help
Click to expand...
Click to collapse
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Need to make decision!
Hi guys!
For first, sorry for my bad english. I hope you can understand me. Greeting from Belarus!
I have ME865 with United Arab Emirates warranty.
I flashed my Atrix 2 from 2.3.6 to 4.0.4 6.7.2_EDEM-18-MEARET. It worked fine.
Then I flashed official 4.1.2 leak, rooted it.
Which region firmware I need choose to success downgrade from 4.1.2 to 4.0.4?
Really need your answer! Thanks!
I have some bugs on JB:
1. Can't send and recieve mms.
2. APN dissapear after every reboot. Fix - after reboot turn on/off airplane mode.
3. Bad GPS. Fix - install GpsFix app.
4. Recieve USSD message with sound.
_________________________________________
Just had flash 4.0.4 mearet. All works.
jimbridgman said:
I would not take any OTA, since we have FXZ files that are properly made for the regions our phones are made for, if you know what I mean. The only difference is that an FXZ will wipe your phone clean and you have to resync with google for calandar and e-mail and contacts and apps and such.
With out knowing the EXACT firmware you are on right now, I can not really tell you how safe an OTA or an FXZ will be for you. I am only guessing at this point, that you are still on the HK/TW firmware, and why I suggested you flash the MEARET/SEARET firmware by hand with the moto-fastboot commands, to get you where you should be again, before you try the JB leak, or whatever you are after.
Click to expand...
Click to collapse
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
amritn said:
As per your question jim I'm currently in android version 2.3.6
system version 55.91.109.ME865.ChinaRetail.en.CN
Model number ME865
build number 5.5.1-1_GC-109
Kernel version 2.6.35.7-g8b6f7f9
[email protected]#1
And I flashed this firmware to get fully boot fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar.gz
-Also tried different firmware like jb 4.1 leak flashed passed booted but stuck in M logo splash screen.
-Flashed both ICS build from china and hk/tw and stuck in M logo as in jb
-Tried searet and Mearet firmware for both ICS and Gb build but failed after 5/21 rebooting to bootloader and failed
-And at last I tried fastboot-p3_edison_edison-user-2.3.6-5.5.1-1_GC-109-52-release-keys-ChinaRetail-CN_chn.tar passed and booted.
Jim What will be my next move??
Can I try fast boot method as u mentioned or OTA update to ICS
Thanks
Click to expand...
Click to collapse
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
jimbridgman said:
But you are supposed to be on SEARET/MEARET as your "real" "home" firmware, correct?
If you are supposed to be on SEARET/MEARET, then I would go here, and grab the ICS FXZ file for the SEARET/MEARET firmware, and use the fastboot commands to try and flash it. As always there is no guarantee, and there is always a chance of brick so be careful.
The reason I am really pushing for using the fastboot commands, as I mentioned earlier, that since you are "manually" flashing the parttitions one at a time, from the command line, there will be no checks to see if the proper CDT.bin is on the phone before it does it, and this will save you, in that you should be able to put your "correct" firmware on the phone, I hope.
I have one last question, are you 100% sure that you actually purchased an international MEARET/SEARET phone, and not an HK/TW version of the phone? This is just a thought, since you did say that you were unable to flash any firmware besides the ME865 china HK/TW version... which does bring up that concern.
Click to expand...
Click to collapse
Jim You are genious, Now with fastboot command i'm in the stage where I was 4 days ago pure stock. The firmware which didnot flashed through RSD , flashed with fastboot commands. But with fastboot commands moto-fastboot.exe flash grfs grfs.img, showed error as failed no such partitions. But even without that i'm now booted in stock Sereat gingerbread firmware. Now I will flash ICS firmware through fastboot and will update if anything goes wrong wrong or write
Thank u:good:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
amritn said:
Update whatever I do I get stuck in splash screen or M logo after flashing ICS fxz file or Jb file using any method either fastboot
or RSD even though i'm fully stock now 2.3.6 sereat
Click to expand...
Click to collapse
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
jimbridgman said:
Make sure you are getting your FXZ files from a well known good source.
This is the best one:
http://sbf.droid-developers.org/edison/list.php
Try and flash the ICS one, I think it is this one, that you want:
http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
Try it with RSD lite version 6+ ONLY, then if that does not work, try it with the fastboot commands again.
You should not try and flash the p3 files, until you get to ICS first. I think it all has to do with the bootloader versions, and why you can not go from GB to JB. You have to go to ICS then JB, I am pretty sure of that.
Click to expand...
Click to collapse
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Pls reply xda senior member or anyone those in similar case.
amritn said:
Jim no matter what I do i cannot upgrade my firmwawre either to ICS or jellybean, Always stuck Im motrolla splash screen at the last stage of boot. But if i return to gingerbread on both chinese and asian retail(using fastboot or RSD) it's working.I've tried everything. It's out of my mind now.
There is something that is causing my mobile not to boot. If u do have any idea, please help me.
Apart from that I want to know do we have ICS stock kernel in zip format which we can flash?
If other ppl had same problem and solved it pls share with me. This seems something new, softbrick in ICS everytime no matter which region firmware i flash apart from AT&T firmware. I'm trying since 5 days.
Click to expand...
Click to collapse
get it done from moto service center
Sent from my ME865 using xda premium