I am starting to work on porting gweedo767's touch recovery to the captivate. This is still a work in progress. I need help knowing how to actually install a recovery.img or recovery.tar.md5. I have tried flash_image, dd, and Odin. None work for me. PLEASE HELP! I will upload my source to github very soon.
Here is a fakeflash: ------> CWMRT-alpha0.zip (just install zip from clockwork)
IMPORTANT: This file is a fakeflash, meaning, it will NOT install anything to your phone. It is just what it sounds like, a FAKE flash. This just loads the files into the ram and runs them. Once you reboot you will still have the same recovery that you have now. This is just to show how the touch part works.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Swipe gestures mean that you slide your finger up and down and it highlights the selections up and down. ONLY up and down work right now, not left and right.
Working:
All clockworkmod functions
Up/down swipe gestures
Volume rockers
Capacitive buttons (they are mapped to the icons right above the corresponding button)
Click to expand...
Click to collapse
NOT Working:
Soft keys on bottom of screen
Left/Right swipe gestures
Click to expand...
Click to collapse
any devs out there that know how to start debugging this?
We already have Touch CWMR (Glitch, Devil, and IDK if there are anymore)
Recovery on the captivate lives in the kernel.
b-eock said:
We already have Touch CWMR (Glitch, Devil, and IDK if there are anymore)
Click to expand...
Click to collapse
not really though. glitch has the exact same amount of touch working that I do (just up/down swipe gestures). and you have to be using glitch kernel to use that recovery. i would like to make a stock cm9 kernel with touch recovery.
and im trying to get all touch aspects of the touch recovery working (i.e. left/right swipe, soft keys, etc.)
boog said:
Recovery on the captivate lives in the kernel.
Click to expand...
Click to collapse
so i need to compile the recovery with the kernel at the same time?
sk8erwitskil said:
so i need to compile the recovery with the kernel at the same time?
Click to expand...
Click to collapse
No, the recovery resides in the ramdisks, but those are packaged in the kernel after the kernel is compiled.
DemonWav said:
No, the recovery resides in the ramdisks, but those are packaged in the kernel after the kernel is compiled.
Click to expand...
Click to collapse
so if i take a compiled zImage and a compiled recovery.img then i can package them into a ramdisk? do i use mkbootimg for that? and if so do i just use a --recovery option or something?
sk8erwitskil said:
so if i take a compiled zImage and a compiled recovery.img then i can package them into a ramdisk? do i use mkbootimg for that? and if so do i just use a --recovery option or something?
Click to expand...
Click to collapse
You could also build the entire cm9 source, replacing the recovery with yours.
That should result in the boot.img in the finished rom. Also should end up with a finished zimage, now that the kernel is built inline with cm9.
I haven't taken the time to look into where the scripts are for building the ramdisk, and finished boot.img.
Related
I know I'm not the only one who can't Odin flash CWM and actually get it to stay after reboot
So, anybody working on an easier, more reliable method?
Migital Warfare said:
I know I'm not the only one who can't Odin flash CWM and actually get it to stay after reboot
So, anybody working on an easier, more reliable method?
Click to expand...
Click to collapse
I was able to get it to stick just now by using this kernel... http://forum.xda-developers.com/showthread.php?t=1307980
Flash mkasik's key fix kernel mentioned above *before* you flash clockwork. Then it will stick. I posted this over in the purple clockwork recovery thread but I don't think its gotten a lot of attention. If you use heimdal you could pull the zimage and recovery.bin from the tar files and flash them at once as well. That should work too.
chrisott9628 said:
I was able to get it to stick just now by using this kernel... http://forum.xda-developers.com/showthread.php?t=1307980
Click to expand...
Click to collapse
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Thanks Stilesja
Migital Warfare said:
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Click to expand...
Click to collapse
I flashed the kernel first, rebooted and then flashed recovery. I used the PDA slot each time.
Migital Warfare said:
Did you Odin the keyboard fix kernel before CWM, or at the same time? If you did it at the same time, does the kernel go in the Phone slot?
Thanks Stilesja
Click to expand...
Click to collapse
Glad to help, what made me think of that is I remembered back when purple clockwork came out you would still go into orange clockwork if you did a reboot recovery from the Clockwork App, and it was because there is actually a copy of recovery built into the kernel, then everyone updated their kernels with the new recovery and it was always purple. So when this happened I thought that sprint must have done something to send the three finger boot into the kernel recovery, turns out that must have been the case because a custom kernel fixes it.
The problem is that after (any) OTA update, the phone will reflash the recovery kernel with the stock boot kernel image on every boot, unless the recovery image is already "up to date". Here's the longer explanation.
Anyways, there's two fixes:
1. Flash a custom kernel, then a custom recovery. (As other have noted.)
2. Once rooted, use root explorer or something to delete the files: "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p". That will let you run the stock EI22 kernel with a custom recovery.
XDA ROX
Thank you folks, you have the questions asked & answered (typically) before I can even ask. Just need to look!!!
mkasick said:
The problem is that after (any) OTA update, the phone will reflash the recovery kernel with the stock boot kernel image on every boot, unless the recovery image is already "up to date". Here's the longer explanation.
Anyways, there's two fixes:
1. Flash a custom kernel, then a custom recovery. (As other have noted.)
2. Once rooted, use root explorer or something to delete the files: "/system/etc/install-recovery.sh" and "/system/recovery-from-boot.p". That will let you run the stock EI22 kernel with a custom recovery.
Click to expand...
Click to collapse
Very interesting read (I actually read your "long" explanation a couple of days ago, then re-read it just now), thanks for the excellent, informative explanation! <Thanked>
Hey Guys
I am sharing the latest CWM recovery images; CWM 6.0.2.5
To be straight, I used Koush's Recovery Builder to build these
latest recovery images in both, touch & non-touch variants.
And so I do not take any credit, all of it to Koush. Also, I didn't
publish a thread for this in development section since I didn't
perform any development on this.
Downloads
Touch Recovery TAR
Non-Touch Recovery TAR
Touch Recovery ZIP
Non-Touch Recovery ZIP
Click to expand...
Click to collapse
How to build on your own?
Visit the Recovery Builder
Click on the "Existing Devices" tab.
Now under the Existing Devices dropdown, select "i9300".
Tick "Touch Recovery" option if you desire for the touch variant, otherwise do not touch it.
Now click on the blue colored "Build" tab.
The page will then prompt you with a reference build ID, take note of it.
Now continue to build server.
Look for the corresponding build ID.
Once its done, click on it.
You can now download your "recovery.img" build.
How to flash?
flash TAR files with Odin or mobile Odin
flash ZIP files in recovery
and dont forget to hit thanks if you like this
tried flashing this recovery but it doesn't flash either through odin or mobile odin.
Open .tar file using 7zip and get recovery.img. Then flash it using Mobile Odin. Works fine for me
m1c4d0 said:
Open .tar file using 7zip and get recovery.img. Then flash it using Mobile Odin. Works fine for me
Click to expand...
Click to collapse
Yes that to forgot odin can now flash img files now lol my mistake
im what Willis was talking about
what the difference with the 6.0.1.2 touch version ?
Is there any reason why to select the 'crespo' build from the existing devices drop down box??
What's the difference between picking the crespo rather than the i9300 choice???
kersey said:
Is there any reason why to select the 'crespo' build from the existing devices drop down box??
What's the difference between picking the crespo rather than the i9300 choice???
Click to expand...
Click to collapse
............. Well um BIGGEST difference would be that i9300 is the intl s3 and crespo from what i remember is the nexus s so if you pick crespo you would build the latest recovery for the nexus s
im what Willis was talking about
XeactorZ said:
what the difference with the 6.0.1.2 touch version ?
Click to expand...
Click to collapse
Well the biggest thing i noticed was the ability to now sideload
and also the multiple no when wiping cache or dalvik is gone
it now only appears when doing a factory reset for good reasons
to i would hate to hit yes accidently
sorry for the bad pics they were taken on my girlfriends
crapple product lmao
im what Willis was talking about
kersey said:
Is there any reason why to select the 'crespo' build from the existing devices drop down box??
What's the difference between picking the crespo rather than the i9300 choice???
Click to expand...
Click to collapse
of course you have to select i9300 for SIII recovery !
crespo recovery is for other phone, don´t try to flash that !!
i guess 1.post is copied from other (crespo) thread, please fix nr.3 (Now under the Existing Devices dropdown, select "crespo".)
greetz
markus
75markus said:
of course you have to select i9300 for SIII recovery !
crespo recovery is for other phone, don´t try to flash that !!
i guess 1.post is copied from other (crespo) thread, please fix nr.3 (Now under the Existing Devices dropdown, select "crespo".)
greetz
markus
Click to expand...
Click to collapse
Thanks lol and yea copied that little bit i hate typing all day haha
im what Willis was talking about
sharingan92 said:
Thanks lol and yea copied that little bit i hate typing all day haha
im what Willis was talking about
Click to expand...
Click to collapse
Tested 6019 touch recovery, created full backup, reset system, format /system, restored, no errors. Note that default backup is now tar good work
Sent via TCP/IP
Something is wrong. I used the builder to build my own touch recovery yet mobil odin can't flash it. Not even if I pack it into a rar file. What do?
sharingan92 said:
Thanks lol and yea copied that little bit i hate typing all day haha
im what Willis was talking about
Click to expand...
Click to collapse
That's what confused me earlier in the thread . All worked fine on building one for i9300
Sent from my GT-I9300 using xda premium
Best feature: apply zip from adb. (install zip from sideload -- adb sideload [package])
- but doesn't work
Not the very best solution to install a recovery manager like Odin Mobile if i'am without a system ... have someone a recovery in this version that i can flash through
Odin v3 with windooze?
Many thanks
I'd need a cwm flashable zip of it.
Theshawty said:
Something is wrong. I used the builder to build my own touch recovery yet mobil odin can't flash it. Not even if I pack it into a rar file. What do?
Click to expand...
Click to collapse
strange... i build one yesterday (http://jenkins.cyanogenmod.org/job/recovery/12031/) and flashed the .img file with mobile odin without problems ...
andy572 said:
Not the very best solution to install a recovery manager like Odin Mobile if i'am without a system ... have someone a recovery in this version that i can flash through
Odin v3 with windooze?
Many thanks
Click to expand...
Click to collapse
new tar files are up have tested with mobile and desktop odin and both are working perfectly
sharingan92 said:
new tar files are up have tested with mobile and desktop odin and both are working perfectly
Click to expand...
Click to collapse
Much obliged, works well now! Never thought I'd see anything past 6.0.1.2 for this device
Sent from my GT-I9300 using Tapatalk 2
From the official Chinese support forum.
Credit goes to counter-stike
/Support flash and update of official rom.
/Support MTP
/Support disabling offical recovery
/Supported Models: E100X (All regional model, Onyx or Ceramic)
Must unlock bootloader and install proper ADB driver before flash.
Now enjoy root and custom rom!
Download Link (English Version)
Resolved!
Here is the english version repacked by me
https://www.dropbox.com/s/zypo7b41lvj0r2h/en-recovery-twrp-onyx-.img?dl=0
md5sum - 164519c4a50ea5e9c1244cd7aedf2c74
What is system image?
When I open the backup menu I get an option I've never seen before in other phones called "system image".
Could someone please explain to me what it contains? And is there a need to back this up?
How to flash ?
hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?
Sherwinnn said:
hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?
Click to expand...
Click to collapse
Simon posted a link with instructions here: http://forum.xda-developers.com/showpost.php?p=63718460&postcount=3
Savya said:
Beware! This Recovery is also in Chinese so its impossible to use for most of us. Maybe mention that too?
Click to expand...
Click to collapse
sorry for the inconvenience, updated the link to English version.
can someone dump system.img and boot.img?
Sherwinnn said:
hey guys, just got my OnePlus X White version. it comes with H2OS and i wanna flash it to OxygenOS. I can't seem to get it working tho. any help please?
Click to expand...
Click to collapse
1. Taking threads off-topic is against forum rules. This thread is about TWRP recovery.
2. Double posting is against forum rules.
http://forum.xda-developers.com/oneplus-x/help/h2os-to-oxygenos-t3243838
Can someone confirm this as working?
Should i rather wait for official twrp?
I have had old phones quite a while now and being a bit causious because i usually don´t spend 300€ to a phone.
Fatsodonkey said:
Can someone confirm this as working?
Should i rather wait for official twrp?
I have had old phones quite a while now and being a bit causious because i usually don´t spend 300€ to a phone.
Click to expand...
Click to collapse
Take a look in the rooting thread.
Mirror links:
Original TWRP by @qwsdert4 -- MIRROR
English repacked by @ukanth -- MIRROR
ckret said:
can someone dump system.img and boot.img?
Click to expand...
Click to collapse
Found OTA (looks like full) from some tutorial which has boot.img and full system dump
http://pan.baidu.com/s/1hq98Uoc
hey, so i just flashed this TWRP recovery and i managed to boot into TWRP recovery. But, whenever i click the 'Reboot' option or 'Power Off' option, the TWRP just stays right there and it won't even reboot or power off. I have to hold down the power button to turn off the phone and power it back. Any ideas why this is happening and anything that i've done wrong in the process?
Sherwinnn said:
hey, so i just flashed this TWRP recovery and i managed to boot into TWRP recovery. But, whenever i click the 'Reboot' option or 'Power Off' option, the TWRP just stays right there and it won't even reboot or power off. I have to hold down the power button to turn off the phone and power it back. Any ideas why this is happening and anything that i've done wrong in the process?
Click to expand...
Click to collapse
Its a Bug, i guess same is happening with everyone. We just have to wait for official TWRP. and also
Bug Till NoW
Extra Option Named System partition Under Backup, Which has no Function and Doesn't Work.
Cant reboot/power off from recovery as it just freezes the recovery.
OTG doesn't work in Recovery.
TWRP gets replaced with Stock recovery after each Boot.
N_lover27 said:
Its a Bug, i guess same is happening with everyone. We just have to wait for official TWRP. and also
Bug Till NoW
Extra Option Named System partition Under Backup, Which has no Function and Doesn't Work.
Cant reboot/power off from recovery as it just freezes the recovery.
OTG doesn't work in Recovery.
TWRP gets replaced with Stock recovery after each Boot.
Click to expand...
Click to collapse
can you dump boot.img for me?
just make a backup with twrp if its working
this way we can build a working twrp version
ckret said:
can you dump boot.img for me?
just make a backup with twrp if its working
this way we can build a working twrp version
Click to expand...
Click to collapse
here u go
N_lover27 said:
here u go
Click to expand...
Click to collapse
thanks.
its weird though.. when i unpack the boot.img it misses some files...
ckret said:
thanks.
its weird though.. when i unpack the boot.img it misses some files...
Click to expand...
Click to collapse
try this one mate..
Hi, this is my 3rd post on the great XDA Forums.
Use this kernel flasher script at you own risk !
I am not responsible for any damage or problems such as you getting late for work because the alarm didn't go off, or the phone causing a nuclear explosion
Click to expand...
Click to collapse
.
PLEASE DO NOT SHARE MY WORK OR NIABOC79's WORK WITHOUT PERMISSION.
I present to you my custom flashing script for recovery.
WHY DID I MAKE THIS SCRIPT:
I made this from my own experience because sometimes I needed to flash a stock kernel back and I didn't want to download a whole ftf or rom to get my phone working again (especially because I will have needed to wait for the 'Android is starting' 'Optimizing Apps' rubbish, so I made this, which flashes the kernel file within the zip in recovery (which you can hot boot) ( I prefer the @DooMLoRD V11 kernel : http://forum.xda-developers.com/showthread.php?t=2735137) .
If you want me to make a kernel flasher for your ROM kernel and any other standalone kernels for the Sony Xperia Z2, please send me the name of the ROM (link) and 'boot.img' file (upload it to Drive, MEGA, Mediafire etc) (I would prefer that you send the file renamed to 'boot.elf'). I will then archive it with credits to the creator of the ROM and/or kernel in the script if needed or existent. :highfive:
I have also attached these zips to the thread in case the original gets removed. :laugh:
List of Kernel Flasher Scripts:
CUSTOM:
23.5.A.0.570/575 KERNELS
Click to expand...
Click to collapse
Abricot 8.1 .570/575: https://drive.google.com/open?id=0B6aEcBP7FwsWNVN1eFBLb1ktd00
STOCK:
STOCK 23.5.A.0.486 KERNELS
Click to expand...
Click to collapse
These are from the beta firmware so don't expect awesome performance
Stock 23.5.A.0.486 Kernel : https://drive.google.com/file/d/0B6aEcBP7FwsWTUJlWkJjNWFDVFE/view?usp=sharing
STOCK 23.5.A.0.575 KERNELS
Click to expand...
Click to collapse
Yes, I know they are the same but people beg to differ...
eXistenZ 2.0.0 Stock 575 Kernel : https://drive.google.com/open?id=0B6aEcBP7FwsWYVlLMWNuOS1sU28
Stock 23.5.A.0.575 Kernel : https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
STEPS ON HOW TO FLASH THE KERNEL ZIP:
DOWNLOAD DOOMKERNEL V11, EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH THE ZIP YOU NEED.
Credits:
DooMLoRD V11 Kernel for making the whole process easy: @DooMLoRD Thanks for all your amazing kernels that we all deeply miss.
eXistenZ 2.0.0 Stock 575 Kernel : @niaboc79 Thanks for the great roms you make, and for your 'updater-script' script which I have modified.
Thanks for your time
Regards,
Mohamed
Can a moderator please move this thread to android development, thanks.
Can you give me the boot.img for Marshmallow stock rom for xperia z2?? Thanks
Mostafa Sherif said:
Can you give me the boot.img for Marshmallow stock rom for xperia z2?? Thanks
Click to expand...
Click to collapse
Sure, which build number?
moman2000 said:
Sure, which build number?
Click to expand...
Click to collapse
The latest one for xperia z2 stock marshmallow .575
Mostafa Sherif said:
The latest one for xperia z2 marshmallow .575
Click to expand...
Click to collapse
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11 (link in OP), EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.
@Mostafa Sherif Here is the zip for .575 stock kernel.
https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
I have updated my previous post with instructions on how to flash it. Good luck
moman2000 said:
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11, EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.
Click to expand...
Click to collapse
Doomkernel v11??? Seriously? Doomkernel didn't get any update since 2014. That's almost 2 years. It was good for a while, when Z2 first released. Now noone is using it. It is dead. Also, @DooMLoRD probably not coming on XDA anymore.
V4LKyR said:
Doomkernel v11??? Seriously? Doomkernel didn't get any update since 2014. That's almost 2 years. It was good for a while, when Z2 first released. Now noone is using it. It is dead. Also, @DooMLoRD probably not coming on XDA anymore.
Click to expand...
Click to collapse
I am using that kernel for the process of flashing it because it has built in recovery that we can all use, also, i provided the links so people do not have to go searching for it.... or for any other kernel.
Regards,
Mohamed
moman2000 said:
Ok, Making it right now... Thanks for the quick reply
Do you also want a flashable version too?
EDIT: IT SEEMS LIKE THE OLD METHOD OF EXTRACTING THE BOOT IMAGE WONT WORK.
I NEED YOU TO DOWNLOAD DOOMKERNEL V11 (link in OP), EXTRACT IT, FLASH THE BOOT.IMG VIA FASTBOOT WITH CMD,
COMMAND FOR CMD: fastboot flash boot boot.img
THEN GO IN RECOVERY (volume down when booting) AND FLASH MY ZIP I AM MAKING.
Click to expand...
Click to collapse
moman2000 said:
@Mostafa Sherif Here is the zip for .575 stock kernel.
https://drive.google.com/file/d/0B6aEcBP7FwsWbHFQUjUzY2JBMTA/view?usp=sharing
I have updated my previous post with instructions on how to flash it. Good luck
Click to expand...
Click to collapse
Thank you, i'm really appreciate your work.
Actually i want it to port boot.img from Xperia Z3 to Xperia Z2 so it will help me. You have a guide or something like that which can help me in porting boot.img from one device to another!!
Another thing, how can i unpack and repack the boot.elf?? Which tool i have to use or what i have to do??
Thanks bro
moman2000 said:
I am using that kernel for the process of flashing it because it has built in recovery that we can all use, also, i provided the links so people do not have to go searching for it.... or for any other kernel.
Regards,
Mohamed
Click to expand...
Click to collapse
All the custom kernels for Z2 have built in recovery.
V4LKyR said:
All the custom kernels for Z2 have built in recovery.
Click to expand...
Click to collapse
I am aware of this but I think doomkernel is the easiest to use in my opinion, I know there are more awesome custom kernels
Such as abricot 8.1
moman2000 said:
I am aware of this but I think doomkernel is the easiest to use in my opinion, I know there are more awesome custom kernels
Such as abricot 8.1
Click to expand...
Click to collapse
Doomkernel is from 2014
ANY kernel is better than it :fingers-crossed: But yeah, Abricot is awesome indeed! :good:
V4LKyR said:
Doomkernel is from 2014
ANY kernel is better than it :fingers-crossed: But yeah, Abricot is awesome indeed! :good:
Click to expand...
Click to collapse
I approve!:highfive:
Hi, I'd just like to thank you for this. I can't access recovery anymore since I flashed the DRM fix. By the way, I'm on the Xperia Z2 (eXistenZ 2.5.0)
Anyways, I flashed the advanced stock kernel to get recovery, then flashed the 2.5.0 update, then flashed this to get my kernel back to 575. I can't seem to fastboot a recovery though. Any ideas?
EDIT: Fixed my own problem. Thanks again, though!
iArvee said:
Hi, I'd just like to thank you for this. I can't access recovery anymore since I flashed the DRM fix. By the way, I'm on the Xperia Z2 (eXistenZ 2.5.0)
Anyways, I flashed the advanced stock kernel to get recovery, then flashed the 2.5.0 update, then flashed this to get my kernel back to 575. I can't seem to fastboot a recovery though. Any ideas?
EDIT: Fixed my own problem. Thanks again, though!
Click to expand...
Click to collapse
Glad you fixed it, what exactly was the problem to begin with so i can help you prevent it in the future?
And by the way if you can flash the zip you do not need to fastboot a advanced stock kernel. I just added it for those running into bootloops from flashing the wrong things or anything else preventing them from booting their phones.
moman2000 said:
Glad you fixed it, what exactly was the problem to begin with so i can help you prevent it in the future?
And by the way if you can flash the zip you do not need to fastboot a advanced stock kernel. I just added it for those running into bootloops from flashing the wrong things or anything else preventing them from booting their phones.
Click to expand...
Click to collapse
The problem was, if you flash the DRM fix, you can't access recovery. Some fixed it by fastbooting a recovery, but it didn't work for me. Apparently the /cache/recovery wasn't being mounted properly. I just repaired the folder using recovery (had to flash the advanced stock kernel to actually GET into recovery) then it's working again.
I cannot get into recovery mode in 575. Only way I found was to follow your suggestion and flash boot.img from DoomKernel.
Flashing your zip at this point blocks again the possibility to enter in recovery mode.
Any app (ROM Manager, ROM Toolbox, ecc.) is able to reboot in recovery mode with 575.
Have you any suggestion?
Thx
mercinellim said:
I cannot get into recovery mode in 575. Only way I found was to follow your suggestion and flash boot.img from DoomKernel.
Flashing your zip at this point blocks again the possibility to enter in recovery mode.
Any app (ROM Manager, ROM Toolbox, ecc.) is able to reboot in recovery mode with 575.
Have you any suggestion?
Thx
Click to expand...
Click to collapse
Are you pressing the volume down to get in recovery?
Are you sure you have flashed the right zip? If not I could also provide you a custom kernel called Abricot 8.1 in the zip you can flash
moman2000 said:
Are you pressing the volume down to get in recovery?
Are you sure you have flashed the right zip? If not I could also provide you a custom kernel called Abricot 8.1 in the zip you can flash
Click to expand...
Click to collapse
Yes, with the DoomKernel boot.img I can get into the recovery pressing Vol Down button and then Vol Up (if not fail with an error saying there is no SW to download). Then I flashed the zip. After that if I reboot with vol Down nothing happens until I release the butto and then normal boot goes on.
I tried also with the Advanced MM Kernel boot, but nope.
TWRP and CWM are there since I can get into them if the Doom Kernel boot is installed, but as soon as I chenge the boot.img with stock they cannot be reached. No app is able to reboot into recovery (even with the DoomKernel boot).
I didn't make them ...
https://sourceforge.net/projects/mocha-roms/
I love you peeps ..
Tnx, did you test them yet?
jollyjesus said:
I didn't make them ...
https://sourceforge.net/projects/mocha-roms/
I love you peeps ..
Click to expand...
Click to collapse
Thanks. The best and smooth ROM ever.:good:
ChooiWC said:
Thanks. The best and smooth ROM ever.:good:
Click to expand...
Click to collapse
did you even test it for real?
because i did it and i can say it does boot up quiet nicely but after booting touchscreen is not working at all.
How did you manage to make it work.....
did you flash any touchscreen fix. If so tell me...
digvijay2505 said:
did you even test it for real?
because i did it and i can say it does boot up quiet nicely but after booting touchscreen is not working at all.
How did you manage to make it work.....
did you flash any touchscreen fix. If so tell me...
Click to expand...
Click to collapse
First reparation system to 1.2 gb
download TosForPSCI-0.1.zip
2) unzip TosForPSCI-0.1.zip
3) download recovery-03.11.2018
4) go to fastboot mode
5) execute command: fastboot flash tos your path to tos.img
6) execute command: fastboot flash recovery your path to recovery-03.11.2018.img
7) reboot to new recovery(u can execute fastboot reboot holding vol+ button)
8) flash the rom and gapps
digvijay2505 said:
did you even test it for real?
because i did it and i can say it does boot up quiet nicely but after booting touchscreen is not working at all.
How did you manage to make it work.....
did you flash any touchscreen fix. If so tell me...
Click to expand...
Click to collapse
i didn't have problem with touch. just use advance wipe / data / system / dav/, reboot to recovery and install the image then opengapps, magisk... tested on 2 mipad. no problem. no tos fix and no kernel updating. btw, i'm using stock blobs.