[MOD][RECOVERY]- ReRecovery for a safer Bootstrap- DX2, MX2, CM7 and Ace's Miui

Search This thread

rprussell

Senior Member
Mar 30, 2011
327
21
I have been able to get to the recovery menu and flash various things also. Just like it was before power off plugin and there you are in recovery (about 8 seconds).

Welll.........CRAP.

I powered off, plugged in and there I am at the battery charging picture.

And it won't boot, sticks at the Moto logo.

Back to the beginning again.

(heavy sigh)

[edit]

Errr.. was that 8 seconds or 8 minutes? Because I SBF'ed back to 2.3.4 and I'm worried I might be stuck loading the BSR.
 
Last edited:

aviwdoowks

Senior Member
Sep 18, 2012
3,174
617
can someone upload the Rerecovery for the photon please... link is dead

There is no ReRecovery made for the Photon specifically. Yet the Tenfar's Dx2 BSR was dual use photon/dx2. IF YOU are on the locked bootloader photon a flash of the RRdx2 is your best shot. Please post success or failure here. Thanks

---------- Post added at 01:31 PM ---------- Previous post was at 01:24 PM ----------

If you just want the apk for the locked photon just use the dx2 apk.They have the same (some did 2 years ago anyway) md5 btw
 

unimatrix725

Senior Member
Apr 13, 2011
246
47
Big Stoned Gap, VA
Welll.........CRAP.

I powered off, plugged in and there I am at the battery charging picture.

And it won't boot, sticks at the Moto logo.

Back to the beginning again.

(heavy sigh)

[edit]

Errr.. was that 8 seconds or 8 minutes? Because I SBF'ed back to 2.3.4 and I'm worried I might be stuck loading the BSR.
I posted a recap of the link below a page back.
http://xdaforums.com/showpost.php?p=37698274&postcount=1573

I may not understand you correctly. Anytime you flash a ROM you have to Wipe Data & Wipe Cache (aka-Factory Reset), otherwise there are nasty outcomes. Also when you Wipe/Reset It Removes Any BSR, on a Locked (bootloader phone). If you are on 2.3.4 and happy then ignore my postings. I wish someone could unlock it so there would be no need for these directions.

If you are USING 2.3.4 IGNORE MY POSTS PLEASE!
This is how I got my recovery working again for CM10A3.
0.-Verify the md5 of your files. (you may regret it if not).
1.-I used the Signed bsr on 2.3.4 then flashed cm10a3+g.apps. DO Not Flash ReRecovery!
2.-You must Factory Reset after flashing cm10.
3.-Boot phone into your new cm10 (this may take a few minutes) You Must verify root.
4.-You must use a root capable file manager Example File Expert, or X-plorer. Than copy that HIJACKBOOT.Zip to /system/etc/. (Link above)
5. Install the BSR From Link above.
6.-Open BSR app. Click install (grant root).
7.-Plug Phone into Wall Outlet (not a computer or nothing).
8.-Click Recovery Mode.
You should be in recovery. I did these steps and had no issues. I hope this will help you. I would verify that you have correct files, they are not corrupt, and double check when flashing that you are flashing correct files. Make sure that the hijack-boot file is in correct loction reboot and check if it is still there. If you are still waiting for BSR to load after 8 minutes then something is wrong! The first time I loaded it was like a few minutes 1-3mins. After success it will be like 8 seconds.
One time have the chainfire3d driver installed and forgot to remove it which screwed up my upgrade.
I did note that SuperSU works better than superuser. I used a slitaz boot cd for sbf, then used the cd again for root. That cd has superuser. Google for [Tool] ezsbf dx2 as I do not think I am allowed to cross link a competitor site.
 
Last edited:
  • Like
Reactions: norse0223 and purrr

CCC0180

Member
Mar 12, 2014
27
8
Charlotte
Mod for CM10a3

Anyone wants to kang it go ahead. I am skwoodwiva backwards

no kanging, but could use some direction to modify it. :p

I am running CM10a3 on my Dx2. It is a working phone but I am flashing other roms often but need to flash back to CM10, are you willing to give me some pointers updating Your script to support CM10? I have reviewed the posts from rprussell and nimatrix725 . I have encountered the sane issues. Currently the ReRecovery does not work for CM10a3 however CM10a3 uses the hijack from CM7 so they should be similar. I want to know if moding your script for CM10 are feasible by a noob like me.

I am currently using the patched hijack-boot.zip http://xdaforums.com/showpost.php?p=37698274&postcount=1573

ReRecovery would be benificial to me as I am changing ROMs often. The patched hijack-boot.zip uses the CM7 BSR apk so it seems if your ReRecovery working on CM7, it would likewise work on CM10 but I had the same issues as unimatrix725 and prrussell.

