Database Develop

[RECOVERY] Official CWM Recovery 6.0.4.7 for Nexus 4; revert recovery disabler

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?

[RECOVERY] TWRP Recovery 2.8.7.0 - Apollo/Thor

Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit

I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?

r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.

vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.

I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!

Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk

Thanks ggow. Could we expect CM roms soon from your new release?

Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.

tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.

dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk

Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?

tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel

r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?

Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0

ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse

I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk

tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...

Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.

Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.

GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers

Get Root after Update to Lollipop on T-800 (WIFI)

Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.

dadanepal said:
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
Click to expand...
Click to collapse
I can confirm that this process does work. It's the method I went through when I upgraded my Tab S.

Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372

ashyx said:
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
Click to expand...
Click to collapse
Thanks for the update. Are you going to keep up with every new SU updated binaries and update TWRP every time the binaries are update. That would be great if you are willing to do that. I rather rely on the actual TWRP and SuperSU Developers to give me the zips etc. and flash my self as long winded as that may seem but people can choose.

Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue now.
Regarding cf-autoroot. I don't think people realise there is nothing special about how it roots.
It basically does the same thing that twrp does itself or flashing a super su zip.
Cf-autoroot simply installs a modified stock recovery which runs a script to Install root then flashes back stock recovery.
If someone intends to install a custom recovery anyway then there is no point in running cf-autoroot.
Twrp will do exactly the same thing and so does installing a super su zip.
They all accomplish the same thing using a slightly different method.
The only difference will be that chainfire may keep each cf-autroot updated with the latest binary.
The reason chainfire created it is for people who want to stick with stock recovery instead of custom

ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse

deno24 said:
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
Mode? Just load it and flash it.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
Mode? Just load it and flash it.
Click to expand...
Click to collapse
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse

deno24 said:
ashyx said:
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
That's the one.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
That's the one.
Click to expand...
Click to collapse
cool so i flash twrp and ill have root? been a cpl oif years since ive done this last root was note2
Click to expand...
Click to collapse

Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.

ashyx said:
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
Click to expand...
Click to collapse
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks

d3xtr0 said:
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
Click to expand...
Click to collapse
That's a feature of lollipop. It overwrites with stock recovery. Happens on many devices. You need to boot into recovery immediately after flashing twrp, twrp will then patch it so stock recovery can't replace it.
When flashing uncheck auto reboot in odin. When it finishes flashing hold power + vol down + home. As soon as the screen goes blank hold power +vol up + home to boot into recovery.

Thanks for the information, but now I've flashed your new package root+twrp and it's working great
Thanks again.
Sent from my MI 4W

Whith this method, what is the knox value?

Knox is one ( .. )
Newer thread opened yesterday.
Edit:
http://forum.xda-developers.com/showthread.php?t=3079488
[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805 [Tab S 10.5 ]
Sent from my MI 4W

Nvidia SHIELD Portable Root

Hi everyone!
This morning I woke up to find my SHIELD with the so waited notification of Lollipop update. I'm really happy to finally have lollipop running on my device, but sadly I found a problem after the update. I was trying to re-root my device, but neither the SHIELD RAM tool or Root Genius could do the trick. But I didn't gave up, I searched in Google any way to root my SHIELD with the still fresh update, and found that the Kinguser app can root it without trouble.
You just need to download the apk, install it on your SHIELD and open it.
Btw, the old recovery isn't working anymore, you can flash it with the RAM tool, but the device will reflash the stock recovery.

twrp works, but SU binary still wont flash :/
edit - the combination of this APK and TWRP gave me all I need for root + rebooting and keeping root

Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.

I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.

Steel01 said:
I can confirm some problem with supersu and update 103. I flashed 2.46 and my portable wouldn't boot. Like, something broke so bad I had to reflash 101 and update again. The later might indicate backups are broke in my twrp, I'll have to look into that. For now, I'm going try kingroot as suggested here and continue other development.
Click to expand...
Click to collapse
So you were successful in getting TWRP installed, SuperSU installed and removing KingRoot clean - leaving only SuperSU on the system, surviving a reboot?

Ink Rampant Wolf said:
Yeah, I was about to say that. The TWRP recovery works like a charm, but Supersu binary won't install. But well, the KingRoot app is pretty good.
Click to expand...
Click to collapse
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks

You might wanna include the instructions as shown here,
http://forum.xda-developers.com/xpe...how-to-root-lollipop-xperia-tablet-z-t3115107
It basically tells you how to install SuperSU and remove the entire KingRoot library after that. It worked on my Z and on my SHIELD as well.

This was essentially what I did:
http://greenrobotgamer.com/shieldzone/root-shield-portable-lollipop-5-1/

Mine seems to be working just fine, after obtaining root and installing SuperSU. I didn't bother with installing TWRP, I just hotboot the recovery. I'm rebooting my SHIELD as we speak, see if there's any issue
EDIT: Scractch that, it's not booting. How do I flash the latest image back in?

JCESAR2 said:
hey wolf, what is the easiest way to flash twrp with the 103 upgrade? thanks
Click to expand...
Click to collapse
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Boot the SHIELD in fastboot and connect it to your pc, then open a command window in a folder with the adb files and the recovery image and type: fastboot flash recovery -the name of the recover-.img, and it will flash the recovery. You can do that with the stock too.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.

JCESAR2 said:
thanks for the reply, also, when i boot the shield into fastboot it says in the first line : boot loader version ..../ device locked, does that matter? i rooted the shield already with kingroot.
Click to expand...
Click to collapse
You need to unlock your bootloader first.

ok long story short: since i had the shield drivers installed and tha adb drivers installed i did the oem unlock and after a confirmation screen on the shield i did it, then i immediately flashed the twrp image from the same command line. now the shield is stuck in nvidia android boot logo. any suggestions? thanks

I am in fact stuck in the boot as well. Anyone's got stock image we can flash?

nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
JCESAR2 said:
nevermind, after like 10 minutes the thing just booted fine, these are the perks of being a newb.
Click to expand...
Click to collapse
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.

Ink Rampant Wolf said:
Search for the SHIELD RAM Tool, it have everything that you all need to flash recovery or old firmware to unbrick the device. It also comes with the necessary files and drivers to work ADB Fastboot.
Sent from my HUAWEI P7-L12 using My-RoM V3.3.
Ask if you have doubts or problems, we're here to help.
Click to expand...
Click to collapse
Guess I'll have to flash the old firmware then, it's been sitting there forever.

341464 said:
I am in fact stuck in the boot as well. Anyone's got stock image we can flash?
Click to expand...
Click to collapse
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870

JCESAR2 said:
try this shield thread
http://forum.xda-developers.com/showthread.php?t=2388870
Click to expand...
Click to collapse
I just re-flashed the system using RAM, should be fine now. I'll just have wait for the OTA all over again. UGH.
I wish someone could provide a KitKat version tho.
EDIT: Annnd battery's at 15% so the system won't let me OTA yet.

SuperSU will work fine with my latest TWRP builds posted here. The older 2.8.5.0 builds will not work, neither will any build in the linked thread before yesterday. I used SuperSU 2.49 Beta and it worked as expected.
Side Note: The older builds will have the problem where boot will just hang. That seems to be because the older builds didn't have selinux policies built in, so some things never get set up right and the boot panics.

[Kernel] [6.0.1] [23.5.A.1.291] [Advanced stock with TWRP] [UB]

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: