[Q] Device won't boot - Nexus 4 Q&A, Help & Troubleshooting

I tried to flash a custom Rom I had tried to build and it didn't work. I thought it might work, though, if I formated system, data, cache, (everything except internal storage). Then this time I couldn't flash the ROM, couldn't work my previous backupe and could make another rom boot, because even if I flashed any ROM it would be stuck at that Nexus Logo.
I'd like to know how to recover my internal storage data so I can flash stock image, as it erases everything. I tried to use ADB to pull my data from the phone but it didn't recognize my device, which was already "bricked" by the time. What can I do? Can I make my backup work or is there a way I can recover my data to flash the stock image?

Xintorrim said:
I tried to flash a custom Rom I had tried to build and it didn't work. I thought it might work, though, if I formated system, data, cache, (everything except internal storage). Then this time I couldn't flash the ROM, couldn't work my previous backupe and could make another rom boot, because even if I flashed any ROM it would be stuck at that Nexus Logo.
I'd like to know how to recover my internal storage data so I can flash stock image, as it erases everything. I tried to use ADB to pull my data from the phone but it didn't recognize my device, which was already "bricked" by the time. What can I do? Can I make my backup work or is there a way I can recover my data to flash the stock image?
Click to expand...
Click to collapse
[EDIT] Nevermind, problem solved.

Related

Partition damage? Not sure whats wrong...

