Develop Bugs

SMT700 - Custom Rom /Installation/Backup

Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:

androidnoob222 said:
Hey guys
I am completely new in this topic. I just got an Samsung Galaxy Tab S (SMT700 Wifi) as a present a few days ago. Its my first android device I had so far.... so everyone will call me "noob" and I am okay with it DD
When I realised that there are different android os development projects like CM and Paranoid, I become interested in trying them out. so...
1.) Is it possible to brick the android device completely or is there something like an recovery/dfu mode in iOS devices?
2.) Can I go back to the stock OS contributed bey samsung itself (Touchwiz Kitkat)? If yes are this files online?
3.) Does I need special hardware to perform a custom rom flash? (micros card/special OS on pc (linux,....)
4.) Does the CM blck mod in the official forums contains alle required drivers and blobs already to perform gpu tasks and so on? (are there currently downsides swell?)
Thx :fingers-crossed:
Click to expand...
Click to collapse
1. There is bootloops but hardbricks are rare. You can enter recovery and download mode(flash stock rom on broke os) in a bootloop. Just hold power, home or vol up for recovery and home +power +vol down for download mode.
2. Yes you can go back to any version of stock os unlike apple you have to be on the latest. The files are online for your device at sammobile. (google it) and also samsung updates.
3. All you need to perform a custom rom flash is a custom recovery called twrp and your device. Theres an app on google play for installation of it. (search on youtube on how to do so). But thats just flashing zip based roms(which most custom roms are). For stock rom installation, you will need a pc and a application called odin 309 to flash a stock md5 file rom in which you will need to be in download mode (like installing new update from itunes).
You will need to backup your whole rom with twrp before flashing a custom rom. You may need a micro sd if your short on space. You will also need to be rooted to install custom roms. Please go to the cfautoroot thread of your device to root your device in which you will viod warrenty.
4. Cm rom as of now still has bugs but is still useable for games and such. There should be a list of bugs on the thread and might have some missing features such as ir blaster and finger print scanner. Battery life may vary. So there are downsides.
5. I can go into more depth of custom stuff and flashing if you wish. Right now my fingers hurts xD. Hope this helps!

1) it is very, very unlikely even if you try intentionally to do so
2) yes, no problem. google for Samsung Firwares, it's all online
3) windows PC, Odin Software, and an USB cable, that's all. You can do it with Linux if you prefer. Some Roms are installed via zip file from the device itself, then you need to flash a new Recovery partition first, that is able to do so
4) ?

Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:

androidnoob222 said:
Thx you very much for the help !
After reading a lot about this topic it seems to be not as difficult as I thought it would be.
But I don't get one thing. Why does I need to make a proper backup only for the flashing propos? If I flash my internal memory, all data will be replaced. And if it goes wrong I will be able to do a complet software reset with odin and the original samsung image found in the Internet?! So why I have to make a backup (there is no data in my current tap I will need in the future)?
And does the cf chain root flash the OS or the firmware ?
As my understanding tell me that the firmware is something comparable to a bios , which should never be flashed to maintain stability.
So as my logic goes further if my device is rooted, after a proper reset it will not be rooted anymore? (Android stock reset function in settings)
Or does armbased devices not have a normal firmware/bios as I mentioned ? And something in the bootprocess itself is manipulated to anable root access?
Hopefully you get what i mean :angel:
Click to expand...
Click to collapse
1. Sometimes odin and kies will fail for you. Twrp backups is to be really safe if you get bootlooped and odin fails for you. Its much easyer to restore a twrp backup and easy to make one. Its just if odin or kies fails which twrpnwould be your only hope. Just in case
2. Cfautoroot only flashes supersu and root. It keeps your apps and everything. So when you flash cfautoroot, it will say andriod is upgrading becuase its installing root and restoring back your apps.
3. After a full proper reset, it will not have root and revert back to stock. Thats where you flash cfautoroot to gain root again!
Hope this helps!

So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?

androidnoob222 said:
So as of now I managed to root my device and also created a twrc backup, which is now transfered to my sd card
Are there major differences between a rom flash with twrc recovery or odin?
Click to expand...
Click to collapse
Most custom roms are to be flashed with twrp. Meanwhile stock roms/md5 is to be flashed with odin(firmware from website).

Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?

