Hi,
okay, so i had a rooted samsung j500f phone running android lollipop 5.1.1 stock rom (downloaded from sammobile). I was using Apps2Sd for linking my apps to the external SD Card. Few days ago, my phone turned off on the battery getting empty and when i turned it on, all linked apps were missing. I was getting an error that "Disable mount namespace seperation in Chainfire SU". I did that but nothing happened and the App2Sd was unable to remount 2nd partition.
Frustrated, i contacted their developer who suggested to reinstall SuperSU. So, i opened the SuperSU app (chainfire) and went to settings and then chose the option "Reinstall from google play store". It uninstalled SuperSU which i later downloaded from Google Play Store. After it had installed, it asked to install binaries and gave me two options:
1) Normal in-app method
2) TWRP/CWM recovery method
I chose the second one (because i had TWRP installed).
Then my phone rebooted into recovery and ran a few scripts. However it later stated that there is no root on your device (which i believe may have been removed when SuperSU was uninstalled). TWRP gave me options to reinstall SuperSU but it did nothing. I downloaded the latest SuperSU zip file from chainfire site and tried to flash it. But the script would show failure. Now, my phone wouldn't boot into the system. Only into recovery mode.
Being really pissed, i decided to do a factory reset. So i did a factory reset from within the TWRP (normal wipe). Still, my phone wouldn't boot but would go to recovery. So i got angry, went into the Advanced wipe option in which i selected dalvik cache, internal storage, SYSTEM and wiped them all.
Now on trying to reboot, TWRP would say "There is no OS installed. Are you sure you want to continue?"
I knew i had messed up my phone and so i decided to flash it with stock rom again using ODIN. But, whenever i try to go into download mode it gets stuck on the Samsung Galaxy J5 Logo screen with "ODIN Mode" written on the top left along with a couple of other details such as Knox void 0x1(4), Rom statusfficial, etc.
Clearly, i am unable to flash using ODIN as my phone isn't being able to go to Download Mode. ODIN doesn't detect my device.
So i thought of flashing the stock rom using TWRP, which failed.
I also have a TWRP Backup but TWRP won't let me select it. I have the backup folder on my SD card.
Now my phone has just TWRP, Can't get into download mode using the key combinations or through TWRP bootloader option which on selection gives me the "No OS" error. I can't boot my device up as it goes into recovery.
Kindly help as soon as possible.
Thank you.
If you wipe the SYSTEM Partition, then of course that no OS is installed. Like a Hard Brick. Good Job...
Related
I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
i am currently using twrp and ive had no problems flashing roms including sky ics which those directions are from also a recovery isnt compatible with odin if you want to odin back to stock or flash anew recovery image you just go into download mode and procedd from there
RAVEN6 said:
I'll post my question after some background:
I was on CWM Touch, downloaded and installed the TWRP from google play. Rebooted into recovery, created backups to internal and external, and flashed SkyICS 4.2f6 by Seanz. I followed OP instructions on how to flash. Did not have any problems and it was very easy to use.
Used TWRP and flashed several MODS and ROM updates without any hitch. All I did was reboot into recovery selected the zip files and swipe to install, did not even had to wipe cache or anything. I am not sure if this is the correct way but I was able to do so without any problems.
I wanted to install the same rom but to do a clean wipe since the rom had several updates. So, I rebooted into TWRP recovery, did OP flashing instructions which were:
-reboot into team win recovery
-wipe system
-factory data reset
-then go to mounts and choose external sd
-no go back and find the rom by choosing install zip
-swipe to confirm
-then install the radio you downloaded
and when complete reboot phone
-at this point everything will be settling and caching
which may or may not seem laggy.... and yes that white line is normal
its a battery representation mod
-im sure youll be eager to update busybox immediatly but let me tell you no
first open super user app.. find preferences and update user binary
hit it twice giving it root permissions
now .. is when to update busy box through the provided installer
-after you have done this
-power down phone
reboot into recovery and flash the latest update
and email package only
However, I was not able to reboot into recovery. I have a Samsung Skyrocket but was not able to put the phone into recovery mode by pressing and holding the power, volume up, and volume down buttons. The phone kept vibrating but the Samsung screen wont come up. Frustrated, I rebooted the phone, downloaded CWM, updated to Touch and proceeded to flash using CWM with no problems.
At this point i'm hesitant on using TWRP. I am not even sure if ODIN supports it. I'm afraid that if i'm on TWRP and brick my phone, I will not be able to use ODIN.
Questions:
Has anyone encounter the same problem?
Is TWRP compatible with ODIN?
Can anyone using Samsung Skyrocket confirm the recovery steps used above is correct?
Thank you for your help.
Click to expand...
Click to collapse
To reboot into recovery you hold power, volume up and down and when you see the first samsung logo let go of the power or it will keep rebooting.
As for being compatible with odin, I'm not sure what you mean. You can flash TWRP through odin, you can get into download mode with twrp installed also.
Have you tried reinstalling TWRP?
Restored the Tablet TF101 back to stock rooted and everything worked. Installed CWM Did factory reset system wipes etc. Tried to install 3 different CM 10 all failed bad installation. Tried to installed the newest TWRP same thing I can't seem to install any rom from the external or internal just keeps saying bad?
What errors did TWRP tell you?
For TWRP why not download the GOO app from the playstore and find the option in the menu to allow it to install the open recovery script for you?
Had similar issues with my S4 with a particular rom but youve tried a few so i doubt its down to the download sites.
You may have to format the emmc and see how that goes as a last resort. (just make sure you have a rom placed on a micro sd as it will completely wipe the TF again but still keep your recovery)
Ok. I have a Samsung S4 mini. Yesterday I installed CM13. Dumb thing to do.
It was an automatic update from CMUpdater, so not through the Recovery menu.
For my surprise, I noticed that this update also updated the ClockWorkMod Recovery to the latest version available.
The CM13 installation went well actually .The phone booted fine. Then of course I needed the new Gapps installed. I downloaded the correct Gapps. Boot into CWM recovery. Choose the Gapps ZIP file. And... Error! I went back to phone to enable root acess (ADB & Apps), and enabled USB debugging also. And...Error! No way to install Gapps with CWM recovery.
After some search I realize that the new Gapps for CM13 is somehow not compatible with the CWM recovery that was instaled. So I downloaded ROM MANAGER to change the recovery to TWRP, which everybody said would perfectly flash the Gapps smoothly. Nothing happened. No TWPR. Only CWM still on. Then I downloaded Flashify and went back and forth on installing and unistalling TWPR and CWM. On and On.
Conclusion: somewhere along the process not only I couldn´t install TWRP recovery, but also have wrecked the CWM recovery. Now, no matter what I do, I cannot enter recovery mode at all, hence i cannot neither install Gapps or Reinstall another ROM to "start from scratch"....
I can boot the phone normally.
I can boot into donwload mode normally.
I tried installing TWRP .tar with ODIN3 but it keeps saying "cant open USB port", so it fails.
I have also installed KIES. It sucessfully install drivers, but fails to connect with my device.
Is there anyway to install a Recovery or a fresh new ROM without having to boot recovery?!
Some help? Please.
Hello,
Welcome to XDA.
Do you have USB debugging enabled in system settings to allow flashing via Odin? You may not even need to use Odin.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s4-mini/help
The experts there may be able to help.
Register an XDA account to post and reply in the forums. Good luck.
So I just rooted my S6 for the first time, and I'm not very experienced in rooting. I used ODIN to download, and did as told in the website here at galaxys6root.highonandroid .com/galaxy-s6-root/how-to-root-galaxy-s6s6-edge-on-android-6-0-1-marshmallow/ This meant my phone has a TWRP custom recovery but a custom one made by ManhIT, and I was successful in rooting, just that each time in recovery I do a system reboot, it hangs there so I do a force reboot which leads back to the lock screen just alright.
Then I wanted to download Xposed Framework, so I followed this tutorial to download it on Marshmellow 6.0.1: android.wonderhowto .com/how-to/install-xposed-framework-android-6-0-marshmallow-devices-0166278/
youtube .com/watch?v=B3qbY2CWz5M
I did everything, downloaded Xposed Framework for ARM64 Marshmallow devices but had to find the latest version, v85 for it and this is where the problem started. I went to TWRP recovery mode, and went to flash the xposed framwork zip, and clicked system reboot (of course it hanged, so force reboot), and since then it always has been stuck on the Samsung logo screen. I went back to recovery mode, did a factory reset, wipe all data, format data, and it still gets stuck on the logo screen.
Please please please please help!!!!
UPDATE: A possibility of this problem is due to having "No OS Installed".
what I would do if I were you is:
1. Smart switch emergency initialization to restore phone to factory fw with sn of the phone (upper right corner in SS menu) (connect phone only when you are asked, otherwise it will say your device is not supported)
2. flash CF autoroot for that model https://autoroot.chainfire.eu/
3 flash TWRP downloaded from https://twrp.me/devices/samsunggalaxys6.html for that phone model
and see what would happen (offcourse I would check after each step if the phone can boot)
brenner650 said:
what I would do if I were you is:
1. Smart switch emergency initialization to restore phone to factory fw with sn of the phone (upper right corner in SS menu) (connect phone only when you are asked, otherwise it will say your device is not supported)
2. flash CF autoroot for that model ]
3 flash TWRP downloaded from for that phone model
and see what would happen (offcourse I would check after each step if the phone can boot)
Click to expand...
Click to collapse
I fixed it already! I think what it was in the end was the lack of OS. Should've backed up my data before doing anything funny. Installed my OS again and bam my phone is up and running again :good: (had to delete the URL from this reply as I'm just a junior member)
Hey guys,
Recently moving back to Android with a Samsung Galaxy S7 (SM-G930F) and I have some problems to get everything working. I didn't find (or didn't managed to find) the informations I was looking for on the forum or anywhere else on internet.
Here is what I did since now:
1. Rooted my phone with CF-Auto-Root.
2. Phone rooted correctly, SuperSU installed => no problem
3. Installed TWRP Manager.
4. Launched installation of TWRP from the TWRP Manager and selected the latest version of herolte (3.0.2-2).
5. Installation failed, relaunched it, didn't get any notice of success or failed this time so I presumed it was good.
6. Restarted the phone in normal mode => No problem.
7. Restarted the phone in recovery mode => Access to TWRP asking me if I want to stay in read only or allow read/write.
> Can I boot up at this stage in read/write without causing any issues since I saw in the TWRP root installation process (http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770)
"By swiping right, you will trigger dm-verity, and if you don't follow step 11 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."
> Since I am already rooted, it shouldn't cause any issues right?
8. I tried to do a backup of my phone but the data folder is showing no data and when performing a backup I am getting a "failed to mount /data error"
> Don't really know how to fix this error.
> I can backup without any issue Boot and System.
Thank you per advance for your answers
1. You need to flash dm-verity and force encryption disabler before you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Thank You.
I just did the steps described but it seems that I lost my root after having wipe the data partition.
Now when I am rebooting the phone I am getting "kernel is not seandroid enforcing" in red on top of the screen but the phone still boot up fully.
Tried to reboot in recovery but it seems that TWRP is not present anymore.
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Julek_Fr said:
I re-rooted the phone using CF-Auto-Root.
Now the phone is rooted, I installed once again TWRP Manager and tried to reboot in recovery mode but getting "dm-verity verification failed…"
I don't have the "kernel is not seandroid enforcing" error anymore.
Do I need to reinstall TWRP in order to solve the issue?
Click to expand...
Click to collapse
Hi
did you do this?
Point 11
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 only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
MAX 404 said:
Hi
did you do this?
Point 11
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 only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Kernel thing is normal ........
Click to expand...
Click to collapse
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Julek_Fr said:
Thank you for your reply.
Since the phone was already rooted I didn't done the SuperSU but wipped the data partition and flashed with the "dm-verity and force encryption disabler".
After reboot I was not rooted anymore, so I re-rooted the phone and reinstalled the aps.
Now if I try to reboot in recovery mode, I get the error "dm-verity verification failed…"
If I try to factory default the phone I am getting the same error.
Do you think I can just flash back in stock firmware using odin and the good version downloaded from sammobile? It will remove TWRP and the root right ?
Click to expand...
Click to collapse
Hi
Flash a stock firmware is an option but not necessary at this point
Go back to TWRP page
http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770
and re do all this steps one by one ( 1 to 13 ), make sure OEM unlock is enables , back up important thing before you do anything just in case
FULL STEPS FOR OBTAINING ROOT
You can follow this video by Max Lee if you'd like: How to Root Galaxy S7 & S7 Edge! [Exynos ONLY]
Otherwise, follow these instructions:
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.
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
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 without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
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 11 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.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
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 only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
Wait 5-15 minutes for your device to finish setting itself up.
try this first....
GerasVille said:
1. You need to flash dm-verity and force encryption disablerbefore you swipe right and activate read/write. Otherwise it won't boot.
2. If you want to do a backup with TWRP you need to format data once, so the encryption is disabled. Just perform a backup via Titanium and format data in TWRP. Afterwards you can make backups in TWRP.
Click to expand...
Click to collapse
How to flash this file? Please treat me like an idiot. What exactly do I have to do?
I am trying to flash the ROM of a different model of my phone, and thus need TWRP, but this needs to be unlocked first somehow.