CAN-L01C02 stuck with seemingly bad backup - Huawei Nova/Nova Plus Questions & Answers

Hello there fellow Huawei Nova users.
Well to keep the story short, I tried updating my firmware to Nougat but I got stuck on a bootloop.
After this failed , I tried to restore my backup. But I keep on getting 'extractTarFork() proces ended with error: 255 on the Data, System and cust Images.
Tried them seperatly, being mounted or unmounted.
Allready tried to update using the volume up button with stock firmware (which all miss the userdata & cust partitions on the ones I found). But gets stuck at 5%.
Also tried flashing update.zip files trough TWRP. (All giving corrupt zip errors)
So I'm kind of stuck on a bootlooping device, with eRecovery, Recovery, an external SD card (with my backup and update.zips on it which I've tried).
Anyone with advice on how to fix this?
Kind Regards
MrMaddTraxx

MrMaddTraxx said:
Hello there fellow Huawei Nova users.
Well to keep the story short, I tried updating my firmware to Nougat but I got stuck on a bootloop.
After this failed , I tried to restore my backup. But I keep on getting 'extractTarFork() proces ended with error: 255 on the Data, System and cust Images.
Tried them seperatly, being mounted or unmounted.
Allready tried to update using the volume up button with stock firmware (which all miss the userdata & cust partitions on the ones I found). But gets stuck at 5%.
Also tried flashing update.zip files trough TWRP. (All giving corrupt zip errors)
So I'm kind of stuck on a bootlooping device, with eRecovery, Recovery, an external SD card (with my backup and update.zips on it which I've tried).
Anyone with advice on how to fix this?
Kind Regards
MrMaddTraxx
Click to expand...
Click to collapse
Welcome, I too have the same problem again with the Huawei nova.
I tried to flash Rom and Rom and Rom but with poor results

MrMaddTraxx said:
Hello there fellow Huawei Nova users.
Well to keep the story short, I tried updating my firmware to Nougat but I got stuck on a bootloop.
After this failed , I tried to restore my backup. But I keep on getting 'extractTarFork() proces ended with error: 255 on the Data, System and cust Images.
Tried them seperatly, being mounted or unmounted.
Allready tried to update using the volume up button with stock firmware (which all miss the userdata & cust partitions on the ones I found). But gets stuck at 5%.
Also tried flashing update.zip files trough TWRP. (All giving corrupt zip errors)
So I'm kind of stuck on a bootlooping device, with eRecovery, Recovery, an external SD card (with my backup and update.zips on it which I've tried).
Anyone with advice on how to fix this?
Kind Regards
MrMaddTraxx
Click to expand...
Click to collapse
I know this guide uses the MLA-L11 variant of the Nova but you should be able to use method 2 for the CAN-L02 variant too if you have the download link for Nougat for your device: http://ministryofsolutions.com/2017/03/huawei-nova-plus-mla-l11-nougat-b313-emui5-europe.html

Related

