I have a problem with RSD lite.... before rsd can easily detect my xt720 but after flashng the xda special rom the rsd lite cannot anymore detect the phone... all moto drivers are updated... please help.....
RSDLite not detecting phone
abet1017 said:
I have a problem with RSD lite.... before rsd can easily detect my xt720 but after flashng the xda special rom the rsd lite cannot anymore detect the phone... all moto drivers are updated... please help.....
Click to expand...
Click to collapse
This doesn't sound good, I hope their is a solution for you. I will repost in the XDA special thread for you as I am hoping it isn't a bug caused by the Special. I will need RSDlite again sometime soon lol.
Thanks....
Have you Resolved it?
Mioze7Ae said:
I don't think it is possible for a change on the phone to cause this problem as it is described. If you can boot into the bootloader (power on with both volume up and camera shutter down) then the problem is on the computer's side. The locked bootloader guarantees this. It could possibly be a problem with the hardware (USB cable, USB port) but driver problems seem to be pretty common on Windows+RSD Lite. If you have access to Linux/Mac OS, you could try sbf_flash.
The symptoms are not very well described. It sounds like what might be going on is a bootloop or stuck (M) after a successful flashing. I would try a factory reset. Let's continue this in the General thread rather then here.
Click to expand...
Click to collapse
Not yet... I tried to use other windows-based computer but still it did not work. The computer can recognize the phone and I can get to bootloader mode... the only problem when i opened the rsd lite, no detection at all. The only option i have is to flash other rom using nandroid and try again to use RSD. If it does not work then it is a problem for me to go back to the 2.1 stock rom... Hope there is other way to do that. Thanks.
After flashing the cbw rom, then go to bootloader mode, but the same problem the rsd cannot detect the phone....
Not to hijack a thread here, but I am experiencing a similar issue. The difference for me is that my phone is recognized, but RSD Lite won't allow the flashing to start even after selecting the SBF file. It's almost as if RSD Lite isn't getting info about the file (doesn't show up in the window on the right).
This happened with both the Singapore SBF and the CBW SBF in an attempt to flash when trying to get to the XDA Special Stock (beta). I've even uninstalled and reinstalled both the Moto drivers and RSD Lite. Running Win7 Pro.
banshee56 said:
Not to hijack a thread here, but I am experiencing a similar issue. The difference for me is that my phone is recognized, but RSD Lite won't allow the flashing to start even after selecting the SBF file. It's almost as if RSD Lite isn't getting info about the file (doesn't show up in the window on the right).
This happened with both the Singapore SBF and the CBW SBF in an attempt to flash when trying to get to the XDA Special Stock (beta). I've even uninstalled and reinstalled both the Moto drivers and RSD Lite. Running Win7 Pro.
Click to expand...
Click to collapse
Not sure how to help, but do you have debugging checked in settings/applications/develpoment/USB debugging and are you using the right sbf here is what I used Singapore SBF
Seems a little weird multiple people having rsdlite issues the last few days
Yes, USB debugging was on. It appears that I used the SBF you are referencing. As the OP is I'm sure concerned, this is a real issue if I can't get back to stock SBF for warranty issues. I suppose I could flash to the CBW Froyo and hook CBW up for warranty issues, but that's...meh...kinda cheating.
I have also read the Windows 7 doesn't like RSDlite and also read somewhere else that the version of RSDlite has been known to cause problems with recognization. I use 4.6 since day one and won't upgrade. Old saying, "If it aint broke, don't fix it." I think the latest version is 4.9 or something like that.
Hmm...I've been on Win7 for the entire time I've been flashing my XT720. I have version 4.6 installed and it said during an update check that it was the latest. I'm pretty sure I've tried doing this with the SD card both installed and uninstalled. It recognizes the phone fine, but for some reason, when I browse and select the SBF, it doesn't recognize the file.
That is wierd. See if someone can give you a nandroid of the stock SBF and maybe try that route through OR. Flash barebones stock nand/sbf and then move on from there. Not sure if the kernal will transfer with the nandroid. I am at work roght now, so I can't up/download anything. Seems to me that if RSDlite recognozes your phone but doesn't recognize the sbf it may have something to do with the file path. Not sure at this point.
OK, I may have figured it out. I'm at work right now (on a WinXP machine, not sure that is the diff) and started RSD Lite and plugged in the phone. It installed the OMAP3430 drivers and will now allow me to flash. I'm thinking the OMAP drivers at home are messed up. When I plug in my phone in bootloader mode into RSD Lite, it already recognizes it as model "S Flash OMAP3430". Perhaps an uninstall of those drivers and let the phone/PC do it over again.
Actually my computer OS is windows 7 ultimate... if my rsd issue will never be resolved so I think I need to have a nandroid of Singapore sbf... hope it is possible....
banshee56 said:
Hmm...I've been on Win7 for the entire time I've been flashing my XT720. I have version 4.6 installed and it said during an update check that it was the latest. I'm pretty sure I've tried doing this with the SD card both installed and uninstalled. It recognizes the phone fine, but for some reason, when I browse and select the SBF, it doesn't recognize the file.
Click to expand...
Click to collapse
I don't know bud, I have done that once and it was simply cause i clicked on the wrong file or wrong part of the file.
I've got a D2G with Clockwork and Bootstrapper installed.
I tried to flash a version of CM7 (http://download.cyanogenmod.com/get/update-cm-7.1.0-DROID2WE-signed.zip), but I'm stuck at the 'M' logo. I used RSDLite 4.9 to root the phone, so I know I have the drivers installed, but now, I can't get my PC to recognize the phone to sbf.
I tried installing RSD5.0, but no dice. I tried deleting the data/cache from the bootloader, tried reinstalling CM7, but nothing. I have a back up image on my SD card, but it doesn't do me any good.
Any help is appreciated. I'm not sure what I can do.
RSDLite cannot be used to “root”. It's a tool that allows you to flash the factory flash image.
Have you entered the SBF loader? http://droid.koumakan.jp/wiki/SBF has instructions for this. You must boot the phone into the SBF loader for RSDLite to detect it.
The link to CM7 you posted above is most probably the Froyo build (for the old Froyo kernel of 2.4.x firmware) and won't work with the kernel from 4.5.x firmware.
Yea, sorry, I misspoke.. i rooted with 'Pete's Motorola Tools 1.06'.
I've got DROID2WE_X6_2.4.29_FULL.sbf, but I think I know my issue. I initially flashed to DROID2WE_X6_2.4.29_FULL.sbf to receive and install the new VZ OTA update of Gingerbread... I didn't flash back to Froyo before installing CM7 (I found instructions to do so AFTER I did the CM7 install attempt), which narsed the whole thing up.
So now, I can't get RSD to recognize the phone and no matter what I do with bootloader, it doesn't get past the 'M' logo.
Am I just **** out of luck? The phone is still under warranty, so I can get a replacement from VZ if I need to.
Do you mean that pulling battery and then pressing and holding power/lock button + up arrow key doesn't take you to SBF loader?
ugg. Yea, that worked. I feel like a total n00b now. I was pressing 'M' to run the factory reset, which of course wouldn't work.
I honestly wish there was a easily accessible wiki with RSD, flashing ROMs and rooting; the info is available in various locations, but some are missing info that others have, so it can be confusing to novices like myself.
Well, the link I posted describes how to boot into SBF loader. It also has instructions for CWM and stock recovery. Along with some info on CM7 installation.
I didn't bother to write an article on rooting yet, though.
Hi there,
I flashed the CronosX 2.3.7 firmware onto my xt720.
it was running superbly until i messed it up .
i purchased a class 6 sd card to test the HD recording smoothness, but it all went wrong. i had no apps installed to sd, and i cloned the data on the OE sd to the new class 6.
the phone went a bit psycho after powering up force vlosing everything repetitively. i reinstalled open recovery, and reflashed the firmware. its not running correct, so i thought of rsd flashing 2.1 and start fresh
RSD picks up the phone in usb bootloader mode, but refuses to flash 2.1. the device description has no IMEI number. even on the phone, the phone details seem corrupt.
Any ideas how to proceed?
Try following the hints in this topic. Might be the same issue.
http://forum.xda-developers.com/showthread.php?p=23327622
OMGN00B said:
Try following the hints in this topic. Might be the same issue.
http://forum.xda-developers.com/showthread.php?p=23327622
Click to expand...
Click to collapse
thanks for the link, but not the same issue.
RSD lite does not recognise it as a motorola xt720 anymore. there are no device details, hence the 'start' button on rsd is ghosted.
i got the firmware[2.3.7] and sd card functional once again. but will consider flashing a 2.2 rom using open recovery if i need to go back for any reason. at the moment i dont want to mess it up further
In case you change your mind:
1. Make sure you run RSDLite as administrator if you run it under vista/7 (Didn't work for me when running it normally)
2. In the list, my device is listed as "S Flash OMAP3430" and not Milestone XT720
3. The IMEI and some other details of my phone are N/A too but I flashed successfully several times.
Also: The bootloader you should be in black with some text.
PS. Found this video on youtube to help:
ID: KA67WaBfGWQ
OMGN00B said:
In case you change your mind:
1. Make sure you run RSDLite as administrator if you run it under vista/7 (Didn't work for me when running it normally)
2. In the list, my device is listed as "S Flash OMAP3430" and not Milestone XT720
3. The IMEI and some other details of my phone are N/A too but I flashed successfully several times.
Also: The bootloader you should be in black with some text.
PS. Found this video on youtube to help:
ID: KA67WaBfGWQ
Click to expand...
Click to collapse
Ok, So i did change my mind. i have flashed 2.2 in attempt to get back rsdlite functionality with no luck.
Rsd recognizes the device as "S Flash OMAP3430" but the start button on rsd is not clickable.
i have tried to flash it on more than one pc, with the same result. i have even tried downloading a different stock rom [German].
Can someone please assist
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