Database Info

[Q] HELP with open recovery

I have bought a motorola milestone three days ago and noticed it didn't come with the market app. I've read online and called motorola and found out it is not available in the middle east which is where i am. so i've been trying to root my phone since then and succeeded at that But when it comes to open recovery and cyanogenmod it says the signature verification failed. also it says "E:Can't open/cache/recovery/command"
I would like a complete noobs guide through this also i would like to know if i would get accesses to the android market through this. if not then what should i do?
with cyanogenmod it says failed to verify whole-file signature.
I used androot to root my phone. but before that i used the rsdlite and vulnerable recovery to root it before androot.
I have all google apps except for the market.
also my brother has an htc desire and it came with the android market (just a note that the market works here, but not all phones come with it)

Hi, don't know if that could help (also a lot of time passed by from your question...).
I had the same error using GOT open recovery 2.01:
On top of the screen I had a little menu with a few options (can't remember well now, I think Reboot, Wipe Phone, Apply update and maybe another one). And in the middle the error ("E:Can't open/cache/recovery/command")
I think that happens because OR is not already on the phone (or something similar).
Just apply update.zip from OR menu and reboot.
Everything should work fine on the next OR boot (it was for me )
bye

[Q] Recovery mode only has 4 options (Vibrant)

I'm trying to flash a new ROM and noticed that my recovery screen now only has 4 options:
reboot system now
reinstall packages
delete all user data
delete cache data
That's it. I'm running TeamWhiskey's Onyx.R4.2
So where did all my other recovery options go? How do I flash a new ROM when I only have those options? I'm pretty confused here.
So I followed reinstall packages (which did nothing earlier) and now see that this is my path. I always figure it out about five minutes after I post in a help forum.

Maybe an OTA replaced your recovery partition? If you want your other options, try reinstalling ClockworkMod.

UPDATE
Here is the latest problem I'm having with this.
Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Device or resource busy)
E:Can't mount SDCARD:update.zip
Installation aborted.
Why is this happening? I have the ROM zip that I've renamed "update.zip" and it's located on the drive... anyway, this is really kinda frustrating. I don't understand what is happening.
-----------------------------------------------
EDIT:
So, once in ClockworkMod Recovery, I apply the update.zip. It displays something quickly (too quickly to read) and then reboots into Android Recovery. It does this same process every time. I simply cannot get this phone to flash this new ROM.

1. Research how to Odin to jfd.
2. The vibrant n00b guide by s1 can help alot.
3. Honestly this could be solved by the n00b guide and just post in the vibrant section next time!
Sent from my GT-I9000 using XDA App

duboi97 said:
2. The vibrant n00b guide by s1 can help alot.
3. Honestly this could be solved by the n00b guide and just post in the vibrant section next time!
Click to expand...
Click to collapse
I appreciate the reply, but this n00b guide doesn't even remotely address my problem. At least not the n00b guide I found by searching Google. (http://forum.xda-developers.com/showthread.php?p=14358771#post14358771)
This isn't about flashing ROMS. This isn't about ClockworkMod Recovery. This isn't about my problem.

This is the all might n00b guide http://forum.xda-developers.com/showthread.php?t=849028
Did you ever try reinstalling packages (you have to do it more than once and you must also have to update.zip file on your internal SD card)
Sent from my GT-I9000 using XDA App

Thanks for the link. I had done the Reinstall Packages thing.
I got to the point where I just wanted to Odin back to stock and start from there. I downloaded the files and did everything as instructed. The problem occurred when I tried to connect the phone in Download Mode with Odin running. My computers (two different Win7-32 PCs) said that the USB device was not recognized or had malfunctioned. I had just installed the drivers not five minutes before and it still would not work. I tried multiple USB jacks and I tried manually pointing to the drivers when necessary.
Anyway, none of that worked. I had a soft brick. I ended up stopping by a store and played dumb: "Hey, my phone just won't turn on." They looked at it, tried a couple things, then ordered me a free replacement under warranty. Problem solved.
It sucks to brick a phone, but I'm not afraid of it! That's how we learn, I suppose. Thanks for your help and the link... I'll read that before working on the new one!
+mf

N00b with a screwed-up Droid 2 global

