[Q] TWRP 2.6.3.0 Not possible to restore efs backup. What now? - Galaxy Note 3 Q&A, Help & Troubleshooting

Hello community,
i made a backup with TWRP 2.6.3.0 of my new Note 3 Qualcomm device cause i wanted to test some custom roms. After that i decided to roll back but it isnt possible to restore my backup, even when i check md5 verifying.
So i downloaded the newer release 2.6.3.7. The Restoring this time worked well but my efs folder wasnt restored. U cant check the efs backup which i made with 2.6.3.0 cause the efs backup wont show up.
So now i have a not fully working device which reboots every 30 seconds. My LED touchlights are off and without function.
Guys i dunno how to fix that. Any suggestions?
Max 1

Max One said:
Hello community,
i made a backup with TWRP 2.6.3.0 of my new Note 3 Qualcomm device cause i wanted to test some custom roms. After that i decided to roll back but it isnt possible to restore my backup, even when i check md5 verifying.
So i downloaded the newer release 2.6.3.7. The Restoring this time worked well but my efs folder wasnt restored. U cant check the efs backup which i made with 2.6.3.0 cause the efs backup wont show up.
So now i have a not fully working device which reboots every 30 seconds. My LED touchlights are off and without function.
Guys i dunno how to fix that. Any suggestions?
Max 1
Click to expand...
Click to collapse
I didn't even have 2.6.3.0 out for the international I believe. What file did you flash?

bigbiff said:
I didn't even have 2.6.3.0 out for the international I believe. What file did you flash?
Click to expand...
Click to collapse
I flashed it from this site. Its for the international N9005. http://www.techerrata.com/browse/twrp2/hlte
Flashed with openrecovery-twrp-2.6.3.0-hlte.img.tar restored successfully with openrecovery-twrp-2.6.3.7-hlte.img.tar but it cant restore my efs backup.

possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot

37_ said:
possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot
Click to expand...
Click to collapse
Thx 37_, i will try it but im no sure if im able to do it. I´ll try it before im asking again. Are you sure about 2.6.3.2, there isnt 2.6.3.2 for my device n9005 international? Which one should i use instead?

Max One said:
Thx 37_, i will try it but im no sure if im able to do it. I´ll try it before im asking again. Are you sure about 2.6.3.2, there isnt 2.6.3.2 for my device n9005 international? Which one should i use instead?
Click to expand...
Click to collapse
2.6.3.7 is the latest. I am not sure about the EFS issues, but I know the 2.6.3.7 works fine with EFS for qualcomm. I have read formatting like the previous poster fixes EFS issues. You might also need to odin system/boot/cache/recovery and start over.

bigbiff said:
2.6.3.7 is the latest. I am not sure about the EFS issues, but I know the 2.6.3.7 works fine with EFS for qualcomm. I have read formatting like the previous poster fixes EFS issues. You might also need to odin system/boot/cache/recovery and start over.
Click to expand...
Click to collapse
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
bigbiff said:
...You might also need to odin system/boot/cache/recovery and start over.
Click to expand...
Click to collapse
What do u mean with this sentence. How to do this?

Max One said:
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
What do u mean with this sentence. How to do this?
Click to expand...
Click to collapse
You need to download the firmware from Sammobile and flash it with odin.

Max One said:
I believe u that EFS works fine with 2.6.3.7. My Problem is i cant see the backup file "efs" which i made with 2.6.3.0 in the latest 2.6.3.7. So it isnt possible to restore the backup file.
I tried the possible solution but somehow i get
List of devices attached
66ee6420 offline.
all the time.
I think im to noob for adb stuff. I think i need a step by step tutorial. Sry for my noobieness
Click to expand...
Click to collapse
You need to enable developer mode by hitting Build number in Settings>About, a few times (around 10) this will allow developer options in settings. Go to dev options in settings and enable USB Debugging.
If you have the latest ADB drivers installed on your PC you should be able to connect, It will ask on your phone to allow the PC to use ADB.... Click allow or yes...
You should now be detected instead of "offline"...
Now do what you need to do...

And maybe try installing latest adb version 1.0.31 to avoid the "offline" message.
Sent from my SM-N9005 using Tapatalk

