Database Info

[Complete] Huawei U8510 Ideos X3 (Vodafone) Australian stock ROM

Hello All,
I have Huawei u8510 x3 (Vodafone branded) Australian (Model: HUAWEI U8510-7).
I rooted my phone, took ClockWorkMod backup and flashed generic stock ROMs (Phones 4 U - UK Generic Stock ROM).
When I revert to my saved backup, I notice that my boot animation has changed. After lot of reading I have realized that ClockWorkMod (did not backup /cust and /userdata2 partition that contained the Vodafone stock branding).
Can anyone please update a Australian Stock ROM (U8510-7 Australian Stock ROM) for this device? If not, can you please link to a backup of the /cust and /userdata2 partition and instructions on restoring this?
Thanks so much in advance.

I have the same phone, still in stock condition. Could back up these folders and upload the data somewhere for you, if you like.
Incidentally, I have been trying to root this phone with no success. How did you do it?

Steps to backup stock /cust and /userdata2 partition prior to flashing new ROMs.
AimUnit111 said:
I have the same phone, still in stock condition. Could back up these folders and upload the data somewhere for you, if you like.
Incidentally, I have been trying to root this phone with no success. How did you do it?
Click to expand...
Click to collapse
Thanks mate. What OS are you using? I used Windows 7 as Windows XP did not work for me.
Even with Windows 7, I had to manually install the driver (device manager, update driver, path to driver files downloaded).
Follow the guide here: http://forum.xda-developers.com/showpost.php?p=19246491&postcount=1
to root your phone. Meanwhile I'll find out instructions for fool proof stock recovery partition backup. For now I have out they only way to backup /cust and /userdata2 partition here:
http://66.163.168.225/babelfish/tra...lash-partitionen-von-supertoast-anpassen.html
Here is another way to completely take a backup of your stock ROM prior to flashing new ROMS:
http://androidarea51.com/q-kernel-a...?PHPSESSID=nk8an4uv09a23ta6q0t05nk3j0#msg2503 --> Follow steps in Reply#2
OK, I have thought about this and reread the backup partitions from the 1st Link in this post. Essentially the steps to take a backup of the /cust and /userdata2 partitions are:
1. Root your phone (If you follow guide: http://forum.xda-developers.com/showpost.php?p=19246491&postcount=1, ClockWorkMod recovery would have been installed.)
2. Download backup_partitions.zip from here http://66.163.168.225/babelfish/tra...change_partition_layout/backup_partitions.zip and save it somewhere in your sdcard (/sdcard is recommended)
3. Reboot into recovery mode (reboot phone, press Vol+ and Power ON button at the same time when restarting)
4. In CWM Recovery mode, Install zip from sdcard and choose backup_partitions.zip (downloaded in step 2)
5. Reboot phone.
6. Check the root of your sdcard. You should see the following files:
cust_backup.tar --> Backup of your /cust partition (with Voda boot logo and branding)
userdata2_backup.tar --> Backup of your /userdata2 partition (more oem stuff I think)
If you have reached thus far, I would really appreciate if you could please zip the above 2 .tar files and load it in Dropbox/rapidshare etc.
Am certain that the above 2 files will NOT have any confidential data. All of your confidential data (account information, sdcard backup etc are in data.img)
Am happy to help anyway I can when you get stuck rooting or taking the backup.
UPDATE: Found another method of backup data in /cust partition.
I quote a post by knzo from: http://pzieye.centelia.net/blaze/viewtopic.php?id=7 (requires registration)
---
Here's a tutorial on how to remove the crap from your operator such as vodafone. You need root for this.
0. Backup first (optional but highly recommended)
- Download busybox installer from market, run it and install busybox (1.19 on /xbin for example)
- Download terminal application from market, run it and do these commands (without the ""):
- "su" (click allow when it asks you for root privileges)
- "mkdir /sdcard/custbackup" (you'll need a microSD card for this)
- "cp -r /cust/* /sdcard/custbackup"
- Done, backed up contents will be in your microSD card on the custbackup folder
1. Removal
- Run these commands on terminal application:
- "su"
- "ls /cust/" (take note of your brand; in this case, let's assume it's vodafone)
- "mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /cust"
- "rm -r /cust/vodafone/"
- "reboot"
- Enjoy your unbranded device
2. Restore (optional, needs step 0 to been made)
- Run these commands on terminal application:
- "su"
- "mount -o remount,rw -t yaffs2 /dev/block/mtdblock8 /cust"
- "cp -r /sdcard/custbackup/* /cust"
- Done
Last edited by knzo (2011-09-17 05:35:11)
---

Vodafone Stock ROM Restore for U8510-7
Thanks to a kind member koolchamp81 in Whirlpool Aussie Forums, we now have a full backup to the Australia Vodafone STOCK ROM for U8510-7 X3.
Before you start, you need to download the following:
1. Whirlpool member Koolchamp81's Stock ROM backup
2. Koolchamp81's /Cust partition backup
3. Koolchamp81's /Userdata partition backup
4. restore_partitions.zip from Android-life.de
Follow these instructions for restoring to Stock ROM. We have confirmed success reports on restoring to stock ROM based on these instructions.

Converting EXT4 and RFS

For rooted Charge owners, some are on the RFS file system, others are on EXT4. The Charge comes as RFS stock, so unless you have converted to EXT4, chances are that your phone is still on RFS. What's the difference? Click on this link to view a discussion among some of the original developers including IMNUTS: RFS to EXT4 - Page 3 - xda-developers
Keep in mind that nobody except YOU are responsible for what happens to your phone. Past performance is no guarantee of future results, always read the instructions carefully before flashing, feel free to ask questions.
Note: the kernels mentioned below are for FP1 & FP5 ROMs - currently, there are only two ROMs with this build, Eclipse and Tweaked
FP5 build is currently only supported by the Tweaked ROM - thanks to kynalvarus for developing the FP5 custom kernel!
Before you begin the conversion:
- make sure that you have root access and can enter the Clockwork Recovery Mod (CWM)
- download and install Terminal Emulator from the market
- once in there, type "SU" then "Mount" (without quotes)
- scroll to the top and look for the text after the following folder names: "/system", "/data", "/dbdata", and "/cache"
- if you see RFS, then you are on RFS, if EXT4, then you are on EXT4
- download Imoseyon's kernel (http://rootzwiki.com/topic/3426-kernel-gb-imoseyon-kernel-stock-repacked-v400-11611/)
- make sure that you've got plenty of battery life on your phone (or plug it in during the process), for me, the process cost me ~5-10% of battery life, but your experience may vary
below are the steps to convert RFS to EXT4:
check to see if you have a folder called "sdcard/VooDoo/disable-lagfix; if so, then delete it, if not proceed to next step
1. boot into CWM
2. mount system
3. install zip from SDcard
4. select Imoseyon's kernel
5. re-boot system (process can take about 10 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
6. check to ensure that the conversion took place by entering into Terminal Emulator and looking for EXT4; if still RFS, then:
a. Download and install voodoo control from market
b. Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
7. boot back into CWM
8. mount system
9. install zip from SDCard
10. select your flavor of PBJ kernel (note: stock FP1/FP5 will NOT work on EXT4)
a. FP1: tonsit
b. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
c. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0524 PBJ
e. FP5: Lazarus Recharged
11. be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSU via CWM)
below are the steps to convert from EXT4 to RFS:
1. check to see if you have a folder called "sdcard/VooDoo/disable-lagfix" (without quotes); if not, then create it; if so, proceed to next step
2. if you have a custom boot animation, change it to read "sanim.zip.bak"
3. boot into CWM
4. mount system
5 .install zip from SDcard
6. select Imoseyon's kernel
7. re-boot system (process can take about 15 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
8. check to ensure that the conversion took place by entering into Terminal Emulator and looking for RFS, if still EXT4, then:
a. Download and install voodoo control from market
b. Un-Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
9. boot back into CWM
10. mount system
11. install zip from SDCard
12. select your kernel
a. Stock FP1
IMPORTANT: you can only convert to a stock kernel from another stock kernel or the 0524 PBJ kernel (presumably the Lazarus kernel as well). For example, if you are on the 0504 PBJ kernel and want to go to stock FP1, you will need to flash the 0524 PBJ kernel first, and then flash the stock FP1. IMNUTS setup this kernel to help prevent issues when folks wanted to flash back to a stock kernel
b. FP1: tonsit
c. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
e. FP1: 0524 PBJ
f. FP5: Lazarus Recharged
g. Stock FP5
be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSu via CWM)

below are the steps to convert RFS to EXT4:
check to see if you have a folder called "sdcard/VooDoo/disable-lagfix; if so, then delete it, if not proceed to next step
1. boot into CWM
2. mount system
3. install zip from SDcard
4. select Imoseyon's kernel
5. re-boot system (process can take about 10 minutes, you'll hear a robot lady voice telling you that the system is partitioning, and will give you an estimated time of completion)
6. check to ensure that the conversion took place by entering into Terminal Emulator and looking for EXT4; if still RFS, then:
a. Download and install voodoo control from market
b. Check all ext4 boxes then reboot
c. Re-check with Terminal Emulator
7. boot back into CWM
8. mount system
9. install zip from SDCard
10. select your flavor of PBJ kernel (note: stock FP1/FP5 will NOT work on EXT4)
a. FP1: tonsit
b. FP1: 0502 PBJ (no longer posted, ask a member of this community for the file)
c. FP1: 0504 PBJ (no longer posted, ask a member of this community for the file)
d. FP1: 0524 PBJ
e. FP5: Lazarus Recharged
11. be sure to "Fix Permissions" in CWM before rebooting or you could lose root (if you still lost root, then simply flash SuperUser/SuperSU via CWM)
Click to expand...
Click to collapse
somewhat easier method for me anyways...
MAKE SURE YOU HAVE A NANDROID FIRST!!!
or PBJ FP5 and your ROM of choice
1. boot into CWM
2. make nandroid
3. flash selected formatter
4. restore said nandroid or flash ROM AND kernel! (make sure it is a supported kernel or you WILL boot loop)
5. reboot
6. enter terminal and type "SU" and then "mount" to check and see if you are EXT4
this method has worked for me every single time.

je2854 said:
somewhat easier method for me anyways...
MAKE SURE YOU HAVE A NANDROID FIRST!!!
or PBJ FP5 and your ROM of choice
1. boot into CWM
2. make nandroid
3. flash selected formatter
4. restore said nandroid or flash ROM AND kernel! (make sure it is a supported kernel or you WILL boot loop)
5. reboot
6. enter terminal and type "SU" and then "mount" to check and see if you are EXT4
this method has worked for me every single time.
Click to expand...
Click to collapse
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?

The Amorphist said:
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?
Click to expand...
Click to collapse
I have never had problems but here is the PIT you asked for

The Amorphist said:
I do not recommend trying this shortcut. I made my Nandroid in CWM, flashed the ALL Flasher, went to restore the nandroid, and was told my file system format was incorrect. I am now stuck in a bootloop, unable to access CWM or Download mode.
I was running Tweaked 3.2 with Laz's Kernel
Update: Yea, this has SERIOUSLY screwed up my phone. I am now able to get into CWM, but I am told I cannot mount /system, so I can't mount it to reflash the ROM, nor can I format it back to RFS. I also cannot install any zips from my sdcard, as the screen simply goes blank when I click "install zip from sdcard".
So....can anybody help me? Now that I can get into CWM, I figure I can prolly get into download mode, so maybe a full Odin would help? Does anybody have a PIT I can use?
Click to expand...
Click to collapse
full Odin with PIT should do the trick.

This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.

barn25 said:
This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.
Click to expand...
Click to collapse
Are you sure? The options are only displayed when you have a voodoo kernel, the last of which was Imoseyon's 4.0 (EP1W IIRC) hacked kernel. This will not work on any of the GB PBJs.

barn25 said:
This guide needs to be removed voodoo doesnt have the option format to ext4 anymore.
Click to expand...
Click to collapse
That's interesting, because I followed this exact guide back in December and it worked perfectly fine for me, just as described in this guide.
Sent from my SCH-I510 using Tapatalk 2

Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.

barn25 said:
Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.
Click to expand...
Click to collapse
That's because you need to flash this kernel first... http://rootzwiki.com/index.php?/top...-(Stock-Repacked,-V4.0.0,-11/6/11)#entry79247 it will convert everything. Use Voodoo and make sure, then flash Lazarus.
Sent from my AOSPA N7 controlled by Metallice's a36 Kernel.

I did do that nothing happened. Which was odd...

barn25 said:
Yup running lazarus ReCharged kernel for FP5E which is voodoo and EXT4 enabled. http://rootzwiki.com/topic/37854-kernel2013-01-09lazarus-recharged-kernel/ Whoops forgot to post a screenshot from my charge.
Click to expand...
Click to collapse
Lazarus has support for voodoo sound, not voodoo lagfix. This app displays voodoo lagfix controls when it is available.

I didnt know that. So what FP5E kernel does support Voodoo lagfix?

barn25 said:
I didnt know that. So what FP5E kernel does support Voodoo lagfix?
Click to expand...
Click to collapse
None of them do. You gave to get imoseyon 4.0 kernel, which is for a really old leaked gb build but works well enough to boot and convert partitions, from rootz.
Once you are done setting up lagfix you can flash the kernel of your choice.
Sent from my SCH-I510 using Tapatalk 2

[Q] Is there a way to install temporary recovery on SGR

Hi I am a new member on this forum, though I had been browsing this forum for long long time, I had not registered. Recently I had the courage to root and install omnirom on my phone (as my phone is getting old, i was ready to take the chances of bricking my device. I verified my device with eMMC brick bug tester and my device is frees from that bug, probably as my motherboard was changed under warranty). After toying with omnirom, I am back on stock rom. I went to Samsung Service Center and got my factory firmware installed for Rs 225/- (I had taken nandroid backup with epsilon 6.0... version of CWM, but it missed preload partition and restored the backup with philz recovery and my preload partition was erasaed and have to go for SSC).
I have few queries regarding the SGR, please help me with them:
1. Is there a temporary recovery for SGR (ie, can be flashed with stock recovery and returns back to stock on reboot. The zip file has to be maintained on SD card)
For SGS2: http://forum.xda-developers.com/galaxy-s2/general/guide-root-unroot-stock-ics-firmware-t1501719
2. In order to restore the partition on my own, I tried and searched net for recovery using testdisk and had taken a file image of the SGR internal flash disk. I opened it with testdisk, but testdisk was not able recognise the partitions I tried EFI GPT as suggested and Intel partiton table type and both did not work. Do you know the partition table type for this?
recovery link: http://www.df.lth.se/~jokke/androidfilerecovery/
3. I was just curious if becoming root (on adb shell) is just running su, thought I would copy su binary from superuser zip ro sdcard and run it with the path, but it just runs and nothing happens (I need this to remove few samsung apps esp, vlingo. I plan to do it from recovery -> adb shell -> su and delete apk & odex files).
This has been a great forum and helped me a lot. Thank you guys for all your effort.

How to fix 'E: Can't Mount Cache' in CWM

This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS

dima234 said:
I have tried this but this does not work. I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages and say "Installation Aborted" and restart phone.
I have also Flashed back the Stock ROM and repeated all of the procedures: 1.Framaroot 2:CWM
Still no success it just keeps giving me these stupid errors, Please Find a FIX.
THANKS
Click to expand...
Click to collapse
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?

meriox said:
I have the same problem.
I tried methods:
$ su
#dd if = / sdcard / recovery.img of = / dev / block / mmcblk0p13
It does not work.
I installed the stock rom and checked the partition mmcblk0p13 with "Partition Table" and the partition is not mounted.
Maybe this is the problem?
Click to expand...
Click to collapse
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.

dima234 said:
Yea even i have tried the same but it does not work, guess we have to stick to the stock ROM till someone finds a fix.
Click to expand...
Click to collapse
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.

meriox said:
Do you think that someone will be looking to solve the problem?
It seems to me that the problem occurs only in the new models that have been bought recently.
I tried to install the older stock firmware but it did not help.
None of the methods that have been on the forum does not work.
The problem occurs only when WIPE DATA / FACTORY RESET.
Click to expand...
Click to collapse
yea getting the same problem here.
cant mount system
cant mount cache
and most of all when install custom ROM. cannot continue since non of those partitions cannot mount properly.
and other errors are flooding the recovery, we have tried Philz, CWM, TWRP. same annoying problems.

Hello,
On another website I found this:
"All worked fine but that like of command in terminal you put there isn't right, i did this
$ su [and then enter]
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32 [and then enter]
# reboot recovery [and then enter]
PS: the $ comes automatically when you start the terminal emulator app; the # comes automatically after you allow the super user [in $ su]
Do consider all the "Spaces" between symbols and paths!"
Has anyone used this method?

syedwaseem said:
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.
E: Can't mount /cache/recovery/log and the other five errors are similar to this.
PERFORM A BACKUP PRIOR TO THIS
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.
Start by going into your recovery..
If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.
KEEPING YOUR CURRENT ROM
1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery
If it is not working, repeat the steps.
FLASHING A NEW ROM
1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM
I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.
Click to expand...
Click to collapse
Thanks worked for me :good:

bricked
I've got these errors on my htc desire x, I made a backup, after that, I try to flash a new rom, with the steps written in the first post. The result was: after the htc logo, it showed a black screen! I try to restore the backup, but I cant restore!!!!! I've got soft brick, so I take it a service. I hope, they can fix it

[HOWTO][TWRP][ROOT] ZTE quest N817 with locked bootloader

First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.

Wow, thanks.
I was able to port KonstaT's CWM for the kis3 to this device and it works almost flawlessly, but when I tried to do the same with TWRP I just got a white screen and had to pull the battery. This boots fine, so I'm interested in taking it apart and seeing what you changed.
External SD card doesn't work on my phone. Since I plan on taking it apart anyway I'll look at the fstab files, if I figure it out I'll be sure to share my changes.

Yeah like I said in post I have no external sdcard so I could not test. With putting in external a few ttimes I was looping. I think I did 6 builds and on my device which is not used. I was able to create boot, system and data backups and flash again amd install supersu from chainfire. I have built a number of kernels but wont boot. I am just going to get working kernel and nethunter it or maybe kexec hardboot for a linux. Also I rhink I used the original recovery kernel, might have gone stock.
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app. Not sure how it will handle it being locked boot. Each of the port guides useless being locked. Days off this week might look into delving into it more. But after 5 months of headaches with exynos kernel and rom might need a break. Tired of these corps releasing broken code to stall people. 3 or 4 from scratch begings with samdung kernel between 2,000 and 6,,000 files edited on each attempt and still borked, with even.trying to back port newer versions of drivers. I have one solid kernel running but just above stock because I removed there fuelgague and charger driver with a Script for deepsleep, might be my best yet before I get a new phone in a few months. Samsung and zte plus any mediatek I'm over them now and swearing off.

I notice the line for the sdcard is commented out in twrp.fstab, I'll try uncommenting that and see what happens, but I remember to get the sdcard working correctly under CWM I had to use vold. The line for CWM was:
/devices/msm_sdcc.2/mmc_host auto auto defaults voldmanaged=sdcard0:auto,noemulatedsd
This seems to work with or without an sd-ext partition (mounting sd-ext normally as /dev/block/mmcblk1p2 works, no need to use vold for that).
jag9906 said:
Did you do recovery or cm 11. I tried about 5 builds of cm11 furthest i got to was loading applications screen and locking. Did you flash this twrp. With rashr app.
Click to expand...
Click to collapse
I did KonstaT's CWM recovery from the kis3. I think the only things I had to change were the kernel (from stock recovery), fstab (based on stock recovery, with some trial and error) and default.prop
Haven't tried flashing CM11 to this phone yet, I have tried building the device/vendor trees to build CM11 from source, but ZTE's kernel source for this device doesn't compile and KnostaT's ZTE msm8610 kernel source doesn't boot, so that's as far as I've managed to get.
I flashed this TWRP with the rashr app, but when I flashed CWM I had no problem using (from a root adb shell) "dd if=/path/to/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
I did need to (once) reboot the device with "adb reboot disemmcwp" when I initially got root before I could mount system rw and install SuperSU.

Yeah that was the issue when.I did stuff with my main phone, I only have one sdcard in main phone so I didn't get around to testung vold. That sould fix the issue. I learned that lesson a few weeks ago with my samsung phone. If it works mind posting that fike so.I can.update this twrp.so people cam atleast have a touch backup with supersu not those roots that auto install garbage apks and have ads.
I found another cm11 I will check later afyer work tomorrow and post link since kis3 is gms this one was cmda for porting rom.

ok can try porting the cm11 unofficial condor, or carbon KK unofficial condor both I think I found through xda, there is an AOPK condor MM nightly if you want to try to up to that or the lineage OS condor 14.1 with a new kernel. can google this cm-11-20140808-UNOFFICIAL-condor to get the link from xda or search here.

I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.

Sorry to double-post, just an update. Between what I already had, your work here and a conversation with KonstaT about kernels, I have the ZTE N817 kernel and TWRP 3.0.2-0 compiling against LineageOS cm-11.0, newer versions of TWRP may build and run fine against KitKat but the OTA tools need a newer version of Android to build.
local manifests:
https://github.com/stevenh512/local_manifest_zte_n817
device tree:
https://github.com/stevenh512/android_device_zte_n817
kernel tree:
https://github.com/stevenh512/android_kernel_zte_n817
vendor tree:
https://github.com/stevenh512/proprietary_vendor_zte_n817
Just repo init -u https://github.com/LineageOS/android.git -b cm-11.0 and copy the local manifests into .repo/local_manifests before you sync, then:
Code:
. build/envsetup.sh
lunch cm_n817-userdebug
make -j4 recoveryimage
adb push out/target/product/n817/recovery.img /storage/sdcard1/recovery-twrp-new.img
(replace /storage/sdcard1 with /storage/sdcard0 if you have no external SD)
I haven't tried to build the ROM yet, but TWRP works flawlessly, external SD and internal "emulated" (/data/media) SD are both recognized.
Have fun.

jag9906 said:
First off doing this will void your warranty and can brick your device. Following these simple steps should work for you. I will state here and further down, make sure you download all programs needed and both recovery.img and recovery_orig.img. I am in no way resposible for your device being bricked.
**Only thing I have not tested is the external sd card, I make no promises that it works. I only have 1 sd micro card its installed in my main device. So install the recoveries and supersu to your internal sdcard.
This is for assurance wireless, I have seen one or two other n817 devices if the specs are the same, they "should" work with this twrp, but use partition backup and restore by wanam on Play store to get a recovery.img for your device. I do not use this program for system back up, for some reason it does not work properly but its fine for boot,aboot, recovery and other smaller partitions.
This is a ported twrp from kis3 twrp version 3.0.2-0 by KonstaT from here http://konstakang.com/devices/kis3/TWRP/. Also this version of chainfire su SR3-SuperSU-v2.79-SR3-20170114223742 download from here https://download.chainfire.eu/1021/. This twrp recovery has Supersu folder but I still installed the zip from recovery to be sure.
The twrp n817 recovery named: recovery.img along with the original n817 recovery named: recovery_orig.img go here https://github.com/jag9906/n817_twrp
Other programs needed [ROOT]Rashr flash tool, online nandroid backup *root*, SD maid from Play Store. The Rashr flash tool is required, you can use any back up you wish, I prefer SD maid for cleaning up system and removing/freezing programs you can use any you use, this is to remove your temp root after recovery and supersu is installed.
**Again I am stating here the Rashr flash tool is required this will allow you to install the recovery.img with a locked bootloader. This is a must to install this twrp recovery. The twrp app will not work until you have supersu installed. There are other flash tools, but this worked flawless with kingo so its the only one I will support for this guide. If you use another flash tool its on you.
First make a back up prior to installing the twrp recovery. Use the online nandoird back up of all partitions I save them as twrp. If you have external SD card you can do all at once if not do all but data and system then copy to your computer and then back up system folder. Your choice on data, I back up my apk so never data.
Next run Rashr flash tool from Play store the first option is recovery from storage, choose this option then go to your location on sdcard and select recovery.img hit ok it will take about 10 to 15 seconds and ask if you want to reboot into recovery, hit yes and then your device will reboot into recovery. Once loaded swipe and go to install, top left find your SR3-SuperSU-v2.79-SR3-20170114223742.zip file and select that, then swipe to install. Once finished hit reboot and system.
Then run SD Maid or any root tool to uninstall you have. You can now delete/remove Kingo or any root you used prior to installing the recovery and have supersu by chainfire as your root for the device.
You now have a twrp recovery, and chainfire's supersu installed on your n817 device.
thanks to KonstaT and Chainfire for the hard work they have done.
Click to expand...
Click to collapse
Unfortunately Kingo can't root my device and neither can anything else...... Sucks but hey the phone was free. Hopefully something can work in the future *shrugs*
Edit: rebooted "adb reboot disemmcwp" and Kingo worked ._.

Yeah, this phone was pretty difficult before King/Kingo supported it, and with no fastboot I don't think there's any way other than a ZTE signed update to alter the /system partition without rebooting with "adb reboot disemmcwp" first. Before I discovered a post mentioning using that command to disable the write-protection on another ZTE device I was able to get a root prompt with the right SELinux context but I still couldn't write anything to /system. Once I got the write-protection disabled, I didn't even bother with any of the one-click rooting apps. I just got a root shell, mounted /system rw and proceeded to put all of the SuperSU files where they go and set their permissions by hand, rebooted and I was good to go. Of course, once I got a recovery installed I did re-flash SuperSU from an update zip just to make sure it was right.

does anyone have a stock backup, i don't kn0w what i did, but now the standard android recovery tells me there are missing files when i do md5 check and it boot loops right back to recovery, anyone have and recommendations for repair, i can get to stock recovery, i can adb side load updates or choose from cache or sd card, when i pop out the battery and plug in its recognized as:
ZTE WCDMA Technologies MSM
right before boot loop to recovery:
Product: ZTE HSUSB Device Manufacturer: ZTE Incorporated (dmesg)
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
whitout battery black screen:
QSHSUSB_BULK qualcom CDMA technologies MSM
i dont know if im in ftm mode, screen just stays black and shows up as above? when in recovery

stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse

morpheous1777 said:
does anyone have a stock backup
Click to expand...
Click to collapse
I also wouldn't mind having a stock backup, unfortunately I didn't remember to take a backup before I started tinkering with my system partition, but thankfully I haven't managed to break anything I couldn't fix.
while in recovery in adb sideload mode
Product: N817 Manufacturer: ZTE (dmesg)
18d1:d001 Google Inc. Nexus 4 (fastboot)(lsusb)
Click to expand...
Click to collapse
While in this mode, are you able to actually use fastboot? I ask for two reasons. First, if you're on a stock recovery, the only way you're going to be able to restore a stock ROM (or install any other ROM) from recovery is if it's signed by ZTE, otherwise you'll need another way (like fastboot). Second, as far as I can tell, there is no fastboot on my phone.

leetree2001 said:
stevenh512 said:
I got my sdcard (with sd-ext partition) working with this twrp.fstab:
Code:
# mount point fstype device [device2, parameters]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot flags=backup=1;
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=backup=1;
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=backup=1;
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=backup=1;
/data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=backup=1; length=-16384
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="MicroSD";storage;wipeingui;removable
/sd-ext auto /dev/block/mmcblk1p2 flags=wipeingui;removable;backup=1
I'm sure that's not quite right, there are probably some flags I'm missing and definitely some other partitions you'd want to back up. I also have TWRP 3.1.0-0 compiling for this device from source (against LineageOS cm-11.0 tree with precompiled kernel from stock recovery) and booting with internal "emulated" SD and external SD both working, but I need to tweak my BoardConfig.mk a bit more to solve a couple minor issues. If I can get that 100% working I might try to "make bacon" and see what happens, I'm pretty sure the rest of my device tree is right and I've pulled all of the vendor files from the device. I didn't remember to take a backup of my stock ROM when I rooted, but I do have a full backup of my device in its current state.[/Q
Change sdcard to sdcard1
Click to expand...
Click to collapse
I'd really love this and I'd love it more if I could contribute in some way... this phone is painfully slow on the stock OS.
Click to expand...
Click to collapse

Have nothing to contribute right now.Just want to THANK all you guys for your unselfish work!!!
Sent from my LGLS770 using Tapatalk

Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help

This worked great, thanks
---------- Post added at 10:03 PM ---------- Previous post was at 09:32 PM ----------
It works, but my system is very unstable right now. I have a feeling it's that KingCrap . It doesn't like to be replaced with another SU. That stuff is malware and I never use it unless I"m desperate. I'm going to try to push 3c toolbox to it. It won't stay up long enough to install it from playstore.

Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson

I can't do anything with it now. It won't stay up long enough. I have a nandroid backup but it's on the external sd which this TWRP can't see. There isn't enough space on the internal to copy it to. I'm giving up for now, I"ve spent way too much time on a $20 phone

slacker8135666 said:
Member96 posts Thanks: 16
Does anyone have the stock rom?? The recovery bricked my assurance n817.Please help
I did a full backup of my zte n817. it's in .img format. pm me and I'll send it to my google drive and give you the link. Do you know what partition goes where? I also have that info too !! After 3 bricked phones I have learned somewhat of a lesson
Click to expand...
Click to collapse
Sent from my LGLS770 using Tapatalk