Related
Hello, I am slowly learning how all of this works, and i have successfully rooted and custom ROMed my phones, and this is the first time I have tried a tablet. I have been trying to boot my Nook Color from sd card with CM7 and I got it to work great, except... I cannot get into a recovery. I even installed das uboot to choose where and how to boot, and it only takes me into a screen with a penguin and writes some code then wants to reboot. I have re done this several times, (I had the thing for 3 hours before I started trying, lol) I have no way to access recovery to install some changes I made to the ROm as Some Icons, animations, ect, I made on UOT. I have done this with my phone several times but this does not give me the option to do anything in recovery, No UI at all..
I was thinking of starting again, and wanted to know before I did if anyone here could give me a suggestion on what would be a good way to go or ROM to choose for a dual boot situation. I have seen on a thread that Dualboot Mirage CM7 / ICS CM9 ROM is a decent setup, but wanted to ask a few Nook users first.
Does this version let you go into recovery and flash things to the sd card ROM like changes and tweaks to the ROM ?
Would there be any better one to try?
Thanks for the answers in advance.
Chris
The screen with the penguin is verygreen's SASD "recovery" mode. To update to your "customized" ROM... name it update-WHATEVERYOUWANT.zip and copy it to the boot partition then go back into that recovery... it will install the updated ROM.
What you had seen was actually a Recovery mode.
Note: with verygreen's image, as soon booting into recovery mode, it will AUTOMATICALLY detect .zip files, install it/them, delete it/them then AUTO shut down.
Youre kidding me, right? I just had it named wrong? Im going to try again, I had the zip file from UOT on the boot partition, changed the name and it did something, but then had an error. Ill try loading the file again. I cant believe it was something so simple, and I have been asking over at CM and on the site where I followed the tutorial for a few days with no answers....
Any suggestions or comments about any other ROMS?
*edit* same error again, but at least it is doing it now! I can work with it now!!
line 1: syntax error: unexpected word (expecting ")")
Redneckhightech said:
Youre kidding me, right? I just had it named wrong? Im going to try again, I had the zip file from UOT on the boot partition, changed the name and it did something, but then had an error. Ill try loading the file again. I cant believe it was something so simple, and I have been asking over at CM and on the site where I followed the tutorial for a few days with no answers....
Any suggestions or comments about any other ROMS?
*edit* same error again, but at least it is doing it now! I can work with it now!!
line 1: syntax error: unexpected word (expecting ")")
Click to expand...
Click to collapse
Might have to edit the updater-script in META-INF\com\google\android of the ROM... I'd suspect the first line is not formatted correctly.
DizzyDen said:
Might have to edit the updater-script in META-INF\com\google\android of the ROM... I'd suspect the first line is not formatted correctly.
Click to expand...
Click to collapse
This is the first line.
ui_print("Applying UOT framework");
Is it supposed to be lowercase or is there a space supposed to be between print and the parenthesis?
Still new to the language but learning. I am on linux (ubuntu) now I self taught myself some of it with googles help! Im going to try mint on another computer soon as well.
Thanks,
Chris
That line looks to be right.. not sure what the issue is.
TWRP 2.8.5.0 YotaPhone 2 recovery imageAfter the bare bones modded stock recovery for YotaPhone 2 it's time for something more advanced. The TeamWin Recovery Project 2, or TWRP2 is just that: a fully fledged, graphical, touch enabled, custom recovery.
This recovery image for YotaPhone 2 is still an alpha version, so expect some rough edges. Which leads me to:
Disclaimer
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device. You are likely to void your warranty by doing so, and on a bad day you might even damage or brick your device.
What is it?
It's a recovery image for YotaPhone 2 based on TWRP2 custom recovery, and the stock kernel from Yota Devices. You can boot it ad-hoc, or flash it permanently to the recovery partition. Use it to root, install software, make backups, update ROMs etc.
What can you do with it?
- adb root & shell access
- All TWRP 2.8.5.0 functionality (except MTP)
- install update zips (signed with testkeys (e.g. SuperSU), Yota Devices software, and also unsigned zips like Xposed framework.
- You can sideload packages, but also install them from internal storage (e.g. Download folder)
- make partition backups
- root your device
What can it NOT do?
- In this recovery image the MTP functionality of TWRP is disabled, it doesn't play nice with YD's kernel.
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0
- Some technical confidence to cope with quirks that come with an alpha version
- USB cable with a PC or laptop on one end
Steps overview:
NOTE: I used less detail in this post than the previous recovery thread, please look there for more detail.
1) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
2) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
3) Unlock the bootloader if you haven't done so before (read warning below!)
4) Download recovery image: recovery_twrp_yd201_alpha2.img
5) boot or flash the recovery image
Unlocking bootloader:
Warning: It is currently not known how to re-lock the bootloader. This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
See stock recovery thread for unlock steps
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
You should see a black screen with a tiny white: downloading...
b) Boot the recovery image:
Code:
fastboot boot path/to/recovery_twrp_yd201_alpha2.img
Alternatively, flash the recovery image (overwriting the stock recovery):
Code:
fastboot flash recovery recovery_twrp_yd201_alpha2.img
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly. TWRP has it's own logfile that you can copy to (virtual) SD card, and access from there.
Kernel sourcecode:
In this recovery image is Yota Device's version of the Linux kernel v3.4.0 for YotaPhone 2. Yota Devices are required by the GPLv2 license to release the source code for this kernel, but so far they haven't taken that step or even shown intention to do so as far as I know. The YotaPhone firmwares and also this recovery image are in effect violating the GPLv2 license if the situation does not change. Attempts to contact Yota Devices on the subject through support, press departement, and an attempt to contact Yota Device's management, have gone pretty much unanswered as of writing. I'm hoping they're just busy making great devices instead of being unwilling.
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info & credits::
TWRP2 is created and maintained by TeamWin. Please donate through their site if you enjoy their work!
Recovery image for YP2: SteadyQuad
Version: alpha2 based on TWRP 2.8.5.0 with Yota Devices kernel (1.39 EU1)
Thanks to: TeamWin for TWRP, @Dees_Troy for hints for getting it up and running, @Jeopardy for testing, @Chainfire for SuperSU and lastly Yota Devices for a great device.
Linking to this recovery image:
Please don't link directly to the download image, link to this post instead. That way users can get the most recent version and any updated info. (It's an alpha version after all)
Created: 2015-06-23
Last Updated: 2015-06-24
SteadyQuad said:
If you would like to help future custom ROM development for YotaPhone 2 please do the following:
Encourage Yota Devices through their twitter or facebook accounts to publish the Kernel sourcecode for YotaPhone 2, and ask them to support the open source Android community. You can also submit a request through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Click to expand...
Click to collapse
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Yeah, I got the same boxed response and replied that it was not relevant, and explained why. Their SDK (for app development) has nothing to do with the kernel sourcecode, and at the moment their developer pages do not mention anything about kernel sources. I think that their support page tickets are handled by an external company (quicksupportlink.com), that is dependent on Yota for definitive answers, and they're probably instructed to send this reply. At least Yota will get reports from them, with hopefully lots of requests for kernel source. On the press page there's email addresses of 2 press ladies, you could try those too (as I did).
So nice to see this! Looking forward to trying, once mine comes.
Jeopardy said:
I just approached Yota for the Yotaphone 2 kernel's source code, and they gave me a link to Yotaphone's developer page (https://yotaphone.com/developer/). It's not there (yet). Maybe they'll release the source code once they finalize the SDK...? That, or the recipient of my query didn't understand the question.
Regarding the recovery: works flawlessly. :good:
Click to expand...
Click to collapse
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
zencooler said:
Hi Jeopardy,
Next great mod by you! Congrats! :good:
BTW: Does it mean that your version of TWRP recovery doesn't work with 1.44 EU firmware?
Or if I flash this recovery it will work, but the kernel is one step back to 1.39 version?
Thanks in advance for the info.
Regards!
Click to expand...
Click to collapse
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Jeopardy said:
This recovery is done by SteadyQuad, only tested by me.
But I can answer your question: this recovery works just fine with 1.44 EU firmware. I have flashed it myself successfully. I'm quite sure it is not tied to the firmware version in any way.
Click to expand...
Click to collapse
Hi again,
Soory for the mistake (I just replied not for the first post). Once again sorry SteadyQuad and congrats for you again!
Jaopardy, thanks for the quick info and confirmation it works on 1.44 EU firmware! It's a good news
Regards!
Jeopardy said:
...Yotaphone 2 kernel's source code...
Click to expand...
Click to collapse
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
elatllat said:
https://srv-fs1.yotadevices.com/public/file/5OyPZKU7Vk6HvML_YZpuRQ/yotaphone2_kernel.tar.gz
Click to expand...
Click to collapse
Thanks, this archive was already known, it contains a kernel snapshot of end of june 2015. I put it on github with some small adjustments to make it build initially. (and it actually boots
I've also put up an initial device and vendor tree there, although both are pretty far from complete/correct at this point.
BTW @elatllat where did you get the link from?
SteadyQuad said:
...where did you get the link from?
Click to expand...
Click to collapse
I did a xda forum search and found that link, this thread, and thought I should link them up.
(as it's not widely known)
so anyone tried xposed??
varun.gid said:
so anyone tried xposed??
Click to expand...
Click to collapse
Yeah. It works as expected. No problems for me.
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
adamo86 said:
Has any flashed this recovery permanently over 1.60
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
SteadyQuad said:
You can use this TWRP recovery image with 1.60 just fine (the recovery image is pretty much independent of firmware version).
Click to expand...
Click to collapse
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
adamo86 said:
I am having this issue with my yotaphone the epd freezen for a long time I'm not sure if it's twrp. At the moment I flashed the stock modified recovery and it stopped freezing for the last 24hrs i will report back in a few days
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
May be my phone is dieing?
Sent from my YD201 using Tapatalk
SteadyQuad said:
TWRP is only doing anything when you boot into recovery. When you're just using your phone normally, Android doesn't even know about TWRP. So your EPD freezing must be something else.
Click to expand...
Click to collapse
Your right my phone is bust does anyone have yota contact details
Sent from my YD201 using Tapatalk
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
zute333 said:
adamo86 said:
Your right my phone is bust does anyone have yota contact details
Have you done a factory reset?
My EPD was freezing and system clock screwing up. Factory reset, wiped caches etc, then cleared out a few apps didn't need and some system crap, seems to be ok now. Battery drain still occurs but I'm resigned to that unfortunately, just hoping 5.1 fixes the issue (and that we get it soon.).
If nothing works you could try emailing [email protected], hopefully you get somewhere. Their customer service was very good initially for me but seems to take a very long time to get anything done nowadays.
Either way good luck and I hope your phone gets some decent function back eventually .
Click to expand...
Click to collapse
I got rid of it I tried everything downgraded wiped data etc clean install then did ota still freezes after a while. I did clean install of Rom twice. I think the screen is dying or something inside it is loose because the epd started off as freezes then moved to very light grey instead of black and would refresh but old pics and widget would be visible and it started to flicker from one side then it would start to work after a while then fade again etc. When these freezes happened I would get a blue screen when phone was rebooted and it would slow device down then reboot it self until the screen got unfrozen. I noticed even after installing rom new the screen would some time be frozen. It's only sometimes the screen would be reseted if I did a new installation.
I will miss my yotaphone. I will be getting a nexus 6p or v10.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I can't yet post in development forums.....
I'm trying to install the unofficial CM13 ROM from Mr COLDBIRD,,great work by the way.
It suggests using a modified version of TWRP. TWRP-2.8.7.0-ham-fixSystem-fixADB.img as the one instead of breadcrusts version.
The issue is whilst I have been able to install tyhe breadcrust version previously, this one just won't install at all.
Does anyone know if the filename is correct or whether there's something I'm not doing that I should?
I get ADB working, confirm device shown etc, moved the filename downloaded as per above .img to ADB folder, open cmd prompt but nothing seems to work...please help
Carmogeddon said:
I can't yet post in development forums.....
I'm trying to install the unofficial CM13 ROM from Mr COLDBIRD,,great work by the way.
It suggests using a modified version of TWRP. TWRP-2.8.7.0-ham-fixSystem-fixADB.img as the one instead of breadcrusts version.
The issue is whilst I have been able to install tyhe breadcrust version previously, this one just won't install at all.
Does anyone know if the filename is correct or whether there's something I'm not doing that I should?
I get ADB working, confirm device shown etc, moved the filename downloaded as per above .img to ADB folder, open cmd prompt but nothing seems to work...please help
Click to expand...
Click to collapse
My image has been fixed the only current issue is encryption mounting however this issue is present in Joao's version too. Please try my image I have just used it and don't seem to have any issues with it.
All now works!!
No idea what the issue was, hazard a guess the ADB interface chucked a wobbler as kept losing my device.
Reboots etc and all then worked fine.
Now running TWRP, thanks Breadcrust, and unofficial CM 13, thanks Mr Coldbird.
Keep up the outstanding work guys, makes a huge difference to people like me.:good:
Disclaimer
**** All flashing is done at your own risk! ****
**** While this recovery should not break your device, don't come back here blaming anyone if it does! ****
This is a TWRP 3.2.3 build based on Android 7.1.2 source kernel for the Galaxy Tab Active 2 (codename: gtactive2lte) - Exynos. The "tar" file should be installed using Odin (tested on Odin 3.12.3).
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options, if its not there, you may have to wait for a few days to access that option, some users claim that its within 10 days before this option appears).
2. KNOX will be tripped once you flashed custom binaries to your phone.
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. It is HIGHLY UNRECOMMENDED to purchase any access to any kind of private forums, ROMs or Kernels.(DO NOT GET FOOLED.)
Installation process:
1. Flash Stock ROM.
2. Flash recovery using Odin (AP = recovery.tar).
3. Load recovery immediately after flashing.
4. Format data (Will erase /data partition).
5. Reboot to recovery.
6. ADB push SuperSU to internal storage / insert SD-Card with SuperSU.zip.
7. Flash SuperSU using TWRP install option.
8. Reboot to system (May bootloop several times. Wait untill system loads).
Bugs:
1. ADB sometimes doesn't work in MTP mode. Need to manually change to PTP in order to get adb usage.
2. Bad label in ADB shell + bad characters appearing while writing through AD. Works well out of recovery and on recovery's terminal.
Sources:
Device tree - Device tree
Kernel - Kernel
TWRP sources - platform_manifest_twrp_omni
SuperSU - SuperSU-2.82-SR5
Recovery download:
Recovery
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 08/19/2018 (DD/MM/YYYY)
Contributors:
Many thanks to TWRP's developers for the support on building this recovery.
Special thanks to CaptainThrowback, Bigbiff and Dees_Troy on TWRP-freenode and Ashyx on xda-developers.
Please post any bugs you encounter. I will try to fix any issues that come up.
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
slomo2 said:
Thanks for the work and sharing. I'm excited to try. Having root would be great, but I'd also like to be able to make voice calls ( using bluetooth as the built-in speaker & microphone aren't adequate ). Do you think this is possible. What changes, if any, are required to have work with T397 Tab Active 2 ( US variant ) ? I'm sure that it's mobile frequencies are different than what the euro-spec'd T395, but otherwise I think identical.
Slomo
Click to expand...
Click to collapse
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Shedaim said:
Well, Samsung has a nice repo of their source kernels for every phone Samsung sources
I guess we just have to validate some data taken from boot.img from the stock rom and then build the same with the appropriate source kernel.
Click to expand...
Click to collapse
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
slomo2 said:
Had no idea the source was available for these devices, thanks for sharing. T397 source is in the repository. Let me know if there is something that I can do to assist. I've not compiled these sources although I've compiled other things. Possible to use this tablet as a phone with this ROM as stock T397 ( even after installing several different dialers does not dial ) ?
Click to expand...
Click to collapse
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Shedaim said:
I can't check the dialer thing, as I don't even have cellular network on my Tablet.
I'll try to build the recovery for the T397 later today, but you will have to check it I guess, as I have no access to that one.
Click to expand...
Click to collapse
This will be great, let me know if I can help, perhaps document.
slomo2 said:
This will be great, let me know if I can help, perhaps document.
Click to expand...
Click to collapse
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Shedaim said:
Ok, so this is a first try, so I believe it's not going to work, but who knows? we may get lucky.
Recovery for SM-T397 - Android 7.1.2
If it doesn't get installed or leads to a bootloop, I'm gonna need you to pull the boot.img from your device, or send me a link of the stock ROM if it's available.
Please follow the intsallation process described on the README file on the github repository
Click to expand...
Click to collapse
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
Click to expand...
Click to collapse
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
7.1.1 is what The T397U should have already been on before you started. Mine is and I have not installed this recovery as of yet. Just wanted to let you know it's where it should be.
slomo2 said:
Thank you! Successfully installed. I found this video helpful for this generation of Samsung device and learning how to navigate recovery and download modes. I disabled auto-reboot in ODIN per your instructions, but it wasn't clear to me how to power-off after download so as to be able to go into recovery without booting so after adequate time I just pulled the battery. I'll spend the evening playing with things and report back, but so far everything seems to be working
---------- Post added at 11:27 PM ---------- Previous post was at 11:15 PM ----------
One thing I notice, 7.1.1 is what was/is installed on my tablet now. Not sure what version of Android available on Samsung Opensource or how to check it, but I suspect it is the same since nothing has been pushed OTA.
Click to expand...
Click to collapse
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Shedaim said:
Awesome. I really had my doubts being it the first build and all. I guess, there aren't really any major differences.
If it's possible, can you go through the TWRP checklist here
Some of the tests aren't really necessary, but it's a good checklist to go by anyway.
That way, I can officially add it to the OP.
Click to expand...
Click to collapse
Sorry for delay. I've done the following tests all with the expected results. The only thing I noticed compared to previous installations of TWRP that I've performed ( some years ago ) is that the load time of recovery seems long at 1:15. Also a message about "RECOVERY NOT SEANDROID ENFORCING" which I suspect is normal. Tablet has been working without incident. Thanks again.
Blocking checks
- Correct screen/recovery size
- Working Touch, screen
- Backup to internal/microSD
- Restore from internal/microSD
- reboot to system
-ADB ( yes, if this means being able to access from ADB while in recovery )
Medium checks
- Screen goes off (and on )
- F2FS/EXT4 Support, exFAT/NTFS where supported
- all important partitions listed in mount/backup lists
===> define important ? - depends on the device, i guess
= Assume we can still boot a recovery (aboot/lk is still there for fastboot), can restore everything left ?
- backup/restore to/from external (USB-OTG) storage
- Correct date
Minor checks
- MTP export
- reboot to bootloader
- reboot to recovery
- poweroff
- battery level
- USB mass storage export
- set brightness
- vibrate
Security Policy Updates should not be applied to this system ?
Since this is stock Samsung OS that is rooted I'm guessing this system is still SELinux "enforcing" so does this mean that I can/should say yes to Security Enhancements automatic updates from Samsung ? Any explanation or link on this matter appreciated.
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
maddada said:
Hey @Shedaim, thanks a lot for this recovery, would it be possible to release an update for oreo?
Click to expand...
Click to collapse
Hey, sorry for the very late answer.
I'm currently not working on Android and I've never tried on OREO, so my politically correct answer would be: "Right now there is no plan to work the same magic on OREO, but whoever wants, can try to use the device tree I created with a new official OREO kernel (didn't know they have one already)".
Anyway, keep checking the forum from time to time, I may have found the time to work on it
Links to the device tree and other tools used are in the main page of this thread.
Thank you,
Shedaim
I Pay 100$ for making my Galaxy Tab Active 2 booting when its charging
Hey guys,
i hope somebody can help me.
Im trying since 2 Weeks to make my Galaxy Tab Active 2 booting when its charging.
I try all the ways i found (fastboot, LPM change and Autoboot App) and nothing was successful.
So i hope to find with this way somebody who would help me to get the feature.
I need it because i installed the Active 2 on my Harley Davidson as my navigation.
And the problem is that i make a Novalauncher thats looking like the original Harley Davidson one and starts without a code.
So when i put the Tablet in the Mask i dont get a method to press to power button and when i make a method (hole trough the mask or something) then everybody can start up my tablet and use it.
So if somebody can help me with that i will pay them 100$ for helping!
you can contact me at [email protected].
thanks alot
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
sCOTTN916 said:
Excuse me for a moment, but i have a Galaxy Tab Active 2 WIFI (sm-t390) and im looking for a custom recovery for it. All i can find for this model is the SM-T395 variant of TWRP,root, etc. Absolutelly nothing for the SM-T390? Does any one have any ideas???? Thank you in advance either way.
Click to expand...
Click to collapse
I used the methods and recovery here for my tablet which is a T397U...works flawlessly. The same should work for the wifi T390 you have aswell.
Flash process
I am new to the rooting process. This will be my first time. What is the actual flash process? How do I flash the rom on my tablet?
All the links are dead can anyone please post this recovery
i can Flash this twrp-3.2.3-0-gtactive2lte-7.1.2.tar, Odin says pass, but there is no TWRP. it boots into System. when i stop and boot to recovery, there is stll custom recovery from T395XXU5CSH2.
Any hints?
This thread is presently about the development of a TWRP port to these devices.
The build is not yet working!
I am in the process of porting TWRP to my 3562 mostly out of pure spite for this stupid device. This thread is mostly for collecting my development process, for anyone who is interested, or wants to help.
Presently, TWRP will boot properly, and does function apart from UI issues and generally not being able to mount partitions correctly.
The UI draws in portrait mode (USB port at the top), but the touch interface responds in landscape mode (USB port on the right). This is very annoying, but it is still usable, so I haven't looked too far into it.
It seems to mount boot and userdata partitions okay, /sdcard is full of garbage data (encrypted? bad mount flags?), /system will not mount at all.
First order of business is to get /system mounted. It looks like this is related to vbmeta, so I have to sort out how to properly wipe the vbmeta on this device.
Here is my current image, if anyone is interested in trying it out: https://drive.google.com/file/d/1kMvKvocKY6AWRR-xkXIwisv27TmF6xcP/view?usp=sharing
I'll keep this updated as I keep working. As always, any input is greatly appreciated.
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
rolenthedeep said:
@tek3195 (moving the discussion here instead of two different threads)
Here are my fstab files: https://drive.google.com/drive/folders/1n-hieMe2r4gaais_pgI_gOMB11VKQUPU?usp=sharing
I don't see where to put the BoardConfig.mk, I'm guessing I need to actually build TWRP from source?
Click to expand...
Click to collapse
Thanks for moving, we were a bit OT in other thread. Yes the boardconfig.mk is for building from source. Does no good when using kitchen, I was just showing you an example of where and how rotation was handled. I still haven't followed up on changing rotation and touch input using kitchen, just got home from another heart catheterization. The only way to get a fully working fully functional twrp is to build from source, but without source code AIK is an awesome alternative. I just can't remember if we can change rotation and touch input in de-compiled img. We can ask @osm0sis if it is possible to edit recovery rotation via AIK. If you've not done so already, check out his work here on XDA. There are a lot of useful tools and scripts authored by him and a wealth of android knowledge that you can only benefit from reading.
Haven't ever messed with TWRP rotation myself, sorry. I'm sure it's something you can Google and find out though.
@rolenthedeep look at this may be helpful with rotation
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
mpalpha said:
I found this, same cpu/gpu as the 100003562
GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA) - GitHub - Yahoo-Mike/recovery_device_lenovo_X606FA: TWRP recovery for Lenovo Smart Tab M10 FHD Plus wifi (TB-X606FA)
github.com
I'm trying to figure out how to compile twrp for this tablet too.
Click to expand...
Click to collapse
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
tek3195 said:
OK, are you building from source or porting in kitchen ? I can try to help you out either way, I've ported a few and built a few but have not brought up new device. Before you start trying to build for a new device you should build for an existing device to make sure you can build successfully on your machine. If you have a device that has TWRP available use the trees for it and build and test your build on your device. If you don't have a device with available TWRP then build any of the current official versions preferably MTK based just to insure build environment is set up and builds correctly.
Click to expand...
Click to collapse
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
mpalpha said:
I've downloaded AIK in windows 10 and unpacked my stock recovery so far. I have 2 of these tablets one is rooted with magisk via patched boot.img. The goal is twrp via patched recovery.
Click to expand...
Click to collapse
I thought I was replying to someone else, but same applies. You're wanting to port one using kitchen the best place to start is here:
https://forum.xda-developers.com/t/guide-porting-twrp-without-source.3843473/
Where it gives the different screen resolutions go with largest, if it calls for a file not present in your device just skip it and don't add extras. There are a lot of guides but that one I know works rather well, I've used it on 3 diff devices. Cooking custom recovery in kitchen works but not always correctly. By that I mean that you may not have the ability to backup or restore or install. You may not be able to control brightness or some other setting or it could be that usb does not work. It can be a combination of any of those things and more. It can also be that you never notice something not working because it does everything you want it to. Just letting you know what to expect and saying that building from source is always best, even when it's unavailable.
If you ever get the time can you port TWRP to the 100015685-E?
@rolenthedeep here is a WIP fstab. I have commented out the partitions that were not first_stage_mount If you try it as is to try to get an idea of which parts are needed for recovery there is no sd card in it as it too is commented out for now. Got caught up in some other issues and stopped looking at it for a while. Maybe it will help a little.
Any updates on this? I have the 10.1 3562 version