ultramag69 said:
You need to enable developer mode by hitting Build number in Settings>About, a few times (around 10) this will allow developer options in settings. Go to dev options in settings and enable USB Debugging.
If you have the latest ADB drivers installed on your PC you should be able to connect, It will ask on your phone to allow the PC to use ADB.... Click allow or yes...
You should now be detected instead of "offline"...
Now do what you need to do...
Click to expand...
Click to collapse
I did it as u said, but no chance to make a connection. No popup no nothing. Even the "Samsung Mobile Device MTP" driver fails to install cause my phone keeps rebooting every 30 secs.
CekMTL said:
And maybe try installing latest adb version 1.0.31 to avoid the "offline" message.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
After installing the latest adb version it shows now "unauthorized" instead of offline.
37_ said:
possible solution for you:
Installe TWRP 2.6.3.2 via odin, rebooted to recovery
Do an "adb shell" when phone is in recovery mode to run commands via TWRP
From the ADB shell: wipe the EFS partition with the following command:
mke2fs /dev/block/mmcblk0p12
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p12 /efs
do a Factory Reset, the phone will now recover efs by itself
reboot
Click to expand...
Click to collapse
List of devices attached
66ee6420 unauthorized
I only see this when the device is on. ( I mean in android os)
When i put it in recovery mode/ADB Sideload
I only see this written.. "List of devices attached" and thats all.
So 37_, i would like to follow ur instructions. But the main problem is to make successfull connection.
Am im doing something wrong? Why is it showing now unauthorized instead of offline?

please check my efs folder. i cant restore nv data files, cuz i dont have it..please check my efs folder and let me know whats missing and what can i do please.
i have only emergency calls, not registered in network..

@leo_hacker82 find any solution?

i dont have this device any more, but maybe u can use any cracked box, like z3x or octopus box..this tools work for wipe efs or repair efs..try it
hit thanks if it help

twrp 3.xx is out! go try to restore using the latest version of twrp

techdude18 said:
twrp 3.xx is out! go try to restore using the latest version of twrp
Click to expand...
Click to collapse
But do look at the dates of the posts you are replying to...

Dejan Sathanas said:
But do look at the dates of the posts you are replying to...
Click to expand...
Click to collapse
._.

Related

[Q] Nexus 4 No OS. Only fastboot [SOLVED]

I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
How did you wipe system within CWM?
But since you say you wiped internal partitions too, it seems to me that you wiped your internal emulated sdcard... so I think your only option now is to flash stock images again... Read this: http://forum.xda-developers.com/showthread.php?t=2010312
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Thanks guys. Found a solution.
Flashed TWRP and sideloaded the ROM file. And flashed it.
Earlier the same process with CWM was not successful. Now the phone is loaded with PA ROM!
Thanks guys! and can u point me to the google stock images??
njarun said:
Thanks guys! and can u point me to the google stock images??
Click to expand...
Click to collapse
Glad you solved it
Here are the stock OTA and images from google and mirrored http://forum.xda-developers.com/showthread.php?t=1971169
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
mrjoeltan said:
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
Click to expand...
Click to collapse
wiped /system? have you tried simple re-flashing your ROM from the .zip ?
no worry... download the nexus 4 twrp latest img from their site, and flash it to your N4
what you needed:
twrp img file
some n4 rom
adb and fastboot
instructions:
boot to fastboot, vol key down + powerbutton when n4 is off.
on your comp, , dos/terminal - fastboot flash recovery twrp.img
reboot in recovery
select the adb side load from advanced tab in the twrp.
on your comp - adb sideload rom.zip
everything done....reboot phone.
Sent from my Nexus 4 using xda premium
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
blackcatvn said:
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
Click to expand...
Click to collapse
did you wipe using fastboot erase command? if so, you need to re-format to the android supported file system to access the partitions!
try installing the twrp recovery and perform 'FORMAT DATA' from wipe. then install ROM.
N4 no OS.
njarun said:
I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
Click to expand...
Click to collapse
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Axelben said:
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Click to expand...
Click to collapse
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Same problem but...
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
El Daddy said:
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Click to expand...
Click to collapse
Got it working
Hi, I got it to work. No worries guys
xXDustinoXx said:
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
Click to expand...
Click to collapse
njarun said:
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Click to expand...
Click to collapse
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
nickboy360 said:
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
Click to expand...
Click to collapse
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
njarun said:
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
Click to expand...
Click to collapse
Thanks for asking mate i got it done... :good:

