Related
Hiii
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
Safe strap doesn't work (Back Option) on this phone due to some partition mapping issue. (Known issue for XT 883, ME863)
Sr. member TBBle suggested a tweak with safestrap & with that I am able to Backup my phone, do disaster recovery etc.
"http://forum.xda-developers.com/showthread.php?t=1625877"
But whenever I install a ROM in safe system it boots to black screen. I tried with Maverick 4.5 & CM7.2 both same result.
I am not able to decide if it's safe strap problem or ROM compatibility with XT883.
So please suggest me what shall I do?
singh.r said:
Hiii
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
Safe strap doesn't work (Back Option) on this phone due to some partition mapping issue. (Known issue for XT 883, ME863)
Sr. member TBBle suggested a tweak with safestrap & with that I am able to Backup my phone, do disaster recovery etc.
"http://forum.xda-developers.com/showthread.php?t=1625877"
But whenever I install a ROM in safe system it boots to black screen. I tried with Maverick 4.5 & CM7.2 both same result.
I am not able to decide if it's safe strap problem or ROM compatibility with XT883.
So please suggest me what shall I do?
Click to expand...
Click to collapse
I have a xt860 and sometimes when I flash something in safestrap and reboot I get a blank screen as well (it almost looks like the screen is off). I just pull the battery and then it boots fine. Maybe that will help if you haven't tried doing it yet, otherwise I'm not sure how to help sorry.
Well I have same issue. I already saw you post in other forum in 4.5 Mav ROM thread.
What are you looking for ? Use TATA CDMA OMH on Droid 3 ??
If Yes, message me, I shall give you a way out. Using mvp's method, you can use any Verzion ROM or custom ROM with Droid 3.
The issue is we can't use Maverick ROM with XT883, do you know any ROM compatible with XT883 ?
may be need Verizon 890 stock rom and XT883 rom mixed together.
flash the mixed rom,which should use safestrap.
Verizon 890 files:
1.boot.img 2.cdrom 3.cdt.bin 4.device_tree.bin 5.lbl 6.logo.bin mbm.bin
7.allow-mbmloader-flashing-mbm-.bin 8.ebr 9.mbmloader.bin 10.mbr
11.preinstall.img
xt883 rom files:
others files except above.
recovery.img file I am not sure whether xt883 or verizon,need test.
modify xml according to md5 of these files.
I'm pretty lazy, if someone successful please tell me,hahahaha!!!!!
kapilthio said:
What are you looking for ? Use TATA CDMA OMH on Droid 3 ??
If Yes, message me, I shall give you a way out. Using mvp's method, you can use any Verzion ROM or custom ROM with Droid 3.
Click to expand...
Click to collapse
Thanks, please guide. I want my phone to work with both GSM/CDMA sim cards, as it's working now. Have not dared to remove stock ROM just cause I am not sure if I will get the same functionality after changing the ROM or not. Due to that reason only I was trying to taste it with safestrap, but of no use.
Thanx for your help, & sorry for late reply, seems I forgot to subscribe the the thread.
NIGHTMARE- said:
The issue is we can't use Maverick ROM with XT883, do you know any ROM compatible with XT883 ?
Click to expand...
Click to collapse
No luck till now. I have tried (in safe mode) CM7.2, AOKP 40, Milestone 6, XT862 .906 ROMs. All installs fine but won't boot at all.
Will update you as soon as I get any thing to work. Or may be we have to SBF with some verizon ROM & then only it will work.
adamskub said:
I have a xt860 and sometimes when I flash something in safestrap and reboot I get a blank screen as well (it almost looks like the screen is off). I just pull the battery and then it boots fine. Maybe that will help if you haven't tried doing it yet, otherwise I'm not sure how to help sorry.
Click to expand...
Click to collapse
Thanx already tried that few times, each time left phone for more than 30 mins, but it stays black with back lights on.
Actually till now I am not even sure if it's ROM compatiblity issue or safe strap version or my Phone current ROM.
Hopefully I will figure it out soon.
mvp3 said:
may be need Verizon 890 stock rom and XT883 rom mixed together.
flash the mixed rom,which should use safestrap.
Verizon 890 files:
1.boot.img 2.cdrom 3.cdt.bin 4.device_tree.bin 5.lbl 6.logo.bin mbm.bin
7.allow-mbmloader-flashing-mbm-.bin 8.ebr 9.mbmloader.bin 10.mbr
11.preinstall.img
xt883 rom files:
others files except above.
recovery.img file I am not sure whether xt883 or verizon,need test.
modify xml according to md5 of these files.
I'm pretty lazy, if someone successful please tell me,hahahaha!!!!!
Click to expand...
Click to collapse
Thanx, but it will take me some time to reach that level. I am just a beginner who is doing things with helpful posts of experts like you.
Meanwhile I will try to figure out some thing easier or learn to do what you are saying.
# Sorry for late respone, I forgot to subscribe the thread. (Changed to automatic for all future posts)
For now I'm only using Xt883 ROM.
I have tried out.
flash Verizon 890 stock rom
then use moto-fastboot flash 4 files of xt883 rom,boot.img system.img recovery.img radio.img
moto-fastboot.exe flash boot boot.img
moto-fastboot.exe flash system system.img
moto-fastboot.exe flash recovery recovery.img
moto-fastboot.exe flash radio radio.img
then use recovery to update ota 60.3.250 and GMS package.
root.
Droid3Safestrap 2.00 works normally.
mvp3 said:
I have tried out.
flash Verizon 890 stock rom
then use moto-fastboot flash 3 files of xt883 rom,boot.img system.img recovery.img
This should let you can use safestrap normally.
Click to expand...
Click to collapse
Thanx
I need it to work with GSM/CDMA OMH, do I need to flash radio as well?
singh.r said:
Thanx
I need it to work with GSM/CDMA OMH, do I need to flash radio as well?
Click to expand...
Click to collapse
yes ,I forgot,sorry
singh.r said:
...
I have XT862 flashed with XT883 (purchased from e bay). It has around 3 GB app partition.
...
Click to expand...
Click to collapse
I've bought 3 of these phones from ebay (XT862 on the label, flashed wit XT883).
Simply SBF them with .890 or .906 and you should be good to go
srtzlyn said:
I've bought 3 of these phones from ebay (XT862 on the label, flashed wit XT883).
Simply SBF them with .890 or .906 and you should be good to go
Click to expand...
Click to collapse
Thanx.
Did you get them to work with GSM/CDMA both after flashing verizon.
Does the verizon dialler has recording button while in call.
Does FM works on verizon ROM.
I know how to SBF, do you know any link for .906 ROM which can be SBFd, or I have to flash .890 & then apply update for .906.
Thanx again
singh.r said:
Thanx.
Did you get them to work with GSM/CDMA both after flashing verizon.
Does the verizon dialler has recording button while in call.
Does FM works on verizon ROM.
I know how to SBF, do you know any link for .906 ROM which can be SBFd, or I have to flash .890 & then apply update for .906.
Thanx again
Click to expand...
Click to collapse
I'm not sure about CDMA because we don't have that here in europe.
Also I haven't really used the stock rom, directly flashed MavROM 4.5 with safestrap, so I don't know about the verizon features in stock...
The .890 (title says it's the .906) SBF can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1686911
there's a better way.
http://forum.xda-developers.com/showthread.php?t=1519844
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
bobdole said:
I have a bionic on stock JB. I have FXZ many times and do not get any errors with FXZ, but it seems that the radio never gets written.
I belive the radio files only get written after the 1st reboot after FXZ process. During that time, I see the robot with the chest open. It appears to be doing some file updates, and I don't get any errors. However, after flashing, I always get "baseband version: unknown" when I check the phone info.
I have attempted to do stock recovery using update_zip. The update zip contains bp.img and lte.imp. When I tried to flashe those file in recovery mode, I see that it goes though some package verification process, then it aborts. So the files never get flashed.
Is there some other way I can flash these radio files? I tried some custom roms like blurry, carbon. None of them include radio files, so the custom roms still run off the corrupt radio files that I have.
Since fxz and stock recovery doesn't flash the radio files, is there any other way to update these file? My phone is rooted, so can safestrap update do it? Or can I do it through adb? Or copy the files in through root explorer?
I heard that the radio files reside on the /radio partition, but I have not seen that directory when I use root explorer. Many it's not normally mounted. Does any know how mount that partition for edit?
The FXZ file has radio.img, but the stock recovery has bp.img/lte.img does anyone know what's the difference?
Click to expand...
Click to collapse
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
useltonm said:
Dumb question, but have you verfied MD5 on your fxz to make sure your download wasn't corrupt?
Click to expand...
Click to collapse
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
bobdole said:
Yes, the MD5 does match up. This brings up the question if I got the file from the right place.
I have not being able to find any other place to down load the JB stock rom other than this place:
http://sbf.droid-developers.org/cdma_targa/list.php
Did I get it from the right place?
Click to expand...
Click to collapse
The bottom one is definitely the correct one for jb on the bionic.
Let me check something and I'll get back to you.
Sent from my XT875 using Tapatalk 4
---------- Post added at 01:32 AM ---------- Previous post was at 01:26 AM ----------
I was going to suggest trying the house of bionic, but it looks like you already went there.
Sent from my XT875 using Tapatalk 4
Can anyone help?
I'm trying to do an experiment to flash just the latest JB bp.img and lte.img (radio files) in stock recovery.
When I do it it fails on package validation.
I found some older 902 and older radio files, those do not fail package validation, but fail to flash.
I assume they fail because of security(no going back to older version).
I need some to help package the bp, lte.img files into a zip. I tried the signapk tool. It seems to generate all the manifest files, but somehow the files do not pass package validation.
I tried taking the 902 radio files that pass package validation and run them through signapk, and sure enough they would fail package validation after signapk.
Can anyone help, please!
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi cellzealot,
I really appreciate your help. I tried flashing your file, but I get the same error as when I flash for full JB update file, which is:
assert failed: motorola.motoflash("/tmp/bp.img")
I was wondering if you could do one more thing to help..
Since it's failing assert, what if we modify the script to no do a assert check, but just run the command?
This is the update-script:
assert(show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img"));
What if we make it like this:
show_progress(0.2, 2),
do_format_cache(true);
package_extract_file("bp.img", "/tmp/bp.img"),
package_extract_file("lte.img", "/tmp/lte.img"),
show_progress(0.8, 35),
motorola.motoflash("/tmp/bp.img"),
motorola.motoflash("/tmp/lte.img"),
delete("/tmp/bp.img", "/tmp/lte.img");
I'm hoping that this might work.
BTW, how did you package the zip file and sign the files?
The original zip file had lots other system/boot files.
Thanks!
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
cellzealot said:
I didn't sign or edit the files at all. The update.zip is pulled from the radio.img using a hex editor.
Te radio image is an ext3 partition that just contains the update.zip which itself contains the signed bp.img and lte.img that are flashed in recovery after the device reboots from AP fastboot bootloader.
This is because the MDM6600 Motorola devices are all hybrid chipset boards and the OMAP AP chipset is separate from the Qualcomm MDM6600 CDMA/EVDO/GSM/WCDMA radio and the Motorola TI Wrigley LTE radio.
The radio chips are setup on a BP passthrough only device interface that cannot be flashed in AP Fastboot mode.
This is why you can't see the radio partitions in the file system of the device and the kernel layer only has access to the radio via the RIL.
Regarding the persistent errors, it sounds like it is failing due to the recovery because there is no reason it would fail asserts with the signed files in stock recovery.
Click to expand...
Click to collapse
Thank you for your explanation.
I was able to find the radio.img file from the OTA xml.zip for fxz.
Indeed, if I open the radio.img I find the update_radio.zip that you have provided.
What I don't quite understand is why we are able to flash various custom roms that are not signed by motorola through CWM, TWRP.
Would there be a way to run a modified update_radio.zip through CWM, TWRP?
"Now to" needed
cellzealot said:
....... link removed because it won't let me post with it in here.......
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
Click to expand...
Click to collapse
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
RichT1 said:
I have found a lot of information about needing to flash the Bionic radios, and that its not included in the custom ROM (I have a current Cyanogen nightly & baseband CDMA_n_05.13.01R LTEDC_U_09.14.00). I downloaded the file you listed above, but now the question that I can't seem to find the answer to.... "Now What"... when I installed safestrap and the custom rom i found some very helpful step by step instructions... I can't not seem to locate the same for flashing in new radio files.... so if someone could point me in the direction of some that would be most helpful...
BTW.... Typing "upgrade bionic radio files" into forums and Google returns everything BUT what I am looking for
Click to expand...
Click to collapse
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
http://www.droid-life.com/2011/09/2...boot-menu-for-recovery-sbf-flashing-and-more/
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
bobdole said:
Put the radio file on a SD card(leave it as .zip, don't unzip it) put the sd card in in your phone.
The follow these instructions to flash in recovery mode:
.... link removed .....
In recovery mood, select update zip from ext-sdcard
Then pick the radio file..
That's it.
Click to expand...
Click to collapse
Thank you.... worked like a charm....:victory:
I'm literally a real noob when it comes to this stuff.. But when I tried to flash the radio files from above via recovery, I got this error.
assert failed: motorola.motoflash("/tmp/lte.img")
I've lost my lte baseband way before trying this, I've actually lost it, running a Carbon nightly rom.
EDIT
I've changed the updater script and now I'm having a problem with it aborting the installation alltogether. Any help would be greatly appreciated. I just want to get my LTE radio working :|
cellzealot said:
https://dl.dropboxusercontent.com/u/7632904/targa_jb_update_radio.zip
This is the radio only update.zip that contains the bp.img and lte.img that are digitally signed by Motorola and is pulled from the radio.img of the Bionic JB release from the XML.zip.
System Version
98.72.22.XT875.Verizon.en.US
Baseband Version
CDMA_N_05.22.00 LTEDC_U_09.1D.00
These are the only files you can flash the radio with on any MDM6600 Motorola device. They must be the signed images in the original file flashed in stock recovery.
If you flash these and still have Baseband Unknown errors then you may have a corrupt amss.mbn and we don't have files to fix that for any recent releases.
That is extremely rare and if you flash the properly signed baseband images it should restore normal function in almost all cases.
Click to expand...
Click to collapse
Hi CellZealot,
Do you have radio.zip file(s) from GB versions by any chance? I'm on ICS and want to try GB radio(s) hoping to get better signal strength and possibly enable 900/1800mhz band if it's disabled in ICS radio. I'm still experimenting to get my Bionic (Hw A, 08/12) to work on 900/1800mhz.
Is Droid Razr also MDM6600 Motorola device? If yes, can I try and get its radio and flash on Bionic? Please advise.
Thanks.
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
Thanks a lot CellZealot. You're a gem!!
cellzealot said:
https://www.dropbox.com/s/vnob615mwf17xxk/Bionic_Radio.zip
I believe that zip has most or all of the older radios. Posting from phone at work.
Click to expand...
Click to collapse
I tried flashing a couple of radios from that zip file via recovery and the update was successful each time. I did NV edits, buildprop changes and the factory data reset each time. But when I checked the Baseband version info, the LTE component was missing e.g..it only shows CDMA_N_04.07.02R. I suspect somehow LTE part was not flashed via recovery even though no error was shown. Also IMEI and SV show up unknown as well. Did I miss some step or did I do something incorrectly? Please advise.
Thanks in advance.
P.S. I didn't rename the radio zip file to update.zip. Just used the files as is from the above zip. I'm trying to use them on ICS, These GB radios aren't fully compatible with the ICS version kernel or something?
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
I have been working on my bionic for months.
Casey Walt said:
This post helped me fix my bionic... the same process applies to the baseband unknown issue that i had and i found a lot of bionic owners have the issue also. the simplest fix is actually not to put the radios on the sd card but instead to make a copy of the xml doc that is in the fastboot files and delete every step but the radio install (the last step) then use rsd lite and change the xml file to the one with the radio
Click to expand...
Click to collapse
This all started back in december 2013. a buddy gave me a bricked bionic.. i was able to "unbrick". and install the 98.72.22 fxz. i only get service half of the day and 3g like maybe 30min...i also have the error where the lte.img will not install. Thus please explain more as to how you were able to fix it. Do you have 4g? i haven't been able to restore it. i had to splice a usb cord and attach the pos and neg to the battery and connect a charging cord from the phone to my desktop to get a led response from the phone during the unbricking process. basically if i install a new rom daily i have steady service all day.. 3g even. but then it just craps out on me. believe me, im not giving up on this phone until i see a 4g icon on my status bar.
I have an S3 now but i can still glady help you.... what i did was put a shim in my sim card holster. then put the .905 radio in the fxz folder and flash it again... you wait like 5-10 min till you have service ( if you did it right there should be no lte in the baseband yet) then put the zip file for the 4.1.2 radio on your sd card and flash it through stock recovery. when you boot your phone up you wait 5-10 min again and you should have both 3g and lte in your baseband
Sent from my SCH-I535 using xda app-developers app
Hi All---
I'm an old-time flashaholic who hasn't flashed in a long time.
However, I'm so sick of the memory bug, that I'm going to try out CM12 on my xt1095.
However, I want to verify that there is a way to later return my phone to stock so that I can recieve the OTA when the fix (eventually) comes.
I can't find a thread that tells me how to do it (on the old moto x you would use an sbf, but i don't see anything about that around here.)
Thanks so much for your help in advance...
1 Making a backup in recovery of your actual stock rom and restoring when needed (with twrp for example)
2 Flash via bootloader with fastboot official rom (no zip to flash)
3 using RsdLite using official rom (no zip to flash)
Cheers
Ps: ota is another thing already discussed here
michyall said:
1 Making a backup in recovery of your actual stock rom and restoring when needed (with twrp for example)
2 Flash via bootloader with fastboot official rom (no zip to flash)
3 using RsdLite using official rom (no zip to flash)
Cheers
Ps: ota is another thing already discussed here
Click to expand...
Click to collapse
Any clue where I'd find the official ROM (either for fastboot flashing or rsdlite)? I can't find any links...
My phone is already on 5.0, fwiw.
Thanks for the help
There is a lot of topic about stock roms on this forum, in your settings you have to search what version do you have (see picture) and download that one.
But i don't kno if you're expertor maybe you know what you are going to do. I ask you: twrp installed? Rooted? Why not doing a backup without downloading tons of mb and going crazy flashig 10 files?
That's my opinion.
Last word, search this forum, there is a lot of discussion like this one
Forgot screenshot
I don't have the link but the XT1095 retail/tmobile 5.0 full image can be directly downloaded from Motorola just like the images for the Moto X 2013.
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
1stStep said:
Hi all, glad to find this
I have ..., guess what ? a RAZR i (Ok, it's a friend's one) that I repaired changing the mad battery after factory resets didn't do anything. Then found OTA was available, applied and the RAZR i was 4.1.2 IIRC and the new battery went OK. My mistake, another OTA went soon, which I applied too, making the RAZR i a 4.4.2 kitkat piece of crap (no more write access to sdcard, this is well known ... by the ones aware , know I'm one).
Then I thought I could make the phone free and search the web for days to try to understand, found a french forum which said I can't do anything without unlocking the bootloader, what I did.
They directed me there to remove the boot-logo-warning but that's a razr hd thread and nothing worked for me. I can't remember where I read I should have CWM to do this, but as the french guy said he rather like twrp I didn't do anything at the moment, only failed to flash some logo from fastboot with various errors....
Well, I'm there, and it's cool because I hope this is the good place to have answers to questions that are still in my mind for years, and 2/3 new ones... fortunately they'll overlap and self-resolve once I get one. I'm not at all skilled in android, I only flashed a phone in 2010 and that's why I still have android SKD in my ubuntu (I also have a xp box, but I couldn't do anything for my old Acer LiquidMT). As you see, I'm a vintage things amateur (... okay, I'm vintage too).
Now the scene is built, please let me dare ask what still puzzles me :
1) For the Razr i 4.4.2 (french from sfr-vodafone kia20.74 now used with another carrier) do I have to search a specifically dedicated recovery ? Parsing this RAZR i Q&A, I found twrp seems to the preferred recovery, but I'd rather like to get confirmation from skilled ones, and also for version.
2) And please tell me if I'm wrong thinking the [RECOVERY] Unofficial TWRP 3.0.2-0 thread aim is to bring support to the RAZR i which is not supported by official teamw.in ? (BTW, @Hazou, the 1st link in the thread - DataMedia - is dead)
3) Assumed I have to go the TWRP way and I only have currently the stock recovery, do I guess right the only way is download img.zip and extract then do
Code:
./fastboot flash recovery recovery.img
, then only after that the phone can be rooted ?
4) You see I'm puzzled here because I still don't have understood the logical path: is this one the good ? unlock boot loader -> fastboot flash reco -> is the device rooted at this point ? If not, install su from recovery option "install zip from sdcard", then it's done and I get a so called "rooted stock ROM" ? Then only I can figure installing a custom ROM if exists for the RAZR i ?
5) And I should always flash a custom ROM based on the same 4.4.2 android release as my current stock one AND disable OTA updates ?
I read so many threads with guys having issues with hard-bricked RAZR i and all are about ICS and JB, so I wander the only custom are for ICS or JB, and still don't understand why they want to revert back.
Thanks for advices.
Click to expand...
Click to collapse
Hey 1stStep,
A lot off assumptions and questions. And most of them are right.
1. Afaik there are 2 recoveries for the RAZR I. Stock and my build TWRP 3.0.2-0 unofficial. (Thanks for the heads up about the link)
2. Answered in 1.
3. Yep. If your bootloader is unlocked it gives u the function to flash non-stock firmware to the phone. Stock firmware are signed to prevent normal users flashing wrong firmware. Firmware consist of a couple of images. Those images contain data for the partition, just like in your PC. Every image does something else. Most known are boot, data, system, recovery and cache. There are many more. Some needed, some unnecessary.
To answer your question: when u have flashed the TWRP recovery u override the stock one. The TWRP can flash zip files and images to the most known device partitions. From here on u can flash a superuser zip(gives root access on the current ROM/system). Make sure u have the right superuser zip. There are many.
4.
Path to root on stock:
Unlock bootloader->install custom recovery (TWRP)->install superuser zip->reboot and test root on device
Path to custom ROM:
Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like (Gapps(needed for Google playstore and more))->reboot and play with your new ROM.
Off course if u already have the bootloader unlocked and installed a custom recovery, u can skip those.
In the recovery u can also make backups, called nandroid backup. Read up on them and everything u wanna do.
5. The only thing u never want/should do is flashing Android 4.0.4 stock firmware without prior modifications. This is because from 4.0.4 to 4.1.2 there was a change in bootloader (the thing u unlock). If u go back it corrupt a part of the firmware which is difficult to overcome or even impossible without some factory stuff. Everything above 4.1.2 is save. And can always be flashed. The latest stock is 4.4.2 (KIA 20.74) and latest available custom ROM is 4.4.4 (CM11 or soon Lineage 11).
Good luck!
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
1stStep said:
Thanks so mush great dev to spend time and even surely repeat yourself (hope you're not under stress) for a newb.
Click to expand...
Click to collapse
Not at all , just replying if I have some time.
1stStep said:
In your answer for path to custom ROM you say "Unlock bootloader->install custom recovery (TWRP)->install ROM zip and extra's if needed like".
Do I have to understand custom ROMs are yet rooted (OOTB), or root yet made on stock will survive flashing the custom (I though flashing a custom was some kind of infant clear brain graft?
BTW, is it general good advice to test recovery before flashing? I found this in Moto Play unofficial recovery 3.0.2-r5 from Vache:
Code:
fastboot boot recovery.img
?
Thanks again
Click to expand...
Click to collapse
- Most custom roms are prerooted.
- Cyanogenmod/LineageOS are prerooted
- Root installed by a zip will not survive any system flashing (rom flashing)
- Any modification to your system partition will not survive and system flashing (rom flashing), though 1 exception:
- installed gapps package (google apps/play store etc.) will survive system flashing on cyanogenmod based roms. But only when updating the rom to a newer version on the same android version. So:
CM11 version 1 to CM11 version 2. (because of a special script in the install zip)
Pre testing a boot or recovery image is blocked on our bootloader. So u can't do it. It's a shame they did it. Working on any boot or recovery changes is a pain in the spoken ass.
If u flash the recovery with:
Code:
fastboot flash recovery recovery.img
there is nothing to be afraid off. The TWRP 3.0.2-0 recovery is well tested on this device.
Thank you again man for all detailed answer.
You're right, it's a shame all these locked things in our phones. I'm sure the guys that agree (our security, blah blah) with these ways to do won't be so happy the day their computers will be locked the same way.
bye bye Hazou.
[Edit] .... hmmm, how long does it take to flash? Yet a 1/4h elapsed and razr still says "Flashing recovery..."
Please, what is the md5 of the image (not the zip, this you give us)? Thanks
[Edit] : Downloaded twice and get md5sum 60dff26f3ee5e9338ee4a6f8cf7df098
but still same forever Flashing recovery ...
[Edit] : I've been puzzled for days being stuck in endless "Flashing recovery ..."
In the ended I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.
While I was running CyanogenMod, I suddenly had a devastating issue where the phone would not even detect SIM Cards, and Bluetooth would sometimes cause the phone to force reboot. Afterwards some custom ROMs have the same issues, and reboot literally randomly, sometimes endlessly bootlooping.
The stock 5.1 ROM also had the issues but also didn't wanna connect to WiFi.
I recently followed a guide to install the 6.0.1 update on the Turbo, and suddenly, everything worked again. No random reboots, Bluetooth working, and WiFi. However ANY other ROM would have the issues.
Is there something that the OTA 6.0.1 update fixes that all other ROMs cause these problems?
No one else has those problems on custom ROMs. So, there's nothing to "fix".
No one would be running any of the custom ROMs if they had such issues.
Stock 5.1 also didn't have connection issues nor Wi-Fi issues.
Flashing 6.0.1 stock reflashed your radio, which "fixed" your issue, probably. THAT was probably all you needed to do. You can also flash @bhb27 clear modem file, which fixes stuff like GPS. Sometimes flashing a custom ROM will confuse a radio/modem and clearing the cache/stats with that file helps as well as reflashing the radio.
I thought that might have been what happened, but even after flashing the 6.0.1, which has everything working, installing a custom ROM gives the issues. Before this I always thought my hardware simply failed but this is the only ROM where it works now, the 6.0.1.
So what I should try is clearing the modem status or reflashing the radio even after installing a custom ROM just to refresh the things?
ethangarsia517 said:
I thought that might have been what happened, but even after flashing the 6.0.1, which has everything working, installing a custom ROM gives the issues. Before this I always thought my hardware simply failed but this is the only ROM where it works now, the 6.0.1.
So what I should try is clearing the modem status or reflashing the radio even after installing a custom ROM just to refresh the things?
Click to expand...
Click to collapse
Yes, some of your symptoms like the endless bootlooping seem very unusual. I don't know of radio-related issues that cause that. But not being able to use GPS, Wi-Fi connection issues, or even not detecting SIM cards are symptoms of radio/modem problems.
When flashing a custom ROM on our Quarks, GPS especially was a complaint. There were workarounds to fix it as early as 2015, but then @bhb27 (who is the dev for several custom ROMs) came up with the @bhb27 Clear Modem File. You flash that. In simplistic terms it clears the cache of your modem. It has helped countless people, with Droid Turbo/Moto Turbo/Moto Maxx.
Often just that fixes any issues, but you can also then take the next step of re-flashing the most current radio/modem for the Droid Turbo.
ROMs don't have radio/modems included inside the ROM. When you flash a custom ROM, it uses the radio you already have. Clearing the cache, and reflashing makes everything new again.
We've had custom ROMs for over two years now for our Quark phones. True the Droid Turbo XT1254 bootloader was finally unlocked back in November of 2015, but still that's been 1.5 years. There's tons of custom ROMs and if you look at the download stats of those ROMs there's THOUSANDS of people using them. If the ROMs had the issues you had, there would be no users, believe me!
The issue is for a percentage of people, not even a majority, but a percentage, the radio/modem becomes confused when flashing a custom ROM. But it's easily fixed...
Go look at this page from just two days ago. Similar issue with AOKP 7.X. EXCEPT it's NOT an issue with the ROM. It's the issue of someone not reading thoroughly.
Phone calls not working
https://forum.xda-developers.com/droid-turbo/development/rom-aokp-7-x-quark-t3504629/page67
Yet, the dev clearly says in post #2:
NepoRood said:
Last, but not least, you just might need to clean your modem:
Download Zip
Click to expand...
Click to collapse
Once the user flashed that, all was well.
raginhomosapien said:
I just flashed the clean modem.zip, and everything seems to be properly working now! I have rebooted and started a call 5 times, and it has worked each of those times. I'll see how things go over the next few days, whether it breaks again or continues to work without issues.
Thanks for the help!
Click to expand...
Click to collapse
and this guy over in RR 7.x last week, with a Moto Maxx XT1225:
Wi-Fi won't connect.
https://forum.xda-developers.com/showpost.php?p=71652207&postcount=1474
I helped him by providing the link to the clear modem file and the latest radio/modem for his model. (He flashed both, just to make sure.)
kenedi jr said:
Ahahah thank you... All works now. You saved my life
Click to expand...
Click to collapse
* Here's the Clear Modem File, also called the Clean Modem file:
@bhb27 Clean_modem_status
https://www.androidfilehost.com/?fid=24531035584725320
*Here's the latest TWRP-flashable Marshmallow radio/modem for the XT1254 Droid Turbo.
TheSt33v said:
By popular demand, here are just the (XT1254) modems:
XT1254 MARSHMALLOW MCG24.251-5-5 100% Stock
https://mega.nz/#!m9xnwDjD!jvvLXbGpCN9QVzRY1hph6JOyZv8kiBcLs2bsCdIgv8w
Click to expand...
Click to collapse
*For those with the XT1225 Moto Turbo/Moto Maxx, here's the latest TWRP-flashable radio/modem:
XT1225 MARSHMALLOW Radio_Flasher_Stock_MPGS24.107-70.2-2.zip
https://www.androidfilehost.com/?fid=457095661767122577
Do NOT flash an XT1254 radio over an XT1225 or an XT1225 radio over an XT1254. I am including both radios in this thread for people who may need them.
The clear modem file/clean modem status file (whatever you want to call it) is for ALL Quarks, but the radio/modem files are very device specific.
I always keep a copy of the Clear Modem file and the latest TWRP-flashable radio in my Download folder on my phone. Whenever I flash a new ROM or even an update to a ROM, I always flash those files too. It can never hurt and can only help.
ChazzMatt said:
* Here's the Clear Modem File, also called the Clean Modem file:
@bhb27 Clean_modem_status
https://www.androidfilehost.com/?fid=24531035584725320
*Here's the latest TWRP-flashable Marshmallow radio/modem for the XT1254 Droid Turbo.
Do NOT flash an XT1254 radio over an XT1225 or an XT1225 radio over an XT1254. I am including both radios in this thread for people who may need them.
The clear modem file/clean modem status file (whatever you want to call it) is for ALL Quarks, but the radio/modem files are very device specific.
I always keep a copy of the Clear Modem file and the latest TWRP-flashable radio in my Download folder on my phone. Whenever I flash a new ROM or even an update to a ROM, I always flash those files too. It can never hurt and can only help.
Click to expand...
Click to collapse
Unfortunately, flashing the clean modem.zip didn't bring about anything than a very temporal fix. Now it's basically a complete crapshoot as to whether I will get complete silence on my end and my mic muted for the other person, or whether the call will go through, but after some a mount of time I will lose all audio and my mic will mute. A couple times calling worked fine. Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
raginhomosapien said:
Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
Click to expand...
Click to collapse
Yes, if you have an XT1254.
In TWRP, flash back-to-back with the Clean Modem file first, then the radio/modem.
Then let TWRP clear all caches (it's an option anytime you "install" something), then reboot to system.
raginhomosapien said:
Unfortunately, flashing the clean modem.zip didn't bring about anything than a very temporal fix. Now it's basically a complete crapshoot as to whether I will get complete silence on my end and my mic muted for the other person, or whether the call will go through, but after some a mount of time I will lose all audio and my mic will mute. A couple times calling worked fine. Would you recommend flashing the XT1254 radio/modem zip you included now that I've flashed the clean modem?
Click to expand...
Click to collapse
ChazzMatt said:
Yes, if you have an XT1254.
In TWRP, flash back-to-back with the Clean Modem file first, then the radio/modem.
Then let TWRP clear all caches (it's an option anytime you "install" something), then reboot to system.
Click to expand...
Click to collapse
FYI: just re-flashing the modem doesn't fix all issues -- and just flashing the Clear Modem file doesn't always fix all issues (but it does fix a lot). However, a combination of the two, YES.
Back before the @bhb27 coded the Clear Modem file, just re-flashing the modem did NOT fix GPS issues which plagued a minority of users. I never had the issue, but for people that did have it, they complained and complained. For us who didn't have it, we couldn't figure out what they were doing "wrong".
Someone figured out a a very complicated workaround (going back to stock, getting a GPS lock, then immediately flashing the custom ROM, etc.) And then someone figured out they could share a TWRP backup of their "good" modem for people with GPS problems.
But the @bhb27 Clear Modem file FIXED ALL THAT, for GPS. All you had to do was flash that, after installing a custom ROM.
But for other radio/modem problems, some people flashing the Clear Modem file AND then re-flashing radio/modem is the key.
You can flash them both back to back in TWRP -- the Clean Modem file first, then the radio/modem.