Hi,
I'm trying for 2 complete days to install android 2.2 on my polaris now but I cant get it working.
Since i'm a complete newby probably it will be something very simple (i hope) but i'm getting verry frustrated at the moment haha.
I'm stepping over from WM6.1
What i have done:
I have a HTC Polaris POLA100
I have a 4gb Micro sd HC class 4
I'm trying to install Incubus26Jc's Super FroYo RLS16 All Languages trough NAND
I have HARD SPL V2 on the phone
I have done all this steps: sourceforge. net/apps/ trac/androidhtc/wiki/HowToInstallWithAtoolsNand
When i boot my phone now i get:
linux logo in top: lots of text lines
then I get:
Mount: mounting /dev/block/mmcblk0p1 on/sdcard failed: invalid argument
sh: 0: unknown operand
found boot parameter for system
system on nand partition
found boot parameter for data
data on nand partition
failed
install module for this kernel
On the sd-card I have
POLAIMG.NBH
andboot
*androidupdate.TGZ
*androidinstall.TGZ
*install-seq.sh
I've tried the NAND option on this page also: http://forum.xda-developers.com/showthread.php?t=921053
But i get the massage:
failed
install module for this kernel
hooliead said:
I've tried the NAND option on this page also: http://forum.xda-developers.com/showthread.php?t=921053
But i get the massage:
failed
install module for this kernel
Click to expand...
Click to collapse
Download the modules form here:
http://sourceforge.net/projects/androidhtc/files/modules/
Rename the tgz file to "androidupdate.tgz" ,than put it in /sdcard/andboot/.install it when you enter the installer menu.Problem will be solved.
Same problems...
When i restart te phone with a soft reset and wait i will get the massage:
Failed
Install module for this kernel
When i manual try to install by keep pressing up the volume button after soft reset i get the massage
there is no such file on sdcard androidupdate.tar
I have checked several times there is a androidupdate.tar and a androidupdate.TGZ (same for androidinstall)
I also tried with only the .TGZ file and only the .TAR file
reformat the sd card.
done it several time... no succes
I need help with my samsung GT-I9000.
I cant start the system anymore, connection with computer works.
I had Adroid v 4.0.3 and it was working ok, just tried to start a new build version. Then i accidently cut the connection, so i had to load via odin .512 and CF-Root-XX_OXA_JVS-v4.1-CWM3RFS now i am deadlocked, no idea how to fix the problem.
My screen shows:
ClockworkMod Recovery v3.0.0.5 (Problem I might have deleted it)
- reboot system now
- apply update from sdcard
....
(tried out everyone, non worked)
E: unknown volume for path [/cache/recovery/command]
E: unknown volume for path ....
Thank you for help
did you check repartition in odin while flashing stock rom?
had the same error once and with repartition and a stock rom everything was okay again..
Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?
Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.
[Problem solved] If anybody faces this kind of problem please notice it is not the problem of Nand-erase but DRK error and flashing with .pit file won't fix your problem. Just go to this discord group, https://discord.gg/Z4UZheJ [permanent] and ask for #Augustin. He will solve your problem 100%. He did for me. Full working network + rooted.
---------------------------------------------------------------------------------------------------
Hello, I was trying to update my s7 edge (SM-G935FD) with Oreo 8.0 from Nougat 7.0 with a custom firmware from sammobile.com.
The used file is: sammobile.com/firmwares/galaxy-s7-edge/SM-G935FD/BNG/download/G935FXXS3ERHD/236500/
But when flashing with Odin I accidentally selected "Nand Erase" option. After the operation completed my phone tried to boot up, showed installing updates, then tried to boot again and now permanently stuck on "SAMSUNG Galaxy S7 edge POWERED BY android".
Still, I can access "download mode" by using "Power + down + home" button and "android recovery" by using "Power + up + home" button.
While loading android recovery screen it shows, "Installing update..." then "Error" with an icon of android eyes crossed.
In my recovery menu, these lines are shown:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I flashed with this same firmware to no avail. I have also tired "Wipe data / Factory reset" and "Wipe cache partition". Nothing worked.
Now, other people who have tired this firmware faced the same problem for #fail to open recovery_cause
But, in my case, as bold lines indicates, this is may be due to using "Nand Erase" in Odin.
I do have :
Nougat 7.0 firmware for my device [Please notice that its baseband is U2 - so I can't downgrade bootloader from S3 to U2 hence can't flash with Nougat]
.pit file for my device [not sure about this one - I actually need a valid pit file from the above firmware, others don't seem to work.]
I have tried Z3box / octopus / smart switch samsung software to recognize my device, but they always reply with "Card not found". My Windows treats my device as unrecognized in this situation.
Please help me fix this issue. I just have bought this phone - second hand.
-----------------------------------
Update - I tried to use stock recovery files to flash with TPRW stock recovery. After I did that It started the tprw recovery and I installled two files
1. twrp-3.1.0-0
2.SR3-superuser
It completed and when I selected to reboot my phone, it just won't turn on anymore. I guess it is due to my partition is all messed up. I forced it to start up using my charger cable and plugging it to charging. Using "Download mode" then I tried to uninstall this TPRW and flashed only "AP" with "G935FXXU2ERD5" with odin as I was unable to find any stock recovery for "G935FXXS3ERHD".
Now, I am stuck with U2 bootloader whereas I need S3 bootloader. My phone still doesn't turn on normally. I have to plug it in charging port / USB cable to pc, then it goes straight up to "Android Recovery" and Now shows this:
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Successfully verified dmverity hash tree
E: Failed to clear BCB message: failed to find /misc partition
Please help me. I know I messed up, I shouldn't have used the TPRW recovery. Now I can't even flash with previous G935FXXS3ERHD or any U2 firmware. Please help me. I feel like crying.
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
https://drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
yakapa40 said:
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
Click to expand...
Click to collapse
jaqjacek said:
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
Click to expand...
Click to collapse
Dear all,
I don't know how to say it, but a miracle just happened. My phone was stuck to "Android recovery" mode for half an hour. The charging cable was plugged in - in this time. Right before I am about to disconnect the cable in order to take it to repair shop, it started booting out of nowhere. :fingers-crossed:
Then I set up the device and the device installed applications by itself. God knows what happened but here is my system spec now :
Android version 8.0.0
Samsung Experience version 9.0
Baseband version G93FXXU3ERHC
Kernel version 3.18.91-13895453-QB19588583
Build number R16NW.G93FXXS3ERHD
The TPRW application is also installed.
I don't know what happened but it has managed to boot.
--------------------------------
The problem I faced is, It doesn't let me select any network carrier for my region instead it just says, "Failed to connect! Try again later."
Now I am afraid to even restart the device fearing if it gets stuck in the boot loop again. I am so scared I don't know if I will flash this device with any stock firmware anymore.
And the "Android recovery" option still shows "Installing updates" following with "Error" with android icons eye crossed out + shows previous error messages still the same.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Thank you, everyone.
If you could just help me solve my problems I will be always grateful to you guys and this community.
@jaqjacek if you can point out a tutorial to me or just explain the steps elaborately that would be helpful.
@yakapa40 if you can help me how to use those files, please.
My device is now booted up but still showing errors in "Android recovery" option + the sim network doesn't work.
What version of Odin are you using to flash?
quasihellfish said:
What version of Odin are you using to flash?
Click to expand...
Click to collapse
Odin3 v3.12.7 in windows 10. Installed samsung driver both manually and via Smart Switch.
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
yakapa40 said:
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
Click to expand...
Click to collapse
Ok, sir, I will try and let you know. One question though, is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
My android recovery says:
Android Recovery
samsung/hero2ltexx/hero2lte
8.0.0/R16NW/G935FXXU2ERD5
user/release-keys
use volume up/down and power.
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
yakapa40 said:
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
Click to expand...
Click to collapse
Dear sir,
I am still waiting for some kind of help. I haven't flashed my phone with .pit file cause I am too scared that my phone will get stuck in boot loop again. Please, somebody, help me. If I get stuck in the boot loop again, I don't think I can revert back to current position [Cause I don't know how my phone was fixed, it just fixed itself somehow.] and I can't take the stress. Please somebody who is an expert on this matter, please help me. I beg you.
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
ukero said:
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
Click to expand...
Click to collapse
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have poor network connection or GSM singal will be gone thats is the problem that I don't have fix for now.
jaqjacek said:
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have a poor network connection or GSM signal will be gone that's is the problem that I don't have fix for now.
Click to expand...
Click to collapse
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https://www.youtube.com/watch?v=C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
ukero said:
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https: //w w w. youtube .com /watch?v= C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
Click to expand...
Click to collapse
hey, im needing the file. i know how to do. please, help me. im with same issue, but with s7 flat SM G930F
Augustin is the best!
Hey there, I have a very similar problem with my S7 G930F. Could someone help me please? Thanks in advance.
(PS. The discord link is down, so I can't talk to Augustin)
After a lot of problems with my computer @ZeroXO helped me to solve the problem
Issue freeze and restarting
ZoOMBeE said:
Augustin is the best!
Click to expand...
Click to collapse
Can u tell me a way to contact him? the discord's link doesn't work anymore. I'm facing a freeze issue with my s7 edge. I mean It freezes when Im using it and also on TWRP so I can't install anything :c. I already flash stock firmware and it boots successfully , but in about 2 minutes it freezes and restart again. Also it happens in safe mode and recovery. Help me :c
Hello everyone
I truly hope that someone can help me. I would like to say sorry in advance because Im asking a question I might find the answer to by reading the thread(s) myselfe. Only thing is - I truy don't know where to look. When it comes to phones Im lost, so to speak. And right now Im lost. I hope you can helpe me:
When I turn my phone on it boots up in androide recovery mode. I have tryed reboot system and wipe data. When wiping data I get this message:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Bassed OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm-verity verification failed...
E[libfs_mgr]is_dt_compatible():firmware info was not valid : ´/proc/device-tree/firmware/android/compatible : No such file or directory
-- Wiping data...
Formatting /data...
Formatting /cache..
Data wipe complete.
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ´/proc/device-tree/firmware/androdi/compatible': No such file or directory
Maybe it can be saved maybe no. The case is I don't know what to do next. All I know is, that a program called Odin might do the trick if you add the right "things" in BL, AP, CP and/or CSC??
Can someone please tell we what I need, and where to find it?
Kind regards
Inish