Trying to sideload ROM via TWRP but PC isn't recognizing phone

I am getting a secure booting error. I can boot in TWRP but when I connect to my computer and type ADB devices, none are listed. Everything was working earlier because I just rooted the phone today. I have no backup and am trying to sideload a stock ROM. For reference, I am following this guide for sideloading. When I get to step 7, I get "system cannot find path specified". Thanks for the help.
dc5_alex said:
I am getting a secure booting error. I can boot in TWRP but when I connect to my computer and type ADB devices, none are listed. Everything was working earlier because I just rooted the phone today. I have no backup and am trying to sideload a stock ROM. For reference, I am following this guide for sideloading. When I get to step 7, I get "system cannot find path specified". Thanks for the help.
Click to expand...
Click to collapse
Hey so you have adb setup and set in enviromentals right?
RubbleTea said:
Hey so you have adb setup and set in enviromentals right?
Click to expand...
Click to collapse
hey thanks for the quick reply and yes I do. Here is a timeline of my events: rooted phone, installed TWRP 2.6.3.2. Made backup. Installed mod. Didn't like mod so restored backup. I didn't wipe so this may have been the problem? Now getting the secure booting problem
dc5_alex said:
hey thanks for the quick reply and yes I do. Here is a timeline of my events: rooted phone, installed TWRP 2.6.3.2. Made backup. Installed mod. Didn't like mod so restored backup. I didn't wipe so this may have been the problem? Now getting the secure booting problem
Click to expand...
Click to collapse
Do you till have the backup on there? If so yah prob not wiping did it. If you can just wipe and restore....if not let me know I'll help you sideload a ROM....you should upgrade to 2.6.3.3 after all this too will help if you use any 4.4 Roms and fix slow wipes on a side note

Stuck on Google Logo after a Nand Restore