I have made a rooted nandroid with the patched hijack-boot.zip and successfully recovered with it The BSR apk for this nandroid is the CM7 System app. The nandroid recovery works as expected (ie from power off, charger inserted into USB port, recovery will loop on the Motorola screen until battery is pulled since no apk applied yet. When Dx2 is powered on and the CM7 System app is applied, Install Recovery run, Recovery run, the Dx2 successfully launches into CWM)

Your files "zReRecovery.Dx2.Cm7.PI.notice.v4.zip" and "zReRecovery.Dx2.PI.notice.v3.zip" share common named files however all files are compiled different. I assume I would start with the Cm7.

My questions:
1. Assuming I start with your files names in your Cm7 zip, would I go about creating a CM10 zip by replacing your Cm7 zip files with the correlating with the Cm10 files? How does the 2nd Init file hijack-boot.zip affect these files?
2. Is there a special way to zip and sign this package to install through CWR?
3. Is there a way to turn off BSR/CWR so that when a charger usb is plugged in to the dx2 port, the battery meter starts as with an unmod dx2 but when I want to launch CWR I run a script/apk to reinstall/reinitiate CWR?

Thanks.
 

aviwdoowks

Senior Member
Sep 18, 2012
3,174
617
The problem may be that /preinstall is not allowed in the root directory anymore? It is not on ics & jb. If so what folder could one use?
 
Last edited:

CCC0180

Member
Mar 12, 2014
27
8
Charlotte
Much thanks!

I made an alpha RR for cm10. I have no idea if it even has a hope of success. PM me.

Thanks, I will try it out and give you feed back. I have not been changing ROMs as often since I have multiple X2 phones to test with and have not been using CM10 as much.

