Related
Hello guys. This my dual booting project for our amazing ZTE BLADE!
What is this?
>This mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of NAND.
FOR ADVANCED USERS ONLY!!!
I WILL NOT BE RESPONSIBLE FOR ANY BRICKED DEVICES, DAMAGED SDCARDS ETC.
DO IT AT YOUR OWN RISK!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more ROMS like CM10, Paranoidandroid etc.
Downloads:
Cyanogenmod9(KonstaKang)
Boot.img - Download
Updater-script - Download
Cyanogenmod10
Boot.img - Download
Updater-script - Download
Gapps::
Jelly Bean Gapps Updater-script - Download
Tool:
Modify-Boot - Download
Now no need to wait for me to mod your boot.img.Mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
SNAP.iT for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
SCROLL DOWN to 2nd POST FOR THE WHOLE GUIDE...
GUIDE
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
GUIDE FOR THE TOOL
Extract the downloaded zip file extract to any concinient directory.Here I will explain the guide as a cygwin user.
Extract the zip to directory say c:\
The extracted folder will look like 'Modify-boot".Now open the terminal or cygwin bash and mount the directory by typing
cd c:\modify-boot
Click to expand...
Click to collapse
Now drop your boot.img in the WORKING_313 folder and execute the script by typing
./modify-boot.txt
Click to expand...
Click to collapse
It will mod your boot.img for dual booting.Output boot.img will be in the WORKING_313 folder as boot.img.
MODDING THE ROM FOR DUAL BOOTING
Open the ROM.zip.
Get the modded boot.img from the tool and replace with the original one.
Now download the attached updater-script from 1st post and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
ADAPTING A ROM TO INSTALL IN THE SD CARD
If you want to mod your own rom other than the posted here,then you have to mod the updater-script in the rom
For that open your rom zip go to /META-INF/com/google/android and open the updater script
Now replace every line looking like following as;
From
mount("yaffs2", "MTD", "system", "/system");
Click to expand...
Click to collapse
TO
run_program("/sbin/mount", "dev/block/mmcblk0p3", "/system");
Click to expand...
Click to collapse
and this one
From
format("yaffs2", "MTD", "system", "0");
Click to expand...
Click to collapse
TO
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p3");
Click to expand...
Click to collapse
and add the following line next to the line written above
run_program("/sbin/mkfs.ext2", "dev/block/mmcblk0p2");
Click to expand...
Click to collapse
Save the file and zip up the rom.Your rom is ready to install to SD CARD!!!!
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
[email protected] said:
So here is the full guide:
PARTITIONING SD CARD TO MOUNT /SYSTEM AND /DATA
Take the backup of your sd card data first
Make sure you have partitioned your sdcard before.
Connect your phone to your computer and mount usb storage.
Download the EASEUS partition manager from here.
Open partition manager and delete all partitions of your sdcard.
Right click on the 'unallocated' and click create partition.Don't label it select partition type as primary and filesystem as FAT32 and enter the partition size bot remember this will hold your photos,media etc,you should leave about 600 mb space free click OK.
right click again and create partition as primary and filesystem as EXT3 and size of 250 mb click OK.
Repeat above step again.
Apply all the changes by cliking on apply tap and you have succesfully partitioned your sdcard for dual booting.
MODDING THE CM9 ROM FOR DUAL BOOTING
Open the konstakang.zip (currently only supported rom, will add more soon).
Download modded boot.img from here extract it and rename the .img file to boot.img.
Delete the boot.img from the cm9 rom and put the downloaded one.
Now download the attached updater-script (remove .txt) or from here (for unregistered users)and replace the orignal one with this modded one(path to udater-script META-INF/com/google/android).
Zip up the rom.
FLASHING GUIDE
Remember, before partitioning the sd card you should wipe data and cache in the recovery during NAND rom installation or it will erase the partitions created before.
First flash the rom you want to install in the NAND,do not wipe data or anything do it before partitioning.
Then install the cm9 rom without wiping data or anything.
reboot the system. You will be in your sd card rom!!!
Now create folder in the sd card as /sdcard/multiboot.
Take both boot.img from NAND rom and cm9 rom rename the cm9 boot.img to bootsd.img and keep the NAND boot.img as it is.
Copy both imgs to multiboot folder.
Now download attached(or use above link for unregistered users) bootnand.sh and bootsd.sh and place at the root of the sdcard.
Open terminal emulator,type su and execute bootsd.sh to boot into sd card rom or execute bootnand.sh to boot into NAND rom.
THAT'S IT . ENJOY DUAL BOOT ON YOUR ZTE BLADE!!!!
Click to expand...
Click to collapse
hi, thank u ....... the link for 'boot.img' is not working. Pls fix it
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
karthiknr said:
Can't thank you enough for this,if it works.. Great stuff btw.. At least,you were the first one that tried and got it working..
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
+1
We've been waiting on this ever since karthik and wbaws discussion made it sound impossible
Just reported as a news tip for the portal
Thanks!!
New update coming for tool soon!!!
Its a great achievement .. future updates will be easy to go on for basic user. Btw thanks man. .
Sent from my Blade using Tapatalk 2
I've found that making four partitions and installing /data to mmcblk0p4 and /system to mmcblk0p3 helps with certain roms that have S2E configured.
I'm also trying to get it to boot two mounted loop filesystems instead, i installed SSRLS7 and GB-Gapps as per your instructions in the OP (just changed the partitions for installation and the updater-script and init.rc so that it would work) did a dd of the entire partitions to files on the sdcard and edited the init.rc like this:
Code:
on fs
# mount mtd partitions
chmod 777 /sbin/busybox
symlink /sbin/busybox /sbin/losetup
mount vfat /dev/block/mmcblk0p1 /mnt/sdcard
losetup /dev/block/loop0 /mnt/sdcard/multiboot/snow/system.img
losetup /dev/block/loop1 /mnt/sdcard/multiboot/snow/data.img
mount ext2 /dev/block/loop0 /system
mount ext2 /dev/block/loop1 /data
mount yaffs2 [email protected] /cache nosuid nodev
on post-fs
# ZTE_JCD_CTSCONFIG, 2011.05.03, BEGIN
mkdir /system/lost+found 0770
chmod 0770 /system/lost+found
# ZTE_JCD_CTSCONFIG 2011.05.03, END
# once system is setup, no need to modify /system , ZTE_BOOT_LIWEI_20110331
mount ext2 /dev/block/loop0 /system ro remount
I also copied busybox to /sbin in the ramdisk before letting the process finish and make bootsd.img
It doesn't work though and i have no idea why not. I've mounted the system.img and data.img files on the phone via the terminal to test if the procedure works and it does mount them just fine.
If anyone has any clue why this doesn't work then please tell me.
Dual boot on ideos x6
[email protected] said:
hello guys. This my dual booting project for our amazing zte blade!
What is this?
>this mod works on the basis of two scripts which are to be executed in the terminal emulator or script manager and a modified boot.img to boot the rom from sdcard instead of nand.
For advanced users only!!!
I will not be responsible for any bricked devices, damaged sdcards etc.
Do it at your own risk!!!
It is in alpha stage, so lot of work is still needed to make it more safer and convenient.
I will add this mod for more roms like cm10, paranoidandroid etc.
Downloads:
cyanogenmod9(konstakang)
boot.img - download
updater-script - download
cyanogenmod10
boot.img - download
updater-script - download
gapps::
Jelly bean gapps updater-script - download
tool:
Modify-boot - download
now no need to wait for me to mod your boot.img.mod your boot image for dual boot with this tool!!!
Guide for the tools is on the second post.
Thanks go to:
Sulthekk for guiding me towards right way.
Snap.it for giving me some mounting ideas.
All the people who have helped me(can't remember all names ).
And the big community to test it for me.
Scroll down to 2nd post for the whole guide...
Click to expand...
Click to collapse
dear friends is it possible on huawei ideos x6?
Plz reply
vimi93 said:
dear friends is it possible on huawei ideos x6?
Plz reply
Click to expand...
Click to collapse
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
QuantumFoam said:
Seriously? Dude can't u see this is the Blade forum. It will not work on any other phones
Click to expand...
Click to collapse
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
I stand corrected.
---------- Post added at 01:42 AM ---------- Previous post was at 01:37 AM ----------
Oh and btw, [email protected], check the xda portal. You're on the front page.
Congratulations
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
Will try it out on my LG P500 then!
thanks
Jinxxed said:
Actually, it'll work on any phone that runs android and has a working recovery that can be used to install boot.img and system files via an updater script.
It works fine on my Mini and Huawai G300.
Click to expand...
Click to collapse
thank you for the reply
TWRP-2.7.0.0 with "All-F2FS" support
NOTE: I don't have a Nexus 7 3G to test this. It should work.
I made this because a lot of people asked me. Please report back after you tried it.
I have modified the standard TWRP recovery to work with F2FS partitions.
This is for "All-F2FS" that mean that /system, /cache and /data are formatted with F2FS.
Keep in mind that this can work only with a compatible kernel and ROM.
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk at Samsung for the Linux operating system kernel. The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Download:
FormatPartitions.zip: Here
TWRP-recovery img: Here
Chagelogs:
- 08/05/14: Initial release
Here are some explanations. Read them
Recovery has the usual red back key to remember you that you are using a F2FS-recovery.
If wiping /system and /cache and making a factory reset from Wipe menu doesn't work, use FormatPartitions.zip. (<- READ THIS)
Instead wiping /data is fine within the wipe menu.
To switch your /system, /cache and /data partitions to F2FS follow instructions:
Keep in mind that you will lose all the files on the memory of your N7.
You need:
- Two files you can download above (img and FormatPartitions.zip)
- A ROM with "All-F2FS" support (Make your ROM with Convert To F2FS)
- GApps (i think you want PlayStore.) Usual GApps. Slim AiO work well.
Copy a ROM with "All-F2FS" support to your N7
Copy GApps to your N7
Copy FormatPartitions.zip to your N7
Reboot in bootloader
Flash this recovery with Fastboot (Maybe Flashify works too)
Reboot in new recovery
Flash FormatPartitions.zip
Reboot recovery (It's needed for some reasons..)
Flash ROM
Flash GApps
Go to Wipe Menu and Format Data (Not a simple wipe)
Reboot
Done.
It's easier than it seems
To restore partitions to stock:
- Download a standard TWRP
- Download RestorePartitions.zip
Flash RestorePartitions.zip (Untested)
Flash standard Recovery
Format Data in Wipe Menu
Hope i dind't any errors writing this down. I personally tested this procedure.
Enjoy.
Ah, about time. I'm gonna try this right away and report back. I've tested back and forth and f2fs does boosts our tilapia device performance quite a lot(according to the benchmarks results at least )
Wow, cool- truly missed all f2fs implementation in my tilapia, will try this ASAP, Thanks!
Hello you legolas, first thanks for sharing your wonderful work
I currently use f2fs 2.6.3 with support for data only, which had so far for tilapia.
I have a question to see if you can help me.
this recovery is worth for what we have f2fs only data? or I have to use a rom reformatted partitions in all f2fs?
I also see an app, which it seems the rom install on it, and it alone will reformat all partitions f2fs? is that easy?
thanks
edit:
I already am with f2fs in data, backup would have to do if I convert the data back to the rom "full f2fs"?
Hello bro. Tried to flash just a moment ago. I got stuck at Google logo, it's not even booting :s
Btw, I also notice cache is unable to be mounted. Any idea bro?
EDIT: My bad, I used the wrong boot image :silly: Now it's working
You guys can modify these scripts for free
figue/f2fs-scripts · GitHub - http://goo.gl/FOK6LO
I turned the tablet to f2fs ... and now I do not start the roms not know I had to convert them too. the problem is that now I can not install the restore partition because this new version 2.7.0 of recovery can not mount usb. with the above if I had problems, I had a flash drive prepared with kernels and roms. but not able to mount it. I do not want to use adb to put stock the tablet, you can help me?
Enviado desde mi Nexus 5 mediante Tapatalk
Fransis88 said:
I turned the tablet to f2fs ... and now I do not start the roms not know I had to convert them too. the problem is that now I can not install the restore partition because this new version 2.7.0 of recovery can not mount usb. with the above if I had problems, I had a flash drive prepared with kernels and roms. but not able to mount it. I do not want to use adb to put stock the tablet, you can help me?
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
I correct myself. I can mount the pendrive and have already restored the partitions. truth is that the recovery does not mount pendrive well sometimes, and you have to restart the recovery several times till you drop mount the pendrive.
but if it works, but not quite right
Can we use the modified Slimkat ROM for grouper (new kernel) slimkat 3.8 with this recovery?
Sent from my Nexus 7 using XDA Premium HD app
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
Working very well here :good:
Using SlimKat build 5 official. I flashed the recovery image with Flashify, rebooted into recovery, applied formatpartitions.zip, rebooted again, flashed ROM and Gapps.
I just had to format /data two times and reboot after the first "format" because it said "/data not found".
Can someone please post a step-to-step guide on how to get a rooted stock 4.4.3 image with F2FS file system? Or maybe a zip to flash?
Thanks
PS: a link on how to get the job done in very well accepted to!
Apologies for being (slightly?) off topic, but the opening page says this is to be used with suitable kernel and ROM. I'm having a hard time trying to find f2fs kernel/rom for my N7 3G (tilapia). Can anyone suggest (or report success with) which tilapia kernel(s) ROMs can be used use (ideally without the need for purchase of "Convert F2FS")...much appreciated.
questions regarding CM11 and Convert to F2FS
Does Convert to F2FS suppor CM11 for tilapia?
If I use Convert to F2FS the will I need a patched kernel? or does the app just do the job?
Regards
Stuck on bootlogo after doing all the steps, using a the latest PA beta converted with the app.. What to do now?
Can we use the latest TWRP tilapia recovery 2.7.1.0 to format the data, cache and system partitions to f2fs? also after we convert the ROM which kernel can we flash, will the stock kernel work?
Wow. It couldn't be easier.
I used ConvertToF2FS to modify the latest official SlimKat build (5961 at time of writing), and used your modified TWRP to install it on my 2012 Nexus 7 3G ("tilapia"), following your step-by-step instructions in the first post in the order given. It all worked first time.
Thanks! Yesterday my N7 was sluggish with the stock ROM; today it feels like a new device.
Thank you for the tutorial. I was wondering, is it possible to restore a non-F2FS nandroid backup if i flash a F2FS kernel right after restoring?
Loganberry said:
I used ConvertToF2FS to modify the latest official SlimKat build (5961 at time of writing), and used your modified TWRP to install it on my 2012 Nexus 7 3G ("tilapia"), following your step-by-step instructions in the first post in the order given. It all worked first time.
Click to expand...
Click to collapse
I've done the same and it works too but now I have some problems with 3G connection: everything is ok with WiFi connections but if I turn off WiFi and try to connect with 3G my Nexus reboots randomly. Sometimes after 2 or 3 minutes, sometimes after 10 but one thing is sure, I cannot use the tablet with 3G on.
Have you experienced something similar? The same happened with "pre-AllF2FS kernel" (Slimkat installed on a Ext4 fs with only data in f2fs format).
I've also tried to install the latest AOKP and Paranoid roms, converted with Convert To F2FS app, but they stuck during first booting animation...
Any help would be really appreciated! Thanks. :good:
Balza76 said:
I've done the same and it works too but now I have some problems with 3G connection: everything is ok with WiFi connections but if I turn off WiFi and try to connect with 3G my Nexus reboots randomly. Sometimes after 2 or 3 minutes, sometimes after 10 but one thing is sure, I cannot use the tablet with 3G on.
Have you experienced something similar? The same happened with "pre-AllF2FS kernel" (Slimkat installed on a Ext4 fs with only data in f2fs format).
I've also tried to install the latest AOKP and Paranoid roms, converted with Convert To F2FS app, but they stuck during first booting animation...
Any help would be really appreciated! Thanks. :good:
Click to expand...
Click to collapse
Me too. After converting CM11 M9 with convert to F2FS, and following all the steps in OP, stuck on bootanimation.
If I flash slimkat converted it works, but no 3G. After compare the update script of Slimkat original and converted i found thos 4 lines changed:
original lines
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/UDA", "/data");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
format("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system");
replaced for:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/mkfs.f2fs", "/dev/block/platform/sdhci-tegra.3/by-name/APP");
run_program("/sbin/busybox", "mount", "/system");
Then I download the original CM11 M9 and replaced the 4 lines in update script.
For the kernel, after flash the manually converted rom and GAPPs, then I flash M-Kernel compatible with All-F2FS.
It works for me!
Guys,
I have had an device impacted by TWRP 2.7.X build that created the problem of not being able to mount /data and sometimes(/cache & /system) partitions.
I have managed to make it run a ROM by using information from
http://forum.xda-developers.com/showthread.php?t=1869673 & http://forum.xda-developers.com/showthread.php?t=1843062.
the problem is that the mounts are not remaining permanent and my modified boot.img does not boot the devices. So i have to mount the partition manually during the boot process over a shell and then the device boots.
Need help from experts to do a kernel which can mount sdext partition and an updated recovery image which also mounts the sdext partition as /data so that roms can be flashed easily.
I will try and do a writeup of how i made it run.
Resurrecting Pyramid
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Jack Daniel's said:
Hi,
I followed your instructions but the Aroma installer always stops and the log shows this:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : Revelation
ROM Version : 1.0.3
ROM Author : SebastianFM
Device : HTC Sensation/XE/4G
Start at : Fri Jan 2 00:00:31 1970
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
line 44 col 70: syntax error, unexpected BAD
2 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
rmann said:
Pick the files from here and then try...
http://forum.xda-developers.com/htc-sensation/help/bricked-htc-corrupted-partitions-t2804222/page3
Click to expand...
Click to collapse
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Jack Daniel's said:
I tried that before.
Same result but it shows one error less.
Code:
...
line 4 col 1: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
Installer Error (Status 6)
Click to expand...
Click to collapse
Which recovery are you using... I have re-tested the script and it works ok for me.
rmann said:
Which recovery are you using... I have re-tested the script and it works ok for me.
Click to expand...
Click to collapse
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
antiziclon said:
I get the same exact error as Jack Daniel's.
I am using as recovery 4EXT Recovery Touch v1.0.0.5 RC5.
Click to expand...
Click to collapse
did you try to update the recovery to the latest version?
rzr86 said:
did you try to update the recovery to the latest version?
Click to expand...
Click to collapse
Just tested with v1.0.0.6 RC3 build 8, same error
antiziclon said:
Just tested with v1.0.0.6 RC3 build 8, same error
Click to expand...
Click to collapse
redownload the zip file
after that i am out of ideas
ok, I found out the issue.
The issue is on the encoding of the "updater-script" file.
It needs to be in Unix encoding. If you use Windows (as I do) when unzipping the Zip file or when creating a new file with a text editor, the encoding gets changed and it is not Unix encoding.
To solve it:
- Open the file in Notepad++.
- Go to Edit --> EOL Conversion --> UNIX
It will change the enf of lines to comply with Unix encoding. Then add the file to the Rom zip file and you are ready to go
Enjoy!
Successful Pyramid rescue
I have a sensation with corrupted emmc caused by TWRP, /data cannot be mounted.
I followed your instructions and addition re script encoding and successfully installed Revelation to partitioned sdcard.
Phone boots and works.
That's great, thanks.
I have some questions:
1. Is 512 MB sufficient for swap partition? What would be the optimal size?
2. My sensation is s-on unlocked, and I had to flash boot via fastboot after install, 4ext did not flash it despite smartflash option turned on. Is that normal?
2. Superuser does not seem to work, I have no root. I checked with root validator and I have su binary, superuser and busybox, but no root is given to apps that require it, su binary update fails, and there are no logs left in superuser to check (or I simply don't know where to look).
Thank you.
rmann said:
As mentioned in the earlier thread, my sensation got into trouble with TWRP 2.7 version and i was having trouble mounting /data, /system and /cache partitions.
I eventually got the /cache partition mounted by using mkfs.ext4 utility but could not get other and hence started working on a way to move both /data and /system partitions completly off SD card. Lot of people have already attempted that for other devices, feel free to go and check the threads linked in the post 1. Lets get started:
Assumptions: You have a sensation on which /data and /system partitions are an issue - not getting mounted / formatted etc. /cache is expected to be ok/working.
Requirements:
1) Your phone is booting and can go into recovery. Please get 4EXT recovery installed. You can download an img file from here
2) You have basic adb and fastboot setup on your machine(Win/Linux). Just google them out, if you dont have , there are plenty of tools out there.
3) Download Revelation 1.0.3 from here. you can choose any other ROM but i worked on this and have the boot image patched to look at /system from sd-ext.
4) download the two files attached with this thread.
Steps to recover:
1) Boot your phone in recovery. We will first get the SD Card set up. A Class 10 card is preferred, you will have a good feel on the phone.
2) Using 4EXT partition tool for sd card, create 2 sd ext partition in addition to your sdcard. I suggest first partition(which we will use as /system) to be more than 800 MB and second partition( which we will use as /data) to be more than 1024 MB.
3) Verify using the 'info' option of 4ext recovery that you can see sd-ext, sd-ext2 and sdcard partitions.
4) Extract the ROM you have downloaded using 7z/Winzip /winrar and replace the following files you have downloaded from this thread.
a) updater-script in /META-INF/com/google/android/ folder.
b) boot.img in /KERNEL folder.
5) Zip the file again and copy to your sdcard. Choose install from sdcard from the 4ext recovery menu. Choose default options in AROMA installer.
6) Reboot.
Hope your phone boots. If not, this is how you debug
Android will create a /proc/kmsg file when the kernel boots. So open two terminal(linux) windowds, in one, type this
Code:
adb pull /proc/kmsg
and in the second terminal(make sure the directory is same), type this:
Code:
cat kmsg | less
and then go through the error messages to see what is going wrong. If you can share your kmsg file created, I can try and help you debug.
Good luck !!!!!
Click to expand...
Click to collapse
Ok try to make that in unix
Extreme lag
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Extreme unuseful slow
With my sensation XE i also followed all steps. Revelation 1.0.3 is booting, but not to use at all, it stucks in every step, cant even receive a call, can't go to any menu. Pls someone help me out of here. Do I need a swap partition? Or are the partitions to small? sd-ext has 1024Mib; sd-ext2 1537Mib.
danilandroid said:
Hi there,
I followed all the staps, but when the rom was installed, it was very laggy and i experinced a lot of force closes. Is this because the partions are to small or because the sd is to slow EDIT: its a class 4 card?
Greetings,
Danil
Click to expand...
Click to collapse
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
probably you need a sdcard with high speed of w/r but i am not sure
Lag
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
danilandroid said:
I'm going to buy a sd-card class 10 and than I will try the same thing agian. I will report later.
@ rmann Btw thanks for the amazing thread, I was completely stuck and now my phone is alive again kinda.
Danil
Click to expand...
Click to collapse
rzr86 said:
probably you need a sdcard with high speed of w/r but i am not sure
Click to expand...
Click to collapse
dididoner said:
Hi Danil, could you solve the problem? I encounter same symptoms. My Phone: Sensation XE; Revelation 1.0.3. Cant use it at all , it boots but gets totally stuck. Have original sd, dont know the class. Greetings dididoner
Click to expand...
Click to collapse
So, I bought a class 10 card, revelation is running now!! At first start it was still very slowly an got stuck allover. But at second start it is running now! Thanks for that perfect thread!!:good:
I wonderd why vipers wont start the same way? When I try to boot it , 4ext recovery is starting rightaway with little delay!
Hi, when I got the same problem with /data, /cache and /system not mounting. I followed the steps from #2 post http://forum.xda-developers.com/showpost.php?p=55157092&postcount=2
and when I try to install from zip it says that the zip isn't meant to be flashed in recovery and it aborts the installation. First I tried renaming the new_boot.img you provided to boot.img but it's the same result.
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
Hi,
firstly I apologise if this is the wrong way to do this but I'm having trouble finding the info I need.
I have a TF700 (WW sku) running CWM and Omnirom 5.1.1
I want to install Katkiss Nougatella which requires TWRP Kang instead of CWM (I think).
I have downloaded TF700K_all_WW_USER_V5.0.4.17.raw from Asus' website as I believe this will restore the tablet to its original factory state and then I can proceed to install TWRP and Katkiss.
But I cannot install the .raw file, #fastboot devices# doesn't show my device, #adb devices# does but when I copy the .raw file to the device I cannot install it via CWM.
My laptop is running Linux Mint 18.1 I have tried running #sudo fastboot devices# but that doesn't work either...if anyone knows what I'm doing wrong I'd love to hear from them. Thanks in advance!
The short answer to your thread title is: You don't. :cyclops:
I have no idea what file you dug up there, but it could well be something for the TF700KL - or something entirely different, I have no idea. what I do know is that it is NOT firmware for the TF700T.
But you don't need to do that anyway.
All you need is:
1. Flash a current TWRP version (kang or official - doesn't matter as long as it is 2.8.+)
2. Format /data in TWRP
3. Convert /data to f2fs
4. Flash the rom, gapps and supersu if so desired.
Best would be if you did figure out how to get fastboot working in Linux. Should be a breeze but I can't help - I'm illiterate in Linux.
Then you could fastboot flash the latest TWRP 3.x from Teamwin's website: https://twrp.me/devices/asustransformerinfinityTF700T.html
If that fails Kang TWRP 2.8.x comes conveniently packaged into a flashable zip: https://forum.xda-developers.com/tr...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
To convert data to f2fs follow this: https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Enjoy
Hi,
Thanks a million for the prompt and detailed response, I will try this out as soon as I have time and report back with how it went!
blimey74 said:
Hi,
Thanks a million for the prompt and detailed response, I will try this out as soon as I have time and report back with how it went!
Click to expand...
Click to collapse
So installed the Kang TWRP zip with no problems and followed your instructions to format /data and change the file system to f2fs. Flashed Katkiss but for whatever reason it wouldn't boot up. Checked file system again and it was still ext4. Reformatted and switched to f2fs and this time Katkiss works. Tablet is reborn, really happy with it thanks again for the help :good: