Related
Hey there!
I'm hoping that someone can help me out. My nephew who's a wanna-be geek was going to update my ROM (which didn't to be done really, but he wanted to show me what he was able to do). He went and downloaded the latest CM 11, rebooted and went into TWRP 2.7.0.1, did a factory reset, an advanced wipe, and did the Format Data. When he did that, it got stuck in a loop. Nothing happened. He tried to install the ROM he downloaded, and NOTHING! Long story short, by him doing the Format Data, he wiped out my partitions. TWRP, no matter what I try to do tells me it's unable to mount 'data' or 'media' etc. etc. Which is leading me to believe I have no partitions left. I've tried installing the latest update from Asus, and no dice. I've tried restoring backups that I have on my micro SD, and that's not working.
Can someone please help me and tell me how to fix this? Can I get my partitions back? I'm really hoping that I don't have to send this tablet off to Asus in Dallas, TX to have it repaired.
I'm using a loaner tablet from a rental store, hoping I can get my TF 300 fixed.
Any help is deeply and sincerely appreciated.
Omega
Sent from my SM-P600 using Tapatalk
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Duchman said:
I was about to suggest you look in the correct forum, but I see you posted there as well. Anyway, your partitions are probably okay, they have just been wiped out, that doesn't mean you lost them. Have you tried reflashing the recovery? Were you able to flash anything with said recovery before that? Wiping the partitions in the recovery shouldn't have any effect on the flashing functionality, no matter which partitions were selected (except for sdcard, since that's where the ZIPs are stored), so there might be a problem with the recovery itself. Are you sure you have the correct one for your device?
Click to expand...
Click to collapse
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Omega Recon said:
Hey there Duchman ...
Thanks for your reply. I have tried reflashing the recovery like you suggested. And after that tried to reinstall CM11.Afterwards reflashing the recovery it says “Unable to mount data." I don't know if I need to flash a more recent version of TWRP, if that would even help.
Before all of this happened I could flash almost any ROM of my choice as long as it was KitKat supported. All of my backups and restores are kept on my micro SD so they aren't accidentally deleted. As far as I know it's the correct version of TWRP. It's worked for me so far, ever since I updated to KitKat.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
You could try flashing a newer recovery first, I think 2.7.1.0 is available for your device. Also try doing a hard reset by cold booting - here's a how-to: https://www.youtube.com/watch?v=oTU38Ewh8qo (wipe the cache afterwards)
If that doesn't help, reverting to stock is probably your best option. Try this: http://forum.xda-developers.com/showthread.php?t=1757077 (be sure to grab the correct firmware and back up your files)
Have you tried installing any other custom ROM? Does it give you the same error when you try to restore your backup?
Here's what I've come across so far. I did the reset, and that did nothing.
Tried to flash the stock version, after a few seconds, TWRP popped up with FAILED.
I've tried flashing Omni ROM. It will flash, load up, and gets stuck at the boot screen or boot animation. This happens with just about every ROM I try to flash.
Been looking for TWRP 2.7.1.0. I'm not seeing it listed on TWRPs site. Where can I get a copy? Thanks!
Sent from my SM-P600 using Tapatalk
Here you go: http://forum.xda-developers.com/showthread.php?t=2772093
Also do try flashing another recovery, PhilZ for instance: http://forum.xda-developers.com/showthread.php?t=2597860
Did you try wiping all of the partitions again?
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Morthawt said:
I have been having a persistent issue trying to encrypt my phone's internal storage. (Samsung Galaxy S4 mini LTE (GT-I9195). I thought it might be related to me rooting the device, since I read that you can't encrypt a rooted phone.
So a few minutes ago I plucked up the courage to follow the tutorial to flash my original downloaded firmware to the phone, in an attempt to erase all trace of root. Well the phone came up and wanted my password, so I rebooted and installed TWRP via odin again, then did a factory reset and then used the wipe data option and proceeded to make a backup, assuming this would be as useful and as good as odin-flashing my original firmware back for future use and more convenient and less dangerous than using odin.
Well, after booting it up, going through the setup wizard and then adding a lockscreen password, I am still unable to encrypt the phone. It shows the green android robot, screen fades out, then very soon after that the phone reboots and it all comes back up as normal unencrypted. Bare in mind that this is still the stock firmware that was odin-flashed and then a factory reset.
After all this, what would I need to do to get the phone encryption working?
Also, is my assumption correct, that the new TWRP backup I made, after flashing the original firmware via odin, is that new fresh backup as good as flashing the original again via odin? At least in terms of the OS status? I know the recovery isn't changed by such a backup and odin wipes absolutely everything, but I think you know what I am asking.
Click to expand...
Click to collapse
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
LS.xD said:
ODIN doesn't wipe everything. Perform a factory reset via stock recovery immediately after flashing the firmware via ODIN to set your phone back to stock. And who told you that enryption doesn't work with rooted phones?!
Click to expand...
Click to collapse
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Morthawt said:
I did a factory reset and deleted data and performed a new backup that I have saved to the computer.
But when I started to realise I could not encrypt I went googling and found a blog post by someone who claimed that he had to jump through all kinds of hoops to get it to encrypt after he rooted his S4 mini. But my problem is even non-rooted on default firmware with TWRP recovery installed I cannot encrypt So I am hoping someone here will have the answer.
Click to expand...
Click to collapse
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
LS.xD said:
The point is that that KNOX detects the TWRP recovery. Enryption is possible with any rooted custom rom and probably with any roms but Samsung's S4 generation and newer due to the stupid KNOX security.
Click to expand...
Click to collapse
Well I did get encryption working one time on a custom rom but I have no idea how I did it. What should I do to improve my chances of getting encryption working? I thought when I rooted the original rom it removed knoxx?
So, I know that OTA will fail since I am rooted. I am on a Sprint S6 with OC9. I rooted using the T-Mobile Auto-Root.
I see that OCF was published for Odin to flash back to stock. My question revolves around the recommended procedure for flashing with stock. I use Titanium Backup. If I backup, then flash OCF, will this also erase all data on the phone to the point where I have to restore all backups and customize the phone all over again? There's just some things Titanium can't restore well. Or is there a way to update the ROM without wiping everything (dirty flash)?
Given the phone has built-in storage and no microSD, does the storage partition ever get wiped unless I do it manually?
Also, is there any sort of change log for the stock ROM versions? Or do they seem to be just modem updates at this point?
I don't know much about this phone yet since I just got it but coming from a nexus 5 flashing a ROM would keep your data but in this case since it is a system image you will probably lose everything in your storage
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
First of all, I'm impressed that you have done as much as you have (or even wanted to for that matter) at 82. Most older people I know (I'm 42 btw)barely know how to use there phones in the os, much less know what recovery is, lol.
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
BarrySamuels said:
First I have an admission - I'm 82 so my memory is not as good as it was. I have been using smartphones for some years now including flashing recoveries and operating systems. This time, however, I have got myself into a real mess.
I have a OnePlus 6 and just recently there was an OxygenOS update from OnePlus which I installed in the normal OTA way. It was only a little later that I realised that I'd updated from Oreo (8.1) to Pie (9) and there was not a version of Xposed for Pie. I want Xposed so I decided that I wanted to downgrade to Oreo. It didn't occur to me that it would be any more difficult than re-flashing the previous version of OxygenOS. I now realise it isn't that easy or, at least, it doesn't appear to be.
Having flashed Oreo the phone wouldn't boot. It got as far as the boot animation and stayed there. I thought the best thing then would be to try and get back to Pie so I reflashed that. At least the phone now booted but I soon realised that some things weren't right. For example if I turn on wifi it turns off again after about two seconds so I can't use wifi at all.
I'm not sure what to do now. I do have a TWRP backup for both Pie and the previous Oreo. Would it be possible to restore one of those (preferable Oreo)? I'm a bit nervous about trying that as I'm not sure how much wiping/restore I'd need to do. There is the Vendor partition (I've not seen that before) and I would be very nervous about wiping and restoring the boot partition which now, I believe, contains the recovery.
I hoping that some kind person will offer some advice to put me on the road to recovery (No pun intended).
Click to expand...
Click to collapse
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
b.huss2 said:
Anyway, I'm pretty sure I've read that with you go backwards to Oreo from pie, you need to do a full wipe including storage. Did you do that?
Click to expand...
Click to collapse
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
MrSteelX said:
grab this file. http://oxygenos.oneplus.net.s3.amazonaws.com/OnePlus6Oxygen_22_OTA_007_all_1805131952_O_MR1.zip flash that to be back on Oreo 5.1.5. this is the special roll back firmware.
also, this will wipe all data as well as internal storage. just putting that out there so you know before doing it.
Click to expand...
Click to collapse
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
BarrySamuels said:
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
b.huss2 said:
I would think that should get you back to where you were. I have not personally been through these specific steps, but seems logical. It's def worth a try.
Click to expand...
Click to collapse
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
MrSteelX said:
going from oreo to pie, no data loss.
going from pie to oreo, data loss.
that is how it is done. after coming back to 5.1.5 then you can go to 5.1.11
Click to expand...
Click to collapse
I think that's kind of understood at this point. However, I see no problem with restoring a Oreo backup once he's back on Oreo.
BarrySamuels said:
No, it was something I was trying to avoid. I was working on the assumption that as going from Oreo to Pie didn't involve any loss of data/internal storage then going from Pie to Oreo wouldn't either.
As I said above I was trying to avoid wiping data/internal storage but if that is the only way then I'll have to do it. I do have a backup of my internal storage so I can replace that easily enough. Would my Oreo backup be of any use after the wipe to restore my original data setup? That version of OxygenOS was 5.1.11 so could I get back to that?
I thank you both for your very timely help.
P.S. Can you see anything wrong with this plan?
1. Flash the roll back firmware.
2. Install TWRP using Fastboot
3. Flash, using TWRP, OxygenOS v5.1.11 over the roll back firmware
4. Restore 'data' from my previous TWRP backup.
5. Restore internal storage from backup.
Click to expand...
Click to collapse
Almost. You are missing one thing.
1. Flash the roll back firmware
2. Install TWRP using fastboot
3. Flash, using TWRP, OxygenOS 5.1.11
4. Before rebooting, FLASH TWRP IN TWRP (This is important, as flashing 5.1.11 will overwrite recovery)
5. Use your TWRP backup
6. Do what you need for files you want on internal storage.
Don't forget to flash TWRP after you update to 5.1.11.
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
BarrySamuels said:
Not having much luck. I flashed the roll back firmware, and twrp, then rebooted but I got the boot animation again and it wouldn't go any further. I re-downloaded the firmware again, in case there was any corruption, and re-flashed it without flashing twrp but got as far as the boot animation again but no further.
Whilst in TWRP I used the file manager to look at internal storage and nothing had been wiped from that.
I'm not sure what to do now so any suggestions would be very welcome.
Click to expand...
Click to collapse
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Use the fastboot ROM recovery. It works (I've used it twice) no data wipe.
chazey2 said:
Fastboot working correctly - try flashing the fastboot Rom. Hopefully that will put you back to square one where you start over. Complete wipe though!
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
BarrySamuels said:
That does sound rather hairy especially as I don't know which one I'd need to use. It does mention that it should not be used to upgrade or downgrade and I'm not sure that I, or my phone, knows which version is currently installed.
ADDENDUM:
I decided to try one more thing of my own. I wiped data and re-flashed the Pie version of OxygenOS then rebooted.
:laugh: It booted and seemed to be working properly i.e. I could use wifi and the time doesn't keep being lost.
I have now installed Blu Spark TWRP and restored my 'data' backup and I am now back to where I was before all this started. It isn't really where I want to be because I have no Xposed but it is significantly better than a non-booting phone. I'll just have to wait for a new version of Xposed (if such ever appears).
I really don't know why those other suggestions didn't work.
Very many thanks to all those who offered support; it certainly does give a morale boost.
Click to expand...
Click to collapse
Your welcome good luck
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?
bregaryevich said:
Hi everyone! Before I describe my problem, I need you to know that I'm somewhat a noob when it comes to resolving and tinkering with software on Androids, but have some basic knowledge. I've look into all options and posting here is my last resort, please be patient
So recently, a customer brought in a J320FN. It is running on an older update (J320FNXXU0APH1, August 2016), and a few days back, after updating it to the lastest version the phone seized up. The owner has pictures and contacts that he really want to recover. After surfing through some forums, I saw that some phones, when being flashed with stock ROM via Odin, don't lose personal data, and some do. Before I try to flash this device, I want to make sure I can flash the stock ROM and eventually save the data.
I've tried wiping cache partition, because that's what I usually do when encountering software issues.
Also, the phone boots to the point where I can see the current time, and swipe down the notification bar. After some seconds, the phone reboots and the whole thing just goes on.
So my questions are;
1. Do I flash the latest version of Android or just reflash the current one?
2. Do I lose personal data, such as photos, videos and contacts?
3. Is there anything else I can do, before flashing fresh ROM on the device ?
Click to expand...
Click to collapse
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When it comes to flashing Samsung devices via Odin and whether or not the user data is erased or not, it depends on whether you are flashing a firmware that has an upgraded or downgraded bootloader.
The user data only gets wiped if you flash a firmware that has a bootloader that is older than the one currently installed on the device or if the bootloader is newer than the one currently on the device.
The user data does not get wiped if you flash the exact same firmware that is currently installed on the device, or at least, a firmware that has the exact same version of bootloader as the one currently installed on the device.
So you basically have 2 questions to answer.
1) does the firmware that I want to flash have an upgraded bootloader version compared to the bootloader version that is currently installed on the device?
2) does the firmware that I want to flash have a downgraded bootloader version compared to the bootloader version that is currently installed on the device?
If the answer to either of these two questions is no, then you can flash without it wiping the user data.
If the answer to either of these two questions is yes, then the user WILL be wiped during flashing.
If you want to try to save the user data before flashing the firmware, you can try finding a version of TWRP for J320N and flash it on the device then use the backup feature in TWRP to create a full backup of all data on the device. Then flash the firmware of uour choice via Odin, then the data can be extracted from the backup that was created via TWRP and restored on the device after flashing the firmware.
Click to expand...
Click to collapse
Hey, thanks for the quick response.
I tried what you recommended but the problem still persists. After flashing the current version, the phone did the exact same thing and started looping.
Also tried TWRP but there's an FRP lock, preventing me from flashing it.
Now that the stock rom flash thing failed, guess there's only TWRP left. I did FRP unlocks before, but not on phones that are soft bricked. Is there anyway around it except wiping all data?
I may have forgot to mention, that the phone indeed has a passcode. And god knows what did the owner install/do with the device, that made ot to seize up.