androidnoob222 said:
Again Thx you very much!! You are awesome!
I managed to install cyanogenmod its insanely fast compared to the touchwiz version
But there is one more thing I have to ask.
I installed TWR in the latest version but the klimwifi (2.8.XX) version (klimtwifixx was not avaible). Is this the right version?
Where exactly does TWR be installed. Afther the wipe and the format it stays, so I have no clue how it can be available even if the internel memory was formated?
I started TWR by the terminal (reboot recovery), becouse I have no clue how to start it instead by button pressing?
And there are no playstore how can i get it on cm11?
Click to expand...
Click to collapse
2.8 is the latest version of twrp. I dont think your device is klimwifixx. It should be klimwifi. What the wipe and and factory reset in twrp does is that it clears all your apps and wipe cache. It does not wipe any folders and it justs wipes your apps. So internal should not be affected unless you formatted it... You just need to swipe the factory reset on it when installing roms. For google play store you have to flash a file name gapps. There should be a link to it on the thread. To get into recovery, turn off your device, then hold power, home, vol up buttons at the same time to enter recovery. To exit recover just touch the reboot rectangle and hit reboot system. Hope this helps!

Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things

androidnoob222 said:
Okay now its clear TWRP replace the "downloade mode", which is the standard recoverymode
You said I do not need to format the disk, but why?
In linux distributions (debian for example) you will have similliar structure for example /var /bin /sbin /usr /proc,.....
If there is the stock touchwiz android it will have this structure listed above as well. So it will courrupt the os by overwriting this folders by a custom rom....
. Maybe you wont do it in the TWRP menue, because it will do it automatically by choose you custom rom install script in the zip?
How is the portioning in those devices? Maybe there are /dev/sda1 (android) and /dev/sda2 (with the recovery setup inside)....? I just want to understand those things
Click to expand...
Click to collapse
No no! Twrp replaces stock recovery. Download mode cannot be replaced. You enter it by holding power, vol down, home button when the device is off. Download mode is when you flash things. Recovery mode is when you clear cache or other stuffs. I have no idea with the linux stuff you explained but custom zip roms just adds some modifications and other stuff to the device. You would need to clear cache and factory reset so you wont have problems installing it. You can easyly go back to stock rooted by restoreing a backup you made in twrp. It has to do something with img and replacing those if thats what your talking about idk. No need to format as the rom add things to it. Just need to factory reset and cleae caches.

But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..

androidnoob222 said:
But now if I want to enter download mode for testing, it will boot into the twrp recovery. So as for me it looks like that it is already replaced..
Click to expand...
Click to collapse
It shouldnt be as twrp only replaces recovery. Img did you try doing home, power, vol down?

Hi
I have a quick question I have the Galaxy tab S 10.5 wifi and was wondering can I install TWRP without the tablet being rooted?
Also there are some builds where it states that its rooted, debloated and de-knocked. Does this mean that they can be flashed without rooting the tablet and tripping knox.
Thanks for your replies, still trying to get my head around this.

İce Rom home button not working

Hi, I am install ice rom but not working home button.
How fix it this?

MM or Android N firmware?
Powered by HTC 10

2WildFirE said:
MM or Android N firmware?
Powered by HTC 10
Click to expand...
Click to collapse
N
3.1.0
Stock and elemental kernel not working

kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
Please Kids, learn to read, before you flash something!!!
You must flash the rom on MM Firmware and homebutton will work.

kallardo said:
N
3.1.0
Stock and elemental kernel not working
Click to expand...
Click to collapse
You know 3.10 is just rom version and doesn't say anything about firmware? Are you sure you flashed correct firmware too?
Corrupt homebutton is usually the case when running N rom on M firmware.
@BladeOne1
Think you're misunderstanding. When first N roms came out, the custom recoveries couldn't yet work on N kernel. To workaround this problem, u could flash rom first from M environment and flash firmware afterwards.
Anyway, since the hero's behind TWRP already have a working version there's no need for this workaround anymore.
Best way now is to flash firmware (including twrp) first and then boot to recovery to flash rom. There's absolutely no reason to flash N-based roms while on Marshmellow firmware.

