I know we've been waiting for this and others have been working on it as well, but here its is, a working build (limited testing) of TWRP for the Mi Mix 3. The source is up-to-date, and I'm not 100% sure why it says 3.2.3-0 and others have 3.2.3-1 on theirs. Feel free to post back with any bugs and I'll see what I can do to help out.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I tested this on my Mix 3 and everything appears to be in working order, or I would not post it here. Edit: Decryption has been reported not working by others. Decryption is working on my device, but I also formatted data yesterday. Checking into this.
Update: v2 linked below. Haptic/Vibration fixed, other fixes, including one that might fix encryption issues reported.
Update 2: Decryption still not working for some. If you format data, it will decrypt after it. You will lose data if you do this. I'm looking into fixes.
Download Here!
Instructions:
Reboot into fastboot using either: PWR+Vol Down or adb reboot bootloader
fastboot flash recovery twrp_perseus_3.2.3-0_PWn3R.img
Hold PWR + Vol Up to reboot to TWRP. NOTE: I have not tested fastboot reboot recovery nor have I tested fastboot boot twrp_perseus_3.2.3-0_PWn3R.img
Enjoy!
Credits: @notsyncing for his Polaris tree which I copied and modified for the perseus.
Source: Device Tree
Will test later
Thanks, but decryption is not working.
min-dfreak said:
Thanks, but decryption is not working.
Click to expand...
Click to collapse
+1
TWRP also boots, but no decryption [emoji849]
Gesendet von meinem MIX 3 mit Tapatalk
pittrich67 said:
TWRP also boots, but no decryption [emoji849]
Gesendet von meinem MIX 3 mit Tapatalk
Click to expand...
Click to collapse
Interesting, thanks for reporting. Decryption is working for me. I did format data yesterday though, which could be why. Edit: what happens when decryption doesn't work? Does it just not prompt for password?
Posted v2 with some fixes, haptic feedback/vibration works now. Also fixed a typo in the device tree around encryption that *might* fix the issues you guys are reporting.
PWn3R said:
Interesting, thanks for reporting. Decryption is working for me. I did format data yesterday though, which could be why. Edit: what happens when decryption doesn't work? Does it just not prompt for password?
Click to expand...
Click to collapse
My data is encrypted. When I go to the TWRP, I always have to enter a password to decrypt the data. That does not happen here. When I look at the File Manager in your TWRP, I only see encrypted file names. I will immediately try your V2 and report.
Thank you, wasn't sure what was happening to you. If v2 doesn't work, let me know and I'll see what else I can find.
pittrich67 said:
My data is encrypted. When I go to the TWRP, I always have to enter a password to decrypt the data. That does not happen here. When I look at the File Manager in your TWRP, I only see encrypted file names. I will immediately try your V2 and report.
Click to expand...
Click to collapse
V2 Dosent required to type password but files have encrypted name on it only sdcard folder tho
Tested the v2, still no decryption (encrypted filenames) and no prompt asking for a password.
Thanks for your fast support!
Abdiel1224 said:
V2 Dosent required to type password but files have encrypted name on it only sdcard folder tho
Click to expand...
Click to collapse
I flashed v2. The same problem. The data partition is not decrypted. So I can certainly install no OTA update. Please fix that.
Your tree is a direct kang of @mauronofrio tree. Congrats on taking credit for others work.
Except this one actually boots....
invisiblewave said:
Except this one actually boots....
Click to expand...
Click to collapse
That's funny, because this one doesn't for me.
---------- Post added at 05:27 PM ---------- Previous post was at 05:13 PM ----------
And besides... That doesn't make it ok to kang someone's work lol.
invisiblewave said:
Except this one actually boots....
Click to expand...
Click to collapse
it boots, but the data partition is not decrypted. Therefore still useless.
Gesendet von meinem MIX 3 mit Tapatalk
---------- Post added at 04:32 PM ---------- Previous post was at 04:32 PM ----------
invisiblewave said:
Except this one actually boots....
Click to expand...
Click to collapse
It boots, but the data partition is not decrypted. Therefore still useless.
Gesendet von meinem MIX 3 mit Tapatalk
Infect_Ed said:
Your tree is a direct kang of @mauronofrio tree. Congrats on taking credit for others work.
Click to expand...
Click to collapse
It's not a Kang, I copied the tree that NotSyncing made for the Polaris (Mi Mix 2). I modified all the configuration files myself. You will also notice that his tree does not have a bunch of the TWRP specific options in the BoardConfig.mk that mine does. Mine also boots, and if you format data does decrypt. I am looking into fixing the broken decryption. Please stop flaming when you have no idea what happened.
I spent DAYS of time working on this so honestly, screw you for saying I kanged his work. I looked at it when I saw he posted it, but I've been working on this for months. I should've put a note in the OP about the polaris tree that I copied from notsyncing, which I have now done.
PWn3R said:
It's not a Kang, I copied the tree that NotSyncing made for the Polaris (Mi Mix 2). I modified all the configuration files myself. You will also notice that his tree does not have a bunch of the TWRP specific options in the BoardConfig.mk that mine does. Mine also boots, and if you format data does decrypt. I am looking into fixing the broken decryption. Please stop flaming when you have no idea what happened.
I spent DAYS of time working on this so honestly, screw you for saying I kanged his work. I looked at it when I saw he posted it, but I've been working on this for months. I should've put a note in the OP about the polaris tree that I copied from notsyncing, which I have now done.
Click to expand...
Click to collapse
I'm not saying you didn't put in work. But you need to realize that what you did is not right. You erased authorship for I lot of things that other people did. I'm not here to troll. I develop as well, and if someone erased all the work I did... I'd be pissed. My suggestion, clone the original tree you based off of, and then make your changes and commit. Then push.
Maybe I should, but I've never cared enough to learn how to use github that much. I think I know how now, but I struggled just figuring out how to sync the tree I made back to Github.
At this point it doesn't really matter. I gave credit in the OP to the person that I copied the device tree from. I will update the readme in the repo to indicate the same. There are also library files that do not exist in the device tree that mauronofrio does not have in his tree, and as pointed out, there are other configuration file modifications that mauronofrio's tree does not have. I don't know where he got his base tree from, but I would bet he copied the same one I did. If everyone is just going to be up in arms, I'll just request this thread be deleted, delete all the code I uploaded, which works, and stop working on this.
PWn3R said:
Maybe I should, but I've never cared enough to learn how to use github that much. I think I know how now, but I struggled just figuring out how to sync the tree I made back to Github.
At this point it doesn't really matter. I gave credit in the OP to the person that I copied the device tree from. I will update the readme in the repo to indicate the same. There are also library files that do not exist in the device tree that mauronofrio does not have in his tree, and as pointed out, there are other configuration file modifications that mauronofrio's tree does not have. I don't know where he got his base tree from, but I would bet he copied the same one I did. If everyone is just going to be up in arms, I'll just request this thread be deleted, delete all the code I uploaded, which works, and stop working on this.
Click to expand...
Click to collapse
Pm me. I'll help you fix it.
Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Asus Transformer Prime TF700T (tf700t)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Click to expand...
Click to collapse
Phil3759 said:
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
Will give it a test run.
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Frostbiter said:
After using this on my phone, I'm excited to see this for my tablet as well. So far the only thing that I have found not working was the mounting the SD card through the recovery doesn't seem to work, it was connected to the computer when I mounted it but my computer couldn't see it. It also seems that the recovery is a bit slower on my tablet than on my phone, d2spr, though it might just be the tablet itself.
Click to expand...
Click to collapse
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Phil3759 said:
mount usb storage relies on device tree, kernel and rc files
Without the device or repo maintainer fixing it, it is hard
Click to expand...
Click to collapse
Ah okay, well so far that's the only bug in the recovery I noticed, and I wouldn't have even noticed it if I had remembered to put the kitkat gapps on my device before wiping it. Haha
Really nice job though, I'm glad you brought it over since I've had issues with plain cwm in the past and twrp doesn't seem to be getting updated at the moment I thank you for bringing this to my tablet.
Thank you so much for this nice tool and give us choices. I flashed it and the UI is just beautiful. Now I'll go test all its functions.
:good:
Nice
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
lj50036 said:
Nice recovery, It the best Ive ever come across. I Dev for CMB ROMS, I have made a flashable zip, so you can flash it from your current recovery.... I have this posted in the Download tab of my ROM forum... Its not my recovery, all credits will be given to Phil3759 It can be linked and given away as any open source recovery, I only say this on the ok of Phil3759, If he would like me to remove it, I will... Untill I here from him.. Here is a nice and easy way to install the best recovery to date for our beloved 700... Thx as always lj
Click to expand...
Click to collapse
Just tried this out using your zip to install. Works great. Recovery is nice and easy to navigate. Thanks to Phil and LJ.
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Thank you so much Philz!
I was dreaming about this, is not a joke, I've been using your amazing recovery in my jfltexx since always because it's the best.
I would be glad to help you.
Lord_Towers said:
i feel a bit silly but the file in the tf700t download folder is a .img and i can't figure out how to flash it...
Click to expand...
Click to collapse
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
soyusado said:
Write this in the terminal:
su
dd if=/sdcard/download/philz_touch_6.08.9-tf700t.img of=/dev/block/mmcblk0p4
Reboot your tablet and that's it.
You could rename as you wish, also, I'm running CM 11 so the file directory might be different.
Or you can flash the zip that lj made.
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Click to expand...
Click to collapse
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Lord_Towers said:
Thanks, i used the zip. I didn't even realize there were download tabs across the individual forums.
Click to expand...
Click to collapse
LOL, i remember when i discovered that too face palm.
Is Philz touch coming to a 701t Near you?
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
SlappyWag said:
HI.... can someone explain how to get to the flashable version ? I don't understand what is meant by " I have this posted in the Download tab of my ROM forum "
Thanks
---------- Post added at 07:51 PM ---------- Previous post was at 07:29 PM ----------
Nevermind... I found it
Click to expand...
Click to collapse
Open Terminal Emulator and enter this command
su
dd if=/storage/sdcard0/download/philz_touch_6.19.3-tf700t.img of=/dev/block/mmcblk0p4
Link is dead !
Another link ?
bump
Anyone got another link to this please?
[Recovery][UNOFFICIAL][SM-T320/SM-T325] ClockworkMod Recovery for Tab Pro 8.4 WiFi & LTE
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features
* included in this RECOVERY
* Before flashing it! YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will point you out to this message ! ! !
*
*/
By using this recovery you agree with the above terms!
WARNING:
Flashing this will trip you Knox flash and officially void your warranty.
You must use Odin to flash this. I am not going to tell you how to do that (there are lots of references on the web).
Download:
* Current: 2014-06-05 for Tab Pro 8.4 Wifi and LTE
Change Log
* 2014-06-05: Added SM-T325 support and selinux aware backups
* 2014-05-04: Faster install / wipe, latest kernel changes, upstream changes
* 2014-03-17: Added support for SM-T320XX (everything outside of north america)
* 2014-03-13: Set the build device name correctly
* 2014-03-02: Add external sdcard support.
Restoring old stock backups
Backups of the stock ROM using a recovery older than 2014-06-05 do not restore correctly because Samsung doesn't correctly restore the selinux contexts on boot.
Backups made with that version of recovery and later should restore normally.
If you need to restore an old backup do:
* Restore
* Mount /data
* adb shell restorecon -r /data
* Unmount /data
If you don't know how to do all those steps, then my best advice would be to do a factory reset after restoring and that will at least get you back to something that boots.
XDA:DevDB Information
ClockworkMod Recovery [UNOFFICIAL], Tool/Utility for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Stable
Created 2014-03-01
Last Updated 2014-06-05
Reserved
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
What gives you a binary error? Is that a message from Odin?
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
Hmmm. Just tried uploading and then downloading a version to d-h.st and it really seems like that site corrupts the odin files.
Sigh. Which probably means that no one has tried CyanogenMod yet which is mildly depressing. It's pretty nice on this hardware.
Looks like it's getting corrupt when I upload to dropbox too. I'll try again.
kdkinc said:
I get a "binary error" from downloaded file.
using Windows 8.1 .
Checked md5 and the checker matches.
7zip says there is a error using archive checker.
Thanks for your efforts
Click to expand...
Click to collapse
Try this one (unzip it before flashing with odin): http://d-h.st/eJQ
crpalmer said:
Try this one (unzip it before flashing with odin): http://d-h.st/eJQ
Click to expand...
Click to collapse
success with te new zip file.....we have a winner CWM boots up.
Thank You for the new zip file.
crpalmer said:
Hmmm. Just tried uploading and then downloading a version to d-h.st and it really seems like that site corrupts the odin files.
Sigh. Which probably means that no one has tried CyanogenMod yet which is mildly depressing. It's pretty nice on this hardware.
Click to expand...
Click to collapse
Give us a chance to wake up (and make our backups)
I'm going to be trying CM as soon as I have the backup done and the CM downloaded. At 90% now...
Yup. Looks like the new upload works. I thought that I was the only one facing the issue.
Thanks!
me0wster said:
Yup. Looks like the new upload works. I thought that I was the only one facing the issue.
Thanks!
Click to expand...
Click to collapse
If something doesn't work, please let me know!
Any info on .android_secure not being backed up by this CWR? I think that's how I wound up needing to reimage my device with Kies to get it to boot.
I'm pm'ing an attachment with a ton of logs pulled once I knew there were some potential issues. Unfortunately I don't know which ones are most valuable.
roustabout said:
Any info on .android_secure not being backed up by this CWR? I think that's how I wound up needing to reimage my device with Kies to get it to boot.
I'm pm'ing an attachment with a ton of logs pulled once I knew there were some potential issues. Unfortunately I don't know which ones are most valuable.
Click to expand...
Click to collapse
Nothing much in the logs.
I did confirm that you cannot seem to restore a stock ROM successfully. I didn't have to reflash with Kies/Odin (a factory reset made it work just fine although somewhat defeats the purpose of backing it up). Restoring CM backups do work fine though.
crpalmer said:
Nothing much in the logs.
I did confirm that you cannot seem to restore a stock ROM successfully. I didn't have to reflash with Kies/Odin (a factory reset made it work just fine although somewhat defeats the purpose of backing it up). Restoring CM backups do work fine though.
Click to expand...
Click to collapse
Yeah, my main hesitation in doing the reflash or the reset was that my stock has a lot of stuff kind of painfully disabled and/or removed. I'm not sure how to get Titanium to restore the settings just so after a reset or reflash. I think the reflash is going to be faster than a restore, though, and will be facilitated by a viable titanium backup.
Although, this time through I don't think I've actually deleted anything and it does feel better than it used to, I think because it was looking to run files I hadn't just disabled but flat deleted.
Samsung source code
http://www.androidpolice.com/2014/0...ource-for-tab-pro-8-4-wi-fi-and-lte-variants/
kdkinc said:
Samsung source code
http://www.androidpolice.com/2014/0...ource-for-tab-pro-8-4-wi-fi-and-lte-variants/
Click to expand...
Click to collapse
Excellent news! Looking forward to more development now.
Can someone verify the settings that need to be done in Odin for this please?
vexille said:
Can someone verify the settings that need to be done in Odin for this please?
Click to expand...
Click to collapse
This is flashed in recovery, not ODIN.
Also, OP...this ROM very well, only strange this is Falcon wont work. Says network time must be automatic, which it is. Any ideas?
jmill75 said:
This is flashed in recovery, not ODIN.
Also, OP...this ROM very well, only strange this is Falcon wont work. Says network time must be automatic, which it is. Any ideas?
Click to expand...
Click to collapse
This is the recovery thread.
As for Odin settings, whatever was default worked for me.
From my Pro Tab 8.4
Ha my bad. I was jumping between cm11 thread.
Sent from my VS980 4G using Tapatalk
oops wrong thread.
https://androidfilehost.com/?w=search&s=dreamlte
i flash this but cant boot stuck in s8 splash screen
That's interesting
Can't find any Github links of it
EDIT: This might use Albe96XDA's sources, but can't confirm
Do not have any videos?
manousos1 said:
i flash this but cant boot stuck in s8 splash screen
Click to expand...
Click to collapse
same here
https://www.cyanogenmods.org/forums/topic/lineage-os-15-1-for-galaxy-s8-android-oreo-8-1/
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Omg this is real? Pls work on g955f too
Crossing my fingers !!!
Can any dev check the validity of this rom?
GeorgeChilian said:
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Click to expand...
Click to collapse
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
tboguizmo said:
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
Click to expand...
Click to collapse
I have the same issue. The problem seems to be with the bootloader, i might be completely wrong. Is there any dev that can check the rom?
---------- Post added at 03:41 PM ---------- Previous post was at 03:33 PM ----------
The same dev also uploaded 2 AICP nightlies for our device. Or the developer confused code names for devices and this is not meant for our device
This is indeed for our device because dev has mentioned it is for "Galaxy S8" but highly doubt it is any different from the ROMs we already have that are not in a condition for daily use
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
GeorgeChilian said:
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
Click to expand...
Click to collapse
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Kizoky said:
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Click to expand...
Click to collapse
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
GeorgeChilian said:
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
Click to expand...
Click to collapse
That would work too.
Kizoky said:
That would work too.
Click to expand...
Click to collapse
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
GeorgeChilian said:
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
Click to expand...
Click to collapse
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Kizoky said:
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Click to expand...
Click to collapse
The zip has inside it a system.new.dat.br where all the system stuff are and I can't open it. Would I be able to just place the vendor files in the root of the zip and just update the updater-script?
Hi All,
I am planning on providing Samsung Galaxy stock debloated ROMs for M series FLOSS or GFS version.
Please contact me here for testing purposes and if anyone is interested.
Few added stuffs maybe given as well, depending on the kind of framework changes, as I will avoid any changes, as the FW breaks a lot.
I do not have any phone, hence all testing will be on the testers, so be sure to keep backups in case you agree to test.
Moreover, OTA is not possible and most probably it will be a decrypted OS. You will need good bandwidth and patience to do it.
Everything that you people do on TG can be done here, needs patience, which is all one should always have.
Share this with others, who wants to join. I will try any other series too, but only android 9 and 10 at the moment. Android 11 is not in my list.
Glad to hear that
TWRP
Nazim navas said:
Glad to hear that
Click to expand...
Click to collapse
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
vdbhb59 said:
So, that TWRP from Christin Koshy work on current version too? (the one released 3 days ago by Samsung?)
twrp_3.4.0_by_nevidimka655.tar
If yes, then I will use it for the build.
Click to expand...
Click to collapse
I am not sure about the twrp it has some bugs
M21_Testing_20200929.tar
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built, and uploading. It is a heavy file, around 4.2 GB (hopefully only one time). Flash with ODIN (in AP). Uncheck auto reboot.
Reboot to stock recovery, format data, mount /system, format data once again, and reboot to DOWNLOAD mode.
Then try each of the following boot methods:
01. Reboot normally (you can keep auto-reboot" checked for this trial) - If fails, try 02..
02. After flashing, reboot to recovery, format data, dalvik/cache, reboot - If fails, try 03..
03. Extract the 3 files, and zip to a .zip extension via 7zip and not WinRAR. Add the META-INF (full folder) folder from the attached zip, to the ROM zip and flash via TWRP (the one available).
-- Unzip the META-INF zip, and unzip the tar file ROM. Copy them all to say desktop and add all 3 files and the META-INF folder to .zip via 7Zip. Resultant file should be a zip file consisting of META-INF folder, boot, system and recovery image (.img) files.
-- The tar file consists of boot.img, recovery.img, system.img. - If fails, try 04..
04. If for any reason you are not able to boot, just replace the boot and recovery with the original/stock boot.img and recovery.img, do not change the system.img I gave. Add all to a tar file (via 7Zip) and flash via ODIN. Please note, do not use any other file. Chances are you will boot.
Please note, booting may take a minimum of 10-15 minutes, so please be patient. Once SAMSUNG logo comes it should ideally boot. I am yet to get a way to make DM-Verity work with ODIN. I will post link of ROM soon.
ROM uploaded. N. B. Testing only. https://cloud.operationtulip.com/s/nb7TjDAskmL47tn/download
Ohh, and in between each try, or failures, you may have to format data (may). At times I have seen for any reason if it fails, clearing or formatting data is needed which is odd on M series, but not always. Probably, trial error mode, but I do recall.
Also, in the 4th option, if you boot with stock boot and recovery, you will not be rooted. I will try and add root to the system, but cannot guarantee as of yet.
Nazim navas said:
I am not sure about the twrp it has some bugs
Click to expand...
Click to collapse
Have built few testing TWRP's. Try them out and let me know what works, what not please.
1. TWRP+Mod - This is a modified version of what I wanted to build out of TWRP. This consists of that old TWRP, but modified to suit the latest builds. - Link
2. TWRP+Stock - This has stock features enabled. Should be good to go anyways. - Link
3. TWRP+vdbhb59 - This I have modified in many many ways, so should be good to go as well. - Link
4. TWRP_20201001_Test - Image/Tar - This I have made from scratch. If you say this one works, then I will load this as Unofficial (until TWRP accepts it) as Android 10 working.
In each let me know, what is working, and what is not.
You should be able to flash DM-Verity through these, post you install the OS I gave. File attached (do not rename the file).
All M21
If you face any issues try flashing twrp+boot via .tar in AP in one file. Then check.
There are telegram groups check thier forums !
prashantp01 said:
There are telegram groups check thier forums !
Click to expand...
Click to collapse
Is anyone working on TWRP? For M21 yet? Android 10
Twrp odin fail
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
ahmad_subqi said:
FAILED. does not installed on new firmware one ui 2.1
---------- Post added at 03:52 AM ---------- Previous post was at 03:41 AM ----------
Twrp not installed one ui 2.1 . The last firmware.
Odin failed
Click to expand...
Click to collapse
Yeah I know. As I mentioned, trial error run and testing to understand what can be done.
Can you post logs?
Nazim navas said:
The twrp not working
---------- Post added at 07:14 AM ---------- Previous post was at 07:10 AM ----------
I rooted m21 through odin
Click to expand...
Click to collapse
Okay, can you try what I mentioned about the ROM through ODIN? I need to know that first. TWRP is not the necessity as of now, but to boot up modified system binary is. Please flash the rom via ODIN, as mentioned in the earlier post. Not with TWRP.
Edit: Also give what ever error you face. Snapshot, in writing, and the stage at which you get the error, etc.,
Check if any of these TWRP work: https://www.androidfilehost.com/?w=files&flid=318632
Nazim navas said:
A51 ported twrp working but internal storage not working not sure about first one
---------- Post added at 02:54 AM ---------- Previous post was at 02:53 AM ----------
The bugs in ported twrp from a51
I checked the twrp last 2 days it is not working perfectly as expected
*unable to backup or restore showing error like key is absent /twrp folder is not found
*error in internal storage may be due to encryption
*error flashing dm verity zip/multi disabler zip (/odm not found )
*unable to flash gsi images as it is not showing system image during flashing it only shows boot,recovery,optics,spectrum and super
*unable to repair /change format in wipe section
*all others like sd card /usb is mounting no issue with that
All this are my personal experience when i tested the twrp hope any developers will fix this soon
Click to expand...
Click to collapse
Okay, these bugs would have been there, as whoever ported they could not get a working one having /superimage and since /odm is not there as separate. ODM is a supra path, rather than individual path. This will take time, else will have to gather latest stock and make it as Pie would be like. Will take time though.
Thanks for testing out mate.
i got m31, ill be happy to test if any m31 develeoping avilible
anilkuruhan said:
i got m31, ill be happy to test if any m31 develeoping avilible
Click to expand...
Click to collapse
Thanks mate. Can you share the latest version and country code details? Also your system details (about) page. It will help me find more information.
Nazim navas said:
Model no SM-M215F/DS
Click to expand...
Click to collapse
The trouble with latest updates is it has superimage. The super unpacker/packer does not work properly. You tested earlier. M21 has that. M31, I have not checked yet. If it has superimage too, then I will have to wait till I get a working one. Will check.
Thanks again.
Nope, superimage. I am having serious trouble with my W10 to run these even with VMUbuntu. Will only be able to work if that acts properly.