I was going to get back with you. I had not had a change to respond to your previous post. What did you have to do to update? Do you use a X2 and if so what ROM?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    Working ReRecovery. Thanks to Tenfar BTW. This is technical and some say maybe hard to read eh....:rolleyes:
    JUST SKIP TO POST 2 for a good outline of how our bootstrap functionality has changed w/ RR.
    Downloads and Updates are in post 3.
    Noob Q&A is in middle of 3.

    PURPOSE: Use to flash duplicates of all files needed to renew Tenfars cwr (our standby) during a cwr "run" where the current installation could be made inoperable by a rom flash and/or data wipe.
    Just be sure to flash it BEFORE YOU REBOOT SYSTEM NOW.
    Once you flash this you do not have to reinstall tenfars again. That is because you always be overwriting one instance for a new one.
    Charge mode is not available. However I do believe charging does occur normally in cwr.

    If you do a Privacy>Data reset you will need to run the apk again. OR
    Run the apk for any reason.
    It will take over again.


    Think of this as a "save your a$$ button". You will have a working cwr if your phone can boot- be sure to try a battery pull if it won't boot on first try. If needed the pull will make BUs, made on this "emergency boot", have a very old date.


    :cool::eek::rolleyes::mad::confused::eek::):(:D;):p:p:p:mad::eek:;):):):):):eek:;)
    Remember to flash at the last to save your a$$.
    Remember too when the ROM BOMBS you must P P P .
    PULL the battery, PUSH the battery back in and PLUG in the charger.
    I wish I could make a rhyme like : “If it doesn't fit, you must acquit.”
    :eek:;):cool::(:rolleyes::p:eek::confused::cool::eek::mad::);):D:D:D:D:(:(:rolleyes::rolleyes:
    8
    Attached Zips to flash from cwr.

    Flash from cwr - Tenfar's.

    Older updates are 1st. GoTo Attached files for latest updates.

    ****update*****
    Maybe not so minor if you don't understand what it's doing.
    On screen notifications/help now may help you understand better how to use it.

    1st DL looks/is the same as the installed apk and now gives on screen notices/help: zReRecovery.Dx2.PI.notice.v3.zip

    2nd DL ( also gives notices/help ) has Atrix at the top of the homescreen so YOU know you are on the flashed version when you shutdown.
    This is just a reassurance that it works: zReRecovery.OLY.PI.notice.v3.zip.
    I have used this as an alternate for ours and it is ,as far as I know, fine.

    Either one you choose, it needs to be flashed ( from cwr ) as the last cwr step to save you

    All action happens while YOU are in CWR AND BEFORE YOU REBOOT SYSTEM NOW.
    When should RR be flashed? Ans: after a data wipe, a rom flash or restore. Just as the last step if any or all are done in one session.

    ***UPDATE NOW A CM7 VERSION***
    I nandroided back to 234 stock, flashed cm7 and gapps, wiped all and flashed RRcm7, pulled battery and it booted to cwr.
    3rd DL : zReRecovery.Dx2.CM7.PI.notice.v4.zip

    ***IN SUPPORT OF VOODOO RK***
    For those of us that have trouble rooting 235 with Zurg Rush and it's variants. Root 234 w/ Pete's and use Root Keeper before upgrading to 235.
    http://androiddev.orkitra.com/download/apps/?appid=-2821155941944302146 One of the rare non-market links. Put it on your SD. RK has an option to delete OR re-enable SU backup. It is there for good reason. The latest Eclipse bombs when being flashed w/ the BU present. Just REMEMBER to delete it b4 you flash OR use RR and it will catch you so you can just nand back to delete it.

    *** update ***
    I have found RRcm7 to work for Ace's Miui. Just be aware that if flashing a non 2nd init rom, flash RRdx2 first to be safe. BUT if the dx2 bsr has already been put in effect the RRcm7 does work as a "do it all" Until a need becomes apparent just use each on their respective roms.

    Q and A

    How to boot to cwr without using the apk? (This only works if charge mode is never put back to normal)
    Just power off while the charger is plugged in. Or if stuck at the big M pull the battery put back and plugin.

    What is "Safe Boot"? It is booting w/o loading anything in /data.
    Power on and at the big M hold the menu key till you get to the vibration and you will see "safe mode". Miui will just loop here BTW.

    What is Android recovery good for? Stock is good for
    1> flashing an OTA update, rather/better than the system auto update, (no need to rename it just make it start w/ a number so it will be first in a mess of zips at the root of your removable sd)
    And
    2> wiping data. When your ROM hangs at the M OR you never feel the "I am done booting" vibration and it keeps looping.

    How to choose DIY update rather than Auto? When the update notice appears choose download only. When the DL finishes choose install later. Goto /cache to find the Blur.zip and the md5. Use Root Explorer>properties to check that the md5s match. Rename the Blur.zip 1Blur.zip and paste it at the root of your SD removable card. Power off>Power on>as you see the Big M push the rocker down>keep pushing down 8 times>push up>you will see the green creature AND OF COURSE HE IS TELLING YOU TO PUSH THE ROCKER AGAIN but IN THE MIDDLE like BOTH AT THE SAME TIME! (rant off)>choose "apply update from sdcard" and it will let you pick.


    Put the empty FILE : ".hidenandroidprogress" in your cwm folder and cut 1/3 off your bu / restore times.

    I add descriptors to replace the seconds: "2011-08-21.09.13.CheeseC".
    Never use spaces in a nandroid bu name. It will cause md5 mismatch .

    Terminology rant: (work in progress)
    For this page.
    BootStrapRecovery BSR is the same as CWR or CWMR.
    Yet there is a need to distinguish the methods used to install the
    recoveries from the recoveries.
    The (CWR or BSR) "recovery" is a zip in our locked boot loader phone. In contrast to a (.img) image for an open boot loader.
    These zips are in each apk (links @ end of post) and have a common name: update-recovery.zip. The UD-R.zip is the "kernel" of the recovery. ReRecoveryxxxx.zip is similar to the apk in that it installs the "kernel" but from cwmr and giving you no options.
    Once booted and @ the green cwmr home screen you may flash any of the "UpDate-Recovery.zips that are in the apks below. A apk is just a zip. Root Explorer>extract all. Its in the assets folder and flashable from cwr. And jump from one cwr to another....you can even jump to one of the latest touch recoveries http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.1.8-olympus.zip (w/ the fstab taken out of http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.5-daytona.zip and put in the former) that can BU to tarballs and mount usb ext sd but won't restore....
    Sub rant re: RM (very restrained)
    Example : Rom Manager (the famous apk) lists a recovery for our phone the Daytona which leads many to install the apk and the recovery which does nothing but frustrate noobs. Not only does RM install a cwmr.zip that bombs it puts it in folders where our phone could never utilize it.
    Our bsr.apk puts the cwmr.zip in the folders that the same apk sets up for charge mode hijacking. RM fails and our BSR.apk succeeds in setting up the phone to run the cwmr.zip (the "kernel") which runs in place of the stock recovery.
    Rants off

    Milestone X2 users Try to use this Dx2 apk first:http://xdaforums.com/showthread.php?t=1166508&highlight=bootstrap OR
    Copy and paste your own bootstrap:
    DL zReRecovery.Dx2.PI.notice.v3.zip
    You need Root Explorer , ES file explorer Or any root file explorer that sets permissions.
    Extract all and paste 8 files (not the folders) to the same folders in your root dir (not the dir: root that is always empty) that you found them in the zip.
    1)paste to /preinstall: the 5 files and set perms to all-rwxrwxrwx but adbd: rw-rw-rw-.
    2)Change charge_only_mode (not the .bin file-leave that alone) ( your original in system/bin) to .bak. Then paste the 2 /system/bin files. Set perms to all- rwxrwxrwx
    3)Then .recovery_mode goes in /data. Set perms to rw-rw-rw-. Power off and Plug in. CWR
    Ignore the meta-inf file.
    End roll your own BSR.

    Testing.

    Note after each you will still be able to boot to system and reinstall the "bsr.apk" if there is a problem.

    1st >
    test the RR version you choose by flashing it w/o flashing anything else THEN pull the battery and see if cwr boots.

    2nd>
    A good test is to: make a BU, I have learned that the easiest test, while you are still in cwr after a BU, is to Advanced Restore the cache of the BU just made. now if there is a problem It will say md5 miss-match. If it does choose backup & Restore> external> restore and note the BU you just made. Reboot sys and view your clockworkmod/backup folder and look for the one you just made- If it disappeared - post here. If the cache restore completed then you should be ok.
    THEN: wipe data from cwr, flash RR, pull battery and see if cwr boots and then of course restore the BU you just made.

    Would some Milestone X2 user on 2.3.5 please upload their wiped nandroid BU? Here's more http://xdaforums.com/showthread.php?t=1507694
    A Mx2 236 SBF is needed also http://xdaforums.com/showthread.php?t=1563297
    Dx2 Mx2 and other SBFs https://sites.google.com/site/motosbf/


    Various DL links for "BSR".apk's:
    The Photon locked bootloader (= "Dx2.apk" )
    http://xdaforums.com/showpost.php?p=16260675&postcount=1
    Our "Dx2.apk" (discovered on some Chinese website )
    http://xdaforums.com/showthread.php?t=1169677
    And the Original (Atrix/Olympus locked BL) and predating the the one discovered (above) by several months. Yet it works on our phone.
    http://xdaforums.com/showpost.php?p=12593538&postcount=1

    :cool:Hey Dude want 2.3.6 on your Dx2 :eek:Yea Where Man
    http://xdaforums.com/showthread.php?p=22756060#post22756060
    7
    I must digress here for Noobs: (BTW CWR = BSR)
    Did you Know:
    You do not have run "MOTODX2_Bootstrap_signed.apk" aka "System Recovery" in your app drawer to get to BootStrapRecovery! Once you choose recovery mode and the phone goes to CWR thereafter the phone will always go to BSR when you plug-in and power off. If this is news to you try it right now. More news: while you are in BSR unplug the charger & pull the battery, put the battery back and plug-in. CWR (BSR) will boot. ReRecovery sets up the same conditions (files and stuff) that you just tested out to take your phone into BSR. With ReRecovery you have no choice power off OR battery pull along with plugging-in = BSR. BUT ReRecovery is flashed from BSR so you can refresh BSR anytime! Like after a Data wipe which kills BSR OR after a ROM flash which kills BSR OR after restoring a wiped Nandroid which also kills BSR. Sorry for the long rant but that is life with a locked bootloader.

    From DaveRichardson (Thanks Dave)
    http://xdaforums.com/showpost.php?p=21116880&postcount=26

    Why use this instead of our " MOTODX2_Bootstrap_signed.apk" isn't it the same? It is the same. But a feature of cwr w/ an unlocked BL is you flash a rom and wipe data the bootstrap does not rely on anything in data or system. Not so with a locked BL. It can be a headache when the rom crashes yet you can sill boot but YOU JUST WIPED AWAY YOUR BOOTSTRAP!

    THIS allows you to refresh bootstrap as the final step in any cwr session.

    NB:

    All benefit of this hack occurs because YOU remember to flash it to save yourself .
    4
    To sum up:

    Whereas before, when we wanted to try a new ROM, we'd:

    1. bootstrap into recovery
    2. take a nandroid backup (knowing that if we have to restore from it, we could kiss 20 mins goodbye because we'd have to SBF --> re-root --> install bootstrap --> THEN boot into CWM to restore)
    3. clear data/cache (killing our CWM)
    4. flash new ROM zip
    5. cross our fingers that everything boots up fine (and if it doesn't follow the above process)
    6. be happy we didn't bootloop, quickly install bootstrap to flash recovery
    7. explore our new ROM

    ...the new process is:

    1. bootstrap into recovery
    2. take a nandroid
    3. clear data/cache (killing our CWM)
    4. flash new ROM
    5. flash this recovery (reviving CWM)
    6. reboot system (and if it bootloops, battery pull into CWM and recover from the nadroid we just took)
    7. explore our new ROM


    If I'm misunderstanding something, please don't be shy about correcting me! I'm used to unlocked bootloaders and true CWM, so I'm still trying to come to grips with the limitations of bootstrap-installed, temporary CWM.
    2
    Bump for CM7 ver added to op.