Is it possible, and how do i do it?
Currently that is a complete no.
Allright, that sucks
Allright, that sucks
Click to expand...
Click to collapse
No, that's the hard work of Paul and the other folks that allow you to play with your Desire today.
-------------------------------------
Sent via the XDA Tapatalk App
Possible , enter in fastboot , then recovery. In recovery press vol-&vol+&power. You will see a recovery screen with some option (wipe , flash update.zip etc).
really .....
michaldepta said:
Possible , enter in fastboot , then recovery. In recovery press vol-&vol+&power. You will see a recovery screen with some option (wipe , flash update.zip etc).
Click to expand...
Click to collapse
Please, giving infos to people is supposed to help them, not to confuse them. The recovery you're speaking about (that, actually, IS a recovery) is almost useless for the average XDA-Developers' user since is unable to flash anything that is not digitally signed by HTC.
So, the right answer to the original question is, as already stated, NO. There are efforts all over here in order to keep the modded console on the sdcard or to flash it into the device, but that's impossible to achieve to date.
Guys, i just want to make clear that i did not mean that the recovery today SUCKS but i just ment that it sucks that htc has implemented this protection.
But anyways, Paul at Modaco is my God, i really adore that guy
I am sorry if anyone missunderstud me before
Related
It shouldn't be that hard correct? I mean I downloaded rom manager and it flashed a DroidX recovery image to my phone successfully. But when I tried going to it it wouldn't bring me to the recovery image just the phone with the green triangle. So if someone just tweaked the DroidX recovery image I believe the Defy could have a simple and quick recovery image.
I'm no developer, but I doubt it would not be just a tweak.
From what I understand DroidX has a different security level than the Defy. In the Defy we will have to use bootstrap to get a recovery working for now, much like Milestone 2. I'm trying to get a recovery working on the Defy, but I haven't had much time this week, but yes, once recovery it's done making a nandroid backup image should be pretty easy .
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
pedrodh said:
From what I understand DroidX has a different security level than the Defy. In the Defy we will have to use bootstrap to get a recovery working for now, much like Milestone 2. I'm trying to get a recovery working on the Defy, but I haven't had much time this week, but yes, once recovery it's done making a nandroid backup image should be pretty easy .
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
Click to expand...
Click to collapse
Take a look here my friend: http://twitter.com/HandlerExploit
This guy is working on CustomRecovery and deblured ROM AFAIK..
Maybe he can help you or you can help him.. Whatever.. Help US
Thanks!
pedrodh said:
If anyone else it's working in a recovery please let me know. At the time I'm looking at porting the open recovery to Defy.
Click to expand...
Click to collapse
I have a Milestone with OpenRecovery. Remember that to get OR working in the first place, a Milestone user has to flash a recovery-only SBF that downgrades to a "vulnerable" version of stock recovery which allows non-Moto-signed .zip files to flash.
Is the Defy stock recovery vulnerable as well? If not, then OpenRecovery might be a dead end. Basically I think we've seen a number of different levels of security in terms of recover for Moto devices:
1) No security at all
The original Droid, as well as the Cliq/Dext and maybe others fall into this category. You can flash a non-Moto update.zip to gain root, and you can install a custom recovery with flash_image that will work.
2) Non-replaceable but vulnerable
The Milestone falls into this category. I think the locked bootloader will fail to work with a custom recovery. However the vulnerable stock recovery (version 2e) can be flashed by SBF onto any device with any version OS. The vulnerable recovery lets you branch out to custom recovery on SD via update.zip (e.g. OpenRecovery)
3) Non-replaceable, not vulnerable
The Droid 2, Droid X and possibly others fall into this category. You can't flash a non-Moto update.zip, and you can't replace it due to the locked bootloader. No signed SBF exists that will add a vulnerability to the recovery. Thus the bootstrap hack is the "next best option".
So the viable options for the Defy will depend on which security level it has.
I can't yet confirm this, but the Milestone 2 might have OpenRecovery, using bootstrap method. That means, whatever security Defy has, it will still be possible. But I'vent had time lately to start working on this. Once I do, I'll take a closer look on how things play out. Maybe HandlerExploit will find is way first than I do, if so, better for me
open recovery with bootstrap isnt a problem. since the defy doesnt have a camera key changes to the key mapping we need to adapt it to touch since the original stock recovery is touch as well... it should be out very soon. If anything it will be posted first on modmymobile (skirlax is the one who does all the open recovery)
Right, but I'm still wondering: is the Defy sufficiently locked down that the custom recovery *must* be a bootstrap? Or can we do better?
Sent from my Nexus One using XDA App
Isn't this the recovery image we need?
i can confirm the bootstrap is working great! using it right now.get fullly rooted,insecured boot.
Very good news !
tenfar said:
i can confirm the bootstrap is working great! using it right now.get fullly rooted,insecured boot.
Click to expand...
Click to collapse
Hey,
that sounds really interessting. Would you mind telling us more about the efforts you already made?
Are you talking about a bootstrap recovery method like we have one for the Droid X / Droid 2 ?
That would be GREAT!
Will the recovery image work on the Motorola Bravo when it comes out? The specs are practically identical except for the camera. Reason I ask is because there is practically no dev section for the Bravo. I've been able to root it and remove all the bloatware but would really like to be able to backup the phone.
Why is it people are still saying that we need a revcovery when one has been posted several weeks ago on another forum?
It's over at mod my mobile (I'm still not aloved to post links...)
pomah said:
Why is it people are still saying that we need a revcovery when one has been posted several weeks ago on another forum?
It's over at mod my mobile (I'm still not aloved to post links...)
Click to expand...
Click to collapse
I'm following just about every forum with a defy section, including modmymobile, and I am not seeing any custom recovery image. There are nuff theads telling you how to get into "recovery mode" but this is not what we need to be able to flash roms
Higgsy said:
I'm following just about every forum with a defy section, including modmymobile, and I am not seeing any custom recovery image. There are nuff theads telling you how to get into "recovery mode" but this is not what we need to be able to flash roms
Click to expand...
Click to collapse
I tried to make a recovery, but failed.
I managed to extract the original recovery and unpack with "unpack-bootimg.pl" from http://android-dls.com. But even if I do not change anything (kernel/img) and just repack it, I got a "Err:A5,69,35,00,2F" on recovery boot.
What I seen is that on defy we have no NAND flash (mtd) device, all is on 2Gb mmcblk(1) device.
In my opinion the recovery is signed....
Ok, I guess than that it's not the recovery posted in http://modmymobile.com/forums/639-m...motorola-defy-system-boot-recovery-dumps.html
Actually, the post there says it all: "I hope u can use them to create custom roms "
And what about the Rom Manager app?
Sent from my MB525 using XDA App
Hi there,
Currently have cyanogenmod recovery 2.5.0.1 and want to upgrade to the latest (5.0.0.?)
Have tried doing this via ROM Manager, but it simply says it's installed and reports the latest version number, but when I restart in recovery it's still displaying the old version (and has none of the new features, i.e. - it hasn't updated at all)
I've read some guides on forcing ROM Manager to install newer or different .img's, but I can't even see any .img's it's downloaded. Are the downloads just failing?
Any help would be really appreciated!
Thanks in advance!
Does this look like Q&A section to you?
Yes, yes it does.
See ^^
Q, then A.
velkrosmaak said:
Yes, yes it does.
Click to expand...
Click to collapse
Nope it's not. This here is the link to the Q&A section.
http://forum.xda-developers.com/forumdisplay.php?f=689
As for your question, there are two ways of accessing recovery. One is via ROM manager and the other is from hboot menu.
ROM manager is a good software and still is. But for our Desire, it gives us problems or at least confusion like the one you are having right now. After you updated the recovery how do you access it? Do you access it via ROM manager or from the power menu (alternatively vol down+power)?
The recovery you access from the power menu or alternatively, via vol down+power, is independent from the one you access using ROM manager. That's probably where you are getting confused right now. If you downloaded the update from ROM manager, then you ought to launch recovery from ROM manager as well.
So in a nutshell you have two recoveries. You updated the one from ROM manager but you are probably launching the other that wasn't updated.
Thank you stankyou (haha!) for the response!
Even when I boot into recovery from ROM Manager I get to the old version of the recovery, 2.5.0.1. Very odd. Someone has suggested using fastboot to flash this? Does this sound like a plan?
Booting to recovery with the power button & volume down yields the same as rebooting into recovery from ROM manager or the restart menu (using Runnymede AIO)
velkrosmaak said:
See ^^
Q, then A.
Click to expand...
Click to collapse
Tell me, do you pretend to be idiot, or you were born as idiot?
I'd say idiocy was genetic, so actually I was born this way, 'fraid I can't help it.
Seriously though, it's time to grow up. It's a forum - by definition - it's a place where people discuss topics.
Yeah, so the odd post may end up in the wrong forum - but if we all act like little kids every time that happens, the place won't be very nice to frequent.
Cyanogenmod recovery? Not ClockWorkMod? - but hey, it was said a hundred times, how to replace the recovery (including update) - S-OFF needed - and yes you can use the fastboot to flash the newest one (even with Android Flasher).
velkrosmaak said:
Thank you stankyou (haha!) for the response!
Someone has suggested using fastboot to flash this? Does this sound like a plan?
Click to expand...
Click to collapse
Yes personally that's what I did for my phone. I ditched ROM Manager a long time and replaced Clockworkmod with 4EXT recovery by flashing. I was S-Off when I flashed a different recovery if that matters.
velkrosmaak said:
Seriously though, it's time to grow up. It's a forum - by definition - it's a place where people properly discuss topics.
Click to expand...
Click to collapse
Fixed.
10char
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??
slixter said:
Hello peeps,
I've just come from an iphone so please forgive my stupidity. I've been looking around XDA and various other places for 2 days trying to sort my One X, but don't seem to be making any progress.
I currently only have access to the bootloader
I managed to unlock and root the phone, but then got stuck on a boot loop which I haven't been able to get out of. I was able to get into the OS, but had no cell or wifi, but now I'm just stuck in the bootloader after a failed flash of probably an incorrect RUU. The phone has been relocked.
I ran Vtool from post 7 here http://forum.xda-developers.com/showthread.php?t=1989358, and my main version is 2.17.206.2
I'm in the UK on the o2 network.
Can someone please help??
Click to expand...
Click to collapse
ok but what do you want to do now? keep it unlocked or not?
matt95 said:
ok but what do you want to do now? keep it unlocked or not?
Click to expand...
Click to collapse
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM
slixter said:
I'd like to unlock it with a custom rom, but I'm quite happy just to have a working phone again.
Additional info, I also have access to CWM
Click to expand...
Click to collapse
Phone is also unlocked again using Hasoons all in one kit.
Happy to hear of a fellow iphone convert :thumbup:
Is there something in particular you did that caused the boot loop?
Do you by chance have a nandroid backup?
jonnyboiii said:
Is there something in particular you did that caused the boot loop?
Click to expand...
Click to collapse
I've got no idea to be honest.
I've got no back ups.
If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.
jonnyboiii said:
If you have access to cwm then you're not totally out of luck, I think your best option would be to flash a stock rom for your particular phone.
Click to expand...
Click to collapse
Can you direct me to a stock rom?
did you flash the boot.img when you got bootloops?
matt95 said:
did you flash the boot.img when you got bootloops?
Click to expand...
Click to collapse
Pretty sure i didn't
slixter said:
Pretty sure i didn't
Click to expand...
Click to collapse
that's why you got bootloops... when you flash a rom you need to flash its boot.img too
matt95 said:
that's why you got bootloops... when you flash a rom you need to flash its boot.img too
Click to expand...
Click to collapse
So do i need to flash the boot.img and the rom from CWM and I should be ok?
Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.
jonnyboiii said:
Just look around in the One-X forum, do some searching, see if you can find a stock rom to download to your computer then move to your phone.
CWM has this handy feature I think in the "mount" tab, where you can mount your phone as a usb device, from which your computer will pick it up and you'll be able to move the roms file to your phone for flashing.
Click to expand...
Click to collapse
Thanks for the info - think I have a rom I can use.
1 more question before i continue, how do i flash the boot.img file? I have a zip with the rom / boot.img
I have mounted as usb storage and copied the zip file across
I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM
slixter said:
I've installed CM, after wiping cache, dalvik, system etc, but seem to be stuck on the JB animation screen.
Wondering if this means the OS is installing, or if I'm still stuffed....
I don't know if I need to do something with the boot.img file as the onlyl thing i did was load the zip file for CM
Click to expand...
Click to collapse
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.
jonnyboiii said:
Personally I've flashed a total of three roms which isn't many, but in all my time spent reading threads of the latest and greatest roms I've never heard anything about a separate boot.img that you needed to flash... (perhaps a One-X specific thing?).
Just be patient with it when it's booting, the first boot after an install always takes longer.
Click to expand...
Click to collapse
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.
How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.
slixter said:
I do need to flash the boot.img first.
I'll do that once my battery gets some more charge.
Click to expand...
Click to collapse
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly
jonnyboiii said:
How much charge does it have right now? It's important to always go into using CWM on a substantial amount of battery life. Upwards of %50 is recommended, but but you should do just fine with around 30, that is assuming you're able to tell.
Click to expand...
Click to collapse
How do you tell how much charge it has?
matt95 said:
download the rom's boot.img and type with the phone in fastboot mode:
Code:
fastboot flash boot path/to/boot.img
after that your phone will boot up correctly
Click to expand...
Click to collapse
Fastboot won't let me flash cos of the low battery, so will let the phone charge for a bit then try again. Thanks.
I have tried to install the 4EXTRecoveryUpdater.apk into my phone and it forced me to try the 4EXT Recovery Control for three days.
1. While I am trying to perform "online install" and "check for news", it required me to install Busybox (however I haven't rooted my phone).
2.The app just shows error and turn off and back to the main screen when I try to connect to the 4ext's server.
Can anymore answer what can I do? Should I just wait for the three day so that the 4EXT Recovery Control will expire?
Is there any setting I can do to fix the "error" while connecting to the 4ext's server?
Really Thanks a lot.:angel:
stc01023 said:
I have tried to install the 4EXTRecoveryUpdater.apk into my phone and it forced me to try the 4EXT Recovery Control for three days.
1. While I am trying to perform "online install" and "check for news", it required me to install Busybox (however I haven't rooted my phone).
2.The app just shows error and turn off and back to the main screen when I try to connect to the 4ext's server.
Can anymore answer what can I do? Should I just wait for the three day so that the 4EXT Recovery Control will expire?
Is there any setting I can do to fix the "error" while connecting to the 4ext's server?
Really Thanks a lot.:angel:
Click to expand...
Click to collapse
4ext updater is related to the recovery app. If you are not rooted and S-OFF, you won't be able to run an app that modifies a partition such as recovery. The app will not expire but won't work either...
As far as I know, the app can't gain access to the recovery partition without root privileges. I could be wrong though...
Sent from my HTC Desire HD using Tapatalk 2
mushtafa said:
As far as I know, the app can't gain access to the recovery partition without root privileges. I could be wrong though...
Sent from my HTC Desire HD using Tapatalk 2
Click to expand...
Click to collapse
Thanks for above, I am trying to install that before rooting my device, may be I try ClockWorkMod Recovery then.:crying:
stc01023 said:
Thanks for above, I am trying to install that before rooting my device, may be I try ClockWorkMod Recovery then.:crying:
Click to expand...
Click to collapse
You can't install a recovery, CWM or 4ext, if you don't have permission to write to a partition. You can only get permission to write to a partition with root and S-OFF (AAHK) or an unlocked bootloader (HTCDEV).
The whole point of rooting (tethering and a couple other goodies aside) is to allow you to install a custom recovery and use it to install custom ROMs.
bananagranola said:
You can't install a recovery, CWM or 4ext, if you don't have permission to write to a partition. You can only get permission to write to a partition with root and S-OFF (AAHK) or an unlocked bootloader (HTCDEV).
The whole point of rooting (tethering and a couple other goodies aside) is to allow you to install a custom recovery and use it to install custom ROMs.
Click to expand...
Click to collapse
Oh....As I am an idiot on technology, Just seeing whether can be more safe to root my phone........:crying:
stc01023 said:
Oh....As I am an idiot on technology, Just seeing whether can be more safe to root my phone........:crying:
Click to expand...
Click to collapse
Read the guide in post #7 of the Ace Think Tank thread in my signature. It will give you all the instructions you need. Come back and ask if you have questions.
He thanked everyone that said what I had said...why??????? :crying:
LOL
glevitan said:
He thanked everyone that said what I had said...why??????? :crying:
LOL
Click to expand...
Click to collapse
I'm out of thanks for the moment, but as soon as I get a spare I'll shoot you one to make up for it.
Although, I'm not seeing thanks from him on this thread...?
bananagranola said:
I'm out of thanks for the moment, but as soon as I get a spare I'll shoot you one to make up for it.
Although, I'm not seeing thanks from him on this thread...?
Click to expand...
Click to collapse
Noobs seem not have an easy thank push...It should be compulsory to thank your elders...
hi i got htc one x running jely bean 4.1 -- cid j_15 -- i unlocked the boot loader successfully -- i copied the supersu to the phone then i booted into recovery but in recovery i got a red triangle over a phone so cant extract the supersu -- i tried volume up plus power but no menu happen -- how to complete the rooting
note- i want to do rooting because i want to install a custom rom because my phone keep getting restarted every know and then by itself
What recovery do you use ? If you are on stock recovery, then you have to flash a custom one first...
To do so go to the clockworkmod recovery website and download the Touch recovery for you'r model, then you need to put you'r phone into fastboot usb mode and run fastboot flash recovery recovery.img, and reboot into recover...
From there you go to install zip, and choose SuperSU.zip, without extracting it... Once it finishes, reboot the phone and you are done.
copy SuperSU on your phone
Flash this
https://www.dropbox.com/s/od4y330zg5brviw/recovery.img
go into recovery (Strongly recommend nandroid backup), install zip from SD card, Click super SU
thanks desmond you solve my problem
thanks stevan0vic for your help
Just to remind you, since I see this is you'r first post...
If a post is helpful to you please click on the thanks button at the bottom of that post since it helps you and us progress
desmond1303 said:
Just to remind you, since I see this is you'r first post...
If a post is helpful to you please click on the thanks button at the bottom of that post since it helps you and us progress
Click to expand...
Click to collapse
How does that progress you ? Serious question. If i asked everybody to thank me with a helpfull post i would be well over 10000 thanks. But i don't .... I think its kinda rude in a way, feels the same to me when a developer is asking for money !
He will see the button....maybe not in this case but maybe the next. He thanked you personally. If you are in it for the amount of thanks you get then you are here for the wrong reasons !
Sorry, I didn't mean to be rude.
Nor do I want to collect many likes.