I was sold an unlocked Droid 2 Global. Previous owner said that the device was rooted and he had installed Clockwork and one or another ROM (can't recall which one exactly, but I don't think it was CyanogenMod). He also said he'd done a factory reset before shipping the phone.
When I received it I turned it on and was greeted by a completely white desktop with no response to the various buttons. The owner said he'd modified the ROM extensively, which is probably why it wasn't working right. Rather than waste time fixing it I decided to install CyanogenMod 7, so I went here and downloaded the update and the gapps file. Then I followed the instructions here, rather than those on the CM page, to flash it - I didn't do a ROM backup because I didn't care for the one originally on the device.
I don't have a reason why I followed one guide instead of the other - that was what was open and that was what I followed. Only later I noticed that the guide I followed omits a step that the one on the official page has: format /system. Not sure if this was the cause, but whatever it was, when I rebooted the phone was stuck on the Motorola logo - and yes, I did let it sit there for a good few minutes before I became convinced something had gone wrong.
I reset it by removing the battery, but it keeps getting stuck on the M logo - I can no longer get to Clockwork. I managed to get it to the standard android recovery menu by booting it with X pressed and then pushing volume+camera; I wiped data and cache and tried to run the update again from the sd card, but now it says:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
This despite the update file clearly having "signed" in the name.
Only other thing I've been able to do was to get it to the bootloader, where it says "battery ok - ok to program - connect usb - data cable". No idea what that is even for.
What do I do now?

you need to SBF from bootloader
try ezSBF http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
also read the FAQs and Droid wiki (links in my sig)
about stock recovery, bootloader, SBF, and clockwork mod recovery
edit: update will only work if you are running stock rom

Thanks, the sbf fix brought the phone back among the living. I read the FAQ and wiki and have a clearer idea, hopefully I can avoid similar screwups in the future.

CWM will not install over the Android recovery 3e ...

I have a Samsung Infuse that at one time had JB on it.
I went back to Foyo for several months.
Now I want to try KK.
My Infuse is rooted but nothing will install - I get "failed to verify while file signature"
everytime I try to use the Android 3e recovery.
For the life of me I cannot get CWM installed on this phone.
How can it be done? I've tried Odin but don't work either.
Help
Carl

Also tried the "modded 3e recovey" copying a recovery file to /system/bin.
I can do this but still have no CWM as the recovery menu.

So, whats happening is that Android system recovery <3e> recovery menu cannot be replaced
nor will it let me install a zip file. Every time I try to install CWM or any other
zip file, I get:
E:failed to verify whole-file signature
E:signature verification failed

cwmoser said:
So, whats happening is that Android system recovery <3e> recovery menu cannot be replaced
nor will it let me install a zip file. Every time I try to install CWM or any other
zip file, I get:
E:failed to verify whole-file signature
E:signature verification failed
Click to expand...
Click to collapse
I am not familiar with that method to install CWM. Usually one would flash an infused kernel via ODIN. Are you AT&T or Rogers? That would determine your method.
On mobile now so myself looking it up is difficult, but what you need should be in either the General or Development forum. Try searching for "infused CWM".
Sent from my LG-D520 using XDA Free mobile app
Update:
Easiest method would probably be option D:
http://forum.xda-developers.com/showthread.php?t=1613523
This will give you Stock Gingerbread with root, and red CWM. What kind of problems were you having with Odin?

joel.maxuel said:
I am not familiar with that method to install CWM. Usually one would flash an infused kernel via ODIN. Are you AT&T or Rogers? That would determine your method.
On mobile now so myself looking it up is difficult, but what you need should be in either the General or Development forum. Try searching for "infused CWM".
Sent from my LG-D520 using XDA Free mobile app
Update:
Easiest method would probably be option D:
http://forum.xda-developers.com/showthread.php?t=1613523
This will give you Stock Gingerbread with root, and red CWM. What kind of problems were you having with Odin?
Click to expand...
Click to collapse
Your diagnosis was spot on.
What I had done when I bricked my Samsung Infuse months ago was that I had used PHONE_UCLB3.tar.md5 for PHONE selection in ODIN. I had JB running but the performance was poor and messing with it
I had bricked my phone. Then when I was able to recover back to Froyo, I said f*ck it and quit messing with it.
Doing what I did several months ago to unbrick my Infuse locks in the Android recovery menu.
Yesterday I was experimenting and used option C to get it working now -- i.e. using I997UCLB3-CWM-root-deodex-extras.tar.md5 for PHONE. I suppose either option C or D would be OK as those provide the red recovery menu for Froyo. I was scimming over all the various texts and had missed the details.
Boy this stuff can be complicated unless one stays with it - AND READ EVERYTHING CAREFULLY.
I'd made a lot of notes when I did this months ago but still it was vague.
Now its coming back to me and I think I'll start hanging out here to learn more about these ROMs.
Not knowing which is better, I chose to install Carbon Kit Kat nightly on my Samsung Infuse. I noted that Bean Stalk did not have any
recent versions and just assumed there was more activity with Carbon. Is Carbon as good as it gets or are there better choices????
Thanks
Carl