Hey all,
I have an S4 i337m model. I've installed a custom ROM that is essentially a rooted stock ROM (I do not remember the exact build/version of the ROM). I realize having this info would be useful, but at the moment, I cannot access this info.
While running this ROM, everything was fine. Last week Friday, I attempted to install FoxHound 1.6. Had to play around with the installation options, but I got FoxHound to work. However, I need to get back on my old ROM as I needed some files that were deleted during the FoxHound install. So I wiped my phone, and restored my nandroid backup of my rooted stock ROM. again, everything was fine. No issues.
Here is where the problem is; after restoring my rooted stock ROM, I could boot into the phone and access the files needed. However, when I reboot/shut down phone, upon restarting/powering up, my phone is stuck at the 'Samsung Galaxy S4' logo right after power on. So, I boot into recovery (the latest version of TWRP) and I navigate to 'file manager' to take a look at my storage/files. And this is where I believe the issue to be; I see virtually no files at all. I can see many folders/partitions, but there are virtually no files anywhere (i.e. the system and data partitions are empty). I am assuming this is the reason why my phone doesn't boot past the Samsung Galaxy S4 logo. Now, when this happens, I wipe my phone again and restore my working nandroid backup. Everything works fine. I can get back into Android without issues. Until I reboot/power off my phone. Then this happens all over again.
I believe I may have damaged(?) the partition(s). When I installed FoxHound, I also installed an option during installation titled 'EXT4'. I know linux uses ext2/3/4 partition tables. Did I damage my storage/partition by installing EXT4 from FoxHound? Do I need to repartition my phone via Odin PIT file or something similar? Am I totally wrong with my analysis? Any help/advise/insight would be very welcomed.
Thanks
Additional info
Baseband: I337MVLUAMG1
Build number: JDQ39.I337MVLUAMG1
ROM: Rooted stock ROM 4.2.2 (with some bloatware removed)
While my phone was in the it's 'logo stuck' state, I entered into TWRP and selected the Wipe option, then Format Data. I must select 'Format Data' in order for my phone to work on it's next boot. Manually formatting System, Data, etc... will not allow my phone to boot up at next boot. And, my phone will only work on the next boot. If I power off/restart phone, it will get stuck at the logo again. So my phone is only good for 1 boot up after a wipe.
And, after I restore a working backup and boot into the phone, everything works until next power down/reboot. Once I power down/reboot phone, I must go into recovery since it will not boot into Android. When I get into TWRP, I see that my Internal Storage has 0MB free and I am unable to see any files. I can see folders/partitions, but there is nothing in any folder/partition. My external SD card shows nothing as well. My external SD card however is unaffected as all the data is still there once I get into Android and look around.
Also, I just restored a backup I had before I was having this issue. After restoring and rebooting, the same thing happens. I get stuck at the 'Samsung Galaxy S4' logo.
So I'm guessing there is some partition troubles here. Maybe I'm wrong, but I'm scratching my head as to the cause of this problem.
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
jd1639 said:
It could be some hardware issues too. I'd Odin back to stock and see if the problem persists. If it does its hardware.
Click to expand...
Click to collapse
I thought the same thing. I'm downloading the stock ROM now and will give it a try.
One other thing I noticed during my last restore/fix attempt... After I perform a wipe -> Format Data (from TWRP), I notice that it reverts to my rooted stock ROM without me restoring anything. So, after I do a full wipe/format, and reboot my phone immediately after the full wipe/format, my phone will boot into the rooted stock ROM. I thought that wiping/formatting via TWRP totally cleans the internal storage of all data. So how can I be booting into any ROM after a wipe?
Unless I'm mistaken in my thinking and the full wipe/format option in TWRP just reverts back to the stock ROM I had installed prior to installing further custom ROMs?
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Do not format data in twrp.
jd1639 said:
If you wipe system and data there shouldn't be any rom it would boot. Don't try that though unless you have a nandroid because it shouldn't boot
What version of twrp ate you using?
Click to expand...
Click to collapse
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
xBeerdroiDx said:
Do not format data in twrp.
Click to expand...
Click to collapse
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Talabis said:
I hear ya... I have several nandroid backups. All work (minus this 'stuck at logo' issue I am having). I am using the newest TWRP version 2.6. It's very strange... after I perform a full wipe, I am able to boot into my rooted stock ROM that I flashed shortly after acquiring the phone. This was a bit over a month ago now. I do not know how this is possible.
Why not?
_____________________________________________________________________
**Should I try using CWM instead?
Click to expand...
Click to collapse
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
jd1639 said:
Use twrp 2.5.0.2 or cwm. The newer twrp has issues.
Click to expand...
Click to collapse
Is TWRP 2.5.0.0 ok to use?
Ok... It's really starting to look like my partition table has been damaged. Every time I flash a new ROM or restore a nandroid backup successfully, and then restart my phone, I get stuck at the S4 logo. Upon starting recovery, my internal storage reads 0MB free. It seems like my partition table is becoming corrupt after a reboot, or it has already been corrupted.
I tried flashing the stock ROM for my phone (I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar is the one I used), but that didn't help at all. After installing this stock ROM, and I go into stock recovery, I get an error: E:failed to mount /data (invalid argument).
This really is looking like a partition problem. Is there some way to re-partition my phone? I remember a PIT file was used to partition my old Galaxy S i9000. Is there a PIT file for the S4 i337m?
I would also like to try CWM but I am having a hard time finding a ODIN flashable version.
I wouldn't mess with a pit file and I haven't seen one anyway. It's sounding more and more like your memory is bad. I'd keep it stock and see if you can get an exchange on the phone under warranty.
Further investigation has lead me to the culprit... sorta. It's my /data partition that is screwing everything up. If I format /data and then reboot, I can get into my phone. But if I reboot again, then my /data partition becomes corrupt and my phone hangs at the S4 logo. And then if I go into recovery, I can see that my internal storage is at 0MB free.
However, after formatting/restoring /data partition and rebooting into android successfully, everything works fine. If I reboot from this point and enter recovery, I am still able to see my /data partition and files. At this point, everything seems to be fine. Once I reboot out of recovery and let the phone boot into Android, I get stuck at the S4 logo and my /data partition screws up/becomes corrupt. It looks like my /data partition is only becoming corrupt after the 1st successful boot into Android. If I enter recovery after the 1st successful android load, I am still able to see all files and partitions. It is only trying to load android after the 1st boot that my /data partition becomes corrupt. Very strange...
So, I can always boot into my phone as long as I format my /data partition prior to loading Android. Anyone experience this before? Any ideas? I realize my memory may be damaged, but I'm leaving that as a last resort possibility since my phone was working fine up until I started installing FoxHound with the EXT4 option as well as installing 1 or 2 of the kernel's FoxHound provides. Namely Adam kernel is the one I tried.
All good... I think/hope
Well, I think I got the problem solved. After toying with this thing all day. It seems like TWRP 2.6 was the problem in some sense. Looks like TWRP 2.6 does not format the /data partition correctly. I had to get restore/install a working ROM, boot into my phone and install ClockworkMod Recovery via ROM Manager. I then used CWM to format /data. Once I did this, and loaded back into my phone, and went through the setup process since /data was formatted, everything was working fine. I just rebooted 5 times and shut down twice and my phone booted back up into android without issue.
So as one user in this thread had mentioned, formatting /data with TWRP 2.6 was the problem.
Hope this helps others avoid a similar issue.
Thanks everyone for all the help. It pointed me in the right direction.
Glad you got it fixed.
I'll be giving these steps a try, having somewhat of the same problem!
i've been having this exact same problem but with TWRP 2.5.0.2 since July. Its been driving me insane and I have not been able to find any one else having this issue until now. I think i might finally try CWM instead as a last measure before I finally give up!
Try TWRP 2.6.3.1 version. It works pretty well even though it's unofficial http://forum.xda-developers.com/showthread.php?t=2262996
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

[Q] Galaxy S4 (....process.media-phone has stopped) Unroot failure! Please Help Devs!

Greetings all,
I have the i9500 S4,
I was running Hassan Rom and everything was fine, yesterday i've tried to boot the OzcanRom, and kept getting the (process.media. and process.phone not working)
The phone was not working, and after multiple tries of rebooting the said rom, i decided ill go unroot it and install the stock official rom (as i need my mobile for work etc...)
What i did is wipe the dalvikcashe and the system files (which i think was wrong) and tried to flash the stock rom via Odin the old simple way.
Everything went fine, when my mobile turned on again, i kept getting the same messages:
(the proccess android.process.media... & the proccess android.process.acore... & the proccess android.process.phone... Unfortunately email has stopped...& the new message Unified Deamon (EUR) has stopped.
The mobile is useless, can't access anything, can't connect to USB media so i can backup the files, can't connect to WIFI as it restarts...
Please help me guys as soon as possible i really need my mobile for my work...
(Preferably without a full wipe, or if necessary offer a backup way for my gallery)
Should i try installing a different stock rom? as i chose one from SamMobile that was the closest to my region...
Perform a factory reset. You can do that from the recovery or from within android. Make sure to backup the files on your internal storage.
Lennyz1988 said:
Perform a factory reset. You can do that from the recovery or from within android. Make sure to backup the files on your internal storage.
Click to expand...
Click to collapse
Thank you for the reply.
I can do that, but i can't backup the files as nothing on the phone is working, pressing the gallery button for example, leads to the (process.media not working) message.
Any other solutions? i don't understand, isn't flashing a stock rom supposed to solve all these issues? should i try flashing another version of the Roms (different region perhaps)?
It does solve it, but you need to factory reset.
What I would do:
- Flash a custom recovery.
- Do the wipe option prepare for new rom.
- Flash stock/custom rom.
That way your internal storage won't be wiped.
Lennyz1988 said:
It does solve it, but you need to factory reset.
What I would do:
- Flash a custom recovery.
- Do the wipe option prepare for new rom.
- Flash stock/custom rom.
That way your internal storage won't be wiped.
Click to expand...
Click to collapse
Great, Got me relieved when you said internal storage won't be wiped.
Thank you for the reply, i don't want to be a pain in the ***, but could you please explain a few things,
What i'm gonna do is, flash a custom recovery (please recommend one that has the wipe for new rom)
Then, Do the wipe option, which wipe option, the recovery i had had only 1 wipe option, how do i know its not the one that's gonna wipe my data)
Finally, ill flash the rom. (Do i need to root my device again then? to flash a custom rom, if yes, im just gonna go with stock rom and let my mobile work for a few days where i need it then root and install a custom rom again)
I really appreciate your help, and your prompt answers.
yzn2612 said:
Great, Got me relieved when you said internal storage won't be wiped.
Thank you for the reply, i don't want to be a pain in the ***, but could you please explain a few things,
What i'm gonna do is, flash a custom recovery (please recommend one that has the wipe for new rom)
Then, Do the wipe option, which wipe option, the recovery i had had only 1 wipe option, how do i know its not the one that's gonna wipe my data)
Finally, ill flash the rom. (Do i need to root my device again then? to flash a custom rom, if yes, im just gonna go with stock rom and let my mobile work for a few days where i need it then root and install a custom rom again)
I really appreciate your help, and your prompt answers.
Click to expand...
Click to collapse
- You can use Philz recovery
- You know the wipe option when you see it. The one that say prepare for new rom. No custom rom will wipe your internal storage. That option is somewhere hidden.
- You don't need to root, just flash.
ps you will lose all your apps. It will not wipe your internal storage.
Lennyz1988 said:
- You can use Philz recovery
- You know the wipe option when you see it. The one that say prepare for new rom. No custom rom will wipe your internal storage. That option is somewhere hidden.
- You don't need to root, just flash.
ps you will lose all your apps. It will not wipe your internal storage.
Click to expand...
Click to collapse
Great, ill try that right now, thanks a bunch:good:

Fix freeze , lags etc.

Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Orangley said:
Hello people my phone getting old i think 1.5 year so far my phone started to freeze having lags getting too hot while browsing. And bootloops started without flashing anything. First bootloop happened 2 weeks ago. Today happened again twice i wiped dalvik cache and everything is fine how can i fix it? I thought rom cause it i flashed stock firmware rooted it and removed bloatware. Still happens lags,freeze,getting too hot and bootloop. Is it lollipop update? I never had this issues with kitkat. How can fix this and keep my alive?
Click to expand...
Click to collapse
Try a full factory reset. Be careful as this will wipe your internal storage.
GDReaper said:
Try a full factory reset. Be careful as this will wipe your internal storage.
Click to expand...
Click to collapse
Thank you for your answer but I did it after flash stock rom via odin. Wiped data / factory reset , cache partition , mounted cache , system , data , wiped dalvik cache..
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
GDReaper said:
Wiping data does not equal a factory reset. Wiping data does just that, wipes user installed apps. But generally leaves the internal storage alone.
A factory reset returns the phone to the settings it came out of the factory with, including a clean internal storage(If you have the stock rom). I heard that changing roms and just wiping data, dalvik and cache will still leave behind some files.
But it could also be untrue.
Click to expand...
Click to collapse
Flashing stock rom is same with factory reset i think clears everything.
I don't know. Haven't flashed stock on this device yet.
But don't most guys recommend doing a wipe before going back to stock?
I dont know i'll try that when i have free time. I did research some guys saying lollipop causing these problems. I'll try wipe before flash stock rom again , if issues keep happen i'll use lates 4.4.2 custom rom. Thank you for your answers i'll report back.
Real reset
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have the PIT file downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Thank you so much i'll try this now.
AndroidInitiate said:
This method will wipe everything, including operating system and efs files. Before you do this:
you must root
Download twrp recovery
Install the recovery using the app from the play store
Boot into recovery mode and have twrp backup everything
save your backup to an SD card and the computer (can't hurt to have two backups)
Doing the above will preserve your phone important data like your imei and efs
in case something goes wrong.
NOW
after you have backed everything up use twrp recovery to wipe data. Have twrp wipe everything except for your SD card (don't won't to lose the backup)
After everything has been obliterated have twrp boot you into download mode.
Download Odin from XDA preferably 3.09 (most stable release) and then grab an official stock firmware from a trusted source. The latest stock firmware should be at least 4.4.2
If you have carriers other than t-mobile you will also need to find a PIT file for partitioning.
When you have all of this open up Odin with your phone connected in download mode and make sure repartitioning, clear efs and nand-erase is checked along with the defaults.
Select pda button and choose your firmware (unzipped tar.md5 format.) Then select repartitioning PIT file button and direct to where you have it downloaded.
now click start (be sure that the Com port is recognized by Odin: will be highlighted in blue or yellow.)
This will take a while depending on your computer.
when it finishes your phone should reboot with a fresh os and filesystem. If you get stuck in a bootloop reboot into recovery mode and do a wipe data and wipe cache. Reboot and your phone should be good as new.
IMPORTANT!!! It is vital you keep your TWRP backups for as long as you have your phone if you lose them and something goes wrong while flashing your phone you will lose important things such as IMEI baseband which will prevent you from connecting to your network and Sim card recognition.
Click to expand...
Click to collapse
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Orangley said:
Odin freeze everytime i put twrp tar.md5 file cant i use philz touch which i use for long time?
Click to expand...
Click to collapse
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
AndroidInitiate said:
Is that another custom recovery?
If so then yes just make sure you have all of your system files and most importantly your efs backed up.
Run odin as administrator if that doesnt work, try using another version of Odin.
Click to expand...
Click to collapse
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Orangley said:
Doesnt work another versions both twrp and odin. I'll keep my custom recovery and try it.
Click to expand...
Click to collapse
What carrier are you using, model number of the phone, etc.
Have you backed everything up? And can you flash the custom recovery through Odin if it fails?
Try it without wiping efs first just to be safe
Look here for your device you will be able to find standalone flash able versions of twrp that should work through odin.
http://twrp.me/Devices/
Using i9500. And i did what you said and works fine thank you! Mods close thread please.

International galaxy Note 3 stuck in boot loop

My international Glalaxy Note 3 just started boot looping. When I turned it on first thing today. Yesterday it was functioning fine.
I removed the battery for 30 seconds still nothing. I booted into recovery, (TWRP) and wiped cache still nothing. So I backed up my phone to an External SDCard, and wiped data still nothing.
So I erased the whole device except recovery, and restored from the backup to try, and retrieve some essential files. Before reinstalling a fresh. The issue is when I go to the internal sdcard on storage it shows as empty with only a TWRP visible. I did get a notification that supersu was not installed. When rebooting the phone after wiping it. But I selected for twrp to install it so it should be there.
I have also tried to recover the data via looking at the backup on my computer but the backup is in a non human readable format.
Any idea how to get the data I need out of the phone or from the backup before I reinstall the OS?
What twrp you are using? Try reflash the twrp recovery to see if the twrp backup still there? Before you wipe did u wipe internal storage too?
Sent from my SM-N930F using Tapatalk
fastfibre said:
My international Glalaxy Note 3 just started boot looping. When I turned it on first thing today. Yesterday it was functioning fine.
I removed the battery for 30 seconds still nothing. I booted into recovery, (TWRP) and wiped cache still nothing. So I backed up my phone to an External SDCard, and wiped data still nothing.
So I erased the whole device except recovery, and restored from the backup to try, and retrieve some essential files. Before reinstalling a fresh. The issue is when I go to the internal sdcard on storage it shows as empty with only a TWRP visible. I did get a notification that supersu was not installed. When rebooting the phone after wiping it. But I selected for twrp to install it so it should be there.
I have also tried to recover the data via looking at the backup on my computer but the backup is in a non human readable format.
Any idea how to get the data I need out of the phone or from the backup before I reinstall the OS?
Click to expand...
Click to collapse
You said you wiped evrything.. So it includes Internal storage too right! And TWRP automatically creates the folder evrytime you boot into it.. If want the data from your External storage, try taking the card out and copy it or use MTP with TWRP. Then flash your fresh Rom.
Sent from my Xiaomi Mi 5 using XDA Labs

file corruption.

hi, i have a sm-t510 with android 9, and im trying to install twrp but everytime i try i get some kind of wierd file corruption. all my files in sdcar are named with random numbers and letters and there is nothing in it. the tablet boot normaly, but i cant install anything or acces any of my normal file. is there anyway to fix that, or does anyone has a data back up i can use for that version XAC-T510XXU2ASK5. thank you.
cwarrow said:
hi, i have a sm-t510 with android 9, and im trying to install twrp but everytime i try i get some kind of wierd file corruption. all my files in sdcar are named with random numbers and letters and there is nothing in it. the tablet boot normaly, but i cant install anything or acces any of my normal file. is there anyway to fix that, or does anyone has a data back up i can use for that version XAC-T510XXU2ASK5. thank you.
Click to expand...
Click to collapse
Didn't read the instructions very carefully, now did you? The very FIRST thing you need to do when booting to TWRP is to FORMAT THE DATA PARTITION. Not wipe, but FORMAT. The data partition is encrypted and TWRP can't read it. That is why everything looks weird. Also, that is why you need to backup any pictures, downloads or anyting else you want to save because formating the partition will erase EVERYTHING and not just system stuff that wiping deletes.
lewmur said:
Didn't read the instructions very carefully, now did you? The very FIRST thing you need to do when booting to TWRP is to FORMAT THE DATA PARTITION. Not wipe, but FORMAT. The data partition is encrypted and TWRP can't read it. That is why everything looks weird. Also, that is why you need to backup any pictures, downloads or anyting else you want to save because formating the partition will erase EVERYTHING and not just system stuff that wiping deletes.
Click to expand...
Click to collapse
I have been rooting phones and tablet for the past 10 years its the first time it happens. Maybe its something new. Thanks for the info. But i already format the data and evwrything disapeared beside a file named twrp. And i cant reatore the data, cause i didnt have twrp to back them up. So if you have another sugestion, i am all ear
cwarrow said:
I have been rooting phones and tablet for the past 10 years its the first time it happens. Maybe its something new. Thanks for the info. But i already format the data and evwrything disapeared beside a file named twrp. And i cant reatore the data, cause i didnt have twrp to back them up. So if you have another sugestion, i am all ear
Click to expand...
Click to collapse
My post pointed out that formatting would erase everything and that you should backup prior to doing it. And there are several other methods of backing up data and apps besides TWRP. Yes, it leaves the data partition blank, but flashing a ROM and gapps will put the directories back. Of course, they will still be empty. If you used a Google Account, then that should have at least backed up your apps and some settings. When you setup a new ROM, it should let you restore them.
BTW, yes it was the first time it happened for most of us. Samsung keeps trying to improve "security" and adding encryption, by default, to the data partition is in all of their new tablets and phones.
lewmur said:
My post pointed out that formatting would erase everything and that you should backup prior to doing it. And there are several other methods of backing up data and apps besides TWRP. Yes, it leaves the data partition blank, but flashing a ROM and gapps will put the directories back. Of course, they will still be empty. If you used a Google Account, then that should have at least backed up your apps and some settings. When you setup a new ROM, it should let you restore them.
BTW, yes it was the first time it happened for most of us. Samsung keeps trying to improve "security" and adding encryption, by default, to the data partition is in all of their new tablets and phones.
Click to expand...
Click to collapse
my point is that i want to keep the stock rom, i was able to install a costum rom no problem after. but it doesnt work with the stock rom
cwarrow said:
my point is that i want to keep the stock rom, i was able to install a costum rom no problem after. but it doesnt work with the stock rom
Click to expand...
Click to collapse
You can't backup a stock ROM with TWRP because it can't handle the encryption. But you can use TWRP to root a stock ROM. In that case you just ignore the wierd internal data and put what you want to flash only on the external SD. IOW, if your reason for flashing TWRP is to use its backup function on a stock, don't bother, it won't work. But if your intent is to ROOT the stock ROM, then go ahead, but DON'T format data. Just put the files needed to root on the external SD and flash from there. You format the data partition in order to flash a custom ROM.
lewmur said:
You can't backup a stock ROM with TWRP because it can't handle the encryption. But you can use TWRP to root a stock ROM. In that case you just ignore the wierd internal data and put what you want to flash only on the external SD. IOW, if your reason for flashing TWRP is to use its backup function on a stock, don't bother, it won't work. But if your intent is to ROOT the stock ROM, then go ahead, but DON'T format data. Just put the files needed to root on the external SD and flash from there.
Click to expand...
Click to collapse
yeah but, i stil have the same problem though, i still cant use my tablette properly. i cant install new games and other app. but anyway i already rooted my stock firmware using magisk. but thanks anyway for the help
its just that i dont like the custom firware we have for it, and the stock firmware is slow af. but ill end up probably falshing a custom firmware anyway. have a good day.

Categories

Resources