Help needed! Firmeware CAN-L11 EU Version

Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
merlin21 said:
Hello,
i need help. I messed up my phone while trying to repair my only read mode system partition after boot.
Current state:
Phone CAN-L11 with EU Firmeware and working TWRP Recovery.
I did a full wipe, but have no data partition to restore, because this couldn´t be saved with twrp while i made my first nand backups during no read access to data partition.
My phone always shows 2 times the huawei logo and then boot in erecovery from huawei where i tried to restore, but it shows always "fail to get data" (wifi works).
When i restore all partitions backups that i own via twrp i miss the data partition (is the cause why it wont boot - isn´t it?)
Now i searched for any img that i can use to get my phone working again - anyone has a tip what img i could use (i have a huawei update extractor) - through twrp or fastboot.
Could anyone help me with a twrp backup or a img file of data partition - or has another tip how to get my phone working again?
Thanks for tips!
Click to expand...
Click to collapse
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Here the full Backup for the CAN-L11:
https://drive.google.com/open?id=0B134drJ4-Ed0R3VSY3A5NGpjVWc
Format /data, reboot recovery and than restore from backup. After the restore is complete make a wipe.
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
merlin21 said:
I restored my system from twrp (original first save). But that did not help.
After that i loaded the can-L11c432 update.zip from huawei and extracted with others the system.img - that also did not help to boot.
Tomorrow i flashed the orignal recovery.img from c432 but i did not find an update.zip wich works to manually flash in stock recovery.
@Vinnom the link you shared leads to twrp.img (no system.img).
@-=MoRpH=- thanks, i will try and report back. Is this anyway a chinese version in there? I think i have the same struggle you had days back. Is your phone completely working again?
So sick that my phone did not work. Now working with my "old" LG G2...
I report back later - first family dinner
Click to expand...
Click to collapse
Inside the folder twrp and its subfolders there it is system.img. I'm downloading it myself.
Sent from my victara using XDA Labs
Share if you have another workarounds for me
Gesendet von meinem LG-D802 mit Tapatalk
@merlin21 yes it sounds like my problem after I tried to flash the emui5 beta.
My phone is fully working again with the backup I posted.
This is not the Chinese version, if nothing works, you can try the caz ROM. But there are massive problems with the gapps, they are not included in the rom.
Gesendet von meinem HUAWEI CAN-L11 mit Tapatalk
@ -=MoRpH=-
i just flashed the twrp.img with fastboot from xelfmade v22.12. and then rebooted twrp.
Then formated data and confirmed with yes - rebooted recovery and tried to restore your twrp. It did not restore and aborted instantly with the error message
during restoreing cust...
extractTarFork() proecess ended with ERROR: 255
what could that be?
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
That only work if the is not rooted... Idk whats up with that, but for now i use the quicksetting screenshot function.
Somehow it worked with my rooted device before. Must be the decrypted data partition?
With the recovery of your backup I could not access data or change memory from data to sd. What version do you use?
I flashed xelfmades v22 and now have rw access and could backup all partitions and restore. Root and xposed modules everything works, just the knock on screen to capture don't...
merlin21 said:
IT WORKS! Thanks @murph... I had to use the cust from my backup, but with your data partition it successfully booted again. Locking forward if i now have still the problem with read only system partition. I am away setting up phone again (and of course rooting, modifying etc.. but FIRST do a full backup after basic setup and safe in PC !!!)
Thanks!
P.S. how did you manage to back up data partition in recovery? I thought this wouldn't be possible?! What is the cost for having this full working twrp?
PPS. Somehow knock on screen for screenshot does not work - could be, that i have to log in with huawei id... does it work for you morp?
Click to expand...
Click to collapse
I have the same problem! What do you mean by "I had to use the cust from my backup" ? Sadly i dont have any data from my own backup..
can you tell me what to do to get the backup from @murph to work without error?
--solved.
P1xl said:
--solved.
Click to expand...
Click to collapse
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
rak500 said:
May I ask how?
I'm kinda stuck personnaly. I have tried both Nand backups but no cigar. Still can't boot. I had the Data issue which I managed to get rid of.
I still end up with a ExtTarFork 255 kind of error. I tried to change the files attributes via adb shell, but it failed so I've got an OS-Less phone...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
P1xl said:
I copied the backup, which is linked somewhere in this thread, to my sdcard and restored it on my Nova using twrp. The extractfork issue showed up while restoring '/cust' so i disselected cust in the restoring menu. After that the restoring worked and my nova was able to boot.
Hope this is any help to you.
Click to expand...
Click to collapse
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Thanks for your help my phone is saved with your method!!!
i downgraded my MLA-L03 variant with this, but now im stuck in french language with no other languages to choose from
Vinnom said:
I think that you need a system.img, so you can flash. This system imagem would write everything you need, so you can boot normally.
Have you tried to dowload @bluesmoothie backup from dropbox from the Root and Recovery post?
Here is the link, in case you don't find it https://www.dropbox.com/sh/qrk0fbpn5rnukxn/AAAmhFwBTNoqq0sWfCH-VMHLa?dl=0
Sent from my victara using XDA Labs
Click to expand...
Click to collapse
someone please make this thread sticky!!!!!!!
there are some guides in internet how to get nougat for nova and that is were I broke my phone. I was searching solutions for a week, DLed Flahsed tons of things nothing worked. this one fully worked!!!!!!!!!!!!!!!!!!!!
rak500 said:
That didn't do the trick for a while, or I might have forgotten a step, but deselecting CUST did the trick.
Thanks for the tip!
Although, maybe flashing the Cust partition I found in one of the two upgrade zips via fastboot might have helped? I dunno...
But in short, for those who haven't followed through, here's what I did, but I'm not sure this is why it worked:
1. Bricked my device : be sad;
2. DLed all the posted Nandroid backup on this thread and others;
3. With fastboot, reflashed TWRP from Xelfmade using "fastboot flash recovery twrp.img";
4. Flashed the CUST.img I found in the UPDATE.APP of the update_data_full_CAN-L11_hw_eu.zip; or maybe the other, only one of the two seem to have it; I extracted it using Huawei Firmware Extractor; using "fastboot flash cust cust.img";
5. Created a "fake" backup to create the right folder structure on my SD (TWRP Couldn't see the backups) and put the Nandroid Backups I DLed earlier in it;
6. Reboot in TWRP and Restore all partitions except CUST;
7. Reboot, sweat, wait, cry, roll on the floor in fear, heard the huawei startup sound, cried as if it was my first born child;
8. Setup the fone and profit; then enjoy Nova goodness;
92.324. and probably most important, TWRP BAAAACKUUUUP!!!!!
All done!
Click to expand...
Click to collapse
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Bunkier said:
Hi. First of all, thanks for the tutorial. I've tried it but I have one problem. My /data particion is ext4. Should be f2fs. The thing is I can't convert coz my /data particion is unvisible
Can any help, please?
Click to expand...
Click to collapse
Frankly, I don't know. I had not modified the partitions prior to bricking my phone, so I think the partitioning was OK. However, I think one of the TWRP availble in this forum can format Data partition properly, which would utlimately allow you to select which File Format you want. I haven't tried it myself, and I haven't been able to do much with TWRP since I flashed Lineage unfortunately. Most of my Mods were just upgrading and I had to ADB Sideload pretty much everything since I flashed Lineage...
Sorry I couldn't be more helpful than that!

Can't mount Data Partition.

These last days have been catastrophic for me and my p9 Lite.
A thousand and one operations I have done ... I have had to reinstall everything via fastboot ... (cust, recovery, boot, cache, recovery, recovery2, syste m)
And still, I do not get it to boot ... I still have hopes, because being in Revolution Nougat Recovery B.9 (or something like that) shows me the 3 partitions of the P9 Lite. (CUST, EXTERNAL SD and INTERNAL MEMORY) this last, says to be totally empty ... (0 MB) But when I give wipe - internal memory - repair partition, it tells me that there are 16 gs free.
When I want to change the format, to repair it ... it gives me error. Both F2sF and ExT4 ...
I think it may have been deleted in the internal configuration of the cell, the route to the DATA partition. Because I can not repair it in any way ... it always throws me wrong ...
If you like the challenges, here's a big one.
I have googled the possibility of re writing the path to the data partition via fastboot, I only get examples of Google Nexus 7 (which apparently in nexus 7 if it can be done), but none of P9 Lite.
Later I will upload screenshots about the errors that the revolution recovery throw me ... (if anyone is willing to help)
At the moment, I am without an operating system. I have access to huawei recovery, also to revolution recovery and I also have fastboot access.
In the eRecovery, when I try to download the complete package ... it throws me "error in the package", putting the UPDATE.APP of the B371 in the dload folder, the update goes up to 50% and then I throw "error in the package".
I hope they help me and that together we can find a solution to my problem.
From already thank you very much.
I think the only solution is to flash firmware via dc-phoenix
simo255 said:
I think the only solution is to flash firmware via dc-phoenix
Click to expand...
Click to collapse
Which exactly firmware?
andrexp31 said:
Which exactly firmware?
Click to expand...
Click to collapse
B161 i think, its the better one
I cant... Im on nougat.
andrexp31 said:
I cant... Im on nougat.
Click to expand...
Click to collapse
This is what happened...[ ATTACH]4106037[/ATTACH]
andrexp31 said:
This is what happened...[ ATTACH]4106037[/ATTACH]
Click to expand...
Click to collapse
Sorry,this one is in english
View attachment 4106043
andrexp31 said:
Sorry,this one is in english
Click to expand...
Click to collapse
Try to flash stock recovery and do a factory reset, maybe it will work
Otherwise buy dc; phoenix (it costs 15€ i think) and it will write nougat firmware b370
---------- Post added at 01:35 AM ---------- Previous post was at 01:19 AM ----------
If flashing recovery via fastboot isn't working,
Download whatever version of revolution recovery
Extract it, remove file_context , replace recovery.img by the recovery that you have downloaded,
Archive meta-inf and recovery.img
Flash it through recovery
Hope it will works
I am stuck with a similar issue, but Meticulus TWRO 2.8.7.0:
I get Failed to mount '/data' (Invalid argument) and Unable to open '' to wipe crypto key
I can neither wipe /data, nor format it, nor do anything else with it.
I tried flashing stock ROM and tried factory reset over there: it failed
I went back to stock B160 from CM13, recently.
Somehow I did wipe /system in order to run an update, which did not work.
So I got deeper and deeper into this trouble.
At the moment, there is CM13 without /data und unable to wipe /data in any ways.
I do not have a SD at the moment.
Would it help to put a complete stock onto SD and install it via update mode?
edit:
I could install an old system backup, which did boot and after flashing stock recovery I could factory reset /data
:hurrayy:

Stuck at LG logo after flashing any Kernel

So I'm having a weird issue. Whenever I flash any kernel other then stock it stays stuck at the LG logo. I have to pull battery and then restore the stock kernel backup. I have no idea why I'm having this issue. I've also noticed that TWRP sometimes says cannot mount system (probably not the culprit but just adding more info).
Model: T-Mobile (h918)
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
pistacios said:
When I had the "cannot mount" issue, a system partition format was needed from within TWRP. I took a backup of system (not a system.img backup), then formatted system only, then restored the system. It's been fine ever since.
I'm not sure if any special pocedure is needed for the h918 in order not to brick anything. I'm on US996.
I hope that made sense. Please wait for a second opinion before trying anything.
Click to expand...
Click to collapse
Yea. Seems like I have to format system all the time. Also have to format my internal storage all the time. My backups never seem to restore correctly. I can't flash a new ROM because it wont boot with a different kernel. I might just flash KDZ and root all over again.

[Possibly bricked] "Failed to mount /data" & no internal storage

Hello everyone!
I have a P9 lite VNS-L31 running 7.0.1. on EMUI 5.0.2..
However during a factory wipe, it stopped booting correctly and I can't get passed from neither bootloader nor recovery.
I have TWRP Revolution v.260317 (TWRP 3.1.0-0) installed and my main problem is that for some reason the phone says that I have no internal storage whatsoever and if I try to wipe the /data partition it fails to mount it (error: Failed to mount /data (Invalid argument)).
I tried any of the methods in videos titled "how to fix unable to mount /data" (sorry, I cannot post links :/ ) but with no luck.
I can't seem to repair nor resize nor change file system of the /data partition. When trying to repair data using e2fsck it gives out the message:
" /sbin/e2fsck -fp process ended with ERROR: 16"
Any ideas?
I can use recovery and fastboot if necessary.
Regards
flash this twrp ;
https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
give me a thanks if it works
Exiatron00 said:
flash this twrp ;
https://forum.xda-developers.com/huawei-p9lite/development/twrp-t3588356
give me a thanks if it works
Click to expand...
Click to collapse
Well, more or less, but I managed to solve it!
I found out that the reason why it said there was 0mb of internal storage was because the bootloader that was previously unlocked turned itself locked, that's why it couldn't mount the /data partition. I just used SKR Tool to unlock the bootloader and after that yes, I installed that version of TWRP that you linked.
I also found out that the Revolution TWRP installed in the eRecovery partition (/recovery2 ?) instead of the normal recovery partition. What image is supposed to be installed in that partition?
That is the second recovery partition (another recovery) aka huaweis last ditch attempt to fix a broken phone. There's no actually problem if u don't have it-as most of the time (in my experience) its utter garbage, but there's no harm in flashing it if u want.
U can extract it from ur update.app file using huawei update extractor.
Exiatron00 said:
That is the second recovery partition (another recovery) aka huaweis last ditch attempt to fix a broken phone. There's no actually problem if u don't have it-as most of the time (in my experience) its utter garbage, but there's no harm in flashing it if u want.
U can extract it from ur update.app file using huawei update extractor.
Click to expand...
Click to collapse
Yeah, I tried to install the RECOVERY2.img that I extracted from the UPDATE.app and it didn't work so I just didn't bother and installed the TWRP again.
But at least everything is solved!
Thanks

Galaxy Tab A 8 (SM-T350) stuck on boot loop after trying to recover stock firmware

Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
skorpien said:
Hey folks. I'm hitting a brick wall trying to figure out this issue and I'm hoping someone will know how to fix this.
I have a Galaxy Tab A 8 (SM-T350) that I rooted and successfully flashed with first crDroid, then Lineage (both Android 9.0) using TWRP. I had made a backup before attempting this just in case I wanted to revert to stock.
Well, that didn't go as smoothly as I was hoping. Ever since trying to restore my backup, I've been stuck on a continuous boot loop that I can't seem to fix.
I keep getting "E:failed to mount /efs (Invalid argument)" and "dm-verity verification failed. . ." no matter what I try. I've googled the error and tried every solution suggested but I still can't get it to boot.
Any help at all would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
ashyx said:
Ignore the EFS error its probably a red herring. Your issue is dm-verity.
3 ways around it. Return to complete stock, including wiping the data partition or flash root (magisk suggested) or disable dmverity using one of the zips out there.
Click to expand...
Click to collapse
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
skorpien said:
Thanks for the reply ashyx.
I've done two of the three things you suggested. I've tried returning it to stock using an image matching my exact model, and I've tried disabling dmverity. I've also tried rooting it but using a method other than magisk.
The flash seems to go well enough, but then I get stuck at the Samsung logo whenever I try rebooting into the system.
I've tried waiting, thinking I'm just being impatient, but it doesn't ever seem to get past the logo. I've tried googling ways to fix it being stuck on the logo but nothing I do seems to work. Is there any other way around it?
Side note: I've been able to flash Lineage OS again and might just have to stick with that if I can't flash it back to stock. Do you know any resources for replacing the default apps? I've tried GApps but I was wondering if there's a similar Samsung installer?
Click to expand...
Click to collapse
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
ashyx said:
You need to wipe the data partition, aka factory reset before or after installing the stock firmware then it will take anything up to 15 mins to boot.
Click to expand...
Click to collapse
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
skorpien said:
I've tried leaving it for a few hours in hopes that it would boot, but unfortunately it stays stuck on the logo.
Is there a way to check where or why it's getting hung up?
Click to expand...
Click to collapse
Did you back up the efs partition with twrp?
If so try restoring it.
ashyx said:
Did you back up the efs partition with twrp?
If so try restoring it.
Click to expand...
Click to collapse
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
skorpien said:
I did and I have been restoring it.
So far, this is what I've attempted:
Flash TWRP (twrp_3.1.0-1_sm-t350_18317.tar using Odin3 v3.10)
Reboot into recovery
Wipe everything from tablet
Format tablet
Reboot into download mode
Flash stock image with Odin
Reboot into recovery
Wipe dalvik cache
Restore backup (including efs partition)
Wipe dalvik cache (again)
Reboot
Get stuck on Samsung logo (left it for hours with no change)
Click to expand...
Click to collapse
Don't restore everything just EFS No need to keep wiping dalvik it serves no purpose when formatting or wiping the data partition.
Also FORMAT not wipe the data partition (note this wipes internal storage)
If it still doesn't boot install the combo firmware. Let it boot, factory reset from settings then reboot to download mode and install the stock firmware again.

Categories

Resources