Sooo heres the breakdown, i was on pure nexus with kylo kernel, i wanted to try benzo, so i made a nand backup of my phone, checked every box, ( Im on Twrp 3.0.0.1) , flashed gapps and AK kernel. Went through the whole set up. Played with it for an hour realized it wasnt for me, so i decided to hop back in twrp and restore my backup.. again rechecked everything i wanted to resotore. system,cache,image, etc. all boxes. and it when it finished it didnt even ask me if i wanted to clear anything or reboot. it just reboot on its own
So now when it boots, i get a google logo and when i hopped in twrp again to see what went wront, it ask for a password that i never even set on Purenexus OR on Benzo, never activated pin, or password or fingerprint on any. Im well aware that these must be removed before backing up roms to avoid these issues, but my problem is i never had it yet Twrp is asking for a password. I hope i dont have to erase my phone can anyone help?
darkenweeknd said:
Sooo heres the breakdown, i was on pure nexus with kylo kernel, i wanted to try benzo, so i made a nand backup of my phone, checked every box, ( Im on Twrp 3.0.0.1) , flashed gapps and AK kernel. Went through the whole set up. Played with it for an hour realized it wasnt for me, so i decided to hop back in twrp and restore my backup.. again rechecked everything i wanted to resotore. system,cache,image, etc. all boxes. and it when it finished it didnt even ask me if i wanted to clear anything or reboot. it just reboot on its own
So now when it boots, i get a google logo and when i hopped in twrp again to see what went wront, it ask for a password that i never even set on Purenexus OR on Benzo, never activated pin, or password or fingerprint on any. Im well aware that these must be removed before backing up roms to avoid these issues, but my problem is i never had it yet Twrp is asking for a password. I hope i dont have to erase my phone can anyone help?
Click to expand...
Click to collapse
When making a backup you shouldn't check every box, only system, data, boot, and vendor are required. So try restoring your backup but only selecting those to restore. It's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
When making a backup you shouldn't check every box, only system, data, boot, and vendor are required. So try restoring your backup but only selecting those to restore. It's all in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
i cant even get into to restore my backup because twrp wont mount.. its asking for a password i never created, i searched around even tried that "default_password" thing no luck.
Good to know about what things to check on twrp tho..
darkenweeknd said:
i cant even get into to restore my backup because twrp wont mount.. its asking for a password i never created, i searched around even tried that "default_password" thing no luck.
Good to know about what things to check on twrp tho..
Click to expand...
Click to collapse
Oh yeah, restoring the system image has screwed things up for you. Flash the MHC19I factory images to get back to a clean slate, then flash TWRP again, then restore your back (only system, data, boot, and vendor). Then you should be fine.
Heisenberg said:
Oh yeah, restoring the system image has screwed things up for you. Flash the MHC19I factory images to get back to a clean slate, then flash TWRP again, then restore your back (only system, data, boot, and vendor). Then you should be fine.
Click to expand...
Click to collapse
i for some reason couldnt get my sdk to work. so i had to use a toolkit, it did the trick. unfortunately i lost everything. but at least now i dont have a paper weight.
Thank you very much!
darkenweeknd said:
i for some reason couldnt get my sdk to work. so i had to use a toolkit, it did the trick. unfortunately i lost everything. but at least now i dont have a paper weight.
Thank you very much!
Click to expand...
Click to collapse
What happened with your SDK? You should really get that sorted out, fastboot is an essential tool.
Heisenberg said:
What happened with your SDK? You should really get that sorted out, fastboot is an essential tool.
Click to expand...
Click to collapse
I agree, for some reason when I try hitting adb devices my serial number doesn't come up, removed all drivers and reinstalled the necessary SDK tools under your guide and it still doesn't want to work.
darkenweeknd said:
I agree, for some reason when I try hitting adb devices my serial number doesn't come up, removed all drivers and reinstalled the necessary SDK tools under your guide and it still doesn't want to work.
Click to expand...
Click to collapse
Do you have usb debugging enabled in Developer Options? Are you booted into Android when trying the "adb devices" command? Adb is much less important anyway, did you try fastboot?
Two things:
1) If you can't get into your android, then ADB won't do anything. You need to use fastboot from the bootloader to flash the system images. Next time, just boot into the bootloader (Power button + Volume Down). That shouldn't have been an issue to get into the bootloader from where you were.
2) Sounds like you don't have the right version of TWRP on your phone (I know this because I did the same thing). Since the build that ended in the letter I appeared, you need to make sure you flash TWRP 3.0.0-1. Otherwise you will be asked for the password to get into TWRP, even if you don't have one.
Just a few notes.
Heisenberg said:
Do you have usb debugging enabled in Developer Options? Are you booted into Android when trying the "adb devices" command? Adb is much less important anyway, did you try fastboot?
Click to expand...
Click to collapse
At the time my phone didn't get passed the Google logo, I should definitely check later tho to see.
dbroer91884 said:
Two things:
1) If you can't get into your android, then ADB won't do anything. You need to use fastboot from the bootloader to flash the system images. Next time, just boot into the bootloader (Power button + Volume Down). That shouldn't have been an issue to get into the bootloader from where you were.
2) Sounds like you don't have the right version of TWRP on your phone (I know this because I did the same thing). Since the build that ended in the letter I appeared, you need to make sure you flash TWRP 3.0.0-1. Otherwise you will be asked for the password to get into TWRP, even if you don't have one.
Just a few notes.
Click to expand...
Click to collapse
My mistake that is the version I had 3.0.0-1
Either way it's all fixed now and good to go, sort of enjoying stock ATM but I know my flashing syndrome will kick in soon ?
darkenweeknd said:
At the time my phone didn't get passed the Google logo, I should definitely check later tho to see.
Click to expand...
Click to collapse
Ok, well adb will only work while booted into Android. Like I said though, fastboot is what you really need to work.
When i flashed twrp 3.0.0-1, I was asked for [default pass]. The only way into twrp like this is to create an actual password, a pin etc, then boot into newly flashed twrp an decrypt it with pin. Then boot back up and remove password. Now you can go back into twrp with out [default_password] prompt. When twrp is created their is an instance where default pass is created, I guess
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!

Stock backup

