Related
As there is now an official version of CWM Recovery I updated this thread now. Thanks to everyone who used my version and helped me. I will keep on what I'm doing and maybe there will be other interesting things I will release.
The official CWM Recovery by Koush can be downloaded here:
Images to flash via fastboot
touch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-mako.img
nontouch-version: http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-mako.img
Flashable zips
touch-version: https://www.mediafire.com/?nx826v1jo0bdqdj
nontouch-version: https://www.mediafire.com/?69kmvtcvgooc0gv
For the fastboot images:
You can try this out and boot it via
Code:
fastboot boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(only Android 4.2.X)
Code:
fastboot -c "lge.kcal=0|0|0|x" boot recovery-clockwork(-touch)-6.0.4.7-mako.img
(Android 4.3 and above)
If you want to flash it you can use
Code:
fastboot flash recovery recovery-clockwork(-touch)-6.0.4.7-mako.img
If you have the touch-version use this commands without '(' and ')' but with its content.
If you have the nontouch-version use this commands without '(' and ')' and its content-
Outdated as all new recoveries already provide this function.
I also want to present you my revert recovery disabler.
As you know if you flash CWM on Nexus 4 it reverts back to the stock recovery. This patch prevents this. This is not needed at the moment for CWM as CWM offers the possibly to disable the revert by itself.
You can download my revert recovery disabler here: http://www.mediafire.com/?78fkhdh5icz3zdg
This disabler is compatible with mskip's toolkit (uses the same methode).
To use it boot in CWM recovery and flash this as a zip.
If you want to restore the default option and make your Nexus 4 reverting back to the stock recovery you can flash the enabler: http://www.mediafire.com/?19enww985e2gpnc
Thanks to:
Stryder5 providing some information
Kstarz for some testing and providing information
mskip for his toolkit and giving me the idea to do this
pankaj88 for his sample update zip
Old thread said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (UPDATED 11/16/2012)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to:
Stryder5 for testing and providing some information
Kstarz for testing and providing some information
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
To clarify, I can confirm the boot method will allow you to boot the recovery and flash a zip file. I did not attempt to flash this as my recovery yet.
---------- Post added at 12:53 AM ---------- Previous post was at 12:21 AM ----------
I tried to flash the recovery instead of booting from it, but that doesn't work. I ran the command:
Code:
fastboot flash recovery cwm-recovery-mako.img
When I try to boot into recovery after that, it'll show the Google logo twice, then proceed with the regular boot.
I think this is because Secure Boot is still enabled.
Same thing here..recovery will not stick if flashed
Sent from my Nexus 4
good news! https://plus.google.com/u/0/103583939320326217147/posts/CzstapsDpYf
fkrone said:
I just want to release my CWM Touch Recovery for the Nexus 4.
This version also allows to flash zips from internal storage (and hopefully other storage related stuff).
If you want to you can download it here: http://www.mediafire.com/?f9b9av06ui5vcdm (more mirrors will be added soon)
Using it is at your own risk!
Please test it first via
Code:
fastboot boot cwm-recovery-mako.img
Flashing is not supported at the moment as secured boot prevents from booting flashed recovery. Please note that you need an unlocked bootloader.
For reverting back to original recovery use this one: http://www.mediafire.com/?57zmq7yw089gcr8 (not needed at the moment as only booted recovery works at the moment)
Thanks to my tester Stryder5.
Also thanks to Koush for creating CWM Recovery and to the other devs for Nexus 4 making it a really good device.
If you have any questions ask below. I will rework this post later the day.
Click to expand...
Click to collapse
What RAMDISK load address are you using? 0x81200000?
Thanks to the tip by Stryder5, I have updated my rooting guide with instructions for rooting via CWM, linking to this thread for the recovery and providing the due credit. =)
g33k3r said:
What RAMDISK load address are you using? 0x81200000?
Click to expand...
Click to collapse
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
fkrone said:
If I could I would provide you that information but as I only used the CWM's online builder I can't tell you that. If you need some information you can pm me
To all: As there is a new update in the sources I am currently syncing the sources and building an new version. Furthermore I am working on a possibility to make the CWM permanent (and easy to do so even without root; I know already what I have to do).
Click to expand...
Click to collapse
Looking forward to it!
Sent from my Nexus 4 using xda app-developers app
does anyone actually build cwm these days?
Sweet!! So our Nexus 4 is codenamed "MAKO?"
DaX05 said:
Sweet!! So our Nexus 4 is codenamed "MAKO?"
Click to expand...
Click to collapse
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
fkrone said:
The hardware is calles mako, the software itself has the codename occam. As of my building methode it was automatically called mako
Click to expand...
Click to collapse
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
mskip said:
Hey do you mind if I put this recovery in the Toolkit for now until koush has released the official cwm?
Is it touch or non touch? What version is it?
Mark.
Click to expand...
Click to collapse
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
fkrone said:
No problem at all. Just give credits and use it. This is a touch recovery.
If koush will release CWM for Nexus 4 it won't be different to this (except he changes some sources).
Click to expand...
Click to collapse
Thanks and of course
What version is it? V6.0.1.5?
Mark.
mskip said:
Thanks and of course
What version is it? V6.0.1.5?
Mark.
Click to expand...
Click to collapse
As I built it this afternoon (GMT+1) it is V6.0.1.5 with the latest bugfix which was released today.
Man I can't wait to see some custom ROM's outta here. The phone is sweet and snappy but I've had a few problems that I'm not sure if they're hardware or software related. Quadrant scores are around 4400-4900, the phone rings hot and I'm getting the worst speed test results. Like I get 11-18 MBS on my gs2 and I'm getting like 2-3mbs now. I got two weeks before I can return it so I hope it just needs to stettle. Anyhoo. Good luck guys!
Sent from my Nexus 4 using XDA Premium HD app
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Arasthel said:
Link to the new recovery (6.0.1.6-mako)
But assuming that I flashed it correctly with Rom Manager and fastboot, it isn't working, it didn't matter which way i flashed it.
Click to expand...
Click to collapse
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
fkrone said:
Flashing does not work at the moment. Only booting via fastboot even with official CWM Recovery.
Click to expand...
Click to collapse
Sorry, I misunderstood you. I thought this bugfix would allow us to flash the recovery in our devices, then I realized that the bugfix was what let us boot it, as you said a few messages back. Anyway, there you have the official build link.
Can somebody please explain, in simple terms, why we can't flash this permanently yet? What do we need to enable us to flash it permanently?
NEW: YOU SHOULD UNLOCK YOUR BOOTLOADER : http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
Hi !
Since @vortox found and created an unlock method (!) for our devices (see original development section) you'll find here twrp recovery for the 7" kindle fire hdx (Thor).
WARNING
THIS OPERATION IS DANGEROUS
THE ONLY WAY TO RECOVER FROM A RECOVERY PROBLEM IS TO HAVE A WORKING SYSTEM ROM
Installation (from stock rom)
Be sure to have a rooted, 7" hdx with firmware <= 13.3.2.3 (for bootloader compatibility)
Use an application from the market to flash the recovery image like Rashr or Flashify (from vortox)
OR use dd application from a root shell : "dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img"
Installation (from twrp)
Flash zip file from twrp recovery...
Download
Please see @ggow thread for up to date recovery : http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155
Thanks
@vortox for the exploit !
Cpasjuste said:
Hi !
Since an unlock method seems to be coming to our devices (see original development section) you'll find here a twrp recovery for the kindle hdx (Thor). I will try to compile an Apollo version as soon as an unlock method is reveled. (Or @ggow will do it )
Oups I'm sorry I didn't fully read the unlock thread. The recovery need to be patched to run so I removed the link for now. The recovery was sent to the right person, well see !
Click to expand...
Click to collapse
Hello, yes I have a build of twrp for apollo waiting here ready to go...
Sent from my Nexus 6 using Tapatalk
Hi !
First post updated with download link ! I'm unable to test the recovery myself as i own an unlocked device so thanks to wait for some experienced users to report back. If the recovery is not working for you then you can boot to your system rom and restore your backed up recovery from there...
Thanks to @vortox again and happy new year !
Cpasjuste said:
Hi !
First post updated with download link ! I'm unable to test the recovery myself as i own an unlocked device so thanks to wait for some experienced users to report back. If the recovery is not working for you then you can boot to your system rom and restore your backed up recovery from there...
Thanks to @vortox again and happy new year !
Click to expand...
Click to collapse
Do you have to be on stock rom or would it work with safestrap and nexus 2.2 on stock slot?
Sent from my A0001
It should work from any rom/configuration as soon as you have root and a rom <= 3.2.4 (version to be confirmed).
I tried applying the recovery with flashify on 3.2.4 and it hasn't worked as far as I can tell, though I didn't remove safestrap yet. It just gets stuck on grey kindle fire logo 9/10 boots then finally gets into safestrap. Don't really want to remove my only safety net unless it's confirmed I have to.
derpadoodle said:
I tried applying the recovery with flashify on 3.2.4 and it hasn't worked as far as I can tell, though I didn't remove safestrap yet. It just gets stuck on grey kindle fire logo 9/10 boots then finally gets into safestrap. Don't really want to remove my only safety net unless it's confirmed I have to.
Click to expand...
Click to collapse
Did you try to power on the device with volume up to trigger the recovery ? Else maybe 3.2.4 is too late for the recovery sig exploit.
Yeah I tried that, no effect.
I'll downgrade to 3.2.1 later today.
derpadoodle said:
Yeah I tried that, no effect.
I'll downgrade to 3.2.1 later today.
Click to expand...
Click to collapse
Cool thanks, let us know !
Looks like you butchered the original post while you were editing.
I just downgraded to 13.3.1.0 so I'm ready to test it out. But —before proceeding — how do you backup the stock recovery?
It's not working on 3.2.4, but works atleast at 3.1.0. I didn't test other versions.
I ended up finding an app on the Play Store to backup the recovery.
Anyways, I can now also confirm that this works on 13.3.1.0.
EncryptedCurse said:
Looks like you butchered the original post while you were editing. [emoji14]
I just downgraded to 13.3.1.0 so I'm ready to test it out. But —before proceeding — how do you backup the stock recovery?
Click to expand...
Click to collapse
Ho crap :/ This is the worst part for me and I screwed it ^^
Should I uninstall safestrap before flashing the recovery?
Is it just me, or does the screen have a yellowish tint while in recovery mode?
EncryptedCurse said:
Is it just me, or does the screen have a yellowish tint while in recovery mode?
Click to expand...
Click to collapse
I do not seems to have the problem here but its possible that we need to update the adreno fw in the persist partition. You'll have a better visibility when you'll try CM to be sure.
I have placed rollback images here...
http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015
I am rolled back from 13.3.2.4 to 13.3.1.0 successfully and the Recovery-Image works fine with locked Bootloader
[email protected]
Cpasjuste said:
Hi !
[*]OR use dd application from a rooted system : "dd of=/dev/block/platform/msm_sdcc.1/by-name/boot if=/sdcard/twrp.img"
Click to expand...
Click to collapse
Not dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img ?
ONYXis said:
Not dd of=/dev/block/platform/msm_sdcc.1/by-name/recovery if=/sdcard/twrp.img ?
Click to expand...
Click to collapse
Thanks for the head up, this was very dangerous :x Main post has been updated.
Hello people,
I was able to successfully build twrp 3.0 for suzuran (our device, duh!) and thought I'd share the recovery.img so you can test and see what works and what doesn't.
The recovery was built in a CM13 similar environment (PAC), so there might be some issues when working with stock kernel.
Since this is an experimental build (I tested main functionalities and they work, but didn't get down to the nitty-gritty), here's a small disclaimer:
By flashing or booting the attached recovery you're risking damaging you device, or losing the data on your device!
Neither I nor anyone else but YOU is responsible should any bad unintended problems appear!
If you're feeling adventurous then feel free to flash the recovery.img (along with Androplus kernel) and try the sweetness that is TWRP 3.0 :good:
Download link:
April 3, 2016 (3.0.1)
March 25, 2016
March 21, 2016
March 12, 2016
Known issues:
Temperature reading is botched
Crypto might not be working, like AT ALL
usb connection doesn't work (only if you use this recovery with Androplus kernel)
There could be more problems, which is why this is EXPERIMENTAL for now
And now let's get to the sources!
kernel:
[url]https://github.com/oshmoun/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7[/URL]
device sources:
[url]https://github.com/oshmoun/device-sony-suzuran/tree/master[/URL]
[url]https://github.com/oshmoun/device-sony-kitakami/tree/master[/URL]
[url]https://github.com/SonyCM/device-sony-common/commits/cm-13.0[/URL]
And now to thank the people who helped in this endeavor:
TWRP team for the awesome recovery!
@nilezon for the TWRP flags (which I still need to go through to check if I missed/need anything, especially crypto flags...)
FXP team for device sources, Especially @adfad666
All of the Sony AOSP contributors, they're awesome people!
It doesn't work on my Android 6.0 device:crying:
doesn't work on sony mm, stuck at sony logo
iMaeGoo said:
It doesn't work on my Android 6.0 device:crying:
Click to expand...
Click to collapse
tanto124 said:
doesn't work on sony mm, stuck at sony logo
Click to expand...
Click to collapse
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
iMaeGoo said:
E5823, version 32.1.A.1.163, bootloader unlocked, in fastboot mode, using command "fastboot boot TWRP3.img".
And it stucks at SONY logo.
Click to expand...
Click to collapse
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
69650eaccdd8b24a3efc0ef1b4bdffb8
The img's MD5 is right.
I'll try to boot Z5C_TWRP_152_v2_nilezon on my device later.
It worked before I upgraded to MM.
oshmoun said:
this is really weird, did the MM update also change something in the bootloader in an inconvenient way?
Could you try the other recovery.img from nilezon's thread? If that boots using "fastboot boot recovery.img" then we'll know the problem is somewhere in the .img itself
EDIT: oh, also could you please check if your download wasn't corrupt? Here's the md5 hash of the file so you can check
69650eaccdd8b24a3efc0ef1b4bdffb8
Click to expand...
Click to collapse
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
iMaeGoo said:
I have no idea.
Z5C_TWRP_152_v2_nilezon doesn't work on MM.
I flash Android 5.1 and try your TWRP3.0, still stuck at SONY logo(with no LED light).
Z5C_TWRP_152_v2_nilezon can work on 5.1.
Now I'm flashing MM again.
Click to expand...
Click to collapse
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
t4656 said:
Hello,
I tried booting(didn't flash) with MM and it seemed to boot into recovery fine. Used it to do a cache wipe, but afterwards phone is stuck on boot screen. I can turn it off with power + volume, but it doesn't seem like I can go back to fast boot.
Click to expand...
Click to collapse
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
oshmoun said:
You should be able to go into fastboot mode by turning device off, holding vol+ button, then connecting the device to your computer through usb
Click to expand...
Click to collapse
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
t4656 said:
Yeah thanks. Took something like 10 tries before it finally went into fastboot. Not sure what went wrong there. Also on my first try I was able to boot into your build of twrp. But afterwards when I try it just gets stuck on the logo again.
Click to expand...
Click to collapse
This is so freaky what the heck!!!
Could you flash bootloader from 5.1 ftf and see if it works properly then?
I'll (finally) update to MM today , so I'll witness the issues first hand.
oshmoun said:
Thanks! Guess the issue lies in the MM update somewhere.
You just said that nilezon's recovery works on 5.1, but did you try it after flashing 5.1, or are you basing that statement on previous tests?
The issue here might be that you didn't downgrade the bootloader when you flashed 5.1 again, which would mean the issue will persist.
Click to expand...
Click to collapse
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
iMaeGoo said:
I tried nilezon's recovery after flashing 5.1 and it worked.
I use FlashTool to write FTF file to my phone fully, include kernel.
Maybe it's my problem...
Thank you for your patience!
Click to expand...
Click to collapse
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
oshmoun said:
nope, not your problem, it's everyone's
seems like my twrp version just refuses to boot sometimes.
Was able to successfully replicate the fastboot issue on 5.1 bootloader, so it's definitely this recovery.
Now the question is if it's a TWRP 3 issue, or just in the way I built it
EDIT: I guess this post answers my question
http://forum.xda-developers.com/showpost.php?p=65808636&postcount=137
another twrp 3 recovery is having the same issue
guess I'll have to make this recovery flashable in order for it to work properly
EDIT 2: wow, Androplus kernel seems to go well with TWRP 3. Updated first post with new instructions on how to use this.
Click to expand...
Click to collapse
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
iMaeGoo said:
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
Can not detect external SD or USB OTG (yet)
This will do the job until a proper dev makes a better version.
Maybe I had better wait...:crying::crying::crying:
Click to expand...
Click to collapse
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
oshmoun said:
ummm, my sdcard is getting detected :|
I'll post screenshots soon
EDIT: attached screenshots
Click to expand...
Click to collapse
Can external storages be found in Android system?
iMaeGoo said:
Can external storages be found in Android system?
Click to expand...
Click to collapse
everything concerning external sdcard function is working here as far as i tested (both in Stock mm rom and twrp3)
oshmoun said:
Could you tell me if you have E5823 or E5803, I have an E5823 and it's working fine.
Also, are you sure you're not FLASHING the recovery.img? You need to just BOOT it directly from fastboot
Click to expand...
Click to collapse
it's E5823 running 32.1.A.1.163 . I am sure that I was just booting , downloaded file is okay .
Unofficial release -TWRP recovery for the Galaxy A3 - SM-A300F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2019/05/22/twrp-3.3.1-0-released.html
*SEANDROID warning fix
*Recovery reboot fix
*MTP fix
*Modem, APNHLOS, EFS and Recovery partition backup
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot:
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a300
twrp_3.3.1-2_sm-a300x_101119
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
I suggest using Magisk as its a currently up to date project. Supersu is no longer maintained:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.
Hmm... could this maybe be flashed with Flashify?
King-V said:
Hmm... could this maybe be flashed with Flashify?
Click to expand...
Click to collapse
It could, but better to flash it with TWRP or ODIN.
ashyx said:
It could, but better to flash it with TWRP or ODIN.
Click to expand...
Click to collapse
Wait... what? Flash this version of TWRP, using an older version of TWRP? Does that really work?
King-V said:
Wait... what? Flash this version of TWRP, using an older version of TWRP? Does that really work?
Click to expand...
Click to collapse
Of course it does, it's been that way since about version 2.8.6.0
ashyx said:
Of course it does, it's been that way since about version 2.8.6.0
Click to expand...
Click to collapse
Never knew that; it sounds quite handy... Thanks a lot!
Well, i wish we had 5.1.1...
Thanks a lot btw.
PlutoDelic said:
Well, i wish we had 5.1.1...
Thanks a lot btw.
Click to expand...
Click to collapse
You don't need 5.1.1.
Sent from my HTC One_M8 using XDA Free mobile app
ashyx said:
You don't need 5.1.1.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
PlutoDelic said:
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
Click to expand...
Click to collapse
Which device model?
Can you post the recovery.log file?
PlutoDelic said:
Obviously.
I stumbled on an issue. TWRP boots fine, but no touch input. Reboot issue seems to remain IF one "reboot to recovery" from the system. Everything works find under the hood, connected through adb without any issue.
Click to expand...
Click to collapse
hi community,
first of all very big thanks to @ashyx to support our device and port the new twrp :highfive:
i can confirm that the recovery start without problems after flashing with android 5.0.2 but sadly maybe the touchdriver not loading. touch have for now no function
my device is the a300fu with touchwiz stockrom and baseband boj4.
@ashyx, please fix the problem with touch and maybe all will be good :highfive:
best regards and thank's for support our community :highfive: :good:
Duke2010 said:
hi community,
first of all very big thanks to @ashyx to support our device and port the new twrp :highfive:
i can confirm that the recovery start without problems after flashing with android 5.0.2 but sadly maybe the touchdriver not loading. touch have for now no function
my device is the a300fu with touchwiz stockrom and baseband boj4.
@ashyx, please fix the problem with touch and maybe all will be good :highfive:
best regards and thank's for support our community :highfive: :good:
Click to expand...
Click to collapse
Yes I'll fix the issue, but I need someone to upload the recovery log from cache/recovery/last_log
ashyx said:
Which device model?
Can you post the recovery.log file?
Click to expand...
Click to collapse
A300FU
Attached.
Reflashing the .tar weirdly gets rid of the reboot to recovery issue, wonder if any flag is being reset...
PlutoDelic said:
A300FU
Attached.
Reflashing the .tar weirdly gets rid of the reboot to recovery issue, wonder if any flag is being reset...
Click to expand...
Click to collapse
hi folks,
i send my logfile too. well done :highfive:
best regards :good:
Duke2010 said:
hi folks,
i send my logfile too. well done :highfive:
best regards :good:
Click to expand...
Click to collapse
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
sorry, no my device stuck into boot recovery process. it is not possible to booting up into recocery. :crying:
try again please :highfive:
thank you and best regards :good:
Duke2010 said:
sorry, no my device stuck into boot recovery process. it is not possible to booting up into recocery. :crying:
try again please :highfive:
thank you and best regards :good:
Click to expand...
Click to collapse
Please post your device model.
Hi mate,
My device is the a300fu with boj4 bootloader and boj5 touchwiz stockrom
Best regards :good:
First of all Thanks for your work!
I´m also on the A300FU Device
ashyx said:
Yes I'll fix the issue, but I need someone to upload the recovery log from cache/recovery/last_log
Click to expand...
Click to collapse
With the TWRP from OP, I confirm TWRP starts but Touch is not working (Log old)
ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
With the "Fix" it stuck bevor TWRP Screen should appear (Log new) btw. flashed both with Odin
Jonny_Hood said:
First of all Thanks for your work!
I´m also on the A300FU Device
With the TWRP from OP, I confirm TWRP starts but Touch is not working (Log old)
With the "Fix" it stuck bevor TWRP Screen should appear (Log new) btw. flashed both with Odin
Click to expand...
Click to collapse
Looking at the recovery log it seems there is an issue loading the graphics, so I have reverted one of the flags that I think is causing the issue.
https://www.androidfilehost.com/?fid=24499762636004909
NOTE: I will not support any posts related to flashing with Flashify, this app has issues with some devices. ODIN(prefered), TWRP and the DD method is fine.
.
Stock kernel with TWRP recovery SGP621
Sony RIC disabled
TWRP 3.0.2
Download
From here and unzip
Flash via flashtool or fastboot
Code:
fastboot flash boot boot.img
Root
Flash this in recovery
Credits
tobias.waldvogel for his awesome tool
TWRP team
shoey63 for guiding me
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
wulfiss said:
there is a low interest in the devs for this tablet. So, everything is appreciated..
Thanks for your work, in an few hours I'll test it.
Click to expand...
Click to collapse
you are welcome buddy!
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
ipharus said:
Thanks alot, I'd love to have TWRP 3.0.2 on stock rom.
But I can seem to get it to work, tried on a customized US an a customized DE stock image, latest version.
Doesn't boot on either, screen stays black when I try to turn on the tablet.
Click to expand...
Click to collapse
No boot screen at all? What's your tablet model?
SGP-612
ipharus said:
SGP-612
Click to expand...
Click to collapse
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
codfx said:
Is your bootloader unlocked? If so send me your kernel.sin from the firmware.
Click to expand...
Click to collapse
Yes bootloader is unlocked. kernel.sin for Custom DE attached (SGP612_Customized DE_1290-4946_23.5.A.1.291_R2D)
I don't get it to work either. SGP611, using SGP611_23.5.A.1.291_1290-0168_R4D customized UK. Won't boot, only flashes its red little light. Did you find any solution to it? Would be awesome to get this kernel.
Hi,
Have I sent you the correct file? Did you get the time to have a look at it?
No stress, just wonderin :angel:
is there a way to unlock bootloader using kinds of special hardware (like HTC xtc2clip)
(thanks O2 for locking the bootloader -_-)
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
vmille said:
Hey
Something new about black screen ?
Same problem here.
SGP621
Thank you
Click to expand...
Click to collapse
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Could a version of this be build with the device name "scorpion"? It won't let me install this ROM since the device name doesn't match (it seems to be empty in this image whereas that ROM requires it to be "scorpion").
Edit: nevermind, figured out I can modify the script in side the ROM to remove the check instead.
Thanks for a working TWRP for my old tablet
codfx said:
If you are getting a black screen after flashing the kernel, just force restart the device. Then the device will boot fine.
Click to expand...
Click to collapse
I get a black screen as well, tried to force reboot, same issue.
danw84 said:
I get a black screen as well, tried to force reboot, same issue.
Click to expand...
Click to collapse
what's your device model?
codfx said:
what's your device model?
Click to expand...
Click to collapse
SPG611
danw84 said:
SPG611
Click to expand...
Click to collapse
This kernel is only for SGP621. It's clearly mentioned in OP.
Think you!
Not easy for an old man, but after several times it went perfect.
Not able to tell you what I did exactly but I have SGP621, french 6.01.
SGP612 boot.img
Hi,
I made a boot.img for the SGP612 [6.0.1] [23.5.A.1.291] unlocked BL.
Sony RIC disabled
TWRP 3.0.2
(DRM fix)
Root and Xposed is NOT included. I recommend flashing Magisk v12 later in TWRP and enable Magisk Core Only Mode and Magisk Hide in the settings. Then it will pass the SafetyNet test and you can use su.
To flash the boot.img, put your SGP612 into fastboot mode (Volume Up + connect USB) and then run:
Code:
fastboot flash boot boot.img
If you have a backup of your TA partition, before you unlocked, see the rootkernel thread by tobias.waldvogel, how the DRM fix works.
Thanks to codfx for give me the idea for a SGP612 counterpart and to tobias.waldvogel for his tool :good: