Related
So I was trying to restore back to my stock ROM backup using the boot strap recovery. There weren't any errors during the process of restoring the image but when it was time to boot the phone up it would stay in a bootloop.
I have tried factory reset with the power button and volume buttons but it'd go straight back to the loop.
I am trying really hard to understand this whole adb thing with the sdk program but I have no idea how to use it.
Can anyone please help this noob?
Return to stock - Windows.
FAQ sticky in the Bionic Development forum.
Thanks for the reply. I'll try this out when I come home from work.
Also, I reactivated my droid x until then. Will I need to go to Verizon for a new sim card for my bionic once I can start it up again?
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
I believe you may have to go for a new SIM card. The way the Verizon explained it to me when I returned my Charge was when you deactivate from a 4G to 3G only phone, that SIM is lost. However, 4G to 4G is fine.
Wouldn't hurt to try, but a good possibility you will have to.
Sent from my DROID BIONIC using xda premium
idefiler6 said:
I don't think so, but I am not sure. Have not bootlooped yet myself or had to FXZ.
Click to expand...
Click to collapse
About 2 hours after I said this, I bootlooped. Good thing this FXZ method works!!
haha yeah with all the new roms u cant help but to explore.
btw after 5 FAILED flashes I tried one more time with rsdlite and it finally worked!
It took about 20-25 minutes for the whole process to fully boot up my phone but I am very happy and thankful for the people on this forum.
The weird thing is that when it booted up... it booted up to an old restore of UNL3ASH3D. confused but im happy its fully functioning.
You won't need a new SIM card. I did an FXZ restore after I rooted my phone, unrooted it (didn't need to have it rooted because there were no ROMs and no CWM yet) and it wouldn't let me root again so I flashed to stock and it rooted just fine. You will need to flash the radio again though (or at least I did after installing DroidTh3ory's ROM because it kept showing 3G in spots I know i had 4G, worked fine after I flashed).
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
First off, I have an XT862 not the XT860. The hijack is a 2nd init hijack. Safestrap does this hijack itself as opposed to with bootstrap where whatever ROM you flash has to do the hijack. Safestrap also as you mentioned uses /preinstall to store /system of the ROM you flash. This means that nothing other than safestrap itself touches your stock /system. This allows safestrap to protect itself so you can always get back to recovery even if there is a bad flash it can't overwrite the hijack and recovery so you can try again.
I also don't remember seeing much of problems with safestrap itself other than a partition size problem. I think I remember seeing that some update took care of that problem. I have seen people having more problems with ROMs on the XT860 than other versions of the phone.
danifunker said:
I think I understand how safestrap works (it installs some kind of hijack to boot /preinstall instead of booting /system) but I have been reading a number of users who have bricked their phone...
I basically have the SafeStrap install screen up, but am hesitant to do this...
Just a few questions before I take the plunge
1) Why are so many users having problems with safesrap? I download the Droid3 version 1.08 for use on my Bell Motorola XT860 4G
2) What exactly does safestrap do in the boot loading sequence? If this is not public knowledge (and might be worked out "against" please, no harm, I'm just wondering, so if I could get an idea as how the hijack works, either in the thread or PM that would help greatly)
3) If you restore the original system and disable the hijack, will that really bring me back to complete original stock? What if they patch the boot partition as they did last time?
Thanks for all your help guys! I know a lot of you have been using custom roms, I really want to load up ICS on here, and it's almost ready for prime-time so I just want to be prepared!
Click to expand...
Click to collapse
First off, the most common problem I have seen people have with safestrap is not understanding what it does and even more common is not knowing how to use it, basically a lot of user error. The previous poster summed up pretty well how it works. Finally, uninstalling safestrap will NOT bring you back to original stock, it will remove itself and the secondary ROM it allowed you to install. Since you have to be rooted to even install it, if you uninstall it you will still be rooted, not stock.
Just so you are clear, you can have whatever ROM you want on your phone BEFORE installing Safestrap and this will become the Safe system by default. You will no longer be able to change this ROM as long as Safestrap is installed. Instead, it allows you to put another ROM, basically a dual-boot, in addition to the original rom you have. Now you have a Safe system and a Non safe system. The Non safe system is the only one Safestrap will allow you to change (and brick for that matter). So if/when you install a ROM that boot loops or crashes, you simply can revert back to your safe system and now your phone works again, neat huh?
AFAIK, he does have the XT860, since the XT862 is the Verizon Droid 3 (3G, not Bell Canada 4G). Also, using it on my 862, I have not been able to brick it. If flashing the experimental system fails, you can just reboot into the Safestrap menu and flash something new. I don't see why it wouldn't work on the 860, as all it does it modify the booting. Any issues would most likely be caused by a ROM flashing issue, not safestrap.
I took the plunge this afternoon... Installed SafeStrap and CM9 nightly on my device... Not sure if everything is working just yet, but will be doing testing throughout the day
No problems were reported with the installation or instructions, so that's great. Thanks a lot!
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Thiago AmP said:
I'm using a XT860 (Brazilian Vivo, but I'm not sure if it's 4G - LTE - compatible, I know that it works with 3.5G).
I have Safestrap 3.0.5 installed and I'm using all the 4 slots (MavROM, Minimoto, CM9 e CM10). All of then runs well (with their particular issues), none of them caused any trouble on the phone.
Click to expand...
Click to collapse
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Endoroid said:
None of the d3 variants are LTE capable
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I realize that before reviewing its radio specs.
Munckster said:
Same here. I'm using it on a Brazilian TIM, no problems at all. I have two active slots( Stock, Gummy 0.90) and two for testing.
It is in fact the best recovery that I've used, so far.
Click to expand...
Click to collapse
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Thiago AmP said:
Yeah, I realize that before reviewing its radio specs.
@Munckster
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
I'm very newbie at linux and Android and I'm doing all that by reading (a lot). I'd apreciate if someone could tell how to deal with this problem.
Click to expand...
Click to collapse
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Endoroid said:
Try shutting the phone off and powering up while holding m, then using vol down select bp tools from the list that appears, and confirm with vol up.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I've already tried it, but without success... I'll keep searching what to do in this situation...
Thiago AmP said:
Actually, after trying to acess a SD Card partition with Link2SD, I lost acess to Recovery. I'm stuck on the stock ROM (root keeps on, but SafeStrap 3.05 doesn't work).
Installed Titanium Backup to keep my data safe, but it isn't working too. I'm going to reinstall it later.
I'm afraid that I'll have to uninstall all my root apps, unroot the phone and do all the process again...
Click to expand...
Click to collapse
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
doogald said:
Unrooting seems like overkill. If you are "stuck" on stock, I would just start the Safestrap app. Click the button to uninstall recovery and restart the phone. Then open Safestrap again, click the button to install recovery, and restart the phone. Hopefully the Safestrap menu will show and you can then activate recovery.
So long as you do not erase anything on the internal storage, your slots should still be there.
Click to expand...
Click to collapse
I've tried it several times before I came with the idea of unroot my phone and redo the process. Here is my dicoveries http://forum.xda-developers.com/showthread.php?t=2082292
I know that it's obvious, but I guess that just few people knew that it would work.
SafeStrap problems
Odd problem, I can't get the menu button to work. In order to get back to my "safe" rom I have to start safestrap,and select uninstall recovery.
Then reboot, and it will bring up my "Safe" rom. If I then go back to SafeStrap, and re-install the recovery, and reboot, it will again bring up SafeStrap, but if I hit Menu, it doesnt' bring up any options it again boots up my non-safe ROM (minimoto 1.6)
Anyone have any ideas...I guess I can try to remove the safestrap directory on the sdcard after I uninstall the recover, and then try to reinstall the App, and try all over again?
I would be ok with this if it wasn't almost every time the phone is left alone.
i thought maybe installing CM would help but it still does it, went back to stock firmware (S5830DTLKI4) with no resolution.
It appeared to only be doing it when it is put to sleep, but after i unlocked it and tried to send a text with my Bell Canada sim card the phone restarted again.
It certainly isnt a SoD, because it is turning itself back on.
wifi is off, GPS is off, Bluetooth is off, and it is doing this on a 100% stock install; no market apps installed, no google account even linked.
so it appears to be restarting when i let it go to sleep, and when i try and send a text using a non-Koodo sim card. (although i dont know the effects with a Koodo sim; never had one)
I went to samfirmware and downloaded a md5 for the UK network Orange, but it didnt fix anything as far as i know, i didnt unlock it but it was still restarting itself.
Im wondering is this a software issue (if so, what is happening and is there a way to fix it?), or is this a hardware issue (perhaps there is a faulty capacitor somewhere on the board that isnt filtering voltage spikes and causing the device to reboot because of that)?
i couldn't find any references to this problem ever really being addressed.
help would be greatly appreciated.
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Narwhal73 said:
The stock Samsung firmware for a Koodo S5830D is unstable, often when I was using it I would get reboots and freezing and a NO SIM CARD error constantly. If you have it rooted and want to install a custom ROM that won't reboot itself, I would recommend taking a look at CM9.1 RC4.1 by Wayland_ACE. I have never experienced a random reboot on that ROM. http://forum.xda-developers.com/showthread.php?t=1868121
Although of course you have to choose the right ROM for you. If you want to stay on Gingerbread, the official CM ROM (or an unofficial version) for the Ace should do the trick. If you don't care as much about stability experiment!
If the firmware is unstable (as it is with Koodo's stock ROM) it won't matter if it is locked or unlocked, if you want stability, change your ROM.
Click to expand...
Click to collapse
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
blueblitzpup said:
i tried installing the rom you linked to but im still getting the reboot problem; is there something im doing wrong?
i wiped the user data, cleared the cache, and wiped dalvik, then installed the rom you linked, using clockwork 5.0.2.6
however it still seems to want to reboot, what is going on here?
Click to expand...
Click to collapse
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Narwhal73 said:
In CWM go into mounts and storage> mount /data, /system, /sdcard. Should fix bootloop.
Click to expand...
Click to collapse
its not a bootloop though, it's booting into CM and then once the screen goes to sleep the phone restarts itself, just like it did on the stock rom.
i already tried mounting data, system and sdcard, but it didnt help any.
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Venomous Viper 119 said:
Last resort... After flashing via odin, reboot into recovery & do a factory reset. If the problem persists, stop posting here & rush to service centre with the unrooted stock rom on your phone.
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
racer_25 said:
i was hoping id get a better answer than that, but ok then.
ive always hit factory reset and clear cache before using a stock rom, else it will boot loop.
i suppose i'll reload the stock firmware and take it in to the nearest mobile center, i dont know how much good itll do though, the phone is from anther carrier and i got no warranty papers when i bought it off a friend.
Click to expand...
Click to collapse
Since you don't have the warranty, you'll have to pay for the service anyway. Just be sure that the phone serial no. that's on the label after taking out the battery is intact & you are all fine to get a clean service. There's nothing much you can do by yourself as it doesn't appear to be a software problem. But it might quite happen b'coz of a faulty battery. My friend's galaxy y had the issue & a replacement killed it. So may be it with you. Anyways, before buying you can try it out with your friend's battery & hope to see if the issue is solved & then go buy one. If this doesn't help, head for service as said earlier.
Sent from my GT-S5830 using xda premium
Just a head up guys. Official Ice Cream Sandwich came out for Lg optimus 3d, and you can easily get it on your Thrill by using Lg Flash tool found here <http://forum.xda-developers.com/showthread.php?t=1491870>
kdz file is here <http://forum.xda-developers.com/showthread.php?t=2185406> have fun with ice cream sandwich!
ICS
Did you flash this for the thrill? Any extra steps to get it fully working on the thrill?
All you have to do is change the kdz file name to similar formats like other ones
Sent from my LG-P920 using xda app-developers app
ICS
I got it flashed and it works great. Everything is fully functional on the thrill so far that I tried. It is a nice change over GB for sure. If anyone is curious how to flash this, here was my method...
1.) Get the KDZ file from here (http://www.android-files.de/P920V28B_00.kdz) and rename it to V28B_00.kdz.
2.) On this page (http://forum.xda-developers.com/showthread.php?t=1491870) go down to number 3 and set up Lg Flash Tool EXACTLY how it says.
3.) Select the renamed kdz file you just downloaded in the lg flash tool program and let it do it's thing.
4.) On my first bootup it stayed on the bootlogo forever and just would not start up so save yourself some time and do a factory data reset before your first bootup and it will load up fine. The proper way to do a factory hard reset after flashing is to hold VOL DOWN + PWR till it vibrates and it will prompt you to press the power button twice to reset.
Everyone enjoy ICS on their Lg Thrills!
thanks so much!
I am running v20p stock, rooted and unlocked.
I suppose I can directly flash the renamed ics kdz?
And my thrill will be not rooted afyerwards, but still stays unlocked?
Sent from my LG-P925 using xda app-developers app
As long as you follow all the steps above it will flash with no issues. Root and recovery are lost but I think there is a method to get both of them already. I will try to root and recovery later today. As far as staying unlocked after flashing, I am using straight talk so I didn't have to unlock. Hopefully someone else can help you out on that one.
Sent from my LG-P920 using xda app-developers app
ktan.us said:
thanks so much!
I am running v20p stock, rooted and unlocked.
I suppose I can directly flash the renamed ics kdz?
And my thrill will be not rooted afyerwards, but still stays unlocked?
Sent from my LG-P925 using xda app-developers app
Click to expand...
Click to collapse
just look in the optimus 3d thread everything you need is there i wouldnt even bother lookimg in the thrill thread anymore
at&t released ics today for thrill
Sent from my SAMSUNG-SGH-I747 using xda premium
kornklown69 said:
at&t released ics today for thrill
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Wow, I had given up hope. I will try it out since the ported ICS I've been on has some lingering issues with MMS and camera.
kornklown69 said:
at&t released ics today for thrill
Click to expand...
Click to collapse
Does that mean the "Software Update" on a stock GB Thrill would install ICS?
Or maybe boot it into "Emergency Mode" (or whatever it is) and using the official LG Tool would work to get ICS without having to do all the smallsrv stuff?
I guess what I'm really asking is, if AT&T officially released ICS, isn't there an easier way to install it?
If you are on stock maybe you can install using the LG Mobile Support Tool. Trying to use that from my ported ICS has messed my phone up though. I'll have to try to rebuild it tonight, hopefully just using the Flash Tool to flash the bin and fls.
I flashed the Korean ICS, hated the bugs, and reverted to GB.
Trying to use the LGMobile Support Tool to install official ICS and it fails. So I guess I'll have to flash the kdz manually.
The Mobile Support Tool appeared to be working for me, until it tried to reboot and I got an "Encryption Unsuccessful" screen.
Now I've used the bin and fls from here - http://forum.xda-developers.com/showthread.php?t=2198069
After flashing the above with LGFlashTool, I still booted into the "Encryption Unsuccessful" screen, but powered down by long-pressing Power, then turning back on into factory reset mode with Volume down + Power. Following the reset, I appear to be running okay now.
Edit: Nevermind, having an issue , the phone won't work with either of the microSDs I have around. First it's saying they need to be formatted so I attempt that. Then it says the card is damaged.
osoryw diforder
ewtdr said:
The Mobile Support Tool appeared to be working for me, until it tried to reboot and I got an "Encryption Unsuccessful" screen.
Now I've used the bin and fls from here - http://forum.xda-developers.com/showthread.php?t=2198069
After flashing the above with LGFlashTool, I still booted into the "Encryption Unsuccessful" screen, but powered down by long-pressing Power, then turning back on into factory reset mode with Volume down + Power. Following the reset, I appear to be running okay now.
Edit: Nevermind, having an issue , the phone won't work with either of the microSDs I have around. First it's saying they need to be formatted so I attempt that. Then it says the card is damaged.
Click to expand...
Click to collapse
I had the same problem. You need to go to settings - storage and clear both memories. After that, everything is going to be ok. Do you know how to root this official ICS version? (Already tried the adb and unlock root methods to no avail)
Jcman8309 said:
I had the same problem. You need to go to settings - storage and clear both memories. After that, everything is going to be ok. Do you know how to root this official ICS version? (Already tried the adb and unlock root methods to no avail)
Click to expand...
Click to collapse
Thanks! I just stumbled into this and was coming to add the fix too! Both cards back !
I was going to attempt this method for root, but haven't tried yet - http://forum.xda-developers.com/showpost.php?p=39338374&postcount=3
I got the KDZ flashed. Running Official unrooted AT&T ICS now.
However, it seems I didn't do a factory reset and didn't NEED to. It's running just fun.
My system ROM is 619MB with 7.38MB free.
I'm wondering if that's normal... That's going to make some things pretty tough. (Guessing unsintalling Gulliver's Travels and that other crap will help)
I did the reset. My system memory is showing 102 MB of Apps (I installed a handful of things already), and 770 MB available.
ewtdr said:
I did the reset. My system memory is showing 102 MB of Apps (I installed a handful of things already), and 770 MB available.
Click to expand...
Click to collapse
I meant System ROM, not internal.
And odd, finally rooted, browsing SystemROM with ES File Explorer. Gulliver's not there. Biggest app is Golf and LG Home at 16MB each...
I remember someone made an app to get rid of most of the AT&T crap. That still work for ICS? I remember AT&T Contacts is required. Don't remove that...
Every boot takes a LONG ASS time, about 10 minutes, to scan my media. That's with no SD card inserted. I might do a factory reset.
ewtdr said:
Thanks! I just stumbled into this and was coming to add the fix too! Both cards back !
I was going to attempt this method for root, but haven't tried yet - http://forum.xda-developers.com/showpost.php?p=39338374&postcount=3
Click to expand...
Click to collapse
no problem...
thank you! but that method does not have instructions and does not seem safe enough...
everyone keeps talking about this rom but no one is saying how to root the rom and no one is pointing out the 3D Converter problem, it does not work at all!!! it works the same way as the xbsall port LOL! and when it does, you can't adjust the brightness...:silly:
Its basically the same version as the xbsall port (v30b) but for some reason it cannot be rooted through the same methods...
I did a factory reset, and the phone stopped booting. Bizarre.
Anyways, I wiped everything but system, and reflashed the KDZ. It's booting now.
Then I flashed the ICS bootloader BUT I used the GB CWM v6. The other recoveries didn't seem to flash properly. So I'm stock rooted now. Now to remember what file to change to make the 3D button work as a shutter.
So in my infinite wisdom I deleted com.android.providers.media using titanium backup. I thought I had backed the file up but apparently I didn't. Either that or it didn't actually back the file up. Either way elements of my phone are now totally burned as you would imagine. No gallery, no music in my music player, and no ringtones. So my question is even if I do a factory reset will that help? Yes this was the stock ROM yes I tried installing a stock image on top of the ROM but the installation froze and I had to reboot and restore my nan droid. No I didn't have a nandroid of before I started dicking around. And finally yes I am a complete idiot. Any help would be much appreciated.
Sent from my MB886 using xda premium
Actually if some one would just be willing to use titanium backup to backup that file then post it here I could probably just restore it? Hope some one can help
Sent from my MB886 using xda premium
Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.
Sweet thanks man. So would u say that I should safely be able to install over the stock ROM? Or should I wipe then install? Also since these are stock I can install them to ROM slot stock right?
Sent from my MB886 using xda premium
skeevy420 said:
Odexed\deodexed....ICS\JB...Stock\Custom....Bell\ATT\Other...not much to go on...either way, go to the Batakang FTP and download which rom you need and you'll always have a backup copy of all the files needed (the bottom two). If your not AT&T, then you can get deodexed versions on my Goo.im page or odexed versions directly from the fastboot.
Click to expand...
Click to collapse
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.
metalmike6 said:
Hey, so I've been doing a lot of research on safe strap and apparently you cannot overwrite the stock ROM slot which would be why I couldn't flash anything to it. So what I did was create a new slot (slot 1) with the stock image. I installed safestrap to that new ROM. My question now would be, If I create a nandroid of that ROM and restore it to the stock slot will that work? Or will it bork due to not having safestrap recovery installed to the system partition anymore and there for stop it from booting along with killing safestrap? Hoping some one can chime in on this one as I'm quite anxious to get back to normal phone use. at least for now all my sounds are back but having a 1 gig system partition is a major bummer.
Click to expand...
Click to collapse
That's where I'm at. On my stock rom, /system/etc/safestrap was added, logwrapper was modified to execute 2nd-init. AFAIK, that's all that was added. I'm so used to the Defy bootstrap method that I'm having a hard time getting used to SS - Defy BS was clearly laid out on what was executed and when that was done -- I've even looked at the SS source and its scripts and still can figure out what's the first script called by the 2nd-init loader....makes me feel super noob .
Well supposedly hash code said that after every restore and flash to the safe slot (stock) safe strap will reinstall itself on /system so if that's the case restoring any backup to that safe slot should be OK. But if that were the case no one would be able to brick. And I've seen people brick with and lose safestrap, and have to use RSD. Which is the road I don't want to have to go down. Really wish I had a definite answer because it seems like it should work but I don't want to do it unless some one who knows more about this than me confirms it.
Sent from my MB886 using xda premium