This backup is b130 stock, once i get update to work i will post stock b140 and b150
The backup contians system,recovery and boot data is empty like a factory restore. I made a debloated backup with root in my other thread its also b130 https://forum.xda-developers.com/android/development/-t3546850
Here is the stock backup you will find guide below which will tell you how to restore it.. You need to download the backup first to proceed https://drive.google.com/file/d/0Bx88t3CJrNjoSkYwZUlHTmEzMW8/view?usp=sharing b1.30
if you do not want to mess with cust skip to step 5
how to backup and restore cust partition
1.load twrp recovery on you phone. then goto your adb folder and hold shift then right click, there will be an option says open command window here click on that, once you have the command window open type adb shell and press enter, then type su
once u have root or aka su, copy and paste this command unless u wanna type itdd if=/dev/block/mmcblk0p23 of=/sdcard/cust.img
2. once the first steps are done now u can pull the cust partition to ur phone by using command adb pull /sdcard/cust.img it will send the backup to ur adb directory.
3. you can verify that it pulled the backup image by going to adb directory where u launched command window from.
4.to restore a stock cust partition links and guide down below flashable in twrp.
5.after the file is downloaded and you have extracted files proceed to next step.
6. goto TWRP\BACKUPS\serial\ replace with your serial number then proceed.
7. once you have done that u can copy to sdcard use usb cord to copy the files over, or wireless what ever method u choose
8. if you are not in twrp recovery yet, boot to twrp now so u can flash the backup. if you did everything right when u goto restore the backup should be listed.
9. now you can restore the back
ps im not responsible if u mess things up or brick you phone do at your own risk.
be nice if someone fixes twrp and ads the ability to backup and restore cust and other partitions.
Im going to try port twrp 6 i think it is first time so may be awhile. if someone else releases a fixed version then were good to go
This is Complete stock cust none modified for b130, if you modified you cust partition by deleting files. k heres flashable twrp with mirror clsA https://www.androidfilehost.com/?fid=745425885120705728and heres a mirror if first link dont work
https://drive.google.com/open?id=0Bx88t3CJrNjoaFNqTE5rbEZuc1E
1. open twrp recovery make sure the flashable zip is on sdcard.
2. click install select the file you put on sdcard swipe let it finish and you are done
Please feel free to ask question if u need help also hit the thanks button if this guide was helpful thank you.
md5 A522D2F7274E4FF0FCCB6CACA8DD4827 use http://onlinemd5.com/ to check the stock.rar
another stock backup hopefully the super su folder is gone https://drive.google.com/open?id=0Bx88t3CJrNjoSVU4SkhlY0x1aVk
I'm sure this will help out some people, you are a good person!
dabadguycr said:
I'm sure this will help out some people, you are a good person!
Click to expand...
Click to collapse
ty
please reupload file, i need the backup
madvane20 said:
I was so happy when I saw you posted this, but the link is broken. Please repost I screwed up installing xposed and now my phone says I have no os installed
Click to expand...
Click to collapse
aedelman24 said:
madvane20 said:
I was so happy when I saw you posted this, but the link is broken. Please repost I screwed up installing xposed and now my phone says I have no os installed
Click to expand...
Click to collapse
k i will let me check google must of glitched my link but its fixed
Click to expand...
Click to collapse
madvane20 said:
aedelman24 said:
k i will let me check google must of glitched my link but its fixed
Click to expand...
Click to collapse
I restored my device using your backup, you made it come back to LIFE!!! Thank you so much, remember guys, DOUBLE CHECK YOUR BACKUP, it can be corrupt always check!
Click to expand...
Click to collapse
aedelman24 said:
madvane20 said:
I restored my device using your backup, you made it come back to LIFE!!! Thank you so much, remember guys, DOUBLE CHECK YOUR BACKUP, it can be corrupt always check!
Click to expand...
Click to collapse
you are welcome make sure to hit the thanks button ty
Click to expand...
Click to collapse
aedelman24 said:
madvane20 said:
I restored my device using your backup, you made it come back to LIFE!!! Thank you so much, remember guys, DOUBLE CHECK YOUR BACKUP, it can be corrupt always check!
Click to expand...
Click to collapse
well even they have corrupt ones my backup is here to save the day lol for those who like to donate if my posts help them i have the donate setup if you want too i dont expect anyone to its optional
Click to expand...
Click to collapse
also post if it works for ya and hit that thanks button
madvane20 said:
restore through twrp its complete stock boot, recovery,system
1 You need to rename a folder which is located here twrp\backups\serial here\ then put on sdcard or upload to phone.
2 restore backup all partitions for full stock or just everything but recovery. I used winrar to compress the back. stock backup https://drive.google.com/file/d/0Bx88t3CJrNjoSkYwZUlHTmEzMW8/view?usp=sharing
Click to expand...
Click to collapse
Great job, @madvane20! Just a suggestion to put the version number in the file name e.g. B130, B140, etc. to help keep it organized, as new versions are released.
Does this stock have all stock partitions including modem, etc?
---------- Post added at 04:42 AM ---------- Previous post was at 04:33 AM ----------
madvane20 said:
also post if it works for ya and hit that thanks button
Click to expand...
Click to collapse
FYI, the rar file has any error when opening it. Can you verify/test it for CRC/checksum and then repost? Thanks!
Does your stock recovery have Cust?
madvane20 said:
restore through twrp its complete stock boot, recovery,system
1 You need to rename a folder which is located here twrp\backups\serial here\ then put on sdcard or upload to phone.
2 restore backup all partitions for full stock or just everything but recovery. I used winrar to compress the back. stock backup https://drive.google.com/file/d/0Bx88t3CJrNjoSkYwZUlHTmEzMW8/view?usp=sharing b1.30
Click to expand...
Click to collapse
dabadguycr said:
Does your stock recovery have Cust?
Click to expand...
Click to collapse
should be all stock recovery and all was my original stock backup only thing different is the formated data partition but that just makes it stock as if u did a factory recovery. it has all stock bloat apps if thats what ur asking bout cust@jilebi if it has errors u might of got corrupt download. someone else posted it fixed their device. for those it worked for please post to let people know that it worked how long it might of took etc. and if u took any extra steps i didnt mention. might of misread or not understood what u were saying bout the crc . thought u were saying it had crc errors when extracting. i will see about get a crc value
If it's a TWRP recovery made using the one and only XT TWRP version we have, it doesn't have the cust partition backup because TWRP doesn't have the option to backup that partition .
dabadguycr said:
Does your stock recovery have Cust?
Click to expand...
Click to collapse
hmm well i dunno if i modded mine or not but i can dump the partiton as a img that can flashed with fastboot while i learn to compile the twrp for out phone or add support for that cust folder. we need someone who only has twrp and rooted to dump there cust partition in adb shell at least for now im not sure if i removed stuff from mine or not i thought it was restored with the system. does it not restore the files deleted in cust partition with my backup if not well yea til we can get someone to dump that partition or do a complete os dump with all partitions i guess it wont be 100% stock but as close as we can get. i didnt think of dumping all partitions til one person who asked for system etc cause i thought twrp was gonna get them all in the backup
madvane20,
How could a backup without the cust partition restore anything to that partition? It's just not possible .
divineBliss said:
madvane20,
How could a backup without the cust partition restore anything to that partition? It's just not possible .
Click to expand...
Click to collapse
if it was in system partition bout mounted virtually as a partition something to that aspect
Nope, cust is a real physical partition.
madvane20 said:
if it was in system partition bout mounted virtually as a partition something to that aspect
Click to expand...
Click to collapse
divineBliss said:
Nope, cust is a real physical partition.
Click to expand...
Click to collapse
i was stating in general im gonna see if i cant add the ability to allow backup of cust in twrp and have someone who hasnt modified it to dump it for us
madvane20 said:
i was stating in general im gonna see if i cant add the ability to allow backup of cust in twrp and have someone who hasnt modified it to dump it for us
Click to expand...
Click to collapse
Good idea, @madvane20! Do you have access to the source code of TWRP for Acend XT, for you to change it to take backup of cust and other partitions?
jilebi said:
Good idea, @madvane20! Do you have access to the source code of TWRP for Acend XT, for you to change it to take backup of cust and other partitions?
Click to expand...
Click to collapse
no however im gonna see if i cant compile twrp 6 if i can