@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
---------- Post added at 12:08 AM ---------- Previous post was at 12:07 AM ----------
BladeOne1 said:
@Switcherd
!:
Backup your data, including internal sdcard
The ROM boots on old firmware and dirty flash of the ROM on top of Android M 3.5.0 works!
On the last screen on the installation, choose the firmware you plan to use. If you pick the wrong one your fingerprintscanner and home button won’t work!
After flashing the Android N ROM, TWRP won’t be able to decrypt your data, so you won’t be able to backup/restore etc. It is recommended to run the rom on unencrypted data, so TWRP is fully functionial.
Flashing the new firmware will break TWRP, you will only have a black screen. Therefore you would need to downgrade the firmware to have access to TWRP again.
A TWRP working on new firmware got released: twrp-3.0.2-7-pme-DEBUG.img
If you decide to flash the new firmware, do it AFTER the ROM, you should know why, since you read the above text.
Downgrading firmware should be safe on that base, it has been done by one of our devs several times. On earlier bases it caused a brick. Do it at your own risk, downgrading is always dangerous
When you downgrade, use a full firmware from Sneakyghosts thread. If you use a partial one, you will brick your device!
If the rom does not boot: Only ways that work are: Changing to Dev ED MID and CID and flash the Dev ED RUU/Firmware or following that instructions
Installation Instructions:
Dirty flashing, to keep your data from Android M
Stick with the old 1.9x firmware to have access to TWRP
Backup your Android M rom, best would be Viper10 3.5.0..other roms should work too though
Backup your internal sdcard
format data in TWRP to get rid of encryption
restore your Android M backup
DON’T reboot, else your device will get encrypted again
Flash the 4.x.x rom
Ensure you pick the correct firmware you want to use on the last screen on the setup, else your fingerprint scanner won’t work
Now you got an unenrypted Android N rom, with fully working TWRP
Click to expand...
Click to collapse
Its from Viper Rom, but its the same

[Need urgent help] Multiple issues on my Oneplus 3

I got my op3 phone loaded up with twrp version 3.0.2-1 but many errors occurred after I flashed this version.
Current problems on my phone right now:
-"The dm-verity is not started in enforcing mode" occurs every time I turn on the phone.
-Twrp won't read any of my files inside the "sdcard" folder wether it's just regular folder, .zip files, and even .img files.
-It also looks like only 1 version works of twrp works on my phone right now since any twrp versions after 3.1.0 causes the twrp program to froze and doesn't completely move past welcome screen of twrp.

I believe I had the same problem. Contact OnePlus on their support page. In a chat support window, tell the operater about your problem, and ask for an appointment with a level 2 technician. They should schedule you an appointment with a technician who should be able to wipe your phone no matter what state/condition it's in. They fixed my phone in a matter of minutes. But PLEASE, try to remember to be respectful and co-operative, it usually gets you better service no matter who you are dealing with.

For dm - verity problem, it's not a problem tough... Just a security breach as seen by Google.
BTW here is the fix...It's easy , follow the thread :
https://forum.xda-developers.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339
Can't comment on twrp as I'm on the 3.0.2-1, haven't tried 3.1. Hope it helps, Thanks!

Use TWRP 3.0.4-1. 3.0.2 can't decrypt internal storage, at least not on mine it couldn't.
Also if you have f2fs file system, TWRP takes a loooooong time to boot. Just wait, even though it seems hung. Takes several minutes. If you have ext4, it's quick. Use the app 'Diskinfo' to check

I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.

mremghz said:
I had TWRP 3.1 and it would not do OTA of lineage, it would wipe the device when I tried and would not restore backed ROMs, stay away from TWRP 3.1. So, i went back to 3.0.4.1 via fastboot. My suggestion is flash the stock recovery from Oxygen 3.8 marshmallow (this can be found in the archived OnePlus 3 tool kit on XDA) and then sideload the stock marshmallow Oxygen 3.2.8 (download from OnePlus support page) and start all over.
Click to expand...
Click to collapse
That doesn't make sense..
The latest recovery works fine here, atleast the official one. If you are in F2fs and encrypted keep in mind it takes a long long time since F2fs is really bad at this.. Depending in how full your internal storage is it can take up to 10 minutesm

