Related
Good morning people.
I rooted my Wildfire with this guide
and then I tried to keep a Nandroid backup before flashing CM7
Nandroid backup allways freeze at random .odex files (at 40-45%)
The first time i said "WTF lets continue..."
I wiped the devices data and trying to install CM7... freeze (didnt start the installation)!
Then I tried it with CM6... no luck (freeze at 30-40%)
I formated my SD to FAT32... Tried again... no luck
I changed SD with my wifes (the one that came with wildfire)... Tried again... No luck
I restored a stock ROM via FastBoot
I rooted again
I tried to keep a Nandroid backup.... same s#it...
Can someone help me?
Try a different recovery image.
arco68 said:
Try a different recovery image.
Click to expand...
Click to collapse
You think that is ClockworkMod's fault?
can you point me to a good one?
(my current version is : 3.0.0.6)
Here: http://forum.xda-developers.com/showthread.php?t=1014498
Or here: http://forum.xda-developers.com/showthread.php?t=1112971
arco68 said:
Here: http://forum.xda-developers.com/showthread.php?t=1014498
Or here: http://forum.xda-developers.com/showthread.php?t=1112971
Click to expand...
Click to collapse
3.1.0.2 fixed my problem
thank you very much
Yesterday, I rooted my wildfire and installed my first custom rom, CM7. Today, I noticed the gps bug so I followed the instructions here
But when I tried to restore the nandroid backup of my stock rom from yesterday, I got a md5 mismatch error and then I tried to restore the nandroid backup that I'd created only moments before (backup of CM7 rom) which also failed because of an md5 mismatch.
So both of my nandroid backups won't restore because of an md5 mismatch (I touched neither backup, both were in the clockworkmod folder where they were originally created) and now I've had to load a fresh copy of CM7.
Why is this and how can I restore them?
Have you renamed the folder name of nandroid backup folder (which will be in date and time normally). If yes, then again rename in such a way that there will be no spaces in the folder name. Either remove the spaces or fill them with some characters. It may solve the md5 sum error.
Sent from my HTC Wildfire using XDA App
The backups are stored like this:
E:\clockworkmod\backup\2011-07-11.14.07.01
no spaces anywhere
anything else that could be causing the error?
No idea. Sorry !
Sent from my HTC Wildfire using XDA App
Has anyone else had this problem before?
What I'm more worried about is that both the nandroid backups that I've done so far have this problem and I have a feeling that the 3rd and 4th... will have the same problem.
Should have really checked that the backup worked before installing a new rom, thought nandroid backups were bulletproof!
Solution is here:
http://forum.xda-developers.com/showthread.php?t=714114
Although I *Think* you can directly use Fastboot as well to flash the data.img, boot.img and system.img, without going through the Nandroid Restore Process (Inspite of the Md5 Mismatch error), it's something I have been vying to test personally but still havent been able to do so.
3xeno said:
Solution is here:
http://forum.xda-developers.com/showthread.php?t=714114
Although I *Think* you can directly use Fastboot as well to flash the data.img, boot.img and system.img, without going through the Nandroid Restore Process (Inspite of the Md5 Mismatch error), it's something I have been vying to test personally but still havent been able to do so.
Click to expand...
Click to collapse
Thanks I'll give that a try.
You seem to be very knowledgeable about this sort of stuff!
I've heard of adb and fastboot but how do I use them?
Also, would you know where I could get clockwork recovery v3.1.0.2? I've looked at your referance thread (which is amazing) but that just links to v4.0.0.5 (which is what I'm on now)
fireice7 said:
Thanks I'll give that a try.
You seem to be very knowledgeable about this sort of stuff!
I've heard of adb and fastboot but how do I use them?
Also, would you know where I could get clockwork recovery v3.1.0.2? I've looked at your referance thread (which is amazing) but that just links to v4.0.0.5 (which is what I'm on now)
Click to expand...
Click to collapse
Yes, arco originally had v3.1.0.2 on that thread, which he updated to v4.0.0.5, removing the previous one.
You can get 3.1.0.2 here:
http://www.multiupload.com/UQGXAGLCJ2
A short how-to for using Fastboot is posted here:
http://forum.xda-developers.com/showthread.php?p=14693680
Fastboot is an amazing thing to have, because you can push stuff like Recoveries, Nandroid Backups etc in just 1 step, using your PC, without any hassles. If you dont get what is stated in the thread, ask me, I'll help you out.
If I use fastboot (as in the how to guide) to flash v3.1.0.2, will it just overwrite my current v4.0.0.5 or do I need to remove v4.0.0.5 first. My phone was rooted using unrevoked if that matters.
Also can a nandroid backup of a sense rom be restored in clockwork recovery v3/v4?
Thanks for all your help, you've been great
- You haven't S-OFF'ed using AlphaRev X? In that case, all this stuff isn't applicable to your device, unfortunately. Because, Fastboot needs S-OFF using AlphaRev X.
- You can overwrite Recoveries. You need not remove your old one, it will still work fine. (Even if you use Unrevoked to flash Recoveries)
- As for Nandroid Restores, it doesn't matter if it is a Sense based ROM or not, you should be able to restore it, even on CWMv3/4
No, I didn't use alpharev x, still on hboot 0.80 so I rooted with unrevoked.
So should I run unrevoked again to flash a new recovery?
Yes, and select Custom Recovery from the "File" Menu, and select the New Recovery's .img file. Also, as far as possible, use an older version of Unrevoked to maximize compatibility, like 3.14
I know to use one of the earlier versions thanks to your help here
I really appriciate all your help, now I know how to root, flash new roms and radios and use adb (a little)
Just a follow up for anyone else with the same problem.
The solution in post 6 works and solves the problem. I don't know why nandroid creates separate md5 files and then wants all the md5's in one file when restoring.
You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/
See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.
Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
Give it a bit of time, before you reboot into recovery, if I remember it takes it a little while to perform it. Maybe it will sort your problem though
It really works
feeeeeeeeeeek
CLICK PIC FOR TEAM HOMEPAGE
ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH (Update 03/05/12)
This version of ClockworkMod Recovery is based on version 5.5.0.4 and has the following "perks:"
Touchscreen
Capacitive buttons can select, move up/down, and go back
Download:
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR_Touch_5504_B15_normalfont_DRH.img (NVFLASH)
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR5504_recovery_B15.zip (Flashable Zip)
How to Install:
There are 2 ways to install. Either run the update through the "CWMR5504_recovery_B15.zip" file or use the "CWMR_Touch_5504_B15_normalfont_DRH.img" image if you will be flashing it with NVFLASH.
NVFLASH Command
To flash use the following commands:
Code:
nvflash --bl bootloader.bin --download 9 CWMR_Touch_5504_B15_normalfont_DRH.img
Changelog:
Added DRH logo
Roboto Font
Changed Mount UDB Storage to the /EMMC
Added the option to format the internal sdcard /emmc
Fixed the magic number mismatch issue
Ability to select update from External SDCard or Internal SDCard
Made internal/external partitions clear
Fixed reboot recovery loop
Allowed the /misc partition to be formatted incase you get stuck in a reboot recovery loop
Swap size bug fixed
Kanged commits to fix the UI overlapping the buttons
Removed /misc (fixes hanging at birds)
Switched from stock Viewsonic kernel to Pershoot's
To Do:
Proper reboot into CWM Recovery
More will be added to the list as more bugs are encountered (if any)
How to Perform a Backup
For those wanting to do backup. Here is the step by step on how to get it to work until a proper fix is done (thanks raj...didnt' understand what you were were saying at first):
REMOVE external sd
Boot to CWMR
Go to "mounts and storage" & select "mount /sdcard" (this is what I didn't understand..how internal could be seen as /emmc & /sdcard)
go back to main menu & select "backup and restore"
select "backup to internal sd"
watch backup complete (including .android_secure on the internal sd)
Thanks to AlAbbo for the instructions!
For the people who wonder what this does:
http://www.youtube.com/watch?v=bGKahQaJadQ
Ported to the G-Tablet by Plastikman
-based on CWM from Koush
-Other credits: gweedo767, cennis91, utkanos
-Original Google+ project page here
Reserved for future use.
I think this was a great idea...nice job...
i have clock work 5.0.2.7...something like that...and wen i install ur zip it works....pull battery...gor right cack into recovery...and its not urs anymore...where can i get clockworkmod 5.5.0.4...so then it willl stay on...i guess i need an update of clock work mod recovery...can you help me out...thanks in advance... ;-)
Guys
I am stuck in a recovery boot loop
How do you fix this?
chief1978 said:
Guys
I am stuck in a recovery boot loop
How do you fix this?
Click to expand...
Click to collapse
Fixed with nvflash
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
dony71 said:
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
Click to expand...
Click to collapse
ROM backups need to be backed up and restored with the same version of CWM.
Sent from my ICS powered g-Tablet using XDA Premium.
rmarinella said:
ROM backups need to be backed up and restored with the same version of CWM.
Click to expand...
Click to collapse
Not necessarily.
rajeevvp said:
Not necessarily.
Click to expand...
Click to collapse
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
Click to expand...
Click to collapse
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Click to expand...
Click to collapse
fosser2 said:
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
Click to expand...
Click to collapse
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities with CWM-5.x which only come up when you create a backup in CWM-5.x and then try to restore in one of the older CWM versions. (Going the other way is no problem--ie. CWM-5.x will happily read and restore the backup files created by all the older versions of CWM.):
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
rajeevvp said:
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities when it comes to CWM 5.x.
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
Click to expand...
Click to collapse
What you've stated should be the case. However, I have had issues with compatibility between versions. Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Sent from my HTC Thunderbolt using xda premium.
Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Click to expand...
Click to collapse
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
rmarinella said:
However, I have had issues with compatibility between versions.
Click to expand...
Click to collapse
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
rajeevvp said:
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
Click to expand...
Click to collapse
How confrontational! Sorry, I don't keep logs.
Sent from my HTC Thunderbolt using xda premium.
rmarinella said:
How confrontational! Sorry, I don't keep logs.
Click to expand...
Click to collapse
Nope. Helpful, actually. Meant specifically to help answer questions like this one.
Originally Posted by chief1978 View Post
Guys
I am stuck in a recovery boot loop
How do you fix this?
Fixed with nvflash
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
hungsohlo said:
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
Click to expand...
Click to collapse
What kind of boot loop?
For an ordinary kind of boot loop, simply boot into CWM and do a "wipe data/factory reset".
For a recovery boot loop see this thread.
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
same as the above poster
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
genei.09 said:
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
Click to expand...
Click to collapse
hungsohlo said:
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
Click to expand...
Click to collapse
Both of you have the same problem. You have a 1.1 bootloader, but, this version of CWM has a kernel built to run on a 1.2 bootloader (this is indicated in the thread title, actually).
Use one of the versions of CWM with a 1.1 kernel in it. See this thread.
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
._.
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