Related
Ok was trying to install a ROM and got an error that there was no OS installed and now the phone wont boot up
I rooted it via Bacon root toolkit and I took a back up before I rooted but I cannot get it to reboot. The back up is saved on the PC and phone not getting picked up by PC
Anyone tried to restore android back up file and went to ab file on pc but it wont load. Can go into fastboot and recovery but not showing on PC
HELP
Delete duplicate post
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
timmaaa said:
This is why you shouldn't use toolkits, you have no access to fastboot and no idea how to fix it. What drivers are installed on your PC? I guess it doesn't matter, my advice is to completely delete anything that the toolkit installed and start fresh. Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
I have links to the Android SDK (which contains adb/fastboot) and the right drivers for this phone. Make sure you reboot your PC after deleting everything, then install the SDK and the drivers, reboot PC again, connect phone.
Transmitted via Bacon
Click to expand...
Click to collapse
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
funkyirishman said:
Live and Learn and got back to the stock using adb/fastboot and installing images and back to normal again. I want to update to Lollilop and Sabermod but after trying may just stick with Stock for a while as I kept getting errors when trying to load the ROM??
Thanks
Click to expand...
Click to collapse
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
timmaaa said:
Exactly what error are you getting when trying to flash? Are you checking the md5 when you download? What recovery are you using?
Transmitted via Bacon
Click to expand...
Click to collapse
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
I have the files saved in the download folder.
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
funkyirishman said:
When I tried to flash initially I got the below
Went into recovery and did Factory reset and then wipe cache partition. Then tried Apply update and scrolled to the ROM file and apply update and I get the below error
Install Failed
Finding Update Package
Opening Update Package
Verifying Update Package
E: Failed to verify whole-file signature
E:signature verification failed
Installation aborted
Click to expand...
Click to collapse
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
funkyirishman said:
Then when I tried to install with TWRP rather than update I clear cache, dalvik and system and tried to load and got the below error
Checking for MD5 File
Skipping MD5 Chekck: no MD5 file found
Comparing TZ Verionsioj TZ. BF.2.0-2.0.0109 to TZ
BF 2.0-2.0.0096
assert failed oppo verify trustzone
I got the message that no os installed and I could not reboot so I flashed it back to stock using the below
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Phone now rooted and unlocked and like to update but afraid I will just experience it all over again:crying:
Any help appreciated
Thanks
Click to expand...
Click to collapse
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Ok, you got this error because you're trying to flash a custom ROM with the stock recovery. The stock recovery can only flash zips signed by CM (official updates)
Your problem here is that you're trying to install a ROM but you don't have the correct firmware installed. When flashing a Lollipop ROM for the first time you need to first flash Lollipop firmware and Lollipop modem. Once you've flashed those they're always there so you don't need to do it again. The only reason you'd need to flash firmware and modem again would be if you wanted to return to a KitKat ROM, and then it'd be KitKat firmware and modem that you'd need to flash. Anyway, you'll find the modems here:
http://boeffla.df-kunde.de/bacon/modems
And I mirror the firmwares here:
https://drive.google.com/folder/d/0B98G0KTJwnBFRGhZeUNpMEI4ajg/edit
PS. I also noticed you weren't wiping properly before attempting to install the ROM. When flashing a ROM you need to perform a full wipe, this includes system, data, cache, and dalvik cache. This didn't cause the problem you experienced, but had the install succeeded you would have had other problems.
It might benefit you to read the OnePlus One FAQ thread:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
And my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
funkyirishman said:
Cheers thanks for that. I thought the ROM updated the firmware and modems so that's a lesson learned
Click to expand...
Click to collapse
CM12 does do that, but no other ROMs do.
funkyirishman said:
So I download the modem and firmware and copy these into the download folder on the phone and install via TWRP recovery correct? Modem first then firmware? This will then put lollipop on the phone correct?
Click to expand...
Click to collapse
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
funkyirishman said:
Then if I want to install a new ROM I need to do a full wipe. I just did not see that option and was just following the video tutorial associated with the Sabermod thread by wiping cache system and dalvik
Click to expand...
Click to collapse
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
funkyirishman said:
Read your thread and will be doing a full nandroid & EFS back up prior to do any of the above
Thanks again
Click to expand...
Click to collapse
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
timmaaa said:
CM12 does do that, but no other ROMs do.
Yes, install via TWRP recovery. It doesn't matter which order you flash them in. So install both, then go to the reboot menu, and select to reboot back to the recovery. This doesn't install Lollipop as such, this installs Lollipop compatible firmware.
Go to the wipe menu in TWRP, then select advanced wipe, from there you can choose which partitions you want to wipe (system, data, cache, dalvik cache), just don't wipe internal storage (that's your virtual sd card).
Very good, that's super important. It doesn't happen often, but sometimes the EFS partition will just randomly become corrupt, if you don't have a backup in that situation your phone is useless (you can't use someone else's EFS backup because it contains unique device identifiers).
Transmitted via Bacon
Click to expand...
Click to collapse
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
funkyirishman said:
Reading about back ups etc on the below when creating a recovery
-Make sure you check the md5 to verify its integrity.
How and what do you check?
Also I first do the back up. Then install the firmware and modems and then update the ROM.
I dont need to flash the stock kernal or fastboot images, correct?
Also doing a back up does it back it up to an internal SD Card or should I keep it on PC
Cheers
Click to expand...
Click to collapse
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
timmaaa said:
The download page for a ROM or kernel usually lists the md5 checksum for that particular file. An md5 is like a digital fingerprint of the file, so once you've downloaded it you use an md5 checking app/program to confirm that the md5 of the downloaded file matches the md5 listed on the download page. This confirms that the file hasn't become corrupt during the download, if even a single byte of information is corrupt in a file the md5 will be drastically different.
You don't need to flash the stock kernel or stock images, the numbered parts in my guide aren't steps, they're sections.
When you create your nandroid backup using TWRP it will automatically be saved to your internal storage. You should keep at least one backup on your phone at all times, think of it as an insurance policy just in case something goes wrong, you'l always have a known working OS there to save you. You should also copy it to your PC for safe keeping.
Click to expand...
Click to collapse
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
funkyirishman said:
Perfect I will google an md5 checking app/program so for the Sabermod I need to check on the download page on their link below
http://forum.xda-developers.com/oneplus-one/development/rom-kernel-sabermod-cm-11-0-t2880407
Just checked their download link is not working but I downloaded the ROM to my PC previously and its in zip format can you check the MD5 v this?
Thanks
Click to expand...
Click to collapse
You have nothing to check it against though.
Transmitted via Bacon
timmaaa said:
You have nothing to check it against though.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
funkyirishman said:
Ok so the ROM I downloaded is called cm-12-20150324-ROBBIEL811-UBER4.8-bacon and is in zip format and the download link on the developers page is dead so I cannot check the md5 file?
Thanks
Click to expand...
Click to collapse
Well yeah, if you can't reach the download page there's no way to see what the md5 is. Not all download pages have it anyway, they should, but not all do.
Transmitted via Bacon
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
6andro said:
Hi
I'm a bit impatient to wait for the CM12S OTA update on my Oneplus One. I have stock CM11S ROM without root (since the last OTA update), but I sill have the TWRP recovery. I downloaded the update.zip for CM12S. Can I just "install" that .zip with TWRP recovery?
Click to expand...
Click to collapse
Just follow this...
STEPS:
1. Download http://builds.cyngn.com/cyanogen-os...263178b74/cm-12.0-YNG1TAS0YL-bacon-signed.zip
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Shankar9822 said:
Just follow this...
STEPS:
1. Download [lurl]
2. Keep in internal storage
3. Wipe dalvik,cache, & data(data if you want clean install,but dirty also works)
4. Install zip
5. Reboot
Click to expand...
Click to collapse
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Update twrp first then flash. You will not loose personal data when doing the wipe.
Sent from my A0001 using XDA Free mobile app
6andro said:
Thank you I tried that. But immediately after swiping to install the .zip in TWRP there is an Error saying that the file is made for device A0001, but my device is "bacon". I read somewhere that I would need to update TWRP to solve that problem?
And another question:
What will be deleted if I wipe dalvik,cache, & data? I suppose not the internal sd, but maybe some other data I don't want to lose?
Click to expand...
Click to collapse
I think you are using the wrong version of TWRP.
http://dl.twrp.me/bacon/
Use the above link, download the latest version 2.8.6.0-bacon.img and flash it...
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
striker280 said:
I was using cm11s, then i flashed the 12s signed zip using twrp, and i had the update cm recovery checked off, but for some reason now i lost twrp and only boots up the cyanogen recovery. Is it alright just to reflash twrp again? Also will flashing this ota cause my bootloader to relock?
Click to expand...
Click to collapse
It's normal for the stock recovery to be flashed during an OTA update. Yes you can flash it again. No it won't relock your bootloader.
Transmitted via Bacon
About to flash a rom on my 920T..
I've created a backup already
when flashing, what should I be wiping first? I noticed by default cache partition isnt selected. Ought that be wiped as well in addition to dalvik, 3rd party and system?
What are your experiences and whats worked best? I saw a video where trying to flash a rom gave him a soft brick and he had to ODIN
Soft bricked mine too with flashfire trying to update to 5.1.1
JusTeN_ said:
Soft bricked mine too with flashfire trying to update to 5.1.1
Click to expand...
Click to collapse
Im not updating to 5.1.1
just trying to install AxisM rom RLS3
tlxxxsracer said:
Im not updating to 5.1.1
just trying to install AxisM rom RLS3
Click to expand...
Click to collapse
Never tried installing Zip file, had twrp. Flashfire sound trusty and also flashify I think.
JusTeN_ said:
Never tried installing Zip file, had twrp. Flashfire sound trusty and also flashify I think.
Click to expand...
Click to collapse
I dont want to trip knox, thats why I'm using Flashfire.
Just not sure why cache partition isnt marked to be wiped by default.. and since its not TWRP I dont want to wipe it if its important for it to flash the .zip correclty.
tlxxxsracer said:
I dont want to trip knox, thats why I'm using Flashfire.
Just not sure why cache partition isnt marked to be wiped by default.. and since its not TWRP I dont want to wipe it if its important for it to flash the .zip correclty.
Click to expand...
Click to collapse
I think flashing custom rom is tripping knox..
JusTeN_ said:
I think flashing custom rom is tripping knox..
Click to expand...
Click to collapse
flashing a rom will not trip knox. installing a custom recovery or custom kernal will
RLS3 uses stock kernal and doesnt use AROMA installer so you can use flashify.
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
costafabiof said:
Good evening, I saw some questions similar to this one in the forum, but none had my kind of doubt.
When a new ROM comes out for both S7 and S8, I install via ODIN using the CSC HOME option, so as not to lose the data.
The problem is in the installation of TWRP whenever I install the same by ODIN, when entering the app and trying to install example no-verity ja start I get the message that the DATA folder has been corrupted and can not be mounted.
This way it only works once again doing WIPE DATA, but then I lose my data and I have to start from scratch.
Is there a way this does not happen or will it always be like this when updating a ROM?
Thank you.
Click to expand...
Click to collapse
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
godkingofcanada said:
Have you tried backing up data with twrp before you wipe and copying it to your pc so you can do a full wipe then put the backup onto the phone and flash It? You can back up data folder only
Click to expand...
Click to collapse
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
costafabiof said:
Good afternoon,
Thanks for the reply.
So from what I mentioned above, I do a full backup as I normally do, and I also do a separate from the DATA folder.
Then I install the ROM and TWRP, will it corrupt the DATA folder so I restore only it? Would it be this?
If so, will it work out, in relation to being a ROM different from the other?
Click to expand...
Click to collapse
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
godkingofcanada said:
The main rom info needed is contained in the system folder. The data folder is application data and whatnot. Reboot into twrp and use the backup option, then copy to pc. Do a full wipe of all, pit backup of data folder and new rom on internal or sd. Go into terp and flash the rom and data folder. Do not flaah system or it will overwrite the new rom. u will restore everything even if you don't have the APK installed in your system. It will return the data, you may need to reinstall the APK. Gmail for example will return will email addresses and messages, contacts and texts will come back to what they were at backup. You should back up modem and efs and boot as well and keep them safe. What I do is I get my phone set up fully, all apps I need and any games and data and then back it up again so any issues and I restore it to a fully functional state and don't need to install tons of things
Click to expand...
Click to collapse
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
costafabiof said:
Good afternoon,
I'm sorry for the text I'm using Google Translate.
I believe that I did not understand correctly, because the error happens in the following way, I install a ROM, reinstall the TWRP, yes yes it corrupts the folder DATA!
If I understood mistake, I apologize.
Click to expand...
Click to collapse
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
godkingofcanada said:
Is it a custom Rom or a stock rom? Also you can backup via ADB
https://forum.xda-developers.com/an...oid-sdk-adb-backup-apps-t3467560#edit68829721
Click to expand...
Click to collapse
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
costafabiof said:
The ROM I use is provided by Samsung, with no modifications, when I install it I use the CSC option the HOME file, in order not to lose the data, and of course, I do not lose anything I only update the ROM.
The problem is that I need to reinstall TWRP after installing ROM, and when I access TWRP it has corrupted the DATA folder.
Click to expand...
Click to collapse
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
godkingofcanada said:
You can extract the samsung md5 and repack it as a zip with superrs kitchen and then flash it from twrp. Just remove the recovery.img from the extracted files before zipping it up. Then you can simply flash twrp. Then the rom and not have to worry about the fact that you are stuck in a loop of being locked out because you don't need odin for the rom and it won't overwrite your recovery. If that's too much work try using a custom Rom from xda
Click to expand...
Click to collapse
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
costafabiof said:
Thank you very much for your patience. But I'm not clear, or you do not understand.
The problem is not in the ROM, but in the TWRP installation. If I install the ROM with the option CSC HOME I do not lose anything, everything is working correctly.
When I install TWRP it corrupts the DATA folder. The problem is there!
Click to expand...
Click to collapse
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
godkingofcanada said:
I was saying to use a zip rom because then you can reflash the rom without reflashing twrp. So you flash twrp, it says data error and then you flash rom from zip, which reinstall system and data but will not copy stock recovery over twrp. So you will not have to reinstall it and be stuck. Or try a different version of twrp might also help. Stock firmware overwrites recovery and the rom. You need to modify it to remove recovery from the firmware, or use a custom Rom to stop it from erasing twrp
Click to expand...
Click to collapse
I think I understood, more or less, since I translate for Google.
But assuming I want to use normal ROM, you have to back up the DATA folder before installing the ROM and after installing the new ROM and TWRP, restore only the DATA?
Thank you again.
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
godkingofcanada said:
Yes a new rom will overwrite data, you need a backup before. You should be able to connect your phone to a linux operating system and use adb to connect and back it up, if twrp will not let you take a back up.
Click to expand...
Click to collapse
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
costafabiof said:
In my case I can back up the DATA folder by TWRP. Is there doubt, if I back up the DATA folder in one version of Android and then restore in another version, will it be compatible?
Click to expand...
Click to collapse
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
godkingofcanada said:
Yes it will be, marshmallow and nougat are completely compatible from the boot loader up. You can also turn your stock samsung md5 into a zip file so you do not need odin to install it. You will be able to flash it from twrp
Click to expand...
Click to collapse
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
costafabiof said:
Again thank you very much.
I'll test it and put it here.
Note: The Thank you button is not working.
Click to expand...
Click to collapse
You are welcome. If you want to have a stock zip file instead of the md5 use this link.
https://forum.xda-developers.com/showthread.php?t=2387941
...
costafabiof said:
...
Click to expand...
Click to collapse
Can you not read the website?
I know what you mean. Twrp can't access the data folder because it's encrypted. But you do have to format it to gain proper access. You have to copy the files out or back them up
godkingofcanada said:
Can you not read the website?
Click to expand...
Click to collapse
I believe that because I am a new user I can not exclude publications, I already tested in CHROME and IE. In the same way I can not give THANK YOU.
thus I don't have OS anymore, so I can't boot into download mode.
I have TWRP, I think the only thing I can do is just get stock .zip ROM. But I can't find it for my G930F, I downloaded some but they are all prepared for odin, not for recovery.
Could please anyone give me a download link for a flashable stock rom?
Or any other ideas?
Thanks
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Beanvee7 said:
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Click to expand...
Click to collapse
So I do have LinkeageOS 16 installed now, but every restart, I can't mount /data in TWRP, I have to wipe it over and over. Why is that?
Another thing is that phone doesnt detect my SIM card (on stock recovery it did detect).
iirc that's something to do with encryption, but I've never experienced it so can't be sure.
Can you tried a stock Odin flash since installing Lineage?
Are you using the most recent TWRP?
Droiderat said:
Are you using the most recent TWRP?
Click to expand...
Click to collapse
I flashed newest stock ROM and updated twrp and everything seems to be working now
Weird, I didn't have to reflash LOS.
But yeah, I will write here if the problem still persists later.