Twrp 3.0.4.1 or
3.1.0 x v.26 blu_spark.
To get OTA you need to be stock, only Oos official stuff.

I do have my oneplus 3 formatted as f2fs, but it is not encrypted. I don't know what happened to it when I tried to do an update with lineage os it basically factory reset the phone (and no I didn't wipe anything but the cache) and it would not install any zips from my internal sd card. I had to go back to fastboot and reflash TWRP 3.0.4.1 recovery. Then I wiped the device and reinstalled lineage, now it works perfectly fine.
They are lineage nighty OTA updates.

Decrypting the phone and flashing new ROM

Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.

cspctec said:
Last weekend, I decided to flash a new ROM since the one I have been using is no longer being developed. I flashed a LineageOS nightly build because I used to like Cyanogenmod and heard Lineage is a continuation. I do like the ROM overall, but for some reason it encrypted my phone during install. I did not want it to do this, it just did it without asking me (when I first got my phone, I remember I was having problems with it being encrypted, with my recovery and such).
Is there any way to reinstall LineageOS without it encrypting the phone? If not, how do I decrypt the phone again and get back to basically stock + root? I downloaded the most up-to-date stock 7.1.2 ROM from Google, and was going to just flash that, but it wouldn't let me in TWRP (said the zip was not valid). I also tried rolling back to an older backup (not LineageOS), but the phone never booted.
FYI - I use Linux Mint and have the latest adb/fastboot, and the latest TWRP for Nexus 5x.
Thank you if you can help.
Click to expand...
Click to collapse
If you want to flash stock rom you have to flash it via fastboot. The instruction is on the Google download side. But if I remember right you have to wipe everything so make a backup of important data.

If I format my "userdata" with fastboot to get rid of the encryption, do you know if it will delete my ROM backups? I think the encryption is why I'm having trouble going to another ROM from LineageOS. I REALLY wish the ROM would simply ask you before deciding to encrypt the phone. I have no reason to encrypt my phone, and I don't want it encrypted.

Updating from OOS_OB12(Oreo) to OOS_OB23(Pie)

Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA

hgaaditya said:
Hello Everyone,
I am currently on OOS_OB12 on my 5T. And I have root + Blu_Spark TWRP running. How do I update to Pie without losing data ? I have the treble update, but still on Oreo. I searched a lot and found mixed information, some say I need to go to a specific version first and then to latest., Some say I just dirty flash and flash magisk on top of that. Clean flashing is not an option as I have a lot of data I can't lose, So please help me out here.
TIA
Click to expand...
Click to collapse
Yeah the treble thing is a bit confusing. I don't remember which one it is for open beta. But the safe way to do it is to install 5.1.3 which installs without problem. Then take an update to 5.1.4. then you can freely update to any pie version without losing data. The problem is that I don't remember the Open Beta equivalent versions for these firmwares.
But like best is that you make a TWRP backup of the data RN before doing anything. OOS is quite picky on what conditions it wants to boot under.
Sent from my OnePlus 5T using XDA Labs

Go to Settings and check for available system update. It will get you the one you need to flash to get Treble. That's how I upgraded from 4.7.4. Downloaded 5.1.3 from Software Upgrade, flashed and booted up, checked update again, received 5.1.4 then 5.1.7 because Pie wasn't out for my country yet.

I checked my 'System Updates ' and it is showing me Open Beta 23 . Does that mean I'm good to upgrade directly to the latest version.?

Update I followed the steps here And everything works as expected. no need to clean flash :
https://forum.xda-developers.com/oneplus-5t/how-to/soon-oxygenos-beta-1-android-o-oneplus-t3726074
[Dirty Flash] For Users with an Unlocked Bootloader and TWRP Recovery coming from H2OS Oreo/Pie, Stable OOS Oreo/Pie, OOS OB Oreo/Pie:
Download the full ROM zip from the downloads section above
Transfer the zip to the root of your device's internal storage
Only needed if you are coming from Oreo: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
Flash Magisk Uninstaller (recommended)
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
Flash the latest stable Magisk in case you want to root
From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
If you were decrypted earlier, flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
Reboot
Closing thread.

[RESOLVED] Updating from OOS_OB12(Oreo) to OOS_OB23(Pie)
Closing thread