Related
Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
New version 2012-02-01: data wipe and then restore, backup to external and to internal (internal is now the default).
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Ok - first identified issue: If we are backing up to the external sdcard. This is fat32. So we have a file size limitation.
Also there may be a tool set size limitation in the binaries (as ported). This mainly affects "data", as this seems to include
pictures, video etc from the /data/media directories. So looks like to me data > 2G wont restore. Although it does create
(in my example 3.5G file and checksum is ok). I found that the 3.5G would not load. I retarred with all stuff in /data/media
deleted, (and fixed the nandroid checksum) then the data file loads (about 900M) and my device is recovered. I'm expecting if you try to back up more than 4G, the file will not be usable due to FAT32. I Hope this is clear.
So please check your file sizes (and nandroid sums) before attempting a restore.
So with this in mind,
Update: 2012-02-01: now backing up in the CWM tradition by default to the internal sd (which is ext4), and there are extra options enabled in the backup/restore menu. Please remember we are still in test mode. I think It is now working as intended and not backing up /data/media its easy to tell from the size of the data nandroid file.
So please backup your precious videos, pics etc from the /data/media directory independently.
Odin tar file (in the pda):
davp said:
Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Odin tar file (in the pda):
Click to expand...
Click to collapse
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
padebije said:
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
Click to expand...
Click to collapse
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
davp said:
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
Click to expand...
Click to collapse
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Ok guys, looks like there are file size issues due to fat32 external sdcard etc.
I believe the tool can still be useful, but be aware its limitations.
Have documented this in the first post as an issue.
The download is the same (I cant fix the fat32 limits).
padebije said:
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Click to expand...
Click to collapse
I use the one I had installed months ago (for phone). It the same version (downloaded mine from Intratech's gs2 official rom thread).
Sent from my GT-I9100 using XDA App
BRAVOOOOO!!!!!
I deleted all movie files > 2GB, and tried backup, wipe data, and restore again.
This time, I could make it thanks to your advice!
davp & ezy now, looks like you're famous.
http://www.theandroidsoul.com/new-g...or-both-3gwifi-edition-and-wifi-only-edition/
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Hi davp,
You should push source to git hub, perhaps we could enlist Koush or Codeworkx to assist us. of all the options i have tried with recovery.fstab i was never happy.
i could never get both internal and external sd cards to mount. when i had them both setup the menu options for flashing and restore / backup will show option for internal sd cards.
IMHO, recovery should back up to external, as if you really bung up your device you will not have access to internal memory. The fact most of us only have 16gb internal memory its makes more sense to back up to external sd card.
i remember the nook colour, had a simalar debacle when they 1st released CWM mod for it. you could look there. i really havn't had a chance to dig into this. perhaps over the weekend i get more time
davp said:
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Click to expand...
Click to collapse
Any chance somebody could please extract stock recovery and send me a target version?
Sent from my GT-P6810 using XDA Premium App
Tar not target...
Sent from my GT-P6810 using XDA Premium App
Help
Hi Guys,
EDIT: - I flashed an incomplete tar file as the download had not finished when I copied to sd card.
Got a small issues,
I have a Tab 7.7 running HC 3.2.
I gained root access and then install mobile odin pro.
I then proceeded to install this CWM and its not stuck at the galaxy tab 7.7 black and white screen at boot.
I selected the file i downloaded here using the recovery option to flash in mobile odin.
any ideas what i can do to get this working again?
Many Thanks
Syl
Sneakyghost in the General M8 forum wrote a script to "image" all your partitions.
I ran it on mine before updating anything. I forget if it needs S-OFF, Root etc. What ever is required for ADB.
http://forum.xda-developers.com/showthread.php?t=2696826
I would not share your backed partitions though, these would only for the specific phone you imaged. There is a lot of phone specific information in many of the partitions.
This recovery zip copies certain partitions to /cache.
The copied partitions are system-critical ones that aren't available online (thus no kernel, system etc as they can be easily obtained online, and are covered by Nandroid anyway; no bootloader as it's available from stock ROMs, it's not directly writable from the bootloader itself, and it's believed we don't have JTAG access anyway).
A practical application I just experienced is recovering from the "connected as installer" bug if you try to enable mass storage mode and now MTP breaks on every boot; other benefits are restoring MAC addresses (from persist partition) and IMEI (unproven).
Only tested on XT1021. A copy of the partition table (boot into recovery, "adb shell", "parted /dev/block/mmcblk0", "unit kb", "p", copy and paste output, "q", ctrl+D) is enough for me to determine compatibility, however!
Like the tool itself warns, it is to be used along with a file manager or ADB.
XDA:DevDB Information
XT1021 Backup Tool, Tool/Utility for the Moto E
Contributors
Ryccardo
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2015-01-03
Created 2015-01-03
Last Updated 2015-01-03
Not mocking about your work, but how this application work? If I wipe a cache from any ROM, they aren't created automatically?
I'm questioning this because I don't see purpose or use, but I don't know very much about development, maybe could this be the reason, and I have never experienced this kind of troubles that you described.
Anyway, good to hear who are more people people working in our device. :good:
marceloterorist said:
Not mocking about your work, but how this application work? If I wipe a cache from any ROM, they aren't created automatically?
I'm questioning this because I don't see purpose or use, but I don't know very much about development, maybe could this be the reason, and I have never experienced this kind of troubles that you described.
Anyway, good to hear who are more people people working in our device. :good:
Click to expand...
Click to collapse
That it saves in /cache has nothing to do with the semantic meaning of "cache", which was completely removed in 3.x -- it's just a sufficiently large partition with a reasonably constant mountpoint (unlike real or virtual SD cards).
Like every backup, it doesn't have a purpose until you need to restore it, and the partitions treated by this tool are not readily available with a full stock image (some are definitely specific to the exact phone you're holding)!
[How To Root] Huawei P smart - Android 8 - EMUI 8.0.0
The Rooting was tested by me on this device:
Model: FIG-LX1
Board: FIG-L31
Build No.: 8.0.0.128(C432)
EMUI 8 - Android 8
"free device"
Whether the following instructions are based on provider-branding is applicable, I could not test
and therefore advise against it.
Warning: Rooting will void the device warranty. Be careful with the newly acquired root rights.
I recommend this only to users who are fit in handling a custom recovery.
This TWRP is not yet perfect and should be used with caution.
Make sure to backup all data on the SD card. (PC, stick, or HD)
Create a backup with the Huawei Backup App.
Make sure the bootloader is open.
OEM and FRP unlocked,
in the device settings, OEM unlock and USB debugging enabled.
The stock kernel is mandatory.
This is flashed in fast boot mode/ bootloader:
If the device is unroot, it does not need to be done.
fastboot flash kernel kernel.img
(KERNEL.img.header must also be in the adb folder.)
This steps must be followed exactly:
Factoryreset in recovery.
Flashing TWRP in the bootloader: fastboot flash recovery_ramdisk FIGO.img
Boot to TWRP and change the file system of the external SD card:
Wipe> Advanced Wipe> Micro SD card> Repair or Change File System> Change File System> FAT:
Execute with "Swipe to Change".
This change deletes all data on the SD card.
Switch to the Mount menu and unmount all partitions. (remove all hooks)
On the internal and external memory.
Then create a backup:
Backup> Select Storage> Micro SD card> select all partitions,
except cache. Then reboot the device into the system and copy the Magisk Zip to the SD card.
Then install in TWRP: Install> Select Storage> Micro SD card> Magisk-v16(1600).zip> Swipe to confirm Flash.
Is there an error message, installing this Zip via MagiskManager App.
Reboot and if not available, install the MagiskManager App and check the root.
The routing is now complete.
Install Magisk modules only with the app; never with TWRP.
Important:
Never wipe the cache or perform a factoryreset.
[*]Please do not experiment with Xposed. This leads to the bootloop and the Firmware must be completely reinstalled.
[*]Please with each backup, make sure to unmount all partitions again. (internal and external)
Update via Firmwarefinder:
Start Firmwarefinder App and select the appropriate update.
Then on GET AN UPDATE THROUGH DNA.
Then on WITHOUT IMEI.
Availability is displayed.
Now click on REGISTER UPDATE and the registration is displayed.
Then click IN-APP PROXY.
Now activate DNS in the router, enter 81.177.139.39 as addresses and save.
Now go to the WLAN settings on the phone, touch and hold the active connection.
Then change to Network in the menu.
Under Proxy-manual, enter localhost and port 8080 as host names for extended options.
Now only set the IP setting to DHCP. Now start the eRecovery.
Vol.+ and Power with PC connection
There on "Download latest version and recovery".
Then click on "Download and recovery" and register there under Select WIFI.
Now the update is displayed and can be started.
When rebooting, the device lands in the bootloop,
execute a factoryreset in the recovery.
After the update reboot and all changed WLAN settings, also in the router
and reboot it again. If you don't, it'll be over by the time
next OTA update is displayed again and again, since the authorization remains in memory.
Themes-Fix, How to Unbrick, FRP-Unlocking and Bootloader Unlocking I described here. Or follow this thread.
https://www.android-hilfe.de/forum/...t-how-to-root-twrp-root-anleitung.866625.html
It is easy to translate with: https://www.deepl.com/translator
All downloads are here: http://www.mediafire.com/folder/7qdu5je08caya/FIGO
Attention: Changing the oem.info can
cause the phone to lock. OEM/FRP=LOCK
Thread Update 2017-03-28:
A new TWRP is now available. It is version 3.2.1-0.
Original Chinese developer version.
Instructions:
First perform the Huawei data backup.
Flash TWRP per Adb as usual.
Then switch from Chinese to English.
Then assign write and read rights by removing the hook in wipe menu.
Now for security, create a backup without data.
Then Format Data.
Create a new full backup including data. This is possible now that the
formatting is the size of Data = 0.
Now reboot the device and set it up completely new.
Now there is a new and configured data partition.
Then turn OEM and USB back on and boot to TWRP.
Then create a new full backup.
TWRP is now fully functional. Only the MTP mode does not work.
http://www.mediafire.com/file/icpfjhw9eysjlao/FIGO321.img
Good luck!
My special thanks for this original Chinese TWRP for free use,
goes to: "weibo.com/xinkid520", FIRE Team(Developer) and "Team Win Recovery Project".
Despite careful elaboration, I cannot guarantee that the execution of this manual will not cause any damage to the device or operating system and therefore I do not assume any liability for any damage or malfunction of the hardware and software! If you are still unsure, follow these steps: Follow the instructions only if you or your device is subject to any conditions (model number, Android version, etc.). Read the instructions carefully and completely, look up unknown terms. Check downloaded files for viruses. Make a backup of important settings and data. Do not follow the instructions if you do not know what you are doing.
These warnings must be logical. Please process my comments correctly.
Many thanks to: funkyhuawei.club, Jrummy, Chainfire, Stephen (Stericson) +
Jmz Software, TWRP, osmOsis,Topjohnwu and Huawei Technologies Co., Ltd 华为技术有限公司
it's alive!!! FIGO-LX1C10B120
Men I love you!!!
Thank you monster!!!! [emoji8]
thanks !! are we getting a Huawei P smart forum here soon ??
Themes
I cannot apply themes after Root ?
Hello,
could you also provide the vendor.img?
Would be really nice.
Thx in advance
@enjac
Forum habe ich beantragt.
I have applied for a new forum.
@JahSound77
Flash the cust.img. Then it works.
@Destroyer706
Vendor kannst Du nicht mit adb flashen.
You cannot flash Vendor with adb.
Hey, guys, I got a brick. Can someone save/extract the "kernel. img"
from the 122. Or can someone from the sources compose a kernel. img? I don't have a linux pc.
:crying:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Themes
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Destroyer706 said:
I know I can't flash with adb, but fastboot. I made some changes and want to role back easily.
I try to provide you the kernel img
Click to expand...
Click to collapse
I uploaded it now. :good:
https://mega.nz/#F!EplhBBzS!UUgXBRC9DRaExP9HY57FKQ
JahSound77 said:
I followed your instructions.... fastboot flash cust cust. img
But no luck, after reboot... still can't apply themes from the store .
Click to expand...
Click to collapse
You must be logged in to the google account and huawei id. Outside Asia. If it doesn't work, wait one or two days. It'll probably work then. It was like that with me.
Thx. I am already compiling the kernel from source
Destroyer706 said:
Thx. I am already compiling the kernel from source
Click to expand...
Click to collapse
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
ChinHon said:
This has never happened to me before. I have always been able to rely on TWRP backups. But without.....
Click to expand...
Click to collapse
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Destroyer706 said:
The thing, I didn't think about, is, I don't know how to repack the image.gz after compiling to flashable boot.img as I don't have a existing boot.img.
Maybe you can advice me.
Click to expand...
Click to collapse
There is no boot. img in the 121 firmware anymore. Only the kernel. img. I flashed that. So I have the bootloop and need the img from 122, so I thought you might be able to extract it from your device.
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
Not included in the UPDATE. APP anymore.
See filelist:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
steveleg said:
Can you upload oeminfo file for FIG-LX1 8.0.0.122 (C432) please?
I would like to rebrand my Chinese version (FIG-AL10).
Click to expand...
Click to collapse
I found another update in the net. Here the oeminfo as a self-extracting archive.
https://mega.nz/#!5gcygYLL!Wdlvg5jUo2hv6L7DBtAVT1-0z_WRmSBLuBin7iUGjig
Destroyer706 said:
Here is the extracted kernel.img. Hope it helps.
https://mega.nz/#!auo2TAaC!7009dtrK8-uBR39s9fNFf2xCQkEzR1EXURSLBabkuk8
Click to expand...
Click to collapse
Hey bro, FIGO's alive again. Thanks a million. You're the best.
:good::good:
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
It hasn't been long since I joined the ZenFone Max Pro M1 forums and since then I was worried about the EFS/IMEI because it is very complex in the Snapdragon SoCs. So all you need to do is to backup EFS partition by using an app created by @wanam
Instructions:
1) Unlock your bootloader (will be available soon)
2) Flash TWRP (if available)
3) Root your phone (Magisk/SuperSU)
4) Install Partitions Backup & Restore app from Google Play Store
5) Back up MODEM, MODEMST1 & MODEMST2 (In simple words, backup the yellow highlighted partition)
Notes:
The backups are saved on /sdcard/PartitionsBackups.
DO NOT leave the EFS/Modems backups on your sdcard, MAKE SURE YOU KEEP IT IN A SAFE PLACE
DO NOT use the restoration feature for tests purposes, it is recommended to use it for small partitions only (EFS, Boot, Modems.), you can restore other partitions backups with FASTBOOT.
Source: Link
Saktis_STi said:
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
It hasn't been long since I joined the ZenFone Max Pro M1 forums and since then I was worried about the EFS/IMEI because it is very complex in the Snapdragon SoCs. So all you need to do is to backup EFS partition by using an app created by @wanam
Instructions:
1) Unlock your bootloader (will be available soon)
2) Flash TWRP (if available)
3) Root your phone (Magisk/SuperSU)
4) Install Partitions Backup & Restore app from Google Play Store
5) Back up MODEM, MODEMST1 & MODEMST2 (In simple words, backup the yellow highlighted partition)
Notes:
The backups are saved on /sdcard/PartitionsBackups.
DO NOT leave the EFS/Modems backups on your sdcard, MAKE SURE YOU KEEP IT IN A SAFE PLACE
DO NOT use the restoration feature for tests purposes, it is recommended to use it for small partitions only (EFS, Boot, Modems.), you can restore other partitions backups with FASTBOOT.
Source: Link
Click to expand...
Click to collapse
I have not backup imei because my phone has been bricked ! I unbricked sucessfull ! And lost imei !
How to fix issue "lost imei" if no backup ?
Saktis_STi said:
I am not responsible for bricked devices and dead SD cards. YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
It hasn't been long since I joined the ZenFone Max Pro M1 forums and since then I was worried about the EFS/IMEI because it is very complex in the Snapdragon SoCs. So all you need to do is to backup EFS partition by using an app created by @wanam
Instructions:
1) Unlock your bootloader (will be available soon)
2) Flash TWRP (if available)
3) Root your phone (Magisk/SuperSU)
4) Install Partitions Backup & Restore app from Google Play Store
5) Back up MODEM, MODEMST1 & MODEMST2 (In simple words, backup the yellow highlighted partition)
Notes:
The backups are saved on /sdcard/PartitionsBackups.
DO NOT leave the EFS/Modems backups on your sdcard, MAKE SURE YOU KEEP IT IN A SAFE PLACE
DO NOT use the restoration feature for tests purposes, it is recommended to use it for small partitions only (EFS, Boot, Modems.), you can restore other partitions backups with FASTBOOT.
Source: Link
Click to expand...
Click to collapse
No modem,modemst1 and modemst2 partition found
There are 8 yellow partitions but none of them named modem,modemst1,modemst2
Please help
Any way out in locked bootloader?
The2k10 said:
Any way out in locked bootloader?
Click to expand...
Click to collapse
Why would you want to backeup efs/imei in locked bootloader?
Only unlocked users should have worried about efd /imei corruption
Anyone has backup?
Is anyone has taken backup of modem1,modem2,modem3 ...
Please send it...
I had hardbicked my phone