Freezes on Google screen after attempted SU Install from TWRP

Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Dathaeus said:
Ok I am sure I did this before without any problem, but this time, through TWRP on the NRTK, I installed Magisk, no problems, and then went back to install the SU with the zip file in TWRP again and then on the reboot it freezes on the Google startup screen.
I didnt even want to install the SU zip, but when I ran SU after Magisk installed after reboot, SU gave an error, so I decided to install SU from TWRP.
Did I do something wrong there, so I dont repeat the same error next time?
And how do I get out of this locked state?
I've tried wiping all cache to factory reset without deleting internal storage data... I am hoping I dont have to delete and wipe everything and start all over. I did not have a chance to eve install TiB yet.
Click to expand...
Click to collapse
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
v12xke said:
Flash the stock boot.img from the image/rom you were using before this and reboot. You will have to re-root (properly) afterwards, but your phone should boot up. If you use Magisk, you don't need SU, and vice versa. Use only one method to root.
Click to expand...
Click to collapse
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Dathaeus said:
Hmmm ya I prob should have posted that SU error message instead of what I did, douche move.
But how do I flash the boot.img... I have an original copy of it on my PC... can I somehow while in TWRP on the phone connect to my PC via cable and run commands from my PC in CMD and execute that old boot.img flash? Or is there a location in the stock Nexus already I can use? Because there is no file in the root drive after I did the soft wipe.
Click to expand...
Click to collapse
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
Dathaeus said:
P.S. Everything I have done so far has not deleted my whole storage, yet.... not sure if that is necessary at this point bec it seems reflashing the boot.img wipes absolutely everything again? If I have to it is what it is... just painful when this happens before I could get TiB running... unless my Nandroid backup file I have will restore and work after I do this?
Click to expand...
Click to collapse
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
v12xke said:
While in TWRP you have MTP (file transfer) so you can add files to your device. Transfer the boot.img over to your device via MTP and then use TWRP to flash. Just be sure to select flash IMAGE rather than ZIP. Lesson here is when you get back up and running, install fastboot/adb and make sure it is working well and communicating with your PC. Then you can learn how to use it. This would take literally 5 seconds to flash via fastboot (device in bootloader mode).
NO, flashing boot.img will not delete any of your files. It will only write to the boot partition. If using fastboot the command is fastboot flash boot boot.img
Click to expand...
Click to collapse
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Dathaeus said:
Yep I actually had those platform files already, and yes the MTP was active there, I just never tried that before so didnt know it was even a possibility or the right way.
So I tried via flashing my very old boot.img and also the one from
https://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
via TWRP "Install" via image install (not zip) and to the "boot partition"
and no change, same stuck on Google logo screen.
I tried the fastboot command from CMD and it says
< waiting for any device >
and doesnt do anything. I had it on the default TWRP menu screen.... I waited over 20 min although I know it shouldnt take near that long, just in case.
My bootloader is unlocked BTW, I dont want to assume anything here.
Click to expand...
Click to collapse
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
See if this helps.
Sent from my Nexus 5X using Tapatalk
v12xke said:
You need help getting the latest fastboot/adb binaries working on your PC. So many tutorials on how to do this. Ugh.
Click to expand...
Click to collapse
Not sure what you mean... I JUST did all that when I redid my phone completely back to factory etc etc.... just few weeks ago and then again on my new replacement. But just to be sure, I downloaded all those files again today and it didnt make any difference.
Still stuck on the
< waiting for any device >
I have to be missing some other step or something else is wrong here.
FYI not sure if this matters but when phone boots to recovery there's a red error message
"Unable to mount storage"
but it loads to TWRP fine anyways.
SlimSnoopOS said:
Which OS security patch were you running? Flash the system (to the system partition in TWRP) and boot images (again) from the 6P factory image of the same name:
https://developers.google.com/android/images?hl=en
Click to expand...
Click to collapse
Yep thats what I been doing.....
So the CMD command still doesnt work, which I think is weird in itself... and when I try to install from recovery, it goes through the whole process, both boot.img and system.img, but then it freezes on the Google logo again, so no change.
Sorry I am not sure what security patch, I just got this used from eBay, and one thing, not sure if this means anything, it says its a beta version or something and that message came up all the time when I rebooted when the phone was working.
Do I need to suck it up and redo the whole phone again........ :/

Categories

Resources