This is a development thread, if your question belongs to general topic, please check the General topic
IMPORTANT : if you've just bought the device, and it is still under 4.2, DO NOT UPDATE with OTA. You would not be able to root the device (unless you buy an expensive cable)
STATUS
TWRP is fully working - selinux is available
On 4.2.2, Root is available via two methods : with cable improved here (great work guys) or without by using Towelroot
On 4.3, root is only achievable with the cable method : unlocking bootloader, booting recovery and flashing the supersu.zip
Recovery, root and unlock
Recovery (updated on 27/02/2015)
On bootloader, you can either :
1) boot it : fastboot -i 0x03F0 boot recovery.img (adapt to .img filename)
2) flash it : fastboot -i 0x03F0 flash recovery recovery.img (adapt to .img filename)
flashing it allows to have access to recovery directly, you need to keep pressing volume down when switching on the tab.
TWRP 2.8.1 Recovery (flashable)
HP's recovery
Rom available
MayaMod - cooked by juanig
Prerooted latest OTA Rom : 4.3-17r20-05-24 STOCK ROOTED : Thanks juanig (mirror by mrzood)
Misc
Partition infos
Data cable ref : 728141-001 SPS-Micro USB to USB - Mandatory to unlock bootloader and flash custom rom Picture
Rooting
With your bootloader unlocked (by cable), flash the supersu zip linked here
If you didn't update to 4.3, you can root with Towelroot v1 (thanks to mrzood for hosting)
once root, you can unlock your bootloader if not yet done.
Unlocking bootloader
With a cable : fastboot -i 0x03F0 oem unlock. WARNING: this will reset your tablet to factory default and loose all your data
By flashing a file, you need to be root : all info there (great work guys)
Sources
HP has released 4.2.2 source code, mirrored here
HP has now released 4.3 source code here mirrored here (thanks Scratz)
My device tree
Archives :
TWRP 2.8 Recovery (flashable)
TWRP 2.7.0 Recovery (flashable) (thanks to Juanig for testing)
CWN recovery - booting but partially working
TWRP - booting but partially working
--
Indeed, I'll update op on that point.
In addition, I need testers for twrp new release, as I don t have my cable yet
Addition of partition layout information
I'll give the new TWRP a try when I have some free time today.
Latest TWRP seems to work fine. Did not cause any softbricking.
Now I just need to make a working 4.2.2 zip to try and flash over my 4.3 install.
Works:
- Backup to external SD (tablet ext SD, did not test dock SD slot.)
- Restore from SD
- Wakes via touchpad/keyboard
- Mounts
- File browser
- Reboots to system and bootloader
Broken:
- Mouse pointer. It's there but does not move when using touchpad.
Here's a 14mb log file that I copied to SD if you wish to view: http://files.mrzood.com/14-7-8.1758zulu.recovery.log
Good news ! Did you flash it or boot on it ?
BENETNATH said:
Good news ! Did you flash it or boot on it ?
Click to expand...
Click to collapse
Flashed.
Ok, so could you do a full backup and share it with me ?
BENETNATH said:
Ok, so could you do a full backup and share it with me ?
Click to expand...
Click to collapse
Sent you a PM with the download link to the zipped backup.
Good work guys and thanks to Ben for starting the development thread. I'll spread the word to a HP forum and also to a Google+ Slatebook site as well.
EDIT: Just had another look at the price of the cable on the HP website and it's gone up to AUD $78!! HP are really not helping our cause here are they?
GrievousMcG said:
Good work guys and thanks to Ben for starting the development thread. I'll spread the word to a HP forum and also to a Google+ Slatebook site as well.
EDIT: Just had another look at the price of the cable on the HP website and it's gone up to AUD $78!! HP are really not helping our cause here are they?
Click to expand...
Click to collapse
i had no reply from their VP HP' assistance..
sad, sad situation.
For people with a cable, and interested in testing a custom rom with TWRP, here is one :
http://www.mediafire.com/download/bk92dlpdctt95tu/cm-10.1-20140704-UNOFFICIAL-maya.zip
BENETNATH said:
i had no reply from their VP HP' assistance..
sad, sad situation.
For people with a cable, and interested in testing a custom rom with TWRP, here is one :
http://www.mediafire.com/download/bk92dlpdctt95tu/cm-10.1-20140704-UNOFFICIAL-maya.zip
Click to expand...
Click to collapse
Flashed. Will not boot. Tired re-flash, wipe data, etc. Had to restore back to HP ROM
thanks for confirming
New build is online :
https://mega.co.nz/#!EBdWAILa!oFF9kSAGbN2OGhG6Jeu_qMLqLN2aBuU4kaKKZ6m8G9w
device tree added in OP
still no cable..it might became painful to be stuck without rom testing capabilities..
addition of a CM10.2 rom to test.
without testers, i'm stuck currently..
BENETNATH said:
addition of a CM10.2 rom to test.
without testers, i'm stuck currently..
Click to expand...
Click to collapse
My Slatebook is on the way, if I find a cable for a reasonable price I would be happy to test...
I got problem.
Do you have original recovery for reflash it?
I cannot try the 4.3 update with custom recovery (fail).
Can i try to flash CM 10.2 directly over the custom recovery?
At this time, i did a backup of 4.2.2 and restore it succesfully.
Thanks for your hard work.
I dont have the cable.
Without cable, your boot loader is not unlocked. You cannot flash a custom Rom.
Related
*** CAUTION ***
*** FOR A700 ONLY ***
*** FLASH AT YOUR OWN RISK ***
I've been getting back into the swing of thing's and decided to upload these insecure boot images for you all
The boot ramdisk is based on the EMEA.GB Jelly Bean ROM but should work for all A700's
About EasyRoot:
Patched Based on latest RV10RC01.EMEA.GB
Fully insecure boot.img
Full ADB access to /system
Installs latest cwm
Installs su and busybox
Can also be used to FULLY remove root (Does not relock bootloader)
You need:
Acer Iconia Tab A700 with an unlocked bootloader & already be running Jelly Bean
How to use:
Download zip and extract it on your computer
Run the included easyroot.bat
Follow onscreen intructions
Download:
A700 EasyRoot 2.0 md5: 8876aca04e29fe69d7368bc02006359c
Thanks to:
Moscow Desire
pawitp
chainfire
plus all those who helped to crack open the A700
Totally new, here...Been working on doing this for an hour and just got it installed..Now I'm at the SuperSu step. How exactly do I install SuperSu from CWM?
Okay..Install the exact same way you install the other zip. This tablet wrecks my nerves, and I can't stand messing with it. I've heard so many horror stories of bricks and I saved for a long time to have enough cash to buy this thing.
Thanks for your work, I've finally got my JB rooted and can play with my emulators and screenshot tools again.
Vorbeth said:
*** CAUTION ***
*** FOR A700 ONLY ***
*** FLASH AT YOUR OWN RISK ***
I've been getting back into the swing of thing's and decided to upload these insecure boot images for you all
The boot ramdisk is based on the EMEA.GB Jelly Bean ROM but should work for all A700's
About the boot.img:
Patched Based on latest RV10RC01.EMEA.GB
IconiaN - Built from Acer Jelly Bean kernel source
Fully insecured boot.img
Full ADB access to /system
You need:
Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean
ClockworkMod Recovery - 6.0.1.5 or newer
How to flash:
Download zip and place it on your virtual or external SD card
Boot your phone into ClockworkMod Recovery (via adb or with a key combo)
In main menu, select "install zip from sdcard"
Select "choose zip from sdcard" and browse to the location of zip
After flashing process is complete, reboot the device
Alternative install for Stock patched kernel ONLY:
Reboot to bootloader
Extract boot.img from the zip
Flash boot.img via fastboot
How to get root:
Install SuperSu via CWM
Install BusyBox from Play
Download:
Stock patched kernel md5: 4638ffe2bcb00352ccc702fdfab1d8cb
iconiaN source built kernel md5: 76b8e1020c6054debedf60efffdca609
Thanks to:
Moscow Desire
pawitp
chainfire
plus all those who helped to crack open the A700
(Kernel is unchanged from Acer other than a single "tag" line in defconfig, I will follow GPL and upload kernel source on request)
Click to expand...
Click to collapse
OK..don't want to sound dumb here. My bootloader is already unlocked. What steps do I need to do to get rooted? I'm not sure so I figured it was better to ask then to guess and mess things up! Thanks to all of you that do these things for us....
Sent from my DROID RAZR using Tapatalk 2
I'm sure it is a coincidence, but as soon as I finished, my external SD card became unreadable/unmountable. Trying it in my PC and it says it needs to be formatted. All my data was lost. (Well...Maybe...I'm trying some recovery stuff before I give up and reformat).
ExtremeRyno said:
I'm sure it is a coincidence, but as soon as I finished, my external SD card became unreadable/unmountable. Trying it in my PC and it says it needs to be formatted. All my data was lost. (Well...Maybe...I'm trying some recovery stuff before I give up and reformat).
Click to expand...
Click to collapse
You can look in the install script, it never touches the external sd card.
I think a lot of these issues are still related to cwm, I'm looking at it a bit to see what's really happeneing.
After flash this KERNEL, MY A700 can't read a NTFS ext-sdcard..
I was able to recover all my files, but still had to reformat the card. Not too big of a deal.
Try the stock one. Source built may not have ntfs enabled.
Seems acer don't release the exact source they actually compile and release
Sent from my EndeavorU using xda app-developers app
But... your kernel release the t3 cpu to 1.4Ghz
better then support NTFS.
casper326 said:
But... your kernel release the t3 cpu to 1.4Ghz
better then support NTFS.
Click to expand...
Click to collapse
Once I have moved house I will get everything setup properly and work more on the kernel
Vorbeth said:
*** CAUTION ***
*** FOR A700 ONLY ***
*** FLASH AT YOUR OWN RISK ***
I've been getting back into the swing of thing's and decided to upload these insecure boot images for you all
The boot ramdisk is based on the EMEA.GB Jelly Bean ROM but should work for all A700's
About the boot.img:
Patched Based on latest RV10RC01.EMEA.GB
IconiaN - Built from Acer Jelly Bean kernel source
Fully insecured boot.img
Full ADB access to /system
You need:
Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean
ClockworkMod Recovery - 6.0.1.5 or newer
Click to expand...
Click to collapse
Hi,
this seem very attravtive, thanks for putting this together. I have a few questions for you. Bearing in mind that I start from a 100% stock JB A700:
- Will any of the install steps wipe data / settings on my system ?
- Will it prevent futur OTAs ?
- Is there there a way to go back to stock if we do this ?
thanks for your help!
benjieb said:
Hi,
this seem very attravtive, thanks for putting this together. I have a few questions for you. Bearing in mind that I start from a 100% stock JB A700:
- Will any of the install steps wipe data / settings on my system ?
- Will it prevent futur OTAs ?
- Is there there a way to go back to stock if we do this ?
thanks for your help!
Click to expand...
Click to collapse
I think I can answer.
1. Shouldn't effect current install. It's a boot.img only and CWM if you don't have it.
2. Yes. Unlocked bootloaders and rooting will make future OTA's inoperable. You will get a message stating "unfortunately you can not receive OTA. Please contact Acer". or something like that.
3. There's always a way to go back to stock. Typically it involves installing a stock rom, which of course will clean all your user data and such.
MD
Moscow Desire said:
I think I can answer.
1. Shouldn't effect current install. It's a boot.img only and CWM if you don't have it.
2. Yes. Unlocked bootloaders and rooting will make future OTA's inoperable. You will get a message stating "unfortunately you can not receive OTA. Please contact Acer". or something like that.
3. There's always a way to go back to stock. Typically it involves installing a stock rom, which of course will clean all your user data and such.
MD
Click to expand...
Click to collapse
Spot on,
Why go back to stock? Any ota ill be repacking so it can be flashed via cwm
Sent from my EndeavorU using xda app-developers app
Concerning bootloader and CWM
Vorbeth said:
*** CAUTION ***
*** FOR A700 ONLY ***
*** FLASH AT YOUR OWN RISK ***
I've been getting back into the swing of thing's and decided to upload these insecure boot images for you all
The boot ramdisk is based on the EMEA.GB Jelly Bean ROM but should work for all A700's
About the boot.img:
Patched Based on latest RV10RC01.EMEA.GB
IconiaN - Built from Acer Jelly Bean kernel source
Fully insecured boot.img
Full ADB access to /system
You need:
Acer Iconia Tab A700 with unlocked bootloader & already be running Jelly Bean
ClockworkMod Recovery - 6.0.1.5 or newer
How to flash:
Download zip and place it on your virtual or external SD card
Boot your phone into ClockworkMod Recovery (via adb or with a key combo)
In main menu, select "install zip from sdcard"
Select "choose zip from sdcard" and browse to the location of zip
After flashing process is complete, reboot the device
Alternative install for Stock patched kernel ONLY:
Reboot to bootloader
Extract boot.img from the zip
Flash boot.img via fastboot
How to get root:
Install SuperSu via CWM
Install BusyBox from Play
Download:
Stock patched kernel md5: 4638ffe2bcb00352ccc702fdfab1d8cb
iconiaN source built kernel md5: 76b8e1020c6054debedf60efffdca609
Thanks to:
Moscow Desire
pawitp
chainfire
plus all those who helped to crack open the A700
(Kernel is unchanged from Acer other than a single "tag" line in defconfig, I will follow GPL and upload kernel source on request)
Click to expand...
Click to collapse
If my bootloader is already unlocked and I have a previous Recovery on the tablet, do I still need to install CWM BEFORE I boot to Recovery adn install the boot.zip file?
bidniss said:
If my bootloader is already unlocked and I have a previous Recovery on the tablet, do I still need to install CWM BEFORE I boot to Recovery adn install the boot.zip file?
Click to expand...
Click to collapse
Depends on your version of the ""previous recovery"". Seems there are many in the past 3 months. Some of them. were "brick-makers".
Generally, you are safe to "install zip only".
MD
Thanks to all who worked on this!
Moscow Desire said:
Depends on your version of the ""previous recovery"". Seems there are many in the past 3 months. Some of them. were "brick-makers".
Generally, you are safe to "install zip only".
MD
Click to expand...
Click to collapse
Thanks MD!- I had ot flash the boot.img via adb becasue the .zip format wouldn''t work. Basically, to play it safe, I installed CWM and then went from there and got rooted. Thanks to all of you dev kind of folks who worked on this for people like me who know just enough to be dangerous!
Vorbeth said:
Spot on,
Why go back to stock? Any ota ill be repacking so it can be flashed via cwm
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Thanks V & MD , i appreciate your skills + patient support!
I am desperate to root my A700, but wasn't keen on having to wipe data/apps + not being able to benefit from Acer's updates.
According to your posts, both are no real issue. So root here I come!
benjieb said:
Thanks V & MD , i appreciate your skills + patient support!
I am desperate to root my A700, but wasn't keen on having to wipe data/apps + not being able to benefit from Acer's updates.
According to your posts, both are no real issue. So root here I come!
Click to expand...
Click to collapse
Well, you shouldn't need to do wipes and such for this process. In fact, I would use CWM just to install things just to play it safe.
In my opinion, the JB build runs good as it is, although you may want to delete a couple of pesky apps running in the background.
If you're really worried, you can try using adb to push SU and the superuser apk after you fastboot the insecure boot.img. ADB should be working with it now.
MD
Moscow Desire said:
Well, you shouldn't need to do wipes and such for this process. In fact, I would use CWM just to install things just to play it safe.
In my opinion, the JB build runs good as it is, although you may want to delete a couple of pesky apps running in the background.
If you're really worried, you can try using adb to push SU and the superuser apk after you fastboot the insecure boot.img. ADB should be working with it now.
MD
Click to expand...
Click to collapse
I have to agree, when I get time I'm going to build a cwm with all the wipe features removed
Sent from my EndeavorU using xda app-developers app
Moscow Desire said:
Well, you shouldn't need to do wipes and such for this process. In fact, I would use CWM just to install things just to play it safe.
In my opinion, the JB build runs good as it is, although you may want to delete a couple of pesky apps running in the background.
If you're really worried, you can try using adb to push SU and the superuser apk after you fastboot the insecure boot.img. ADB should be working with it now.
MD
Click to expand...
Click to collapse
Vorbeth said:
I have to agree, when I get time I'm going to build a cwm with all the wipe features removed
Sent from my EndeavorU using xda app-developers app
Click to expand...
Click to collapse
Guys, this is getting quite technical. How do these useful advices relate to the steps by step initial post. Or in simple terms what are the steps starting from Stock JB and aiming at a safe route to... root
thx
this recovery still has some backup problems.
How to use this Recovery:
1. Download cwm-recovery-6.0.2.7.zip & unzip it.
2. Connect your device to computer with USB-cable and make sure that USB-Debugging is "enabled" !
3. Double click on the "start_recovery.bat" file
4. Now a command-window will opened follow the instructions inside and continue by "press any key"...
5. Your device now should reboot into CWM 6.0.2.7
-Don´t try to flash it!-
NOTE: Everytime you want to use this type of recovery, you have to execute the "start_recovery.bat" file.
WITH THE RECOVERY ,EASY ROOT OUR DEVICES .
1. Flash 316root.zipwith the recovery.
2.Reboot,your devices is rooted !
I'd like to be the first tester of the new method,
i'll report my results as soon as possible
I tested it, you're the best!!
I'll link my outdated thread to your thread here so people use this better method
but it's also stuck at backing up system, but it can mount all the storages :good:
and i think adb isn't working?
detects the phone as offline
Please add to the op that people shouldn't restore boot/recovery because of locked bootloader, and the backedup ones aren't signed
Thanks your link.
backup problem ,i cant solve,
but I will try to fix adb Pro
Good Job Chen! Keep it up :good:
Did you build the recovery from source?
if so, can you build one of version 5? it's more compatible with gingerbread.
Yes ,I build it from source.
I built cwm5 before , but it also stuck on backup /system.
Why cwm5 is compatible ?
chen2011521 said:
Yes ,I build it from source.
I built cwm5 before , but it also stuck on backup /system.
Why cwm5 is compatible ?
Click to expand...
Click to collapse
i don't know i just read that cwm5 is for gingerbread, cwm6 is for jellybean
@chen
Just a query. For now can we boot custom kernel like this?(executing it from bootloader). If so we can try it and work for stable version? What you say?
PS : I recommend you to use Bing translator, it is much better than others.
I have not tested,but ,first we must have a custom kernel.
You mean, everytime we enter the system to boot custom kernel ? It would be a lot of trouble.
Thus, why defy can flash a custom kernel? 2Ndinit?
Perhaps we can do the same work.
But I don't know where to begin. And custom kernel is booted by 2nd-boot not 2nd-init(I think).
hi, i would to try but the link is not working anymore
nervermind thank you for your work
This is TWRP Recovery for the HP Slate 21 (phobos).
!! USE AT YOUR OWN RISK. !!
Kernel:
Stock prebuilt Kernel 3.4.66, source not avail. yet.
Devices:
HP Slate 21
Requirements:
Your bootloader must be unlocked, see the instructions-link in this post.
Download:
img for fastboot: TWRP-2.8.4.0-phobos.img
flashable zip: TWRP-2.8.4.0-phobos.zip
The official changlog is here.
Installation instructions:
unlock the bootloader
download the recovery image
boot your slate
reboot to fastboot mode, don't select anything from the menu:
Code:
adb reboot bootloader
flash recoveryimage:
Code:
fastboot flash recovery twrp_phobos.img
[where twrp_phobos.img is the name of the file image you downloaded]
now you can select Recoverymode in the menu to reboot into recovery
or if you have already flashed a recovery:
download flashable zip
flash it via recovery
Root:
If you flash an unrooted rom, TWRP asks you to root after installation, say yes here.
Or you can flash SuperSU zip by @Chainfire, you can download it from this thread.
Have fun!
Changes:
- v2: working adb, mtp, gui update (mtp button in mount-menu, font)
- Update to TWRP 2.8.4.0
Thanks to:
TWRP Team
CyanogenMod Team
@pershoot
@xdaca
@hetzbh
Greetz, evilp
Oh man...
You made CWM and TWRP both on the Slate 21, which is really, really great!
What next, plan to build Kitkat for the Slate 21?
Thanks for your great work!
hetzbh said:
Oh man...
You made CWM and TWRP both on the Slate 21, which is really, really great!
What next, plan to build Kitkat for the Slate 21?
Thanks for your great work!
Click to expand...
Click to collapse
first build ready but failed to boot waitinf forma new hardware nVidia from cm sources
Inviato dal mio Nexus 4 utilizzando Tapatalk
hetzbh said:
Oh man...
You made CWM and TWRP both on the Slate 21, which is really, really great!
What next, plan to build Kitkat for the Slate 21?
Thanks for your great work!
Click to expand...
Click to collapse
Thx very much
I mean that @vocoderism is doing a great job to building the first rom for the slate.
He has more knowledge then i, but i would like to build omnirom, need some time...
greetz, evilp
evilpfeiffers said:
Thx very much
I mean that @vocoderism is doing a great job to building the first rom for the slate.
He has more knowledge then i, but i would like to build omnirom, need some time...
greetz, evilp
Click to expand...
Click to collapse
take patience and perhaps in a few week first alpha rom
Inviato dal mio Nexus 4 utilizzando Tapatalk
Hi,
i have an update: TWRP 2.8.1.0 for phobos v2.
Changes:
- v2: working adb, mtp, gui update (mtp button in mount-menu, font)
Look at OP, its updated.
greetz, evilp
slate 21 pro
Any idea whether this recovery will work on slate 21 pro?
bill g.
ps good job
I am tempted to just try it on the K100 anyway. Then I just have to get myself and my wallet ready for a kitkat rom.
Hi,
I just installed the TWRP, but it seems it doesn't see the external SD card. Any way to fix it?
@vocoderism - there are many devices who are based on Tegra 4 and have Kitkat. Could you share what is the problem when preparing the ROM?
Thanks
hetzbh said:
Hi,
I just installed the TWRP, but it seems it doesn't see the external SD card. Any way to fix it?
@vocoderism - there are many devices who are based on Tegra 4 and have Kitkat. Could you share what is the problem when preparing the ROM?
Thanks
Click to expand...
Click to collapse
I know but i am outside for work this period .at the begin of january i start build
Inviato dal mio Nexus 4 utilizzando Tapatalk
hetzbh said:
Hi,
I just installed the TWRP, but it seems it doesn't see the external SD card. Any way to fix it?
@vocoderism - there are many devices who are based on Tegra 4 and have Kitkat. Could you share what is the problem when preparing the ROM?
Thanks
Click to expand...
Click to collapse
Hi, for me backup / restore from / to sdcard is working fine, 16Gb card, vfat. Maybe filesystem?
Greetz, evilp
I keep checking back here like a giddy little girl thinking she will find candy.
Could it be that i bricked my Slate 21 s100
Hi evilpfeiffers,
hope you can help... After updating my slate 21 (which was rooted) OTA to Kitkat, i had this sound problem, which made the slate 21 useless for me. So i was looking for a way to get back to 4.2.
Somehow I got lost and the last thing i remember was "flashing twrp_phobos.img" but my bootloader wasn't unlocked yet. Since then, the slate 21 got stucked while booting at the HP logo with the streaking lines flying around forever....
Do you think I can fix this with a recovery? Maybe using your newly posted file "HP OTA Update 17r25.1-010-10-WW V2, with SDCard/USB storage permission mod"?
Thanks for your time!
sidibay
evilpfeiffers said:
This is TWRP Recovery for the HP Slate 21 (phobos).
!! USE AT YOUR OWN RISK. !!
Kernel:
Stock Kernel 3.4.35, build from source.
Devices:
HP Slate 21
Requirements:
Your bootloader must be unlocked, see the instructions-link in this post.
Download:
twrp_recovery_phobos_v2.img
TWRP-2.8.1.0-phobos_v2_flashable.zip
Installation instructions:
unlock the bootloader
download the recovery image
boot your slate
reboot to fastboot mode, don't select anything from the menu:
Code:
adb reboot bootloader
flash recoveryimage:
Code:
fastboot flash recovery twrp_phobos.img
[where twrp_phobos.img is the name of the file image you downloaded]
now you can select Recoverymode in the menu to reboot into recovery
or if you have already flashed a recovery:
download flashable zip
flash it via recovery
Root:
Now you can flash SuperSU zip by @Chainfire, you can download it from this thread.
Have fun!
Changes:
- v2: working adb, mtp, gui update (mtp button in mount-menu, font)
Thanks to:
TWRP Team
CyanogenMod Team
@pershoot
@xdaca
@hetzbh
Greetz, evilp
Click to expand...
Click to collapse
sidibay said:
Hi evilpfeiffers,
hope you can help... After updating my slate 21 (which was rooted) OTA to Kitkat, i had this sound problem, which made the slate 21 useless for me. So i was looking for a way to get back to 4.2.
Somehow I got lost and the last thing i remember was "flashing twrp_phobos.img" but my bootloader wasn't unlocked yet. Since then, the slate 21 got stucked while booting at the HP logo with the streaking lines flying around forever....
Do you think I can fix this with a recovery? Maybe using your newly posted file "HP OTA Update 17r25.1-010-10-WW V2, with SDCard/USB storage permission mod"?
Thanks for your time!
sidibay
Click to expand...
Click to collapse
Hi sidibay,
you can try this:
With the slate powered off, press and hold the Volume down button and Power button at the same time, hold it till you see the bootloader screen.
When working, then you are in bootloader mode now and have fastboot (no adb).
From here you can unlock the bootloader (with your usb connected pc or notebook):
Code:
fastboot oem unlock
then flash the twrp recovery image twrp_recovery_phobos_v2.img:
Code:
fastboot flash revovery twrp_recovery_phobos_v2.img
now you can reboot your slate into this working recovery by select the appropriate menu item.
From the recovery you can flash my 4.2 zip as usual, you can download it here.
Hope this helps,
greetz, evilp
Hi evilp,
thank you so much... now we have our slate back again thank to your help! It's used as a media player, internet station, mail, calender, lots of things for the whole family.... and we missed it a lot. Now it's up and running again . I think I just forget Kitkat, since there is still no fix for the sound problem with the headphone jack.
Again, mille grazie!
sidibay
TWRP Recovery 2.8.4.0
Hi,
i have an update: TWRP 2.8.4.0 for phobos.
Look at OP, its updated.
greetz, evilp
sidibay said:
Hi evilp,
thank you so much... now we have our slate back again thank to your help! It's used as a media player, internet station, mail, calender, lots of things for the whole family.... and we missed it a lot. Now it's up and running again . I think I just forget Kitkat, since there is still no fix for the sound problem with the headphone jack.
Again, mille grazie!
sidibay
Click to expand...
Click to collapse
Nice to help you and your family, have much fun with your slate.
To fix the problems we must wait for a update from hp
greetz,
evilp
Hey!
I have compiled the Cyanogenmod 12.1 for the Slate (both s100 and k100 work). There are a few issues but I hope I can clear them up soon. You are more than welcome to test it out. You can find more information in this thread:
http://forum.xda-developers.com/android/general/rom-cyanogenmod-12-1-hp-slate-21-t3201416
Peace,
Quaesar
TWRP
2.8.7.0
UNOFFICIAL
Just as the title says this is an unofficial build of TWRP recovery v2.8.7.0 for the HTC DESIRE S (Saga).
*** I DO NOT OWN A DESIRE S*** This has been tested on by numerous users previously and I test all my releases on the nearly identical Desire HD. It has been tested with both Sense roms and current KK/LP AOSP roms. I have put it to the test and not found any issues so far. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Version for ODP Saga builds
<<HERE>>
Current Version for ODP Saga-opt builds
<<TWRP for SAGA-OPT>>
For more info on SAGA-OPT see the original release notes for ace-opt cm-12.1 HERE
Special thanks to @Mustaavalkosta & @kylon for all his work keeping this device alive for so long.
SOURCES
Recovery built in a CM-12.1 environment using device trees/kernel
from Mustaavalkosta's OpenDesireProject github
My modified trees/kernel are HERE and HERE
TWRP source from Omnirom
Code:
Changelog:
7/30/15
-2.8.7.0
4/14/15
- 2.8.6.0
2/28/15
- fix reboots
2/27/15
- 2.8.5 release
- LP cm-12.0 based
- updated offmode blobs
1/10/2015
- 2.8.1.2 release
- MTP support is back on, no more USB mount. CM-12.0 went this direction and so shall recovery
- by-name partition mount support. Needed for 1/10 nightly and beyond.
1/5/2015
- 2.8.1.1 release (i know i'm falling behind)
- /sd-ext support
- f2fs support
11/15/2014
- 2.8.1 release
- Performance profiles in recovery, should speed up backup/restore just a bit
- Offmode charging images are back!!! Thanks to @mdmower for the guidance from 8960 series HTC's
6/13/2014
- fixed adb in recovery
6/12/2014
- fixed ability to use encryption
6/11/2014
- initial release
XDA:DevDB Information
TWRP-Desire S, Tool/Utility for the HTC Desire S
Contributors
jrior001, jrior001
Source Code: https://github.com/OpenDesireProject
Version Information
Status: Stable
Created 2015-11-23
Last Updated 2015-11-22
I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.
jrior001 said:
I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.
Click to expand...
Click to collapse
Thank you very much for your kind contribution to the community. I am very appreciated.
Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!
moesus said:
Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!
Click to expand...
Click to collapse
It might be possible by using Fastboot.reg method as it is working for me.
Hi,
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
I can get twrp-2.6.3.0-saga.img to work OK.
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
i have
HBOOT 2.00.2002
S-OFF (unlocked)
RADIO 3822.10.08.04_M
thanks
stehaworth said:
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
Click to expand...
Click to collapse
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
stehaworth said:
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
Click to expand...
Click to collapse
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB
i23098 said:
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB
Click to expand...
Click to collapse
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...
stehaworth said:
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...
Click to expand...
Click to collapse
Yeah, if you have an Hitachi panel you can't run a recent CM... It shouldn't affect the recovery, though... I think
lool, I flashed TWRP-recovery-sagaopt-2.8.7.1.img and issued factory reset... and it formatted my SD card (coz it takes it as internal memory)... I already recovered files most of files, but was "a bit" surprised... was it also like that in previous versions?
Unauthorized
i recently got to stupid situation - i wanted to try cm13 so i used tweaked twrp 2.8.7.1 for saopt sm13 and formated my sd card, loosing everything - i had to load the rom to the phone by using ./adb push. the rom was not stable enough to be used, so i wanted to go back - flashed back twrp 2.8.7.0 formated again my card and finding that i cannot mount phone to my macbook (dunno why?) and that ./adb push returns with info that device is unauthorized. i had to use different phone to put rom on sd card to be able to install it.
tweaked version or older version of twrp did not have this problem.
Hi, where can I read Step by Step instalation proces of TWRP
Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay
c_kay said:
Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay
Click to expand...
Click to collapse
Same problem
mentodsman said:
Same problem
Click to expand...
Click to collapse
use Rashr - Flash Tool apk to flash the img
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.