Hi guys
Guess what? Yes that's right I have a corrupted efs folder from a bad flash, and my back up has disappeared from my PC. I've searched via Google and directly on xda and am aware that there is a proposed method to rebuild the efs but the tablet needs to allow adb access which I cant do as it wont boot past the boot logo and i apologize now if this has been asked previously and I've missed it. I've had numerous Android devices and flashed custom firmware on them all including this tablet so im not a complete novice when it comes to sorting them out however this time im struggling. So im throwing the following questions out there to see if you can help:
I can enter TWRP and Download mode
A: Does anyone have a backed up EFS that i could flash via recovery (is this possible/allowed due to it being a tablet and not a phone)?
B: Is it possible to force the tablet in its current state to allow ADB access?
Your Help will be gratefully accepted
I have the same problem.
Also been looking for EFS backup file. Flashed several ROM's but every time I have a bootloop.
Can anyone help?
bump.
is anyone able to offer any advice on this otherwise ill be putting the tab in the bin which i dont particually want to do
BUMP
does anyone have a backed up efs i can use??
sefo1979 said:
does anyone have a backed up efs i can use??
Click to expand...
Click to collapse
As far as I know, EFS contains the serial number as well as other device specific info so someone else's EFS might not work. If you can boot into recovery, adb should work then. If not, use Odin to flash the latest @Android-Andi TWRP recovery and then adb should work.
Sent from my SGH-T989
jrc2 said:
As far as I know, EFS contains the serial number as well as other device specific info so someone else's EFS might not work. If you can boot into recovery, adb should work then. If not, use Odin to flash the latest @Android-Andi TWRP recovery and then adb should work.
Sent from my SGH-T989
Click to expand...
Click to collapse
I can get into twrp but have not been able to get adb access, I am aware that there is a way to rebuild the EFS if this can be done(would you be able to provide assistance?) I have tried refreshing both original and custom rooms but all get stuck at the Samsung logo as I belive the boot sequence looks for the EFS info at that stage.
can anyone help??
it would be really helpful if someone could provide:crying: a copy of their backup to see if i am able to revive the tab ???
Related
[Q]
Hi,
I have nexus s GRJ22 Android 2.3.4 I904. I tried rooting it using clockwork and super user but after doing that when i reboot It stays in the google logo. I could find that i was not able to mount system in the clockwork recovery with means that its not having sufficient permissions .
1. Factory reset - not working
2. Tried fixing permissions - not working
3. tried remounting - not working
what i'm possible to do is get into fastboot mode and clockwork recovery mode and in the normal booting it stays at the google logo.
with this i can say i messed up something when i was rooting. and the phone is useless now.
The last option i know now is fastboot flashing of all the images (boot, system, recovery). How to flash everything finally and bring it back to the state which I got from the factory?
I'm looking for if any one has theses images so that I can fastboot flash it and bring it back in an operating condition.
I'm new to android development, android devices and a noob.
Please do ask If you guys need any more info.
I appreciate any answers and thanks for reading my question.
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
suksit said:
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
Click to expand...
Click to collapse
Thanks for the reply.
its not I904 I'm sorry its I9020 which is the model number of the phone.
I tried the link that you had posted already but it stops at getprop function in the script when i do the update and says status 7 error and the update fails because the /system is not mounting.
Kindly suggest me to bring this phone back.
Hmm, I still have the impression that you have the incorrect version of CWM. What is your service provider? As far as I remember, the I9020T and I9020A require a different version of CWM. And also what is the version of CWM installed?
If you've got the I9020T, try installing this one (from kouch's site)
But if you've got the I9020A, you should try the recovery from this guide (Part 3 - Recovery)
Sorry for the delayed response ,
I have the Tmobile carrier and its I9020T. The version of CWR is 3.0.2.4 which is running. As i said before its not monting the /system.
any other options that I have. ?
Please suggest
Thanks for your time..
I got the nandroid for GRJ22 I9020T.
I'm unable to fastboot flash boot boot.img from this ROM.
it says FAILWrite..
also tried to do the same way for system.img it says Invalid Magic Code !
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
rakeshpatil1983 said:
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
Click to expand...
Click to collapse
Glad you made it!
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
rakeshpatil1983 said:
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
Click to expand...
Click to collapse
your phone was never bricked. bricked means itll never ever work again. if your planning on using it later and using it now, then bricked is definitely not the right word to use ;-)
well then its appropriate to say
"It was broken for two days"
nexus S was in locked state...can't able to unlock thorugh "fastboot oem unlock" (FAILED <remote:ERASE FAIL>.. even all drivers were installed properly...if i try to get in to recovery mode there is an exclamtion mark...what it that..??? plzzzz help me with this
I know i should've backed up everything before flashing but whats done is done!
I have tried at least 10 ways to restore IMEI ranging from:
1-Flashing Color OS
2-Flashing Stock ROM
3-Flashing Modem drivers
4-Flashing CM nightly
5-Flashing Old Stock ROM
6-Flashing persist.img
And the list goes on
Can anybody save me please
awsan said:
I know i should've backed up everything before flashing but whats done is done!
I have tried at least 10 ways to restore IMEI ranging from:
1-Flashing Color OS
2-Flashing Stock ROM
3-Flashing Modem drivers
4-Flashing CM nightly
5-Flashing Old Stock ROM
6-Flashing persist.img
And the list goes on
Can anybody save me please
Click to expand...
Click to collapse
Have you a backup of your EFS folder ?? Restore it
Or try another modem
Or try to flash cm12s via fastboot
jamal2367 said:
Have you a backup of your EFS folder ?? Restore it
Or try another modem
Or try to flash cm12s via fastboot
Click to expand...
Click to collapse
Fixed it after 6 hours of trying stuff thanks to this thread:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
And learned a very important thing ~Modem Drivers flashed through recovery never work you always need to use fast boot for them to work
awsan said:
Fixed it after 6 hours of trying stuff thanks to this thread:
http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
And learned a very important thing ~Modem Drivers flashed through recovery never work you always need to use fast boot for them to work
Click to expand...
Click to collapse
Good to See your phone works again ... I have never problems to flash Modems via recovery ...but fastboot are better....
I know this is an old post. But I'm trying to regain my IMEI. I updated my phone to Oxygen and started having problems and I noticed I had no baseband, imei and the phone would constantly reboot. I put in a ticket at OnePlus and the only way they will help ya is if you open your computer up to them for a remote session. I will never buy another devi e from them again!
Anyway.. So this post has given me some hope. From what I'm reading I need to flash these modems through fastboot and not recovery? I can try all these modems to see if I regain my IMEI?
Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.
Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.
Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!
I am new to rooting, and decided to root my Galaxy Note II SGH-i317m a few days ago. I used a method with no adb access...i think. Here's the reference thread, just in case I'm wrong: http://forum.xda-developers.com/showthread.php?t=1980644
I got a bit overenthusiastic, and got TWRP while forgetting to unlock my bootloader first. Now, my phone will only boot into TWRP. All 4 reboot options go back to TWRP. What is the best way to get my phone back to working? I understand that I may have to lose my data. It doesn't matter: my top priority is getting my phone to work again.
Thanks in advance!
EDIT: I'm sorry if this is in the wrong place. I'm new here.
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
EMONESSboy said:
if you can boot into recovery than try to wipe cache and dalwik cache than try to too boot again it may work
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I just tried that, and no change. Just to clarify, the only thing I can boot into at the moment is recovery mode.
I think what I need to do is flash the stock recovery back onto my phone. Is this a possible solution? If so, how should I go about doing it? I currently cannot access download mode.
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
I Can Help
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
[email protected] said:
@phoenix204
im sure i can help you
u sure can boot into recovery mode and that too TWRP?if yes ...,
then install usb and adb drivers for your note 2 search minimals adb and fastboot and universal adb drivers on google and download them install them reply if u did it and i will tell u to unlock your bootloader and flash a rom if necessary
we sure can fix it
just tell me when u r done
Click to expand...
Click to collapse
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Phoenix204 said:
Well, the thing is, my problem isn't with the ROM at all. It's that TWRP does not work with a locked bootloader. So the way I see it, either I need to replace TWRP with something that works with a locked bootloader, or unlock the bootloader. In your opinion, how would replacing the ROM help with my problem?
It's done. It's worth noting that my root method, linked in the OP, doesn't give adb access. I'm not sure if this changes anything.
Also, I discovered that by removing and replacing the battery, my phone can power off. From here I can access download mode. Something that might be useful, especially if the solution involves odin.
Click to expand...
Click to collapse
tried system restore with twrp?
try it first and if ur not sure that it will work just make backup of boot , efs , system and data(if necessary) via twrp to sd card copy the backup to pc via card reader or something and extract the system backup there should be a file named build.prop in system folder edit it and do it like this :
under #additional build properties
ro.adb.secure=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.root_access=1
find the above lines and edit the parameters as i have shown to you use notepad++ to edit the file save it the last line will give ya root access by default and second last will make it debuggable just save it repack and flash with twrp cheers
hit thanks
Alright. Since I can't find another thread like this one, I will assume that I am one of the first to have this problem. Here is what I did.
I used samsung-firmware.org to find the latest firmware for my phone, which includes both ROM and recovery. Other brands probably also have a website like this.
I used Odin to flash the firmware onto my phone - this wiped my data, but removed TWRP, which is an acceptable solution to me. I might also have wiped my data while playing around with TWRP trying to fix my phone - I'm not sure.
Thanks to both EMONESSboy and [email protected] for their help. I ended up going with something similar to EMONESSboy's solution, since the commands seemed a little risky. Thanks anyways, your help is much appreciated!
IRIS Fuel50
EMONESSboy said:
i think u should install your current rom again if u insall stock recovery you may not able to do this with stock recovery even cant get twrp back
so..do a nandroid backup and install a rom which u like stock1 or custom1
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
mzn.facebook said:
Same problem with my lava iris Fuel50. My phone is stuck up. I am able to get recovery menu using volume + power button.
Pl advice what to do now ?
Click to expand...
Click to collapse
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Kingaroot
Phoenix204 said:
If your situation is the same as mine was, I would recommend the same solution. Just to clarify - you rooted your phone? And then you installed a custom recovery, which is now the only thing you can access?
If so, you should install your stock ROM the same way you installed the rooted ROM. I'm not sure how you would go about doing that, or even if you can access that mode, since your model is not very common.
Click to expand...
Click to collapse
Actually, what happend was that i tried to root my phone through Kingaroot. It shows some error at 90%. After few seconds my phone gets rebooted and snce then, it is showing Mfr LOGO only.
I have tried Factory reset, wipe cache partition etc.
I had lollipop earlier on my phone.
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.