cwmoser said:
Not knowing which is better, I chose to install Carbon Kit Kat nightly on my Samsung Infuse. I noted that Bean Stalk did not have any
recent versions and just assumed there was more activity with Carbon. Is Carbon as good as it gets or are there better choices????
Click to expand...
Click to collapse
It's all subjective, but with the time I used it I think Carbon is as goods as it gets.
There's CyanFox, which I didn't try, which is still quite young. CM11 and BeanStalk have been getting updates, it's just their key developer is absent right now. But there is a bug with CM11 and BeanStalk that leaves ADB unable to work. If you plan on using ADB, I would stay away from those two. Other than that, I did like the BeanStalk experience when I used it, but in the end wished I switched to Carbon earlier.

Unable to fix
Hi,
I am trying to update kitkat, it gives me the error of:
" signature Verifucation Failed"
Tried loading CMD RED on my infuse $g, but unable to download , the link does not work
Pleas Help me , i am trying for the past 10 days. i am a poor guy and my only phone is infuse with broken screen which gets restart and drains out the battery on every restart. i tried putting New battary, still same issue
Please Help me XDA, You are my only HOPE :crying:

John Don said:
Hi,
I am trying to update kitkat, it gives me the error of:
" signature Verifucation Failed"
Tried loading CMD RED on my infuse $g, but unable to download , the link does not work
Pleas Help me , i am trying for the past 10 days. i am a poor guy and my only phone is infuse with broken screen which gets restart and drains out the battery on every restart. i tried putting New battary, still same issue
Please Help me XDA, You are my only HOPE :crying:
Click to expand...
Click to collapse
Disable voodoo lagfix and you should be good to go. If not, try downloading a different kit Kat Rom (one with a working link).
Sent from my Asus MeMO Pad 8"

Completely messed up rooting my S7 Edge with a custom ROM

So, I wanted to root my device in order to modify games, but haven't ever encountered Custom URL's before, so I decided to watch a YouTube tutorial, not realising that it was several months out of date.
So, the tutorial took me to Odin, and a custom ROM, which I then *tried* to install. Damned thing wiped my device with a "Verification failed" message. So the next morning, I reset my device as I couldn't find a way around it, I then tried to install Majisk v16.0 using TWRP. Though this seemed way easier than installing the custom ROM, I have had a lot of trouble with the installation of the .zip file, due to my earlier failures with the custom ROM.
TWRP keeps giving me the error:
! Boot image patched by other programs!
! please restore stock boot image
Updater process ended with ERROR: 1
Error installing zip file ' /sdcard/Magisk-v16.0.zip '
Other XDA threads have pointed me in the direction of a stock boot.img file, but I cannot seem to find one for my device (Since most of the threads with this problem are over a year old, and many updates have occurred since then).
Anyway, I am looking for either a link to an updated boot image, or a possible solution to this problem.
Thanks in advance.

Largestella said:
So, I wanted to root my device in order to modify games, but haven't ever encountered Custom URL's before, so I decided to watch a YouTube tutorial, not realising that it was several months out of...
Thanks in advance.
Click to expand...
Click to collapse
I kinda did the same thing with my S7 edge before. I believe you havent turned on OEM unlock so you got the error while flashing with Odin. Now i have installed GALAXY 8.0 rom on my s7. It comes rooted, with magisk, custom kernel. Everything you set up in aroma.
As for twrp part i used this https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
After installing twrp, flash rom with it. Hope that helps.
https://androidfilehost.com/?fid=24591020540823532
This is the link I got myself a boot.img
Used it on 935F, also im not responsible if you mess up your device even more but it worked for me.
BTW its worth mentioning my s7e using exynos

Cheers for this, this seems way more logical than what I have been trying to do. I will try this now.
Thanks