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
Related
I've been flipping through the threads to find out how I'm suppose to update the radio and still can't find anything.. Maybe it's because I'm an extreme noob when it comes to forums and software. Can anyone point me to the right direction?
P.S. What does updating the radio do? I've been curious about it since it seems like a plus to keep it up to date.
I have been looking for a how to for updating the radio. My main concern is that since I got the official OTA update, then rooted with Superboot, then installed Modaco's Desire rom will updating the radio as is brick my phone?
In one of these threads there will be a radio update.zip (check cyanogens thread, i think he hosts the latest radio on his forum)
before you put the radio on your phone, check the md5. If you are on linux, use furious ISO mount, if on windows, look it up on google how to.
Place the radio on your SD card ./ folder, then boot into recovery
Make sure you have plenty of battery, or are plugged in and charging.
Flash the radio from recovery and wait.
Alternatively you can place the radio.img (either downloaded by itself or take it out of the update.zip.) in your /sdk/tools folder and type "fastboot flash radio radio.img"
The very first stickied thread in the Development forum is called "Roms - Kernels - Radios *Links*" and it has links to .zip files that install from a hacked recovery. The Radio links are in the third post. Just use one of those.
http://forum.xda-developers.com/showthread.php?t=654869
If your recovery isn't hacked, you could just unzip one of those files and pull out the radio.img file, which you can then flash with fastboot.
Hi!
I use Android 2.2.1 FRG83D (Nexus One T-Mobile version). I found that a lot of users use a newer version of baseband which is 5.12 or 5.08. I still use 4.06.
Should I update my baseband version to 5.12? is it official? or still in the beta stage? Any change-log?
Thanks,
Would like to know too.
Is there any difference?
It's official. Just try it YMMV. If it doesn't perform any better switch back.
What does YMMV mean? And how can I know if it will perform better or not?
Your Mileage May Vary
Means it may or may not be better basically. Try and see.
If possible, flash via fastboot rather than recovery.
People who use 5.08 or 5.12 notice speed and battery life improvement, while few people experiencing problems with those two radios or notice degrade signal or speed.. I'm using 5.12 there's no problem for me, it saves battery
I tried to update my device radio version by using the recovery.. no luck!! should I rename the file to update.zip for example? :\
Salah9 said:
I tried to update my device radio version by using the recovery.. no luck!! should I rename the file to update.zip for example? :\
Click to expand...
Click to collapse
You need a custom recovery where you can disable signature verification.
Please make sure to verify the MD5 hashes BEFORE flashing. It's VERY important or else you could easily brick your phone.
Even better, if your bootloader is unlocked, flash it with that.
I already verified MD5. I couldn't find anything about disable signature verification!! I use RA-nexus-v1.5.3
You can't just slap radio.img on the SD card and flash it, you have to make an update.zip from it.
This is what I did. I downloaded zip file from this thread http://forum.xda-developers.com/showthread.php?t=816917 and tried to flash it from the custom recovery.
Looking at that thread, it's an unsigned update, so you would need to ensure that the recovery you're using doesn't use signature verification.
The one you currently have is far too old, try Amon Ra v2.0 or a new ClockworkMOD instead.
Yep that file is flashable, just get a recovery (1.9 alpha or 2.0 from amon_Ra, although in 2.0, you have to MANUALLY disable signature verification in the "More" section) and you should be fine.
Thank you guys. I used ROM Manager to update the recovery and then I updated the radio version to 5.12
* Update: This version is really so nice!! The wifi didn't drop when I set the wifi sleep policy to Never!! I'm a happy user now
So in my attempts to undo unbrick my bionic i was able to get back on the path and got into a rooted 901 version YEAH.
Problem is my webtop version is WT 1.3.0-105_DBN-1 which is not the current version. Does anyone have a way to get an updated grfs version onto the phone or a process that works coming from 901?
The problem as I see it, is that you aren't really on 5.9.901 because you couldnt have updated with the leaked update.zip without having all of the signed components from 5.5.893 including the webtop partition. You must be using a ROM that updated only your system and nothing else.
The solution is to use the full 5.5.893 xml.zip released recently and flash it with RSD Lite and it will put you back on the path with all the stock images.
If you wanted to only flash the grfs.img from that file then you need to use the moto-fastboot.exe instead of the fastboot.exe because it is modified to handle larger than 256MB images.
It is difficult to tell where you really are with all of your firmware components and whether just flashing the webtop will do you any good. That is why i recommend the full xml.zip and RSD Lite.
This is the method that a technician would use to fix a returned device to stock and is what the file is designed to do. Its like an SBF file but uses the fastboot interface instead of the old flash interface.
We have all the tools we need to recover virtually all problem flashes at this point, and its up to everyone who is modding these devices to understand the options before you flash any ROMs so you dont find yourself returning a device that you destroyed to VZW for warranty replacement, a practice all to common unfortunately.
Dear Experts
I am first time android user, have rooted Droid 3 XT883 & installed Safestrap 1.08.
Later I came to know that it wont's work due to some partition issues.
Now safestrap 1.09 is available for droid 4, will it work on my device?
Also please tell me how shall I uninstall safestrap 1.08 without damaging my phone.
Thanx in advance
Still Unanswered, please help
Please suggest, I am noob in this matter & can't try any dangerous stuff.
use this one!
all the explanations are there also.
if you decide to uninstall safe strap, you go to the main ROM. and nothing bad happens. you just choose disable SAFESYSTEM from recovery, and open SAFESTRAP in phone menu, uninstall recovery...and thats it.
Thanx but still unclear
your link directs to how to safestarp page which I have already gone through several time while downloading 1.08 & installing .
My question is that 1.08 doesn't support XT883 due to some issue with partition size, so shall I try 1.09 releases recently. On site it says it's for Droid 4 so I dont know if it will support droid 3 or not. I am afraid to try without any confirmation as I may brick it & I don't have any backup of ROM till now.
If 1.09 supports XT833 then please tell shall i just install the apk over 1.08 or shall i uninstall 1.08 first then install 1.09?
Droid 4 is a completely different phone. I wouldn't. I would tweet Hash if no one knows why here.
Sent from my XT862 using XDA
Thanx Mr. Obivious
I have posted on his blog & will wait.
Thanx for your advise.
I have a working build of Safestrap 1.06 for ME863 that should also work for the other non-Verizon variants too.
Instructions are at http://forum.xda-developers.com/showpost.php?p=20976390&postcount=294 and the download's attached a little earlier in the thread, with more instructions.
Thanx
TBBle said:
I have a working build of Safestrap 1.06 for ME863 that should also work for the other non-Verizon variants too.
Instructions are at http://forum.xda-developers.com/showpost.php?p=20976390&postcount=294 and the download's attached a little earlier in the thread, with more instructions.
Click to expand...
Click to collapse
So I have 1.08 installed on my 883, what I understood is that i need to unzip your file which contains two files (recovery & fixM3android.diff. Then I go to etc/safestrap & copy the 2nd-init.zip to my laptop. Extract it & replace the recovery file with yours & zip it again & replace the new 2nd-init.zip in phone /etc/safestrp folder & reboot. It will take the backup.
Few doubts :
1. Is there any chance that I may brick my phone by doing this?
2. Once backup is successful do I need to replace the original 2nd-init.zip for flashing another rom.
3. If i need to restore my original rom do i need to put back your's version of 2nd-init.zip
And many thanks to you for your help. All international droid 3 users shall get benefit if it works out well.
Edit : While zipping your version do I need to specify any specific compression method. As i faced while creating custom bootanimation for droid 3 that if you do a normal zip it doesn't work, it has to be selected store method in compression type.
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
TBBle said:
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
Click to expand...
Click to collapse
Hii, It didn't brick my phone, I am able to do backup & restore, enable safe system & install another ROM but the new ROM always boots to Black Screen. I have tried CM7.2 & Maverick 4.5. Going to try 1 or 2 more ROMs mean while to make sure it's not ROM problem. Could you suggest something what could be the reason or any workaround.
Thanx
We have same issue. I think we have to install Verizon ROM with .906 then we can install any other ROM.
NIGHTMARE- said:
We have same issue. I think we have to install Verizon ROM with .906 then we can install any other ROM.
Click to expand...
Click to collapse
Today I am gonna try few more ROMs with my tweaked safestrap, if it doesn't workout then I think we need to SBF with .906 & install safe strap then do it. But as I have heard on forums some features of XT883 ROM is comparatively good than others.
Please share if you find some other working solution.
Sure one of my friend having same problem, he well aware of android as compare to me. My primary device is iPhone, So I don't have such knowledge as compare to you also. We are looking into Gummy ROM let's see. And XT883 more stable than these ROM.
TBBle said:
That sounds right.
I guess it's possible to brick your phone doing this, but I think if it goes wrong you can just battery-pull to bypass 2nd-init for the next boot, and reinstall safestrap normally.
I don't know the answers to the other questions as I don't know what changed between 1.06 and 1.08, and I don't know if restoring works with my code, let alone with stock 1.08.
Sorry, I only threw it together quickly, so it's not massively user-friendly at the moment. I was hoping hashcode or rick#2 would integrate it or something similar, and my version could quietly fade into the mists.
Click to expand...
Click to collapse
Hey, I've been reading through everything I can find about the ME863. I've got Saestrap installed but I can't seem to get it to backup anything or to run any ROMs in safeboot after they've been installed. I have read your solution and done exactly what you say to. I copy over your recovery file then in ES File Explorer I copy over the 2nd-init to a new folder extract it delete the old recovery, put the new one in, compress it and then put it back in the original directory, (I leave the original renamed 2nd-init_original ) however when I go to boot to safestrap it just loads a black screen. Then I have yank out the battery reboot to the bastardization that is Chinese Android and put everything back and then safestrap goes back to sort of working (except not at all really). What am I doing wrong?
daniel0524 said:
Hey, I've been reading through everything I can find about the ME863. I've got Saestrap installed but I can't seem to get it to backup anything or to run any ROMs in safeboot after they've been installed. I have read your solution and done exactly what you say to. I copy over your recovery file then in ES File Explorer I copy over the 2nd-init to a new folder extract it delete the old recovery, put the new one in, compress it and then put it back in the original directory, (I leave the original renamed 2nd-init_original ) however when I go to boot to safestrap it just loads a black screen. Then I have yank out the battery reboot to the bastardization that is Chinese Android and put everything back and then safestrap goes back to sort of working (except not at all really). What am I doing wrong?
Click to expand...
Click to collapse
Probably the problem is your in zip, I also went through the same. Do as below
1. Install safestrap 1.08 on your phone
2. Copy /etc/safstrap/2nd init.zip to your PC. (file size 1.13 mb)
3. Extract it with winrar to some folder
4. delete the recovery file
5. copy TBBie recovery in folder
6. select all files & zip it to 2nd-init.zip (don't ZIP the folder, that's what mistake i had made & had same problem)
7. verify that zip size is 1.19 mb & when you open it in browser you see files not any folder.
8. replace the tweaked zip with original in etc/safestrap
9. set permission & ownership as original
10. Reboot & you shall be good.
Hi Everyone,
I bought a used phone, verizon droid 3 with the XT883 radio flashed on it, and have working safestrap 3.05. Currently I am able to use CDMA OMH, but without data. I have tried multiple options including flashing the newer version of the radio, as well as pppd-ril.options editing but it does not work. CDMA apn settings are disabled. I have also made changes to build.prop without any results. Anything else I can try?
One of my options is to flash the chinese ROM as it supports CDMA apn settings. I am not sure I can use RSD lite in one of the ROM slots.Can I select one of the ROM slots as active and flash the xt883 files on it? I think it will write to the stock ROM partition itself? Any help on how to go about it?
EDIT:
So I uninstalled safestrap and tried to flash the XT883 ROM(57.1.60) using RSD lite as described, but the following files showed an error in flashing and the phone bricked 1) Cdt.bin 2) Recovery 3) boot. I tried to flash by editing the xml file and skipping these files, but the phone showed a black screen on normal boot.
I tried to recover using psouza's rar file, but even there recovery and boot failed to flash. The phone is working though, and I am able to retain former functionality using motofail and flashing the XT 883 Radio again. Can someone suggest me a solution by which I can install the XT883 ROM and/or be able to access CDMA APN settings? Currently my fastboot suggests that my system is on .890 version, though the settings>about phone suggest I am on XT883 (possibly because of the radio)
dinu_dr said:
Hi Everyone,
I bought a used phone, verizon droid 3 with the XT883 radio flashed on it, and have working safestrap 3.05. Currently I am able to use CDMA OMH, but without data. I have tried multiple options including flashing the newer version of the radio, as well as pppd-ril.options editing but it does not work. CDMA apn settings are disabled. I have also made changes to build.prop without any results. Anything else I can try?
One of my options is to flash the chinese ROM as it supports CDMA apn settings. I am not sure I can use RSD lite in one of the ROM slots.Can I select one of the ROM slots as active and flash the xt883 files on it? I think it will write to the stock ROM partition itself? Any help on how to go about it?
EDIT:
So I uninstalled safestrap and tried to flash the XT883 ROM(57.1.60) using RSD lite as described, but the following files showed an error in flashing and the phone bricked 1) Cdt.bin 2) Recovery 3) boot. I tried to flash by editing the xml file and skipping these files, but the phone showed a black screen on normal boot.
I tried to recover using psouza's rar file, but even there recovery and boot failed to flash. The phone is working though, and I am able to retain former functionality using motofail and flashing the XT 883 Radio again. Can someone suggest me a solution by which I can install the XT883 ROM and/or be able to access CDMA APN settings? Currently my fastboot suggests that my system is on .890 version, though the settings>about phone suggest I am on XT883 (possibly because of the radio)
Click to expand...
Click to collapse
I have same problem plz if have any idea about it plz share
Thanks