Related
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Giving your device the ability to flash your favourite custom ROMs, Kernels, Mods in the future. Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img. As you can see, it works:
Acuap said:
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
Click to expand...
Click to collapse
This has not been tested by me but is reported to work, but is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #2: http://d-h.st/jca
Stock Recovery: http://d-h.st/1OW
Changelog:
Code:
[I][U]Experimental #2[/U][/I]
Mount partitions fix
Backup / restore directories fixed^
Now with touch
[I][U]Experimental #1[/U][/I]
Public release
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
scott14719 said:
Thank you. I have always preferred to use CWM for custom recovery. By chance, are you planning to release a i9505 version of CWM. I'm sure one will surface as soon as the official phone release or as soon as the forum splits, but I thought I would ask just in case. Again, thank you.
Click to expand...
Click to collapse
Yeah I can build for it too. I just require the stock recovery img and thr stock boot.img
After trying TWRP i don't want to come back to CWM anymore.
Thanks! Gonna try it today and give you info if this works!
emwno said:
Hey, I bring to you, Clockworkmod Recovery or commonly known as CWM for your beloved i9500 (S4). Thankyou to 'as i9000' for giving me the stock recovery and stock boot.img
This has not been tested by me and is extremely experimental. I hold no responsibility for
any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
Anyways I have provided CWM and the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
CWM Experimental #1: http://d-h.st/MWE
Stock Recovery: http://d-h.st/1OW
Click to expand...
Click to collapse
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Hey! I can confirm that it works flawlessly on i9500. No Bricks, instalation went smooth, boots to CWM without problems. Gonna post some more details later. See ya!
sorg said:
After trying TWRP i don't want to come back to CWM anymore.
Click to expand...
Click to collapse
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Ill build that too. after CWM is fixed completely.
KINGbabasula said:
Can i add your recovery in my tool?
Inviato dal mio GT-I9070 con Tapatalk 2
Click to expand...
Click to collapse
sure
PLUG313 said:
how long until TWRP is released for the S4 after it's released?
I've always used CWM or CWM-based, so this time I'm going to try TWRP
Click to expand...
Click to collapse
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
sorg said:
TWRP is opensource. Technically, SGS4 is not much different from SGS3 (from TWRP point of view). So, it won't be a problem to compile for those who already has SGS4 and has experience with compilation.
Click to expand...
Click to collapse
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
CWM works flawlessly
If any i9505 user or Korean galaxy s4 user reads this. Please post your devices stock recovery.img and stock boot.img. so thst I can provide CWM for you as well
Experimental #2 released. Now more reliable with backup / restore
emwno said:
I dont think so. I have compiled twrp before many times and it has never worked like that for me. A device tree needs to be set up for the i9500 which im working on to compile twrp (maybe im wrong here)
Click to expand...
Click to collapse
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
sorg said:
Only very basic device setup required for TWRP. Can try some existing device with the same display resolution and then tweak some parameters.
I will try it by myself when i will get SGS4.
Click to expand...
Click to collapse
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
who have galaxy S4 ???
PM me please
emwno said:
I have setup the tree for both building source roms and twrp recovery. Tho, the device tree for roms is incomplete, you can find it here: https://github.com/emwno/android_device_samsung_ja3g . And as for the twrp, I cant build it as ill need to sync source code again. (wiped some directories accidentally)
Click to expand...
Click to collapse
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
sorg said:
For SGSIII i build just TWRP binary, not whole recovery image. I like to make my own custom ramfs. I don't use exfat_fuse. I use native samsung kernel modules with simple modification of TWRP to let it think it uses FAT volume. Also i use sdcard binary to mount /sdcard as it mounted in android to avoid files access rights mess. That's why i get only TWRP binary linked statically (instead of dynamically).
I use CM9 source tree. When i got first patches for SGSIII TWRP - they were for CM9. So I continue to use CM9 since there are absolutely no reason to switch to CM10.x in terms of recovery building.
Because my recovery requires some amount of manual work and many tries, i cannot make it without having device in hands. So, i will wait for SGS4.
If there won't be SGS4 tree in CM, then i'm going to use SGSIII's one with adjusted resolution. Everything else should be the same as in SGSIII, IMHO.
Click to expand...
Click to collapse
I should have thought of that. ... anyways I set up one with the twrp flags. Tried building on a 32bit system but failed to do so. If you want, I can send you everything you will need
Will it support extfat?
Because if extfat is the default file system on a S4,there is no point without it.
... And don't give me no license BS. M$ already got my cash when I put my 649€ on the electronic stores counter.
Sent from my GT I9300
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
dekraan said:
Hey all,
I love stock android! So when i read about OpenKirin I was excited. Did anyone use this to install LineageOS on our mate9 successful? What are your experiences?
I have another question as well: I changed my model to the MHA-L29, rooted with a custom recovery.
OpenKirin says it needs to have the stock one. Does anyone have a link to the stock MHA-L29 recovery and a guide on how to install it?
Click to expand...
Click to collapse
First off, this thread probably belongs in Q/A.
Moving on:
I've run all 3 provided ROMs, Carbon as my daily driver and Lineage and RR for testing various things. They all work pretty well.
For stock recovery & ramdisk, download your current firmware (or if you've run other Treble ROMs as well, the version that corresponds to your current build number in Settings / System / About Phone) using Firmware Finder - you only need the main update.zip for this. You'll also need one of the utilities for extracting them. There's Huawei Update Extractor (I think that's what it's called anyway) for Windows, or https://github.com/marcominetti/split_updata.pl for Linux / Mac. Extract the ramdisk and recovery ramdisk images and there you go.
Installing those is a matter of rebooting into the bootloader and running:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash ramdisk ramdisk.img
(The name for recovery_ramdisk.img may vary a bit - the windows app will extract it as RECOVERY_RAMDIS.img.)
From there, just follow their instructions. If you have any problems, hit up the Telegram chat linked off the site, someone will be willing to help.
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
dekraan said:
@irony_delerium, thank you very much. That sounds like something even I can do without too much problems
How do you like it, being on LineageOS?
Click to expand...
Click to collapse
Like I said in my original reply, my daily driver is Carbon; the Lineage builds I've only run briefly because NFC wasn't enabled, but the CarbonROM builds there have it. I use Google Pay every day, so it's kind of a requirement for me.
With that said, the only thing that's got issues for me is the camera app, and most of the blame for that is with Huawei. It generally works, but it'll close & restart often when switching modes or trying to start a recording.
I know there are various other minor issues with recording video in all 3, again because Huawei. (They put together bum codecs, and then patched the system side of the EMUI media stack to deal with the bum codecs, instead of fixing the codecs.)
Also worthy of mention (especially because I see people asking about this all the time): there is no VoLTE support. The devs are aware of it. Unless you're on a network that is pure LTE, it's mostly a non-issue. If you are, it's probably a deal breaker.
Getting on from there, they're all clean Android experiences, without the overbearing weight of EMUI. They don't try to pull some of the things EMUI did - the final breaking point for me was when it insisted on terminating apps in the background regardless of how much you might actually be using them. (In my case, AdGuard as a VPN service.)
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
talpur1 said:
Dear Sir
How Can I Revert to Stock Emui?
I am on Lineage baeta 4 ROM.
With Stock Recovery.
Tried Update and Hwota Methods but no Success.
I have Searched Everywhere.
Please Do A Step By Step Guide for Newbies.
Regards
Click to expand...
Click to collapse
Some comments before, Huawei Firmware Extractor. Extract system.img from the stock rom you used before flash Lineage.
Flash stock system.img in fastboot.
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
talpur1 said:
I have downloaded and tried to extract 4 roms but The Extractor tool is Giving error.
Its Giving invalid Hearder crc error.
Click to expand...
Click to collapse
Go to settings in the app and disable CRC checking. (Bug in the app.)
I was on OldDroid's OpenKirin, but today switched to Carbon Beta 2 from https://openkirin.net/download/. This installed without problems and I did a hard reset as part of installation. The earlier version worked very well, except there were a few bugs. I haven't found any bugs in this ROM yet.
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
jellmoo said:
Random question: Does anyone know if it's safe to go from one build to another directly? I'm trying Lineage but would like to give Resurrection Remix a go. The instructions say that you should be coming from EMUI...
Thanks
Click to expand...
Click to collapse
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
irony_delerium said:
It's fine to go between them, provided you reload the stock ramdisk (if you installed Magisk) & factory reset before booting into the new ROM.
Click to expand...
Click to collapse
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
mcc2005 said:
You can switch between the Custom Roms. I always do. Backup your data on the data partition via USB to PC, go to TWRP do a factory reset and then install the new image via fastboot. Reboot and rejoice
Click to expand...
Click to collapse
TWRP only works right on a Huawei device if you're either decrypted or running EMUI. (On a custom ROM, with an encrypted device, TWRP doesn't even start up - it locks up at the splash screen.)
Factory reset using stock recovery. Only using stock recovery. The OpenKirin team will not support any other configuration.
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
mcc2005 said:
yes you are right. but there is still the possibility to do these things with a patched TWRP. I use this for my Mate 9 https://drive.google.com/file/d/1h50RJ6LNNSEVW9CS16C0NjeP7ZZNTECE/view?usp=sharing
Click to expand...
Click to collapse
And the reason why I say anything is because the 2 most common problems I see are:
1) "I'm on Jio, where's my VoLTE?"
2) "I used TWRP and (it's not working | I screwed up | it's broken)".
The response to the first is universally, go back to stock.
The second, restore your entire stock firmware and then follow the instructions exactly as they are written.
With root, you can back up your apps with Titanium. I haven't had good luck with backing up settings with Titanium and after attempting to restore settings, I usually wind up wasting an hour or two and then factory-resetting and just reinstalling the apps. Now I don't even bother backing up settings, but just back up my apps. Even then two or three seem to be botched but uninstalling/reinstalling those will fix that problem. (It isn't always the same ones, either; not sure what causes this). This approach avoids the pain of configuring apps, e.g. travel app usernames and passwords, as well as preserving messages and the like. The biggest nuisance for me is that I carry around 40 unread Amazon books, which have to be sent to the phone (and I'm not so good at remembering which ones I've already read out of the more than 500 in my account), and I carry a bunch of google offline maps, which have to be manually recreated. Lastpass helps with login information too.
In my most recent (Carbon B2) install, I didn't bother with the backup but installed everything fresh and I had a fully functioning phone with 99% of the configuration I like within 2 hours, since I'd been pretty careful to put all the passwords and so on for my roughly 80 apps into a secured text file, as well as backing up my Nova launcher settings.
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Caguayote said:
Hi guy's I got a question if anyone can help me out
I'm on MHA-L29 8.0.0.360 (c567)
No custom rom but I got root with supersu
How can I install this carbon rom I try allready but twrp ask me on what partition I want to install the .img file and It shows bunch of it
I'm running twrp latest by pretoriano
Thank you very much guys
Click to expand...
Click to collapse
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
irony_delerium said:
Restore your stock ramdisk and recovery partitions. (I'd actually start with a full restore to stock firmware first: get your vendor patches in order. 8.0.0.369 is available for most phones on c567, 370 might be available.)
Factory reset using stock recovery. Flash with fastboot. Magisk for root & SafetyNet.
Click to expand...
Click to collapse
do you know where can i download the stock ramdisk and recovery partition for mate 9 i was running 8.0.0.369 sorry i put 360
im stuck on twrp splash screen and i cant go to access my backup file to restore and i only access fastboot mode
but my phone says unlocked then frp says lock thanks for all your help
Now i'm using android 7.0. based rom aur 2.3, if i want to install that stock android rom, do i have to flash android 8 based twrp?
Hello all,
I understand that TWRP on our devices is built on the Nougat kernel (hence why we can't boot with it) because the touch-screen doesn't work in TWRP when building it with the Oreo kernel (and presumably the Pie kernel -- I don't know if anyone has tried).
However, even if it still has to be built from the Nougat kernel like the current version of TWRP we are all using, could someone who has the skills and knowledge build the latest 3.2.3-1 version, which was just released a few days ago for the Pixels, for our Essentials? It has the capability to unencrypt data in Pie, regardless if you have a lockscreen pattern, pin, or password (along with many other new features and fixes since 3.2.1-0 was released), so it would finally no longer be necessary to delete all fingerprints and lockscreen pattern/pin/password before going into TWRP and then having to restore them all back after leaving TWRP and then teaching all apps the changed fingerprints.
Much, much thanks in advance to anyone who can do this!! I know that anyone who knows how to build a ROM could build TWRP in almost no time at all.
Thanks again,
Chris
and if the new TWRP can flash Magisk to both slots we wont need stock kernel when rooting. Magisk 17.1 has the ability to flash to both slots, but current TWRP patches only active slot when flashing Magisk zip.
supposedly some devs are working on it. Seems like it'll be a while
https://forum.xda-developers.com/showpost.php?p=77421949&postcount=16
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
AndroidDevices said:
Not to jump too far ahead, but a Developer and friend I am working with wants to build an updated TWRP, especially now that Pie is out, we could use those Treble and Pie fixes.... He is also working on a ROM, but we are at the early stages, and he has an Essential and I got mine today. He was finishing up on another Project at the moment, now that I received my Essential we can get things going and work our way, all the way to Official Perhaps? Time will tell...
Click to expand...
Click to collapse
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
starcms said:
Simply awesome to hear that! Seriously looking forward to what you guys release in the future!!!
Click to expand...
Click to collapse
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
AndroidDevices said:
I am hoping we get started on TWRP this weekend. My friend is adamant about getting us a new Recovery or an update one at the very least, but i believe TWRP is the 1st thing on our to do list.... :good: With September breaking our current, outdated Recovery, made it a Priority....
Those of you who came to the channel, we thank you for your support!
Telegram Essential PH-1 Dev Group : https://t.me/EssentialPH1DEV
By the way, we have another Mata Dev working with us!
Click to expand...
Click to collapse
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
starcms said:
Things are worse than I thought. I didn't use TWRP to root the September release. What exactly did September break on the outdated TWRP we currently have available?
Thanks again in advance for getting us Mata users an updated TWRP!!
Click to expand...
Click to collapse
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
starcms said:
That's bizarre. I thought that was specifically the reason TWRP for the Essential is built on a Nougat kernel, so that the touchscreen would work in TWRP. I was told if it was built on the Oreo kernel (this was before Pie was released), so that we could boot with TWRP installed, the touchscreen wouldn't work in TWRP.
I don't know how the September update (or any ROM) could stop the touchscreen from working in the existing, old TWRP version we have. I thought you were going to say it couldn't mount /system or /data or something to that effect with September. I'll have to try it myself and see.
Regardless, still really looking forward to what you and your team come up with! It'll be great to have an updated TWRP version for the first time in a year. And being able for it to unencrypt Pie (and possibly being able to boot with it installed like on the Pixels) will be a Godsend.
Click to expand...
Click to collapse
In order to have TWRP boot and have it installed, we actually need a TWRP.img to Fastboot Boot into Recovery. At that point you would flash your ROM and then there is a 2nd TWRP required that is a zip file called an installer. This is what allows you to boot into recovery from either the hardware power and volume button, or a standard Reboot to Recovery without having to use Fastboot. So again, (2) TWRP files are needed, a boot img and a zip installer. 1st we need to get the boot img working properly and then the installer.
Also, I was informed there is another DEV working on TWRP. Hopefully we can put 2 and 2 together and produce the proper Recovery.
I will update this thread as things get accomplished, and then hopefully all said and done and we can create an Unofficial TWRP thread.
I hoped, now that prices came down on this phone people would jump on it and development picking up. But even the current state seems slow.
I wish we had a nice working TWRP already, and as far as a ROM being mentioned, oh how we need some ROMS that don't have Gapps preinstalled.
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
hmm
AndroidDevices said:
On TWRP on September build, the device's display digitizer or the screen didnt feel touch, I read one member using TWRP with an OTG mouse to root the device. I believe the Dev already knows the problem, but I think he is doing a total over haul of TWRP to update for PIE and Treble....
Of course, we are, some of us at least are here to help and learn what we dont know...
Click to expand...
Click to collapse
It was not a TWRP issue but an issue with the Sept update. Some files were left out and the flash left the touch screen dead. I had the issue and just had to flash tow additional files that Essential issued in their flash download.
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Can you choose options or screen frozen? Because we know it boots and options can be chosen with the use of a OTG mouse...
*edit*
Remember guys, TWRP11.img still works for the August Factory Image as well as anything before August...It is only the September Factory Image is the only build at this time, that TWRP is frozen FYI
Nburnes said:
3.2.3 is surprisingly easy to boot, comparing kernel and /vendor changes is not.
Click to expand...
Click to collapse
Awesome! So glad this is gaining some traction! What kernel/boot image is this based on? Nougat, Oreo, or Pie?
Do you have an alpha or beta 3.2.3 TWRP boot image that you could share?
Also, just FYI, 3.2.3-1 was the version made specifically for the Pixels that was just released about a week ago to allow lockscreen pin/pattern/password decryption for Pie.
...
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
starcms said:
Here's the reason why touch stopped working in TWRP. In the September update, the hyp and rpm partitions were updated for the first time ever. This is what broke touch in TWRP. However, to confuse the issue, those who downloaded the September fastboot package when it first came out lost touch in Android, but kept touch in TWRP because Essential failed to update the two partitions in the fastboot download package (the updated partitions were initially only in the actual OTA and the OTA download package). Essential has since fixed their mistake and put the new hyp and rpm partitions in the fastboot download package.
You can't simply go and flash the older versions of those partitions, because even though it will fix touch in TWRP, it will break touch in the September (and newer) versions of Android.
More info here: https://www.reddit.com/r/essential/comments/9d3kru/the_september_update_twrp_and_touch/
Click to expand...
Click to collapse
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
stryver said:
So basically twrp needs to be repackaged with the updated hyp and rpm partitions and we should be home free?
Click to expand...
Click to collapse
TWRP needs to be made compatible with the new hyp and rpm partitions. TWRP (or any recovery) lives in the ramdisk in the boot image/partition (kernel). So I don't think it can simply be repackaged with hyp and rpm which are two completely separate partitions.
I have a Dasaita MAX6 with TWRP recovery.
I would like to reinstall my stock recovery for two reasons:
1) I'm having issues with my device (like freezing or rebooting in the first few minutes after car start) and I want to go back to a full stock software components
2) I get a signature verification failure installing latest system (2019-10-31) with TWRP, while other versions install just fine
Is it possible to go back to stock recovery?
Where do I get the correct recovery.img?
Sorry if this has been already answered, I have not found a solution to my issues yer.
Thank you,
Francesco Comi
Frankk said:
I have a Dasaita MAX6 with TWRP recovery.
I would like to reinstall my stock recovery for two reasons:
1) I'm having issues with my device (like freezing or rebooting in the first few minutes after car start) and I want to go back to a full stock software components
2) I get a signature verification failure installing latest system (2019-10-31) with TWRP, while other versions install just fine
Is it possible to go back to stock recovery?
Where do I get the correct recovery.img?
Sorry if this has been already answered, I have not found a solution to my issues yer.
Thank you,
Francesco Comi
Click to expand...
Click to collapse
I had the same issue with Dasaita Max6 PX6, after installing the Malaisk Rom. Untill now i didn't solve the issue, every stock Rom it give me the signature verification error 21. So i bought a new SOM PX6 and it work again. What it means TWRP?
Do you have any recovery.IMG? or which one version worked for you?
Thanks
Twrp have one big disadvantage - it can't flash MCU's.
So it is useless for android radio.
BTW Hal9k has released his Android 9 Rom.
MarcoZ76 said:
I had the same issue with Dasaita Max6 PX6, after installing the Malaisk Rom. Untill now i didn't solve the issue, every stock Rom it give me the signature verification error 21. So i bought a new SOM PX6 and it work again. What it means TWRP?
Do you have any recovery.IMG? or which one version worked for you?
Thanks
Click to expand...
Click to collapse
I dont understand what has Malaysk rom has to do with twrp? It dosent flasg twrp and you can revert to stock firmware easily. Also its interesting the errors you describe, I hav px6 dasaita, with Malaysk rom and have none of the above mentioned issues.
It might all be casued becasue you flashed twrp maybe? I doubt that those issue have to do something with the rom
I remember I also could not go back to stock after installing Malaysk ROM. What it helped me was to move update.zip to sdcard and installed from there. I run stock firmware for a few days and then went back to Malaysk ROM. Sometimes you had to format SD card a few times, mine did not accept for the first few times but then the same file I transferred from another laptop and it worked fine.
mariof said:
I remember I also could not go back to stock after installing Malaysk ROM. What it helped me was to move update.zip to sdcard and installed from there. I run stock firmware for a few days and then went back to Malaysk ROM. Sometimes you had to format SD card a few times, mine did not accept for the first few times but then the same file I transferred from another laptop and it worked fine.
Click to expand...
Click to collapse
Did you expirience it with px5 or px6?
matrixx1 said:
Did you expirience it with px5 or px6?
Click to expand...
Click to collapse
PX6
See my signature for various recovery links and wiki.
MarcoZ76 said:
I had the same issue with Dasaita Max6 PX6, after installing the Malaisk Rom. Untill now i didn't solve the issue, every stock Rom it give me the signature verification error 21. So i bought a new SOM PX6 and it work again. What it means TWRP?
Do you have any recovery.IMG? or which one version worked for you?
Thanks
Click to expand...
Click to collapse
Unfortunately I don't have any recovery.img.
TWRP is a custom recovery that got installed automatically by Malaysk installer.
I'm not sure that the cause is TWRP or Malaysk, but I have been unable to resolve the issue.
What is the cost of a SOM PX6? what is it exactly? Where do you buy one?
At the moment I have uninstalled the MAX6 and reinstalled stock radio because sometimes it freezed and I had to unplug the power cable to make it work again.
Hope someone have a solution.
Ati_gangster said:
Twrp have one big disadvantage - it can't flash MCU's.
So it is useless for android radio.
BTW Hal9k has released his Android 9 Rom.
Click to expand...
Click to collapse
I have installed many times MCU with the custom TWRP that got installed my the Malaysk installer, It has a MCU update menu and seems to work fine.
Frankk said:
Unfortunately I don't have any recovery.img.
TWRP is a custom recovery that got installed automatically by Malaysk installer.
I'm not sure that the cause is TWRP or Malaysk, but I have been unable to resolve the issue.
What is the cost of a SOM PX6? what is it exactly? Where do you buy one?
At the moment I have uninstalled the MAX6 and reinstalled stock radio because sometimes it freezed and I had to unplug the power cable to make it work again.
Hope someone have a solution.
Click to expand...
Click to collapse
The cost of SOM of PX6 from Dasaita is about 150 USD. I have ordered one and everything now work good, but i'm scared to install the Malaisk ROM, insfact i'm still using the standard ROM that came with the radio.
Frankk said:
I have installed many times MCU with the custom TWRP that got installed my the Malaysk installer, It has a MCU update menu and seems to work fine.
Click to expand...
Click to collapse
DASAITA PX6:
MCU V3.37
https://www.sendspace.com/pro/dl/wauclf
PX6 HA2_rk3399_9.0_ota(20190828)
https://www.sendspace.com/pro/dl/9sdgyp
MarcoZ76 said:
The cost of SOM of PX6 from Dasaita is about 150 USD. I have ordered one and everything now work good, but i'm scared to install the Malaisk ROM, insfact i'm still using the standard ROM that came with the radio.
Click to expand...
Click to collapse
Then install the rom from Hal9k_
Both roms are good and nothing to fear.
Hi there. I'm looking for a solution to boot into recovery mode on PX6. Any suggestions?
Ammby said:
Hi there. I'm looking for a solution to boot into recovery mode on PX6. Any suggestions?
Click to expand...
Click to collapse
Suggest reading the forums, including wiki.
Ah okay. So... Thanks for nothing.
Hi, I m in 'same' situation, I have 'brick' my PX6 coreboard.
I arrive to start the recovery, or "flash?" a ROM, with the method of PX5 sdcard (in MAPs slot).
But I cannot find the good way to get all working.
I have find two methods to get recovery screen:
1) (THE BAD WZY I THINK !), when the SOM boot in "updating", remove power cable, and at the next reboot I m into recovey.
2) (Think beter way), create with the PX5 OS Configurations Tools\SD_Firmware_Tools.exe an "SD Boot".
Put the SD in the "MAPs" SD slot, and power on, I get the recovery screen.
For informations, in MY case, before crash my ROM, I had (hourra !) an backup (with dd if=/dev/block/platform/by-name/XXX of=/path/to/external_storage/XXX.img). I have tried to replace files (with https://roc-rk3328-cc.readthedocs.io/en/latest/fw_pack_unpack.html method) but not sucesss...
Any ideas ?