Database Develop

[Q] MCR script missing

hey guys, just rooted my Samsung Captivate. Everything has been going great till now. i Downloaded a lagfix, which is honestly the main reason i rooted my phone. however after everything (yes, i did everyting right) i didnt have the app that was included in the .zip file iput in my phone. the app is called MCR scripts.
i did some reseach and i found this key line
"*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******"
in this thread:
http://forum.xda-developers.com/showthread.php?t=750869
so how do i just get the MCR scripts? i downloaded tayutama's zip file and i found the folder named "scripts" with the 3 files in there but they are .sh files.
so what do i do here? do i need to convert then to apk or something? please help!!!

forgot to mention...because i have a captivate i can not just go to setting/applications/ and choose for any app to be allowed or what not. i simply do not have that option. i use android central to get my apk files working on my phone. I have tried to run a zip file that will just let me install the apk file on my phone with no need for a computer. But that was to no avail.

bumping this.....this forum moves fast haha

thats an old thread and deprecated now im sure. why not flash a kernel with voodoo enabled? That would be a much safer and logical approach

woooah what?
i would like to get all technical and hardcore with this rooting thing but step by step lol. I'm still in my beginning stage i have a lot of experience to be earned ahead of me. is there no way to just get the mcr scripts as an apk?

nismoasfuh said:
woooah what?
i would like to get all technical and hardcore with this rooting thing but step by step lol. I'm still in my beginning stage i have a lot of experience to be earned ahead of me. is there no way to just get the mcr scripts as an apk?
Click to expand...
Click to collapse
have a look at the date on that thread, and the FIRST LINE in the thread asking to be deleted....

right, i didn't notice that...wow. either way that new thread the link is dead. and for me to run that packaged zip file i would need to completely set my phone to stock, nor do i know how to do that. Im simply asking for just the MCR files in apk format if that is possible at all. If not then can you please point me in the right direction? Thank you for all the help so far, i truly do appreciate it.

i guess the real question here is what is your ultimate goal?
you want froyo? install a rom (most everything on the dev forum will install a lagfix for you, click on the link in my sig)
you just want a 'lagfix' on stock eclair? install a 2.1 kernel with voodoo

rom would be customizing the android correct? like a new home layout and what not? That would be cool but im happy with what i have...i would just like to be able to download any app for free. and get the lag fix. i got the first part down (apps for free) by rooting the phone, all i have to do is get the apk downloaded on my comp then run android central to install it on my phone.
so i download kernel with voodoo, is it just a drop into internal sd...same as when i rooted my phone? then go into recovery and choose reinstall packages?
ok found this thread:
http://forum.xda-developers.com/showthread.php?t=784170
sooo i would definitely be installing the one WITHOUT the back light notification, as...my hpone doesnt have leds. Hopefully it works for all galaxy s phones because this seems to be for only the 19000 captivate? while i have the sgh captivate from AT&T.

3rd page in less than 24 hours...wow lol

so at this thread
http://project-voodoo.org/download
i downloaded the lag fix for my phone which is like near the bottom of the page. i renamed it to lag fix zip file tp "update" but since i have the other files that are also renamed to "update" like for my rooting and stuff the file ended up being update(3) idk if that makes a difference but when i booted my phone from recovery mode after choosing resinstall pacakges, the phone boots up normally no long pause durgin the at&t screen or anything so i know the lag fix didnt work...also because the phone is still...slow. helllp! please.

you need to remove ANY other update.zip files from your phone and rename THAT file to update.zip
then reinstall packages
once you have installed an update.zip it is no longer required on your sdcard

thats what i was thinking, just wanted to make sure. Ill check back once its done thankyou.

YES!!! i knew it was going to work when i heard the freaky computer lady's voice haha. Even still, i didnt notice a HUGE improvement, my quadrant score is a bit dissapointing only 1400...

yea, so do you guys think i should maybe overclock? its still laggy/slow to me. Im sure becuase of the preious iphone usage lol. whats the best way to o/c? i heard that the overclock app isnt very reliable...i know , i know, overclocking itself isnt relable but are there other ways about doing it?

off your original topic ...

understood. making a new thread.

[Q] Okay I give up...

Okay I give up... I can't keep looking through these forums, youtube, google. I have tried everything. And I need help. I have a rooted Verizon, samsung, fascinate. I am changing carriers this weekend to metro pcs. Anyway the problem at hand is It wont let me apply any roms, at all. I have (update.zip) with clockworkmod recovery v3.0.0.8. And I have read that I need to go back a version. But that wont do it, it wont even let me choose to go back. The thing I am having so much trouble with is when I (Choose zip from sd) it says "Please switch to Edify scripting (Update-script and update-binary) to create working update zip packages. Installation aborted"

Well, here I go:
1. Download a recent custom rom, or even a stock rom.
2. Replace in the zip everything with the rom you want to flash.
3. Now you have a flashable zip.
Pay attention to each folder. Double check them. It will take some time but you don't have any scripting knowledge, do you?
f.
Sent from the Dark Side using Sith knowledge (and a SGS 2)

Sounds like the .zip you are trying is probably amend, CWM3 uses edify. If you need to flash that particular package you may need to flash an older CWM (v2.5 something)

