Related
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
mido_ameer said:
Turned on my Wi-Fi
Samsung account asked to make update, and install push service
Play store forced to make updates
Facebook app section expired
Then the phone starts to be super slow, then the screen's touch stopped responding and everything was going crazy and lagging and not working.
I was successfully able to stop the PLAY Store updates and turned off my Wi-Fi
then I removed the battery only to force restart
The phone was stuck at the message of ( SAMSUNG Galaxy Note N7000 ) and nothing, after several seconds the processor area is super HOT
Sometimes I was able to see the BootAnimation with the whole music played.
I can successfully enter the download mode and Recovery mode
A message in red is written in Recovery mode:
E:Error in /data/log/recovery_kernel_log.txt (read-only file system)
I am currently using PhliZ
I don't want any format of any type please, the device contains important information especially the SNote app
any way I can recover my phone back, and if possible without formatting ?
By the way I downloaded Odin, rooted the phone with the right matching version, updated to official German jellybean, then downloaded the UAE version to support Arabic language and the system just went updating and all the information was not erased, then the whole things I mentioned above happened.
One of the apps that was always crashing (Root Toolbox PRO), caused the system to hang for several seconds then a message appear saying it stopped responding
Click to expand...
Click to collapse
I got that error message too E:Error in /data/log/recovery_kernel_log.txt this morning while trying to reflash JB but it was something odd i was trying and i think i got it due to that, as you can enter recovery you will have to format data in order to fix this or format everything to reflash firmware but before you do that, go to philz recovery and then to mounts/Storage go to last option mount USB (while it is connected to the computer ofcourse) you should see both the internal and external card on computer after that with all your data. Back it up on computer. Unmount once you are done and then do all the wipes and reflash JB.
Cheers!!!
Mounting failed
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
mido_ameer said:
I am currently working on PhilZ-cwm6-JPLSB-UAE-4.93.6-signed
then I coped recovery CWM-6.0.1.2-n7000.zip to the external sd card
I booted in recovery mode, and installed update
then I followed your instructions but no mobiles where detected by the windows 7, a unknown Samsung android is detected in control panel > printers & devices
every time I restart the phone it returns back to PhilZ
Is there is a windows drivers problem ?
Click to expand...
Click to collapse
Download from http://forum.xda-developers.com/showthread.php?t=1901191
this:
Code:
<< 12.05.2013 - PhilZ-cwm6 v5.03.0 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT5 - ZSLO2 Fixed for bootloop
go to recovery and choose install zip and choose the file i mentioned above (zip file) and go the location where you have saved it (external SD) and reboot into recovery, mount storage.
Go to Dr. Ketan's thread for latest samsung drivers install them and see if it shows up your internal and external storage on computer. Backup and go to dowload mode and flash JB again.
Thanks so much
I installed PhliZ 5.0.3.0 updated and installed succussfully
I was able to mount the sdcard and copied all the folders was there to my PC
Then I downloaded a new LSB jellybean UAE edition and worked like sharm
Now my note is working
Thanks for your support
Noise Cancelling is not working
It seems that the phone noise cancelling feature is not working any more, whatever I do in the options while call in progress
Mobile GT-N7000
Android 4.1.2
Baseband N7000XXLSO
Kernel 3.0.31-906407
Build number JZ054.N7000JPLSB
I download this roms
-Resurrection Remix V.5.4.4
And also download this.
V.5.7 Remix -Resurrection
Download the gapps and did the normal procedure for installation.
what happens is that after attempting to install the ROM. I get this error.
(Enclose all text that I no longer like spending a capture)
Installing: Storage - sd card1-Resurrecction Remix_Lp_v.5.4.4
finding update package
opening update
installing Update
Detected Fylesystem ext4 for /Dev/block/plataform/msm_sdcc.l/by-name/system
mount: Failed to mount /dev/block/plataform/msm_sdcc.l/by-name/system at / system: Invalid argument
unmouunt of / system failed: no such volume
patching system unconditionally
E: error in /storage/sdcard1/REsurrectionRemix_Lp_v5.4.4-20150511
(Status 0)
instalation aborted
This is me 2 rom mentioned.
after that the micro sd is disabled and must be reintroduced to recognize it the team
Try installing the ROM CM By beto, and is not installed not simply do nothing and pass the phone around two hours in the instalalcion and never proceeded
Now my phone does not pass the logo of motorola
help-'
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
FCorvin said:
Did you perform a „factory reset” wipe? Changing ROMs kind of requires you to - a factory reset wipes the old sd-ext, and you still have it.
And are you sure you downloaded the right ROM? I can't access the RR site now, but they don't have ROMs for Thea.
What phone do you have, actually?
Click to expand...
Click to collapse
I have xt1045 4g
I've done all the procedures to install the rom .
but gave those mistakes.
try putting on a rom 5.1 stock xt1045 according to what I found here on xda but I do not install it .
the phone did not stay at the logo and not as most do.
Then you need to flash this ROM: CM Peregrine
Or this one: RR Peregrine
See the ROM's discussion thread here.
You are also on the wrong part of this forum - you'll get better advice here: Moto G
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/hero2qlte/twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
travis82 said:
You going to compile with DM-Verification off? You can check my device tree it has the kernel built with it disabled.
Click to expand...
Click to collapse
It doesn't matter, dm-verity isn't enabled in the fstab, nor does the TWRP image contain any verity signatures to enforce.
finally...
thank god!finally!but the front cam issue have been solved?
Anyone know what roms work with this device? Also how to return to stock?
When compression is enabled on backups the device freezes.
What happened to CROM Service? It's not in the Galaxy Apps and .apk's from mirror websites crash when opened.
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
ryan49er said:
I flashed this twrp but recovery won't boot. Get blue screen with red writing up top that says custom binary blocked by secure boot (recovery.img). I have gs7 edge AT&T version. Now what?
Click to expand...
Click to collapse
this recovery is for unlocked bootloaders only. IE chinese and hong kong models only.
Well that sucks
Report...
jcadduono said:
Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9350 Qualcomm model only! Do not flash on Exynos models!
If you have a SM-G9300 or SM-G9308, look here instead!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy S7 edge stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys7edgechina.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
Extract Odin_3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for hero2qltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (USA): https://github.com/jcadduono/android_device_samsung_hero2qlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_hero2qltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy S7 edge China, Tool/Utility for the Samsung Galaxy S7 Edge
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_hero2qltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
Click to expand...
Click to collapse
I had G9350ZCU2APK2 ROM (China), so I installed the Hong Kong ROM G9350ZHU2APK2 (I needed the google services) and the phone work great except the part of receiving or sending SMS's, I have two sim cards cards (China Telecom and China Mobile), if I sent a message from the CT the message was sent also from CM, if I send from CM is not working, when I receive messages I received on both sim cards... , big problem for me, so, I installed the last G9350ZCU2APL3 ROM (China) and is working ok but no google services...
I've tried your method and is working... (kind of) once I installed the TWRP and the last SuperSU the phone had no Wifi and no network signal, so I put back the original firmware...
All I need are the google services because Signal is not working without, the email client is not receiving the email (automatically) without and so on... I've tried all the "possible" ways, no luck...google installer v2 and so on...
Any ideas on how to put the google services?
----- Edit - 28 January 2017 ----
I reinstalled the TWRP provided in the first post and the phone is working, has signal (China Telecom and China Mobile) and also the WIFI is working, I didn't install the SuperSU, kind of weird, with SuperSu installed the phone has no WIFI and no signal...
I've tried to install the gapps pico and the TWRP is saying that "could not mount/data and unable to find crypto folder", "Failed to mount '/data' (invalid argument)", "Unable to recreate /data/media folder", "failed to mount '/data' (Invalid argument)", "Unable to mount storage" , "Unable to mount / data/media/TWRP/. twrps.
The last error is: "Failed to mount'/data' (invalid argument)
After reading more posts on the forum I found the following:
"You CANNOT mount an encrypted partition in TWRP.
You do NOT wipe the partition.
Use the FORMAT DATA button. It's right there under the WIPE options next to the ADVANCED WIPE button."
Probably I will try this method when I am in the mood...
This works for SM-G935P? It says manufactured in china on the back.
Salanrm said:
This works for SM-G935P? It says manufactured in china on the back.
Click to expand...
Click to collapse
The post is for the Qualcomm, Galaxy S7 Edge SM-9350, China Open and Hong Kong, same hardware, different software (the Chinese one has no google services).
For your phone SM-G935P, search on google and you will find more instructions, I don't know if I am allowed to post here links from other websites.
jcadduono said:
As a joke, here you go USA!
twrp-3.0.2-0-hero2qlte.tar.md5
It works for all USA variants of the S7 edge, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
good afternoon
Reference is unfortunately not working
Can somebody share twrp-3.0.2-0-hero2qlte.tar.md5
thank you in advance for your response
So, this will 100% NOT work for the g935A? (Att s7 edge)
Craz Basics said:
So, this will 100% NOT work for the g935A? (Att s7 edge)
Click to expand...
Click to collapse
No. Locked bootloader
Sent from my SM-G935T using Tapatalk
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Craz Basics said:
Ahhh. That's some crap. Think it will ever be able to be unlocked?
Click to expand...
Click to collapse
It's a serious long shot but it is slowly being worked on.. check out this thread. It's for t mobile but the solution if found will apply to all us carriers as we all use the same method to root on marshmallow.
https://forum.xda-developers.com/showthread.php?t=3544220
Sent from my SM-G935T using Tapatalk
Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09
Thanks!
OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!
Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.
any chance for g800h support?
sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.
ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.
I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).
ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk
Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...
fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.
The rooting status of my phone says: 'Bootloader unlock allowed: No'. Some hours of research made me believe that on the user side it is not possible to change that status. So I am stuck with my locked bootloader. Originally I wanted to flash LineageOS, but this ROM seems to depend on an unlocked BL. Please correct me, if I'm wrong. Now I am looking for an alternative that can be installed by a not so experienced user (me). Surely, I don't want to brick my phone. My first question is, what conditions does a ROM have to meet to be installable on a BL locked device? Are old ROMs of CyanogenMod an option? Or plain Android? Any suggestion is appreciated. Thanks.
https://forum.xda-developers.com/xperia-sp/development/xperiasp-locked-bootloader-lbl-t2947194
That's lolipop and was the last one made for locked bootloader. It has all the steps in there. I don't know if all the linked stuff works, but I can confirm that the ROM's link is still up.
The download links on d-h.st only redirect me to advertisement pages, but no file can be downloaded
Anyway, can I conclude, that all ROMs based on Marshmallow and later cannot be flashed with LBL, and ROMs based on Lollypop and earlier can?
Basically, yes. Not all of the ROMs not based around Marshmallow/Nougat can be installed on LBL phones, though. If the op or the thread title doesn't mention that it can be installed on LBL phones then you can't.
https://drive.google.com/drive/mobile/folders/0B9ezDTx7eDfLNHVsUE9ub3FCeUU
I have an archive of last CM builds on my gdrive
There are also one stable build of 4.4 for unlocked bootloader
laim_name said:
https://drive.google.com/drive/mobile/folders/0B9ezDTx7eDfLNHVsUE9ub3FCeUU
I have an archive of last CM builds on my gdrive
There are also one stable build of 4.4 for unlocked bootloader
Click to expand...
Click to collapse
Is the installation process the same as for this ROM?
Do I need a kernel upgrade? Current: 3.4.0
Please, could anyone check and comment on my work-flow for the installation of CM11 on my Xperia SP with LBL? I haven't done it yet, but want to make sure this is the correct way, so I will not brick my phone. One thing, I am not sure of is, whether I need to upgrade the kernel, since CM11 is based on KitKat (I believe) and I still have the JellyBean kernel... Another open question is, will the Nandroid backup be erased from the internal storage as well by applying the 'Wipe' function of TWRP?
Preparation:
- Download CM11 ROM from https://drive.google.com/drive/folders/0B9ezDTx7eDfLLW0zODZRWkdKZUk to desktop PC
- Export contacts etc. to backup file(s)
- Charge phone battery to full capacity
- Remove SIM card from device and insert SD card for Nandroid backup
- Establish Wi-Fi connection
- Ensure that USB and cable drivers are installed
- Select 'Settings > Xperia > USB Connectivity > USB connection mode > Media transfer mode (MTP)'
- Connect phone to desktop PC by USB cable
- Copy backup files for contacts etc. to PC
- Copy ROM from PC to device's internal storage
Root device:
- Install Aptoide from http://www.aptoide.com/
- Install Root Checker with Aptoide
- Select 'Settings > Security > Unknown sources: yes'
- Install TowelRoot from https://towelroot.com/
- Run TowelRoot
- Check root with Root Checker
Install TWRP:
- Install official TWRP app with Aptoide (also available at https://eu.dl.twrp.me/twrpapp/)
- Run TWRP app and install TWRP recovery for my device
- Shut down device
Nandroid backup:
- Boot to TWRP recovery (press Vol— and power buttons)
- Select 'Custom recovery > Backup' to copy full device backup to SD card
Wipe device:
- Boot to TWRP recovery
- Select 'Wipe' to wipe the device
Flash ROM:
- Boot to TWRP recovery
- Select 'Install' to flash CM11 ROM from internal storage to boot partition
- Shut down device
- Insert SIM card
- Reboot