I tried updating from the leaked 5.5.893 to this new 5.9.901 with no luck. Has anyone have any luck with this? If so how did you do it?
Throw it on the sd card, use stock recovery. What method did you use and what error are you getting?
I put it on the sd card. Tried from stock recovery and its failing at the verification. Tried to install as a zip.
Then I don't believe you're on 5.5.893. You're SURE you're not on 5.7.893? Cause if you're on 5.7.893 then you're stuck like the rest of us.
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
cellzealot said:
If you are on the leaked 5.5.893 and not the official OTA version, then it is possible that the checksums are different between the two versions and it fails the asserts in the updater-script.
The important thing to note is that the error messages are very specific and will tell you which file is failing. Then you can fix it, if at all possible, dependent on what was changed and how.
Click to expand...
Click to collapse
I thought someone checked the CRC's for the leaked vs OTA and they were identical?
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
GeoMandell said:
Not sure if anyone has seen or tried this yet, but the error I get (running 5.7.893) regards two attributes in the build.prop file. Gonna try modding them to see if the update takes afterwards.
Click to expand...
Click to collapse
Don't bother. I spent a lot of time on this last night. I went so far as to put 5.5.893 *system* on and tried to flash from that. (Obviously with boot image from 5.7.893 still). It got past the build.prop error and gave me a boot error. Meaning it fails asserting the boot image. No chance for this update to work for us I'm afraid.
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
djr4x4 said:
I am on the leaked 5.5.893. I'm on the liberty rom. Would I have to put my phone all the way back to stock? Then start from there? At one time I had restored my phoned and did the 43v3r root and my system version went from the 5.5.893 to 5.5.886. Is that my culprit right there? Even though my radio and kernel is still from 5.5.893?
Click to expand...
Click to collapse
Woa woa woa. Slow down. You're trying to apply this over a custom rom? Is that what you're saying? That definitely won't work. It has to be stock system for the version that the update is made for. So, in this case, you need stock 5.5.893. The kernel and radio are fine as a custom rom can't touch those. But you will need to restore stock 5.5.893 if you want to apply the update to get the new kernel and radio. Then you can put your rom back on. Hope that helps!
Do I need to reflash the original bionic stock ROM with RSD lite, then flash the leaked 5.5.893 and then flash to 5.9.901?
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
No don't do that. For sure don't do that as it will not work. You didn't make a backup of the stock rom when you did the 5.5.893 update before putting a custom rom on?? UGH. If that's the case and you don't have a nandroid backup of 5.5.893 then this is going to be a pain. Not impossible but will cause you some headaches. First thing's first. Go make a nandroid backup of your existing rom install. I'll see if I can put some steps together that'll get you upgraded.
---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------
cellzealot said:
If you made a nandroid backup of your clean 5.5.893 installation then restoring that would be the easiest method to get the 5.5.901 to install properly.
If you have changed anything at all in your system beyond simply rooting and mount-ext3.sh for permanent root, then the update will fail.
Click to expand...
Click to collapse
But not with RSD using the FXZ now that he's on 5.5.893, yea? That'd be...bad.
---------- Post added at 03:45 PM ---------- Previous post was at 03:38 PM ----------
1) http://rootzwiki.com/topic/5484-r3l...he-bionic-v21/page__view__findpost__p__127684
Get that, unzip it, run it, and choose option 1. That will put you back on 5.5.886 stock *system* but will not touch anything else. And will of course, will install permanent root.
2) http://www.multiupload.com/0ZEN69NGO2
Get that, throw it on the SD card, and boot to stock recovery. Flash it.
3) Now you are ready to try flashing 5.9.901 again
4) NANDROID THAT THING
Then restore your custom rom and you should be good to go. CZ, did I miss anything?
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
djr4x4 said:
I've lost my nandroids backup. . I have made a new nandroid backup of this current setup incase I screw something up.. I am unable to restore back to fully stock at this time which I'm rather upset about.. Am I screwed?
Click to expand...
Click to collapse
Make sure you have a nandroid of your current (custom, apparently) rom. Then do the steps I outlined above.
Just to reiterate, this will not work for those of us on 5.7.893, correct?
GeoMandell said:
Just to reiterate, this will not work for those of us on 5.7.893, correct?
Click to expand...
Click to collapse
No it will not. Nothing will at this point in time.
awesome. It worked. I am now 5.9.901!!!! Thanks for the help... And I kept root!!!
Grumble grumble lucky jerk... J/K I'm sincerely glad that worked for you. *NANDROID*.
WHAT?!!
I am on 5.7.893
You guys mean to tell me that even if I nandroid back, to my clean back-up of 5.5.893... This 901 update will still fail??!!
Is it checking the kernel also? I have a nandroid that is completely stock so if I flash back to that this 901 update should go unless it checks the kernel version too.
Related
tried to restore stock with one click and it wont flash the boot.img . Said something like INFOPreinstallaton error. Cant root either. What to do?
Well, first off, your question is in the wrong thread...it will most likely be moved soon...
second....did you update to .893?
Edit: if so and your bootlooped.... this is the one you want http://rootzwiki.com/topic/7801-roo...v10-linuxwindows-get-root-after-893-ota-oops/
ill move my questions. Sorry! Yes and no. Did forever root, flashed update, flashed liberty rom. Then i noticed the version was back to 886 so i tried the oneclick instead of backup and thats when the error for boot.img showed but everything else flashed. My phone is running but i cant root it shows an error as well. thanks for the reply.
antonioj78 said:
ill move my questions. Sorry! Yes and no. Did forever root, flashed update, flashed liberty rom. Then i noticed the version was back to 886 so i tried the oneclick instead of backup and thats when the error for boot.img showed but everything else flashed. My phone is running but i cant root it shows an error as well. thanks for the reply.
Click to expand...
Click to collapse
when you flashed liberty, you flashed .886 system, but the .893 kernel and radio remained. not sure which one click you used to lose root, are you sure you lost root? if, so.... this is just my opinion and what i would do....I would run th3orys and dhackers fix above and flash 2.1 when it comes out.
i will try that. Thanks for the info.
So I rooted, using one click method, backed up stock .886 and installed blurry 2.0, based on .893. I know now that the kernal and radios are changed from .886. Does this render my stock back up of .886 useless? Also, what if the OTA update coming in November is actually different than .893, will I be able to update to what ever that may be?
stevessvt said:
So I rooted, backed up stock .886 and installed blurry 2.0, based on .893. I know now that the kernal and radios are changed from .886. Does this render my stock back up of .886 useless? Also, what if the OTA update coming in November is actually different than .893, will I be able to what ever that may be?
Click to expand...
Click to collapse
I would take an educated guess and say yes your 886 backups are trash, but don't take my word on that.
If you made those backups through ROM Manager, you're in luck.
https://market.android.com/details?...wxLDEsImNvbS5oYW5keWFuZHkuYXBwZXh0cmFjdG9yIl0
That app can extract apps, contacts, and SMS/MMS from Nandroid backups done through ROM Manager.
Tivo7 said:
I would take an educated guess and say yes your 886 backups are trash, but don't take my word on that.
If you made those backups through ROM Manager, you're in luck.
https://market.android.com/details?...wxLDEsImNvbS5oYW5keWFuZHkuYXBwZXh0cmFjdG9yIl0
That app can extract apps, contacts, and SMS/MMS from Nandroid backups done through ROM Manager.
Click to expand...
Click to collapse
Im loving blurry just fine and see no reason to go back, but I just hope I didnt cut off my nose to spite my face in regards to future updates.
So I did a data reset in bootstrap, and reinstalled my stock .886 back up, and it installed fine. Rebooted and everything worked as it should.
stevessvt said:
So I did a data reset in bootstrap, and reinstalled my stock .886 back up, and it installed fine. Rebooted and everything worked as it should.
Click to expand...
Click to collapse
Awesome.
10char
If you just install 2.0 over stock, you do not get the .893 radio or kernal. You only get the system. To get the radio and kernal you need to to go back to stock, do the permanent root method, install the cheesecake app, then update to .893 through cheesecake, and then flash 2.0. If at that point you flash .886 again, you would have the .893 radio and kernal, and the .886 system. Because the bootloader is locked, you cannot flash a new kernal or radio via cwm.
Sooooo by flashing blurr3y 2.0 in cwm I never got .893 radio/kernel?
stevessvt said:
Sooooo by flashing blurr3y 2.0 in cwm I never got .893 radio/kernel?
Click to expand...
Click to collapse
Correct.
Sent from my DROID BIONIC using xda premium
lawtalking said:
If you just install 2.0 over stock, you do not get the .893 radio or kernal. You only get the system. To get the radio and kernal you need to to go back to stock, do the permanent root method, install the cheesecake app, then update to .893 through cheesecake, and then flash 2.0. If at that point you flash .886 again, you would have the .893 radio and kernal, and the .886 system. Because the bootloader is locked, you cannot flash a new kernal or radio via cwm.
Click to expand...
Click to collapse
Following this will do the trick.
http://forum.xda-developers.com/showthread.php?t=1320414
Tivo7 said:
Following this will do the trick.
http://forum.xda-developers.com/showthread.php?t=1320414
Click to expand...
Click to collapse
Thanks for putting that guide up Tivo. I figure when the next update comes out, you might have to be back with the .886 and I was wondering whether there was a way to downgrade the radio and kernal to stock after going to .893.
lawtalking said:
Thanks for putting that guide up Tivo. I figure when the next update comes out, you might have to be back with the .886 and I was wondering whether there was a way to downgrade the radio and kernal to stock after going to .893.
Click to expand...
Click to collapse
The next update IS 893, I've already gotten confirmation of that.
Rootable?
Tivo, will the new bionics being shipped with .893 be rootable? Will they need to be rolled back per the method you detailed here ?
anarchy4sale said:
Tivo, will the new bionics being shipped with .893 be rootable? Will they need to be rolled back per the method you detailed here ?
Click to expand...
Click to collapse
We will have to wait and see what root methods work after the ota is released. Painfully to wait, I know.
Sent from my DROID BIONIC using xda premium
It will revert you back to system 886, but your kernel/radio will stay with whatever update you installed. I currently have a hybrid going on. 5.5.893 system and 5.6.893 kernel.
Sent from my DROID BIONIC using xda premium
Hello
I have jb 4.1 with safestrap.
I accidentaly updated SU binaries on the Stock rom. Now my root is gone, but I can flash roms just fine. I have old version safestrap where you cant install on stock rom(even roms that have root). But I want root on the stock rom.
I think I can Restore to it.
If any of you can post the safestrap Backup image of a clean rooted install of stock 4.1 that is rooted, backed up from the stock rom slot, I'd be very happy.
Thanks.
This has been solved, read last post.
I'll try modifying a backup of my own... can you guys tell me what version of SuperUser binary is good for root?
If you can post your system/xbin/su or system/bin/su file and have working root on 4.1, that'll help too.
Re: Can someone post a Safestrap 4.1 Backup
If you have a backup, why don't you flash that?
Sent from my phone.
---------- Post added at 05:37 PM ---------- Previous post was at 05:22 PM ----------
My backup has a modified build.Prop and probably a few extra apps added into the system/app folder
I don't mind uploading it, I just don't know the best site to upload it to.
Sent from my phone.
I dont have a backup, thats the problem. If you have a fast connect you can upload the whole, but only if you had it as stock_rom slot.
Looking for file share site.
https://www.wetransfer.com/
Try this and click the share button, then the link button. You dont need emails that way. Also it didnt work in firefox for me.
EDIT:
OK, he sent it, I'll try in a few.
EDIT 2:
IT WORKED!!!
so what youre saying is you flashed back ICS with safestrap?
can i get this ics rom?
aarons6 said:
so what youre saying is you flashed back ICS with safestrap?
can i get this ics rom?
Click to expand...
Click to collapse
No, I restored a rooted JB rom back because I lost it on stock JB rom.
He had an old version of safestrap that doesn't allow flashing on the stock, or safe, slot, so he was unable to simply flash a superuser zip.
But, by restoring a previously rooted safestrap system backup, root was regained.
Sent from my phone.
Is AT&T stock ROM image still available?
Markyzz said:
He had an old version of safestrap that doesn't allow flashing on the stock, or safe, slot, so he was unable to simply flash a superuser zip.
But, by restoring a previously rooted safestrap system backup, root was regained.
Sent from my phone.
Click to expand...
Click to collapse
Hi, saw this thread as a search result and while I think my issue is similar, I'm not sure, so if I need to post a new thread, I'd appreciate knowing that.
I have an Atrix HD with Batakang in slot 1 and of course the stock AT&T ROM in, well, the Stock slot. I have Safestrap 3.11. I wanted to unlock the phone for int'l use, and it simply would not give me the prompt to enter the unlock code (said "Invalid SIM" or something like that), so I left it with an AT&T dealer because the process should have been simple, but wasn't.
They couldn't do it either, but when I got the phone back, the entire 8GB ROM space was wiped! Batakang was gone, the Stock slot is empty, and unfortunately, the Safestrap backup I made of Stock (and left on the internal SD) was gone too!
I did have a Batakang backup which restored fine, I entered the unlock code OK in it (I assume that worked - there was no confirmation message), but still have an empty AT&T stock slot.
What ROM images I've found are not compatible with Safestrap, so what I'm looking for is either a Safestrap backup or a zip installer compatible with Safestrap, or any other suggestions appreciated! Thanks!
So its been awhile since I flashed a ROM to my BIONIC. That was back before ICS was even released for the BIONIC. So I started looking at updating to one of the more stable ROMS that has way better performance that this stock one. Currently I have 6.7.232 on my phone and I would like advice on which ROMs are best for this device. I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.
Any help out there?? Thanks.
HarielA4 said:
I have looked into some such as Gameblur, Raging Bionic, and Icarus HD. Thus far I havent really decided on one but I have noticed that some of them are on Jelly Bean. I am not sure if I have to return to the OTA path to update to any of these. I also have Safestrap 3.11 installed. Any advice would be appreciated. thanks.
Click to expand...
Click to collapse
Well Gameblur and Raging Bionic both require one to be on the 98.72.22 Moto 4.1.2 Jellybean update. Incarus HD however is ICS base and can be flashed with your current setup.
If you are destine to update your stock side I would first prep what you currently have on there right now. See this HERE for getting stuff ready.
I would backup anything on the internal storage before hand and make sure that you have a full battery.
You will find the proper FXZ files HERE. If you are on 6.7.2-223 update then use the one for 4.0.4. It would be easier to root again through the update process. After you have completed the restore processes and root through the HOB. Make sure you have VooDoo Root Keeper installed on your phone to back up Root and to disable Root. Then with a good Data connection you are going to take the update Via OTA. Once the update is complete and you are fully booted up. Use VooDoo to restore your Root and test using root explore or NoFrills CPU.
nobe1976 said:
See this HERE for getting stuff ready.
Click to expand...
Click to collapse
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?
HarielA4 said:
The link provided there has a post from the OP that states House of Bionic is discontinued and to use House of Moto. Should I do that?
Click to expand...
Click to collapse
You can try using the House of Moto stuff also depending on what you feel more comfortable on using. The HOM was desighned to have one interface for all Moto devices instead of each having its own individual setup. I would still use HOB for your purpose only because I don't know if he added in the script to root the device, which was made for ICS versions not JB hence the discontinued portion of it.
HarielA4 said:
Secondly I havent for sure decided which Rom I will be moving to. I feel that the interface I have been using is kinda laggy. I installed Next launcher to see if that made a difference and it was more responsive but still my system memory usage skyrockets after a couple hours and sometimes the only way to resolve it is to restart the device. Any recommendations as to which Rom I should move to?
Click to expand...
Click to collapse
I have tested and played around with a lot of different ROMs and tweaks to find the one that I am ultimately satisfied with. Flying Jelly, well the name speaks for itself, Rage, and GameBlur (which I had minor help in) all work fine for there purpose.. One must pick and choose which one suits there purpose. So my suggestion would be to install SafeStrap 3.60, which is the latest updated one, and create a few slots and run each the same as you would Stock or any other firmware to measure which one suits your needs.....
In a previous post you wrote "If you are on 6.7.2-223 update then use the one for 4.0.4.". I went to the FXZ site and it shows that the 4.04 rom has version 6.7.223 on it already. I already have root. Why would I need to install the same version again and reinstall root to get on the OTA. I just want to make sure I understand this to avoid making mistakes. Thanks.
Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..
nobe1976 said:
Then if you feel confedent that all will go well then just install Voodoo to backup and disable root. Take the OTA update and see if it will install. The most that will happen is that if it detects that something is missing from the current firmware you have the installation process will fail and reboot back into what you currently have. At that point you will have to FXZ your stock back to the way it was installed originally, root, then backup root and disable, then take the OTA. ICS is way easier to root then JB. I have kept Root before via OTA when I got it, so I know it Voodoo will keep the backup and install it..
Click to expand...
Click to collapse
I think I miscommunicated what my question was. The instructions say to install the FXZ for the 4.0.4 that has the same version of Android OS that is currently installed. the further instructions say to install the OTA from verizon but everytime I check for an update nothing shows up on my phone. Where else can I get the OTA?
In addition I want to know what I should do about safestrap. Should I remove it before installing the OTA or is it fine to leave as is when I go to install the OTA?
OK... If you cannot even get Big Red to send you the update. You can fxz the update, but at that point you will loose root, but have the option to keep your current data. Go see House of Moto or House of Bionic over at droidrazr.com
As far as Safestrap I would just uninstall recovery through the app the reboot so it clears out before the fxz process.
$3π+ £®m€ ×X× BiOπI¢ oπ $ø|/|£ťhïñğ ¢ű$ț¤|/|
fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).
mikemikemikexxx said:
fyi I think he took House of Bionic down, didn't see a link. I can however attest that House of Moto worked perfectly fine. Flashed fresh .232 and VZW sent me the OTA (I tried voodoo rootkeeper before updating). I did lose root despite following all of the steps. To get it back your best bet is to boot up a live Ubuntu disc. I tried the VM that someone compiled but it kept failing.
PS: nobe1976, how the hell did you fit 3 ROMS on your phone? I can only fit one ROM (besides obviously stock). Wish we could install ROMs through safestrap to SD (internal or external).
Click to expand...
Click to collapse
This is the Exploit I have been using the past few days.. HERE.
However Samuri didn't remove the HOB site, He just doesn't maintain it as much since HOM. Here is the LINK to that f needed.
I'll try to keep this concise. I've been rooted since I first bought this phone over 3 years ago, I received the 2.3.6 OTA Bell update from 2.3.4, rooted again and it's been like that until a month ago.
I successfully installed SafeStrap, made two backups, and installed CM9 onto a slot, it didn't work well but it booted on the first try. I then tried MiniMoto 2.3.4 which worked perfectly, then a 4.0.4 "Motoblur" build in which enough things work to get by. All of these I installed using SafeStrap and they booted fine on the first try. They've even held up to me modifying them.
If I disable SafeStrap my stock 2.3.6 rom boots perfectly. If I try to restore my backup to a SafeStrap slot and boot it, it bootloops and freezes every time. I backed up my stock reset rom and tried to restore that, same result. I also tried the "Bell 2.3.6 Optimized" build I found here, which should be my stock rom only cleaned up, same result.
I've cleared caches over and over, tried copying the build.prop from my stock rom (although I'm not certain I did it correctly) and at this point I'm at a loss. I've searched and read all that I could find, but it's my phone's own default rom that I can't get to boot... Any ideas would be appreciated.
Thanks!
-Kurt
Reference:
CM9
[XT860][CM9] Working 3G data... finally!
Minimoto 2.3.4
[ROM - Stock-based] Minimoto v1.7 XT862/XT860- Less is more.
Motoblur 4.0.4
[ROM]Motoblur + Android 4.0.4 -- [Development Discontinued]
Motoblur 2.3.6 Optimized
[ROM]Stock Motoblur 2.3.6 rooted, deodexed, zipaligned, optimized[xt860]CWM
Bob_760 said:
I'll try to keep this concise. I've been rooted since I first bought this phone over 3 years ago, I received the 2.3.6 OTA Bell update from 2.3.4, rooted again and it's been like that until a month ago.
I successfully installed SafeStrap, made two backups, and installed CM9 onto a slot, it didn't work well but it booted on the first try. I then tried MiniMoto 2.3.4 which worked perfectly, then a 4.0.4 "Motoblur" build in which enough things work to get by. All of these I installed using SafeStrap and they booted fine on the first try. They've even held up to me modifying them.
If I disable SafeStrap my stock 2.3.6 rom boots perfectly. If I try to restore my backup to a SafeStrap slot and boot it, it bootloops and freezes every time. I backed up my stock reset rom and tried to restore that, same result. I also tried the "Bell 2.3.6 Optimized" build I found here, which should be my stock rom only cleaned up, same result.
I've cleared caches over and over, tried copying the build.prop from my stock rom (although I'm not certain I did it correctly) and at this point I'm at a loss. I've searched and read all that I could find, but it's my phone's own default rom that I can't get to boot... Any ideas would be appreciated.
Thanks!
-Kurt
Reference:
CM9
[XT860][CM9] Working 3G data... finally!
Minimoto 2.3.4
[ROM - Stock-based] Minimoto v1.7 XT862/XT860- Less is more.
Motoblur 4.0.4
[ROM]Motoblur + Android 4.0.4 -- [Development Discontinued]
Motoblur 2.3.6 Optimized
[ROM]Stock Motoblur 2.3.6 rooted, deodexed, zipaligned, optimized[xt860]CWM
Click to expand...
Click to collapse
you are trying to restore a stock rom slot backup, to a rom slot?I think that some modification is needed, maybe as simple as adding a file.
---------- Post added at 07:07 PM ---------- Previous post was at 06:58 PM ----------
could try an advanced restore, and just restore data over minimoto, wipe caches before booting.
---------- Post added at 07:24 PM ---------- Previous post was at 07:07 PM ----------
do you want the data or the system restored?
backups and rom.zips work differently, don't think you can restore a stock system backup on a rom slot
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
when stock rom slot is selected to boot, the safestrap's boot menu always says "disabled", that is how it works
sd_shadow said:
you are trying to restore a stock rom slot backup, to a rom slot?I think that some modification is needed, maybe as simple as adding a file.
could try an advanced restore, and just restore data over minimoto, wipe caches before booting.
do you want the data or the system restored?
backups and rom.zips work differently, don't think you can restore a stock system backup on a rom slot
when stock rom slot is selected to boot, the safestrap's boot menu always says "disabled", that is how it works
Click to expand...
Click to collapse
As separate tasks, I'd like to...
1. Restore and boot my backup and go into it to check some settings. I guess the easiest way would be to restore it back onto my stock rom? I was under the impression I could put it in a SS rom slot. If that were relatively simple I think I'd rather it in a rom slot. (adding a file?)
2. Install the Motoblur 2.3.6 Optimized rom to a SS rom slot and get it to boot.
I understand safestrap is "disabled" when you boot the stock rom, I was just pointing out that my stock 2.3.6 rom works fine, I just can't boot the backups or "optimized" versions of it.
I tried to install Motoblur 2.3.6 Optimized over top of Minimoto to no avail, but I'm not sure if I did it correctly, I'm going to try that again I guess.
Thanks
-Kurt
your Bell 2.3.6 Optimized.zip is 176.69 MB?
sd_shadow said:
your Bell 2.3.6 Optimized.zip is 176.69 MB?
Click to expand...
Click to collapse
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Bob_760 said:
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Click to expand...
Click to collapse
check the posted md5 checksum, thats how you verify the file is the same
https://sites.google.com/site/sdshadowscollection/home/hash-checksums
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
I just downloaded from the mediafire link, and uploaded it to DevHost, but didn't try it.
Bob_760 said:
Yeah, I got it from that Mediafire link. I see you uploaded one, I'll give it a shot but they appear to be identical.
Click to expand...
Click to collapse
MediaFire file was not safestrap ready
see http://forum.xda-developers.com/showpost.php?p=55372958&postcount=95
sd_shadow said:
MediaFire file was not safestrap ready
see http://forum.xda-developers.com/showpost.php?p=55372958&postcount=95
Click to expand...
Click to collapse
I thought that rootfs folder was the key, but i had only gotten that far, i didn't know how to go about adding it, i made a zip that looked the part but obvously i had no idea what i was doing xD
md5 checks out, I'll try that and report back. Thanks so much for the help!
Bob_760 said:
I thought that rootfs folder was the key, but i had only gotten that far, i didn't know how to go about adding it, i made a zip that looked the part but obvously i had no idea what i was doing xD
md5 checks out, I'll try that and report back. Thanks so much for the help!
Click to expand...
Click to collapse
the trick is added to the zip without unzipping
I use 7zip or winrar otherwise you need a zip signing program
sd_shadow said:
the trick is added to the zip without unzipping
I use 7zip or winrar otherwise you need a zip signing program
Click to expand...
Click to collapse
I'd pulled the folder from the minimoto rom and tried to make a zip that was just the folder (in the correct place in the tree) thinking I could make a "patch" but it failed when I tried to "install" it. I had even added the folder to the motoblur rom zip using winrar but I hadn't tried installing it yet. I assumed it wouldn't work since I didn't really know what I was doing...
I installed your uploaded motoblur safestrap rom and it worked perfectly first go! It took forever to boot but I'm assuming its setting things up. I was even able to restore the data from my backup and things look good so far! Well, to be honest things are painfully slow right now, but hey, this phone barely worked when I backed it up, so I was sorta expecting this. Now I at least have a good reference for how I had things set up.