Hi,
Can someone explain how to delete OpenRecovery in case of we have to send back our to Motorola to fix and harware problem.
Thank you
Zachary57 said:
Hi,
Can someone explain how to delete OpenRecovery in case of we have to send back our to Motorola to fix and harware problem.
Thank you
Click to expand...
Click to collapse
The safest bet is to flash your SBF using RSD Lite/sbf_flash. You should make sure that you have the appropriate sbf somewhere in your possession now so you don't have to hunt for it later. If you have ever used RSD Lite/etc to flash a sbf that isn't your carrier's, you should use RSD of the whole sbf because some parts can't be flashed in nandroid.
Sneaky Open Recovery suicide mode: If you want to get really tricky you can extract the system, logo (the white M--only if you changed it) and boot partitons from the appropriate sbf and use nandroid to apply them. On linux you can do this with "sbf_flash -x your.sbf" and then CG39.img is system.img, CG42.img is logo.img, and CG35.img is boot.img and they can be restored using nandroid after you create .md5 sums and put them in a /sdcard/nandroid/openrecovery/suicide directory on your sdcard. You want to use the ones for your carrier.
you are way ahead of me...
I'm still trying to figure out how to install it...
SilverKeiser said:
I'm still trying to figure out how to install it...
Click to expand...
Click to collapse
Follow Dexter's instructions to install 1.3.
Zachary57 said:
Hi,
Can someone explain how to delete OpenRecovery in case of we have to send back our to Motorola to fix and harware problem.
Thank you
Click to expand...
Click to collapse
Uninstall the app, if Motorola say anything just say you wanted to back-up your system ,
mintaeroboy said:
Uninstall the app, if Motorola say anything just say you wanted to back-up your system ,
Click to expand...
Click to collapse
That won't remove the Open Recovery hijack. Look at /sdcard/OpenRecovery/orbootstrap/install_script.sh for more info about what modifications Open Recovery makes.
Related
hello,
i want to install khal's rom but when I try to dump my stock rom with openrecovery 1.46, I can't dump Boot, Baseband Software, Linux Bootloader and Device Tree.
Can someone help me ?
Thank you
Using OpenRecovery on the xt720 you need to skip the Baseband, Bootloader, Logo & Device Tree Partitions. This hasn't caused me any problems, When I restore a backup all my stuff is still there. You should be able to back the boot partition though.
HTH
3rdstring said:
Using OpenRecovery on the xt720 you need to skip the Baseband, Bootloader, Logo & Device Tree Partitions. This hasn't caused me any problems, When I restore a backup all my stuff is still there. You should be able to back the boot partition though.
HTH
Click to expand...
Click to collapse
Thank you, I was meaning I will have problem to restore.
I think all the ROMs posted here are the boot & system partitions only so the other partitions will remain as they are.
How to Install?
Obviously, people here have installed Open Recovery and want to know how to remove it. My question is: How do you INSTALL it?
In his videos the reverend acts like you just click a couple of icons and open recovery is installed on your phone but I do not see how to do that so if someone can explain the process, Thanks...
p.s. Have downloaded OR 1.46
SilverKeiser said:
Obviously, people here have installed Open Recovery and want to know how to remove it. My question is: How do you INSTALL it?
In his videos the reverend acts like you just click a couple of icons and open recovery is installed on your phone but I do not see how to do that so if someone can explain the process, Thanks...
p.s. Have downloaded OR 1.46
Click to expand...
Click to collapse
You just have to follow instruction for milestone xt720 here : http://modmymobile.com/forums/563-motorola-milestone-roms/531599-open-recovery-v1-46-11-21-2010-a.html
To have a terminal install android terminal emulator from market.
Noob.
Trying to flash to INFUSED V2
one step says to DELETE the RECOVERY file.
Can I rename it instead (like "Recovery2")?
Why delete when I can rename?
Noob
Thanks so much!
benyben123 said:
Noob.
Trying to flash to INFUSED V2
one step says to DELETE the RECOVERY file.
Can I rename it instead (like "Recovery2")?
Why delete when I can rename?
Noob
Thanks so much!
Click to expand...
Click to collapse
Rename should work fine. Untested though.
Entropy512 said:
Rename should work fine. Untested though.
Click to expand...
Click to collapse
thanks!
If I delete it, though, how will I recover my phone in case something goes wrong (sorry is this a stupid question?)?
benyben123 said:
thanks!
If I delete it, though, how will I recover my phone in case something goes wrong (sorry is this a stupid question?)?
Click to expand...
Click to collapse
The kernel in Infused comes with an alternative (and standard in the third-party Android world) recovery called Clockworkmod Recovery. Deleting the "original" recovery prevents it from interfering with CWM.
Also, even if you delete Samsung's 3E recovery and CWM is hosed, the phone still has download mode (aka Odin/Heimdall mode). Odin/Heimdall can be used to recover the phone from anything except a bad bootloader flash. Our phone has a lot of protections against this, to the point where there is a grand total of 1 hardbricked Infuse, and that was a volunteer running a known dangerous experiment.
For more information on your "safety net" look at AdamOutler's Heimdall One-Click or gtg's Ultimate Unbrick. (These are basically the same thing with different user interfaces.)
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
jpearn said:
Hi,
I'm in the situation of having a working tablet, but the dodgy version of CWM. The original thread has been deleted and I remember there was adb command at the end to stop the original update.zip from flashing the factory recovery, but not what it was so I can reverse it !
So if anyone can help me out, that would be great, so I can avoid a bricked device !
Click to expand...
Click to collapse
go finding a original recovery dump,and flashing it in fastbootmode.
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
1
californiarailroader said:
Has anybody been able to find a stock recovery for the A700? JP, I also flashed this broken CWM, thankfully I haven't used it but I want to put the stock one back on to avoid any issues.
Click to expand...
Click to collapse
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
lsnc said:
reflashing the official update.zip
but,delete the first and the third comands in the updating list,this could avoid wiping/formating action to avoid damage to the /data partition.
Click to expand...
Click to collapse
Thanks! However, the US Version doesn't have an update for it, at least not yet, and I haven't been able to find a stock US A700 ROM.
So we would need to rename the install-recovery.old back to install-recovery.sh in /system as this was disabled in CWM ??
So has anyone managed to successfully put on the stock recovery ?? !!
jpearn said:
So has anyone managed to successfully put on the stock recovery ?? !!
Click to expand...
Click to collapse
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Moscow Desire said:
Take a little advice folks. If you don't know what you're doing, and your tab is running fine, don't be messing with anything. Just leave it alone til a better method comes.
My guess, if you rename your recovery.sh, is that when you boot, you will either get;
A. a "loading recovery kernel" message that just stays there
or
B. an "invalid recovery image", or something similar.
MD
Click to expand...
Click to collapse
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
californiarailroader said:
That's what I'm doing, I'm just leaving the CWM on there until somebody comes up with a fixed version.
Click to expand...
Click to collapse
Sounds like a plan I'll keep things working for now, thanks !
jpearn said:
Sounds like a plan I'll keep things working for now, thanks !
Click to expand...
Click to collapse
View attachment updater-script.rar
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
I don't understand these instructions. What original file is being replaced? What update.zip are you referring to?
EDIT
Well, I tried to swap out the update script that came in the ROM: SDs_Acer_A700_AV043.RV00RC00_AV043.RV07RC04_EMEA_CUS1, with the one provided above and seemed to have made some progress...I put on an external SD card and renamed to update and then flashed it through the CWM recovery and it completed. A random offset was noted and then the SD update completed note. However, when I rebooted the device it stuck at the Acer logo and never went any further.
EDIT
So, it then occurred to me that the flash through CWM was probably only partially successful - maybe the replacement of the recovery worked. So, I took the same ROM I noted above, unmodified, placed on the external SD card, renamed, etc. and flashed it and it worked - I never saw any signs of CWM during this process. I hope this helps others too.
EDIT
Looks like I spoke too soon...the flash never got past a 1/4 of the progress bar. Looks like I still have a non-functioning device.
lsnc said:
View attachment 1190247
use this attachment to replace the original file,then reflash update.zip via cmw.
'cos i delete the formating commands in the list,u could reflash the official package to restore the official recovery.
Click to expand...
Click to collapse
Hi, I'm a A510 user. I used the CWM to wipe data/factory reset, after that i cant flash any zip, and even cant enter the system. When i turn on the tab, it stuck on 'iconia tab' LOGO, I tried to hard reset, then i got a 'Unrecoverable bootloader error (0x19000008)'
I enter the fastboot and flash the stock recovery back. next i use the recovery to flash update.zip as usual, but every time the flash will stuck in 1/5 of the whole progress bar, I changed it with other rom zip, or even change the SD card, it didn't work anyway!
every time the flash stuck in the same place of the whole progress bar, i guess it is not an accident! After read your solution, I check the script in my zip, then i delete 2 lines about 'format' command. I think this time will be ok! but to my surprise the green turtle fell down when flashing.
I think the idea is great, but it maybe make the script incomplete, so it cant be flash in.:crying:
Coming from ATRIX 4G I never had to flash, now with ATRIX 2 I know I need to flash to bring my phone back from bootloop.
I know I can use RSD Lite (is this the best tool, isnt there a simple ATRIX 2 Fastboot tool?) to flash but can I just flash the /system or do I have to flash the entire file system?
I am asking 'cause I bricked my phone by deleting one of the moto files in system/app, that's all. The phone was working fine until the reboot when it enterered the bootloop.
Again, do I have to flash the entire file system or can I just flash my /system ?
Just put the default_flash.xml file in RSDLite and hit start.
And you will flash everything.
brianmoyano said:
Just put the default_flash.xml file in RSDLite and hit start.
And you will flash everything.
Click to expand...
Click to collapse
Is there a way to flash just the /system partition?
duchski said:
Is there a way to flash just the /system partition?
Click to expand...
Click to collapse
There is, but unless you are skilled, and know some dev stuff, I do not recommend it.
Just flash the whole thing, it is the safest way to get you back to normal.
jimbridgman said:
There is, but unless you are skilled, and know some dev stuff, I do not recommend it.
Just flash the whole thing, it is the safest way to get you back to normal.
Click to expand...
Click to collapse
Sent from my MB865 using Tapatalk 2
Thats what i did and now CWM enables partial restores
brianmoyano said:
Just put the default_flash.xml file in RSDLite and hit start.
And you will flash everything.
Click to expand...
Click to collapse
Is restoring stock ICS literally as simple as what you have stated above? OR are the steps as below:
1. Should one boot into the stock "boot manager menu" (if that is the right term used around here?) by holding down both vol up & down buttons and hitting the power button?
2. Select AP Fastboot, connect via USB and then push the "InlineFlashing_Edison_67.21.125_CFC_P3_APBP.xml.zip" via RSD Lite?
And oops I got a doubt now: do I use the ".zip" file as a whole in RSD lite?
(yes, I have been reading the various noob threads . )
And lastly can the above be used as the ultimate fallback option to restore an Atrix2 to working/stock ICS state from any screw ups? (well most screw ups ... like if something goes wrong with I am trying custom roms, trying the overclocking mod etc...). Thanks!
RSD lite will unzip it before flashing, or you can unzip it then load just the XML. Works either way.
Sent from this thing.
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Jesse72 said:
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Click to expand...
Click to collapse
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
USBhost said:
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
Click to expand...
Click to collapse
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Jesse72 said:
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Click to expand...
Click to collapse
Then can you just restore that backup?
USBhost said:
Then can you just restore that backup?
Click to expand...
Click to collapse
How do I do that?
Jesse72 said:
How do I do that?
Click to expand...
Click to collapse
How did you even do a full ROM backup
Or you used that tool to do so?
USBhost said:
How did you even do a full ROM backup
Or you used that tool to do so?
Click to expand...
Click to collapse
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Jesse72 said:
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Click to expand...
Click to collapse
NP I was a noob too
What do you mean by adb working
In recovery and or booting up?
If you get adb while the bootloop
Can you do "adb shell mount"
And is your bootloader unlocked
Do you have download mod?
Edit nvm thanks @karandpr
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
karandpr said:
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
Click to expand...
Click to collapse
Stuck at step 3, won't accept scatter file.
Jesse72 said:
Stuck at step 3, won't accept scatter file.
Click to expand...
Click to collapse
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
karandpr said:
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
Click to expand...
Click to collapse
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Jesse72 said:
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Click to expand...
Click to collapse
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
karandpr said:
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
Click to expand...
Click to collapse
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Jesse72 said:
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Click to expand...
Click to collapse
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
karandpr said:
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
Click to expand...
Click to collapse
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Jesse72 said:
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Click to expand...
Click to collapse
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
karandpr said:
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
Click to expand...
Click to collapse
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Jesse72 said:
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Click to expand...
Click to collapse
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
karandpr said:
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
Click to expand...
Click to collapse
I'm confused with what you want me to do with SP flash tools. Can you please explain?