And that (revert to CWM 2.5) would be done via odin.
Swyped...

No, I do not have any scripting knowledge. But I will try what you said.

And to get CWM 2.5 (If the other thing does not work) where do I get that file. And once I get it I put it in the PDA tab, Right?

Wesanator said:
And to get CWM 2.5 (If the other thing does not work) where do I get that file. And once I get it I put it in the PDA tab, Right?
Click to expand...
Click to collapse
CWM 2.5 here:
CWM-recovery-all-3-30-fix

I have been working on this for three straight days, and all I had to do was ask... You guys freakin' ROCK!!!! HAHA.... Thanks

That is what this place is (supposed to be) all about!
glad you got it sorted.
Swyped...

[MOD][CWM][Bell][Gobstopper] Stock 2.2.2 for Bell Updated 10/01/2011

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.

[Q] Rebuilding my replacement Captivate

I just replaced my Captivate with a refurb from AT&T. FWIW... the guys at the warranty replacement center were very nice and knowledgeable. I have everything backed up with TiBu, moved my pictures off and all that.
My old phone had existz KB1 kernal and of course voodoo file system. Should I put this phone in the same state before I copy pictures back and restore apps? I'm wondering because voodoo as I understand it converts the file system from RFS to whatever voodoo is. That would mean my backups have been converted too.
Also, exixtz kernal is KB1 and this phone came as KB2. Any problem reapplying that kernal which I was very happy with?
I did all this stuff so long ago I've forgotten all the little stuff!

No, shouldn't be a problem. The only difference in KB1AND KB2 is the kernel and modem. But, you have to root first. Here is what I'd do.
Root
Odin flash a kernel with CWM(I used a speedmod kernel)
Flash the kernel of choice from recovery
Restore your backup.
Converting to ext4is up to you. Your back up is not dependent on using rfs or ext4.

Thank you sir! Where in north GA? cold today isn't it.

Dalton area. And yes it is.

Bad start... it won't root
I've Super one click in the past but no go now... just waits for device
helps to put it in debugging mode

dumb question... I've never restored a tibu back up... I have the backup on my pc... where do I put it. Also tibu is complaining that I won't be able to restore due to "allow third party app" not being checked in applications but there is no where to check that?

Need Superoneclick to enable non market/3Rd party apps.
Put the folder labeled Titanium Backup on your internal SDcard. Open TiBu, menu/batch/restore missing apps.

I'm mostly posting these things now in case someone else is in the same boat I am and has to go through this.
Superoneclick worked. I was a little surprised I needed it as my old phone had this enabled from ATT.
Restored most everything although TiBu died 4 times. The only thing that did not restore right was Beautiful Widgets. Fought that. Still not completely right as I can't find the same widget I had for style... FWIW.. I had 93 apps... took over an hour. I now understand the paid version if I was a heavy ROM flasher.
I enabled 3e recovery with no sig required via Truesselo's method. It worked great.
Bluetooth re-paired without requiring a password... I thought that was odd.
Had to re-enter my wireless password. Expected that.
Still evaluating whether or not to reapply Plumb Bob's GPS fix.
Still haven't updated the kernal. A reply above recommended SpeedMod but that looks like an i9000 kernal.
All in all dinked around about 4 hours with it... much of it trying to remember what the heck to do and how to do it.

CWR won't work now... What to do
I've rooted and restored. Along the way I also ran Truesello's (sp?) 3e signature fix as I had done that before with no problems.
Today I was going to flash something and it booted into recovery 3e but it os blue, I thought it was orange before.
I selected reinstall packages and I get this error
E: Can't open /mnt/internal_sd/update.zip Installation aborted.
I'm just trying to get to where I can select the zip file I want to use. I know I've done it the past.
help please.

Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.

mrhaley30705 said:
Did you name it"update" or "update.zip". The phone will actually add the.zip part for you. Try renaming it just update.
Click to expand...
Click to collapse
Thanks for your replay... I was thinking I hope mrhaley replies... he seems to know his stuff! I have plumbbob's fix on the phone and was going to flash that. it is named PlumbBob-1.0-CWM-USA.zip. It is not giving me the secondary menus to get there. I don't have an update.zip on the phone. I seem to recall it was for rooting.
Like I said, the only other thing I've done is to run the fix to allow non-signed files.
When I flashed the fix and the kernal last time I was able to navigate and select them.

The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.

mrhaley30705 said:
The old update.zip was to install cwm. On 2e recovery it worked like a charm. 3e was not the same story. You really need cwm if you are going to flash stuff. Custom kernels haves it baked in. I don't have a copy handy, or I would upload it for you. You might try using ROM manager just to install cwm.
or rename everything you flash to update, which can cause problems if you forget to change the name back to what it really is. But, you can't have more than1 thing named update on your internal sd at a time.
Click to expand...
Click to collapse
Well whaddya know... I have a folder on my pc in my Android folder called CW and in it is an update.zip file and directions. Bread crumbs... gotta love'm.
Took your advice and installed it through ROM manager. Aaaand we have PlumbBob... 7/7 and 16 ft accuracy.
Still wondering about flashing the KB1 kernal over KB2 though... the phone is sluggish. I probably will in a bit though.

[Q] Droid 3 XT 883 Backup with Safestrap 1.09

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.