Related
Here's a basic tutorial I wrote up to install Froyo on the N1. Seems like most are having trouble with it. All Files Included. Follow the steps as listed. Report any problems but I have yet to hear from anyone about any issues... Enjoy!
My Way also updates to the newest radio. New radio includes new Video Encoders so you'll want to try the new radio first.
Tutorial Here
Please Post your Results - Feedback. Thank You.
If you try any optional kernels, try .34 kernels, not 33.4. There is positive feedback w/ .34kernels + new radio. If you're using the Old Radio and a 2.1 Build then stay on the 33.4 kernels.
I know it's redundant to install CM first as it mostly gets overwritten. Again, these are the steps I took and it's what's worked for me and others. Don't skip steps, if you have any issues let me know. I also just updated the CM 5.0.7 to Final, it's not test-3 anymore.
Like I always say... ENJOY!
+1 - Worked like a charm
The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?
adamxadam said:
The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?
Click to expand...
Click to collapse
Did you wait for the radio update to finish (the picture of the box with the arrow coming out of it pointing to the android) and have it go back to the recovery screen again?
The instructions don't appear to make any mention of the radio flash & reboot. I also don't see the point of installing the Cyanogen ROM first, what's the benefit of doing this considering the majority of it gets overwritten by the FroYo /system flash anyway, and the gapps all get replaced as well. (Cyan installs nothing to the /data partition).
adamxadam said:
The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?
Click to expand...
Click to collapse
Try the tutorial again, the radio part wasn't the issue as you haven't even gotten to that step yet. I re-uploaded CM 5.0.7 to final, it's not test 3 anymore... Try again and post results please... and follow steps exactly. As far as doing CM first, it's not necessary, I just include that step because it's how I did it and it works great for me and everyone who's tried it this way.
Also, make sure you do the prerequisites first like installing the recovery
Why not just load up FRF50 straight up, why the need for the EPE54B, and CM 5.0.7?
DXL007 said:
Why not just load up FRF50 straight up, why the need for the EPE54B, and CM 5.0.7?
Click to expand...
Click to collapse
Again, this is the way I used and it worked... Also, there are 2 update.zip's floating around. 1 Is an update from 2.1 to 2.2 and one is the full update.
Better safe than sorry
Pretty basic release. This is a deodexed version of the touchwiz wifi update.zip available in this thread: http://forum.xda-developers.com/showthread.php?t=1167250
I have not changed anything else in this ROM (though I am now working on a more streamlined touchwiz ROM using this deodexed version)
So no, this ROM is not meant to improve performance or fix any bugs from the stock touchwiz update. A deodexed ROM simply makes it possible/easier for devs to create patches that can address these issues, make themes, etc.
Warning: I am not responsibile for any damage you do to your device from flashing this update. Please be careful and follow the instructions below, and use at your own risk!
md5: 5a6a04a24f7f799b1b122d9e445110b2
Uploaded 7/22/2011: http://www.multiupload.com/WTU98VP2D5
-Fixed WiFi issue (thanks to DocRambone for the fix)
-Fixed /system not being wiped properly during update
Installing:
Download and place somewhere on your /sdcard directory
Boot into CWM
Wipe Dalvik Cache
Wipe /data and /cache (you can skip this if you had flashed the r4-7/19/2011 previously)
Install this zip from sdcard
---
Rooting:
Flash su_busybox_misc-sam_tab_10.1-051511.zip using CWM / Rom Manager: http://droidbasement.com/galaxy/tools/su_busybox_misc-sam_tab_10.1-051511.zip
---
Before reporting any bugs please make sure you have followed these directions. If you are getting a boot loop you most likely missed one of the steps above.
If you are getting the "service temporarily unavailable message" you need to sign into your google account, it should go away after you do that
Have fun themeing and modding!
~Shev
Thanks to:
pershoot - for the update.zip and the rooting zip
mughalgxt - for finding and sharing the stock touchwiz update
Does this mean i am the first...
To try this.....HMMMMM - let me sleep over it.
Oh - what the heck!
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Interesting....very interesting. Might have to give this a look-see...
rvrugg90 said:
is this intended to be any less laggy or faster than other roms? Thanks for your hard worK!
Click to expand...
Click to collapse
No, this update will make it possible to create and use modified versions of the apps + framework resources contained within the touchwiz ROM (i.e create themes, etc)
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Nice work here.
xSunny said:
Damnit i just want panning and zooming working is it working on this one maybe deoxing it helped it work somebody willing to tesT?
Click to expand...
Click to collapse
Are you talking about the special tilt / pan control? Just tested that, still doesnt work, but it may be possible now to patch the problem if someone can find it (in the deodexed resources).
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Yeah i still didnt go back to stock 3g im just hoping somebody can find it in this deoxed rom but lets see
Can you pleaseeeee hook me up with the 3g touchwiz .zip??? IV looked everywhere! My tab is sooo slow with the wifi version but the 3g version, even with errors, was smoking fast! Thanks!
je2345 said:
Yeah I like the zoom feature, that's why I went back to the stock 3g touchwiz rom
Click to expand...
Click to collapse
Sent from the best phone on the planet (SGS2) running the best ROM on the planet (Cognition S2)!
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
I don't think it really matters when you flash root bro. Make sure you are using pershoots tools pack though.
roborob1969 said:
Do I need to flash root, right after flashing the ROM? I tried to flash, without rooting right after and got caught in a boot loop. Restoring right now...but would like to flash touchwiz
Click to expand...
Click to collapse
The linked root zip is optional, you don't have to flash right after, you can flash it whenever (but dont use any of the other rooting zips available for this tab, the linked one is the only compatible version). Your bootloop is probably caused by not wiping /data+/cache or the davlik cache. Follow the instructions in first post.
daddymatt said:
Can you pleaseeeee hook me up with the 3g touchwiz .zip???
Click to expand...
Click to collapse
Enjoy.
http://www.megaupload.com/?d=XBAH8X7P
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
nakedninja42 said:
Followed the steps in the first post and it bootloop on me during the anime startup. I ODIN back to stock and then tried and the same. I then ODIN KFC stock, root and installed ROM Manager and followed the OP and still bootloop...
Click to expand...
Click to collapse
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
are you sure thats the 3G version? I went to download it and my pc sees it as exactly the same as the new wifi version... thank you sooo much for it either way! good looking out!!!
SellswordShev said:
Did you try without ROM Manager the first time? If not try that first to be sure. Also provide device info please (wifi/3g/io/retail/v). I have not had any other reports of bootloops from people that were wiping data+cache+dalvik properly. You can try formatting /system (under CWM mount / storage menu option) if you are still getting this after manually doing everything through CWM at boot.
Click to expand...
Click to collapse
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
nakedninja42 said:
Wifi Retail, Locked Bootloader
I am downloading it again to make sure its nothing weird with the zip. Every time I have flashed it was CWM not in the ROM Manager. Should I try that instead?
Click to expand...
Click to collapse
No if its not working in CWM it wont work if you do it through ROM manager. Redownload and verify the md5 hash from the original post. Boot into CWM recovery, wipe everything mentioned and retry.
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
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.
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