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
Related
I know we have a thread for all the ROMs but we just got included in the new update for ROM manager so the EVO is supported. What do we need to do to start getting our ROMs on there? If there is anything I can do please let me know!
134 views and no one at least agrees?
mastermayhm069 said:
134 views and no one at least agrees?
Click to expand...
Click to collapse
aww, its ok... +1
mastermayhm069 said:
I know we have a thread for all the ROMs but we just got included in the new update for ROM manager so the EVO is supported. What do we need to do to start getting our ROMs on there? If there is anything I can do please let me know!
Click to expand...
Click to collapse
To get added to the ROM list, and use the OTA system and customizers, etc, devs should follow the instructions here:
http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
There's like 2 dozen ROMs for Droid listed (as well as a bunch for N1/Dream/Sapphire). Hoping to build up the Evo community on it as well!
Id love to see a guide on [HOW TO] install this on evo..
joey3002 said:
Id love to see a guide on [HOW TO] install this on evo..
Click to expand...
Click to collapse
Go to the market, search for "ROM Manager" and press install.
lol, i got that part.. I just found this:
http://forum.xda-developers.com/showthread.php?t=699043
on how to install it..
Im doing this for you bugless... i want your rom
thanks
BuglessPete said:
Go to the market, search for "ROM Manager" and press install.
Click to expand...
Click to collapse
I thought rom manager required flashing it's own customer recovery. Is this not the case anymore or has clock figured out how to flash a recovery to the evo???
dcmtnbkr said:
I thought rom manager required flashing it's own customer recovery. Is this not the case anymore or has clock figured out how to flash a recovery to the evo???
Click to expand...
Click to collapse
All I did was flash a rom manger friendly rom and installed it. Went to market and downloaded rom manager. Then loaded it and downloaded clock boot from there. Went through that process.
Now I just click reboot to recovery from rom manager and it boots me right into the custom clock recovery and you can do however from there.
It's worth every penny!!!!!
Sent from my EVO via Tapatalk!
dcmtnbkr said:
I thought rom manager required flashing it's own customer recovery. Is this not the case anymore or has clock figured out how to flash a recovery to the evo???
Click to expand...
Click to collapse
not yet but toast and maejrep say they do have a method to flash /recovery its just manual and includes an older version eng hboot.
the clockwork rom manager method basically puts itself into an update.zip which is signed so the stock HTC recovery loads it and bam! custom recovery appears!
im still wondering how hes able to sign an update.zip file which HTC allows cuz IMO, that was the missing key!
joeykrim said:
not yet but toast and maejrep say they do have a method to flash /recovery its just manual and includes an older version eng hboot.
the clockwork rom manager method basically puts itself into an update.zip which is signed so the stock HTC recovery loads it and bam! custom recovery appears!
im still wondering how hes able to sign an update.zip file which HTC allows cuz IMO, that was the missing key!
Click to expand...
Click to collapse
This is absolutely great news. Seriously. Friggen fantastic!
just bought this app ( my first paid app ) well worth the 3.99
joeykrim said:
not yet but toast and maejrep say they do have a method to flash /recovery its just manual and includes an older version eng hboot.
the clockwork rom manager method basically puts itself into an update.zip which is signed so the stock HTC recovery loads it and bam! custom recovery appears!
im still wondering how hes able to sign an update.zip file which HTC allows cuz IMO, that was the missing key!
Click to expand...
Click to collapse
It's just a test signed zip that does a hot recovery replace (it doesn't actually flash). You guys are running a Test HTC image, so test keys work on it.
Will this work with Froyo?
TREYisRAD said:
Will this work with Froyo?
Click to expand...
Click to collapse
I was going to test it and I keep running into problems.
Maybe it's the ROM Manager? It won't auto reboot (maybe I don't get the whole idea) and if I manually try to update it with the recovery mode with update.zip, it fails immediately.
Anyone else having this issue?
I notice that when installing the recovery, there is a update.zip place in the root of the SD card. I think that is the recovery file. Anyway, I did a reboot to recovery mode, and it worked no problem. Reboot the phone again, it will boot back into android OS.
Man..this one sick program but brilliant.
PS. Got the paid version also. I think this will comes in handy later.
Koush said:
It's just a test signed zip that does a hot recovery replace (it doesn't actually flash). You guys are running a Test HTC image, so test keys work on it.
Click to expand...
Click to collapse
yea the hot recovery flash is not a big surprise ...
aaahhhh, the test HTC image part with the test keys, that makes so much sense!
sorry for the n00bness, still new to signing zips. where can test keys which work on the Test HTC image be obtained from?
joeykrim said:
yea the hot recovery flash is not a big surprise ...
aaahhhh, the test HTC image part with the test keys, that makes so much sense!
sorry for the n00bness, still new to signing zips. where can test keys which work on the Test HTC image be obtained from?
Click to expand...
Click to collapse
The ones found in the android source
does anyone know if rom manager will work if you used the unrevoked method to root?
This won't work on unrevoked. It requires rooting via toast's method using the test image. You can find instructions for this method in the sticky thread pg 1 of this forum, how to root the HTC EVO.
rgds,
frank
-------------------------------------
Sent via the XDA Tapatalk App
Just tested out and confirmed that the Motorola FlipOut Recovery also works for the Motorola Flipside. Apparently the flipside/flipout/charm software are all pretty interchangeable. I plan to find more info about the non-blur version of the ROM for the Flipout and see if that also works. Anyways, here is the link for the FlipOut Recovery...just follow the simple instructions and should you have a recovery in a matter of minutes! Hope this hleps!
http://modmymobile.com/forums/624-m...90-flipout-recovery-cwm-based-v2-5-1-2-a.html
Use my recovery it's more advanced :3
will do...do I just put it on the sd and install from sd?
Nevermind....got it installed...whats the difference between bootstrap recovery and reboot recovery?
so jballin.. what's your opinion? which one would you prefer to recover with, the one from modmy or the one polovina suggested which would be his recovery.. called bootstrap?
JBallin4life27 said:
will do...do I just put it on the sd and install from sd?
Nevermind....got it installed...whats the difference between bootstrap recovery and reboot recovery?
Click to expand...
Click to collapse
Look at code.
My code is more compact and it written in C not shell
Vahnyyz said:
so jballin.. what's your opinion? which one would you prefer to recover with, the one from modmy or the one polovina suggested which would be his recovery.. called bootstrap?
Click to expand...
Click to collapse
Hmm tough to say...they both seem pretty similar to me...either seems to get the job done well enough
JBallin4life27 said:
Just tested out and confirmed that the Motorola FlipOut Recovery also works for the Motorola Flipside. Apparently the flipside/flipout/charm software are all pretty interchangeable. I plan to find more info about the non-blur version of the ROM for the Flipout and see if that also works. Anyways, here is the link for the FlipOut Recovery...just follow the simple instructions and should you have a recovery in a matter of minutes! Hope this hleps!
http://modmymobile.com/forums/624-m...90-flipout-recovery-cwm-based-v2-5-1-2-a.html
Click to expand...
Click to collapse
Could you give us steps to install custom rom for flipside?
sharethl said:
Could you give us steps to install custom rom for flipside?
Click to expand...
Click to collapse
unfortunately, there are no custom roms out yet. Im sure our wonderful developers will come up with something.
How enter the CWM recovery? My phone kept restarting!
Anyone put this on froyo yet?
Sent from my MB508 using Tapatalk
tisk said:
How enter the CWM recovery? My phone kept restarting!
Click to expand...
Click to collapse
It wont work for FLIPSIDE, so no point in getting frustrated over trying. Does not recognize our phone.
Sent from my MB508 using XDA App
rignfool said:
Anyone put this on froyo yet?
Click to expand...
Click to collapse
I would, but it messed up for me with eclair, so I wont try with froyo. Got enough bugs without adding more.
Sent from my MB508 using XDA App
I tried both on Froyo, just to see... polovinamozga's release claimed to install correctly, but when trying to reboot into recovery, it would just boot loop. Pzyduck's release (modmymobile.com) also installed, and actually rebooted into recovery, but the recovery did not work correctly. Trying to make a nandroid backup caused it to spit out an error when it hit the /data partition. Both worked fine for me on Eclair, so I think we're going to need a recovery of our own now.
I have froyo 2.2.2 on my flipside. When I install the recovery apk and run it, the flipside sticks in reboot mode. And then I have to reinstall froyo.
Rocky
Any idea when someone will port a recovery that works with froyo?
Boot Loop
when you had it boot looping how did you get it out of the boot loop and restore it
i tried installing this on froyo and after installing i get this on boot up tried flashing and downloading over again but to no prevail
Bootloader
91.7B
Err:A5,70,70,00,1F
NEW_MAP Blank
service Req'd
Battery OK
OK to program
transfer mode:
USB
nowseewhatudid said:
i tried installing this on froyo and after installing i get this on boot up tried flashing and downloading over again but to no prevail
Bootloader
91.7B
Err:A5,70,70,00,1F
NEW_MAP Blank
service Req'd
Battery OK
OK to program
transfer mode:
USB
Click to expand...
Click to collapse
Froyo needs an updated bootloader. Posted somewhere in here, but if you can't get into rsd mode to flash, you may have a problem. Btw, this recovery also does not work with froyo only eclair.
Sent from my MB860 using XDA App
i was able to flash this thanks
SAGE_U3_3.4.2-159.17_SecATT_SIGNATT_USASAGE02B25ND0ATTNA02E.0R_S AGEFRATT_P011_HWp4_1FF.sbf.gz
I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.
bobharding said:
I have an HTC Explorer and have installed CM 9 easily. Unlock bootloader through HTC , install custom CWM recovery using fastboot, then install CM 9 zip from sd card using CWM recovery. I have tried to do the same with my daughter's Wildfire. I get as far as installing a CWM recovery but it hangs at a "hat" icon when I try to use it. I have tried several CWM img files, including the one in the "cm49?" zip. None work. Is there a way for me to get a CWM recovery working? I don't want to go through all the s-off process, I don't think it is needed. My Explorer works great with s-on. I hope someone can help. I promised my daughter I would get ICS on her phone as her Christmas present.
Click to expand...
Click to collapse
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?
miniAndroidian said:
If I'm not mistaken you have to flash the boot.img manually with S-ON so I think a S-Off'd device is much better and it isn't that hard to S-Off it. I don't know if the S-Off methods still work if you unlocked it before but they should.
Besides you haven't taken the CWM from Pico/Explorer and tried to install it on the Wildfire, have you?
Click to expand...
Click to collapse
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.
bobharding said:
Thanks for your reply. All the cwm img files I have used have come from this forum. I had high hopes for the one I extracted from "pc49img.zip" as it seemed to say it might work on another post. It installed like the other but doesn't work.
Click to expand...
Click to collapse
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide
miniAndroidian said:
I got a question are you just unlocked or already rooted on the WF? I think you can't install CWM if you're not rooted. That would be nice to know. Otherwise you can may follow this guide
Click to expand...
Click to collapse
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.
bobharding said:
Just unlocked after following the procedure on "htcdev.com". With my Explorer you can root the phone with the aid of the CWM recovery you install after unlocking it. Maybe the CWM recoveries for Wildfire assume your phone is already rooted, but I don't know how to root it without having a working CWM recovery first.
Click to expand...
Click to collapse
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.
miniAndroidian said:
Yeah you're right. I think the progress on S-ON should be like this:
-flash CWM
-flash superuser rights (thats how it worked on the HTC One X)
I found this:
http://forum.xda-developers.com/showthread.php?t=1484124&highlight=recovery
Let me know if it worked.
Click to expand...
Click to collapse
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.
bobharding said:
Thanks for all your help miniAndroidian (the Nexus 4 should be awesome, (I am saving up, but they are not available in Australia at the moment. I told my daughter she should get one too, but she hasn't got the money either, so that's why I am working on the Wildfire)
Unfortunately the post you directed me to says you have to flash the CWM recovery from the stock recovery but I don't have that anymore as I have replaced it with the CWM recovery which just hangs. There must be a way round it, but I am no expert at all.
Click to expand...
Click to collapse
Same in Germany with the Nexus 4 but it should be avalible in the middle of january
Back to the topic:
You have to put the "update.zip" to the root of your SD-Card and boot into the bootloader menu (the white screen with 3 android's on the bottom) and then it should recognize the new CWM.
Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.
bobharding said:
Terrific. I didn't understand it. My daughter lives 100km from me so I will have to visit her this weekend. She left after Christmas saying "Dad, admit it you are a failure" after I had spent hours on it, so this might show her I am not as useless as she thinks. I am intending to flash the "mini" CM 9 rom. I hope this is the best one.
Click to expand...
Click to collapse
I really hope it works (i'm out of solutions ) otherwise you should really think about S-Off'ing it.
miniCM 9 is the fastest one but the sensor buttons don't give a vibration feedback it's a kinda annoying.
Good luck
I have had a very very frustrating day. I tried "update.zip", didn't do anything. I even renamed it "pc49img.zip" nothing. I finally found a windows program called "unlock root". I used the free version. You just connect up the phone via usb and press root. It gets you to confirm it is a wildfire and then after a bit says successfully rooted. I then installed Superuser, Rom Manager and ES File Explorer to check it.
I backed up the present rom successfully with Rom Manager. It even has an option for flashing Clockworkmod recovery and one for rebooting into recovery for manual management. It downloads CWM recovery 5.0.2.0 but it doesn't work either (looking at the files on the SD card I think it is just the same as the "update.zip"). There is also an option for installing a rom from sd card but when I went to this it asked if there was any addon, and of course I need tiny gapps. It then said I need the paid version for this. Seeing the recovery didn't work I didn't want to risk it.
My conclusion is all the present CWM recoveries require S-Off. I have read some people like the Aroma installer. I know nothing about it, but I wonder if it might be possible to install the CM 9 rom with it.
I have worked out what my problem has been. I have fallen for the old Trackball trick. I must be the only person not to know you use the Trackball in CWM recovery not the power button. I sent my daughter an email and she has confirmed the recovery in Rom Manager actually works when you use the Trackball. I will have to visit her again now to install CM 9.
MiniCM9 installed. Working great. I will put a how to in "General"
I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
Doesn't work:
Basically everything. You can only boot into CWM, and scroll using the Volume keys, but you can't select anything.
WiFi glitches on first reboot. To get WiFi working again, forget the connected WiFi network, and disable WiFi, then reboot.
NOTE: I have personally flashed this recovery image, and works, but FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Built second test build!
RoboticBuddy said:
I have built a CWM recovery image for the AT&T Fusion 2. If anybody would like to test it out, here is the link.
http://jenkins.cyanogenmod.com/job/recovery/18266/
NOTE: I have not personally flashed this recovery image as of now, so FLASH AT YOUR OWN RISK. Enjoy! :cyclops:
Click to expand...
Click to collapse
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Shagerty said:
Flashed the img I am able to scroll up and down in CWM but not select anything. I went ahead and make a second build using recovery.img and the fstabs file. Still no more functionality, so I am searching for the graphics.c file and the postrecoveryboot.sh file.. I cannot find them.. YET
here is my version of the second build for the fusion 2 https://www.dropbox.com/s/r281aa12zko1brr/recovery.img try it with the installador tools from the fusion 1! (i will write a guide later..)
Anyone have any advice on how to find the files? I am guessing they are needed to get CWM working. This is my first build though, and any help will be GREATLY appreciated.
Just built my second build and third total for the fusion 2. The second worked fine, but not any better than the first. The third wouldn't boot into recovery. The third incorporated what I thought was the postrecoveryboot.sh
Click to expand...
Click to collapse
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
RoboticBuddy said:
I have been searching for those files as well, but being new to this, I don't know what they are used for
And your own build of CWM, isn't it the same thing as mine?
And you can just flash it over to the phone using fastboot; "fastboot flash recovery recovery.img". . . .
Click to expand...
Click to collapse
In the second build I used the recovery.img and fstabs files. No more functionality. Third build I used the recovery.img and the fstabs and what I thought was the postrecoveryboot.sh. it wouldnt load on the third build.
I found a tool that pushes the recovery.img files with the click of a button.
Thanks guys!
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
I am certainly shooting for it! But am in the same boat! I'm just getting into developing. Learning java code right now but I am just scratching the surface.. I would greatly appreciate your assistance as much or as little as you know the help is awesome! Like you said it is a little known device. We need all the help we can get!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
CenterTurkHD said:
Hey guys it's great that you two are working on a CWM recovery for this 'not very well known' device. I would love to help, if you need me to do anything just ask! My brother is getting into some more development with his device (Galaxy Player 4.2) and he might be able to help, I'm not a developer but I could start learning . Anyways, will you guys be able to build a CM10/JB for this device?
Click to expand...
Click to collapse
I'm too busy with school to start learning Android development, so I just can't really work on this device that often.
First of all, we need a working CWM before we can move on to ROM development.
Thanks for your future help!
Sounds great
Wow, sounds great guys! And I will keep completely up to date with this. I am also busy with school, but I do have time at home to do things with this [project]. I'll post and keep you guys updated if I can find or improve on anything!
Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?
This would be the wrong section, but that's alright it'll get moved once a moderator sees it if I'm not mistaken! I don't think that method will work at all tbh.
tasar said:
Hi,
i hope its the right section here. As we known, the bootloader isnt able to open at the moment. I know this problem from some other device and there its possible to use an temporary CWM.
I found THIS here at XDA but it doenst work on Zenfone 2, error is unknown trigger
Is here someone that can it make usable on our Zenfone 2?
Click to expand...
Click to collapse
Thanks for pointing out
It works! Well, at least i can start CWM, but i didn't try functionality yet.
Use this version: http://forum.xda-developers.com/showpost.php?p=60770086&postcount=352
Choose T4 option.
You will get some distorted animated logo at the center for several second, then you will get CWM menu.
Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!
Need CWM version compiled for Zenfone 2.
sorg said:
Need CWM version compiled for Zenfone 2.
Click to expand...
Click to collapse
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.
Reviewers said:
It's not as easy as you think, we have an locked bootloader so in-order to compile or install the CWM/TWRP recovery it'll be possible.
We need our bootloader unlocked first by ASUS which might take a few weeks/months (No ETA) yet.
Click to expand...
Click to collapse
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
tasar said:
Thanx, i allready found this version and i came into CWM, backup seems to work without errors but after restore, it ends in a bootloop Restore runs without erros but when i reboot it hangs for a while in Asus bootlogo and then it reboot to recovery. Clear cache, data but nothing help.
Must completly new flash
And sorry for wrong section!
Click to expand...
Click to collapse
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.
sorg said:
Who "we"? I'm using Zenfone 2 as well.
And if i told above "It works!" then it means it works (at least it starts), ok?
It means, that fastboot hack works on Zenfone 2 and allows to run any unsigned code, i.e. CWM recovery. The only problem, is correct configuration of recovery and other binaries included in CWM package.
According to you reply, you even didn't try by yourself.
---------- Post added at 10:53 PM ---------- Previous post was at 10:49 PM ----------
Zenfone 2 uses SELinux in enforcing mode. So, after restore, if extended attributes didn't applied (and i believe it didn't) then Android won't boot.
So, this hack is more a Proof-Of-Concept. Need to compile and create correct CWM package.
Click to expand...
Click to collapse
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM
Reviewers said:
"We" as in everybody in this forum would need the bootloader unlocked.
I've spoke to people who compile CWM + TWRP and they said that even if you were able flash something, you'd have to fastboot flash it every-time you boot.
I tried and this temporary CWM recovery did indeed work, I actually tried it about 30-40 minutes ago.
But yes, this is a great step into development!
We have pre-root on the latest firmware which is 2.17.40.12.
Now we have temporarily CWM
Click to expand...
Click to collapse
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).
sorg said:
Compiling CWM has nothing to do with locked bootloader. Either you flash it permanently or temporary, in both cases you need recovery compiled correctly for specific device. Each device has specific features. And if you want to use CWM fully, it should know about these settings. I've found already this version cannot mount SD card for example. So, i have to manually insmod texfat.ko module and then mount. So, recovery definitely needs additional tweaks or even compilation.
Actually, having temporary CWM is enough. I've made batch file to start it by one click and then can do whatever i want.
The only difference from permanent CWM is unable to use it when you are not at home. But in several years of using Android phone i didn't use recovery outside my home
One reason less to unlock the bootloader.
P.S.: This kind of hole in security can be patched in future versions of fastboot, so it's wise to stop updating fastboot (droidboot.img) and bootloader (ifwi.zip).
Click to expand...
Click to collapse
can you share one click batch file with us? if we only could back up the rom it would be awesome..
With this temporary CWM custom recovery, am I able to flash any zips in it? Sorry about the noob question, wanted to use it to flash the disguised version of Cerberus.