Database Info

Factory Restore Question

I'm trying to do a factory restore of my gtab removing Clockworkmod and restoring it back to it's original out of box state (I'm not returning it, just want it back to stock for the moment). I downloaded nvflash, the drivers and the nvflash gtablet image and got it all setup. I run the batch file, everything goes through as it should, no errors. Yet when it finishes and the device reboots I still see it connecting to a wifi I had it connected to before (yet running TnT stock) and Clockworkmod is still on the device.
How exactly do I go about returning the tablet to stock if the nvflash isn't going to?

bekit's nvflash image from early November? I am pretty sure he had standard recovery in there, as I always had to replace it when I used it.

roebeet said:
bekit's nvflash image from early November? I am pretty sure he had standard recovery in there, as I always had to replace it when I used it.
Click to expand...
Click to collapse
I followed the instructions from this thread, by you So whatever you were saying to get, I got.
http://forum.xda-developers.com/showthread.php?t=861950

User data is retained with that setup - it's the only thing retained.
But I'm surprised that clockworkmod was still there. I had used this all the time and I always had standard recovery, afterwards. I actually had to re-run the nvflash later on to add clockworkmod. "part9.img" is the recovery partition - maybe bekit added cm later on that, and I have an old image.

roebeet said:
User data is retained with that setup - it's the only thing retained.
But I'm surprised that clockworkmod was still there. I had used this all the time and I always had standard recovery, afterwards. I actually had to re-run the nvflash later on to add clockworkmod. "part9.img" is the recovery partition - maybe bekit added cm later on that, and I have an old image.
Click to expand...
Click to collapse
Here is the output from the nvflash, let me know if something looks off. Not to mention I still have Superuser listed as an installed app. ><
How do I go about a FULL reset of this thing?
Code:
C:\nvflash>"nvflash.exe" --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0270308342a0d397
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: gtablet.bct
- 4080/4080 bytes sent
gtablet.bct sent successfully
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 1 0
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBT
creating partition: BLO
creating partition: MSC
creating partition: OGO
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 MBT please wait.. done!
Formatting partition 6 BLO please wait.. done!
Formatting partition 7 MSC please wait.. done!
Formatting partition 8 OGO please wait.. done!
Formatting partition 9 SOS please wait.. done!
Formatting partition 10 LNX please wait.. done!
Formatting partition 11 APP please wait.. done!
Formatting partition 12 CAC please wait.. done!
done!
sending file: part4.img
/ 2097152/2097152 bytes sent
part4.img sent successfully
sending file: part5.img
\ 131072/131072 bytes sent
part5.img sent successfully
sending file: part6.img
/ 4194304/4194304 bytes sent
part6.img sent successfully
sending file: part7.img
/ 16777216/16777216 bytes sent
part7.img sent successfully
sending file: part8.img
/ 33554432/33554432 bytes sent
part8.img sent successfully
sending file: part9.img
/ 16777216/16777216 bytes sent
part9.img sent successfully
sending file: part10.img
/ 16777216/16777216 bytes sent
part10.img sent successfully
sending file: system.img
\ 117292032/117292032 bytes sent
system.img sent successfully
Press enter to continue:

Your log looks correct to me (I've ran several restores on two different gtabs over the past few days). The only thing I wonder is if you got the right image(s) to begin with. I'm using bekit's restores from early November and not the ones with the "46" in the name (those are from later November).

part9.img is recovery. If you grab a recovery.img from stock and replace part9.img with that, you should have stock recovery after flashing.
User data is just a post-flash user data wipe and you are done.

markgolly said:
Your log looks correct to me (I've ran several restores on two different gtabs over the past few days). The only thing I wonder is if you got the right image(s) to begin with. I'm using bekit's restores from early November and not the ones with the "46" in the name (those are from later November).
Click to expand...
Click to collapse
Yea the one I got is named nvflash_gtablet_2010110500.zip, didn't grab the one with 46 in the name.

Seems you are doing everything right. I dunno - my restore has worked every time.
Anyway, I've got one of my gtabs in a boot-loop right now, so I need to do another restore (not using clockwork yet - one step at a time... ). I'll do the restore and repost once I am through it.
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.

Well, chalk that up to a learning experience - seems I can't get out of a boot-loop via a TnT restore. Time to actually put cwm on....

markgolly said:
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.
Click to expand...
Click to collapse
That would make sense then =)

i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.

That's exactly what I was gonna suggest!

madsquabbles said:
i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.
Click to expand...
Click to collapse
Sounds good, thanks a ton for the help guys.
So is anyone aware of what this update Viewsonic keeps talking about on Twitter is going to be?

Check out my post in the Developmet Section called "From Viewsonic"

madsquabbles said:
i used update-smb_a1002-3053-user.zip flashed with cwm.
after reboot i restored the device from the system menu. it reflashed the original recovery and i don't see su anywhere.
Click to expand...
Click to collapse
Stupid question, but what do you mean you restored from the system menu?

Can't see the micro SD card in my desktop
I inserted a 16GB SD card and is acknowledged in the tablet' storage, but once I connect the tablet with my desktop, the tablet shows as a removable disk with
13 GB. Why ???
I'm trying to install TNT_Lite and Flash.After downloading ClockworkMod I couldn't unzip the file to the microsd card because the SD card was not visible and couldn't locate it.
Can the "DiskCacheIndex1234.temp files be safely deleted?

markgolly said:
Seems you are doing everything right. I dunno - my restore has worked every time.
Anyway, I've got one of my gtabs in a boot-loop right now, so I need to do another restore (not using clockwork yet - one step at a time... ). I'll do the restore and repost once I am through it.
Oh, one last thing - I think bekit put Superuser on before he ran off the images. When I do my restore, it already has Superuser, too.
Click to expand...
Click to collapse
Hi,
Sorry to jump in, but what is "SuperUser'? I notice it's on my Gtab. Does it get installed as part of z4root?
Thx,
Jim

StirCwazy said:
Stupid question, but what do you mean you restored from the system menu?
Click to expand...
Click to collapse
if you go to settings, security, and do a factory data reset. this will wipe everything and restore the original recovery.

madsquabbles said:
if you go to settings, security, and do a factory data reset. this will wipe everything and restore the original recovery.
Click to expand...
Click to collapse
OK sorry, I know that one just didn't know if you were talking about that or something else I wasn't familiar with on the gtab.

No longer able to install ICS, stuck on HC.

I recentlly attempted to update my P6800 from ICS LQ1 to LQ2 via Mobile Odin.
The result was a tablet that would only boot as far as the Samsung Logo and boot chime and would hang there.
Many attempts were made to clear caches, reset data via both stock recovery and CWM versions 5 .5 and even 6 with no change.
Tried using PC Odin to go back to LQ1 and has the same exact results. suspected an error in a partition and used a stock p6800 .pit along with stock LQ1 .tar and still have same problem. Cm9 and 10 gives same results.
However I am able to install stock Honeycomb via PC Odin which seems to work fine except CWM backup is unable to restore a backup and hangs just after starting.
I still suspect a bad partition somewhe but dont see a way of verifying this. Have read many posts both here and in the Galaxy Note forum but none have solution that has worked for me.
Does anyone know if the .pit file actually recreates your partitions? Or does someone have instructions on how I can manually do this via adb shell? Specifically the cache, data and system partitins.
Any help is appreciated.

Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted

Astrix Ashburn said:
Try this.
- In HC use Locerra' CWM v5.x
In recovery:
- Clear cache.
- Dalvik.
- Data reset.
- Flash rom: http://www.androidtablets.net/forum/showthread.php?p=223379
- Fix permission.
- Reboot.
If stuck after reboot...boot to cwm recovery again.
- Full wipe.
- Reboot and wait a while.
Hope it help and keep us posted
Click to expand...
Click to collapse
followed above and got non stop rebooting.
wonder if ics uses a different partition structure.

While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium

I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.

zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
This has been tried several times with the same results each time. Boot loops.
Thats what I don't get, HC works but as soon as ICS is put on I get /Data partition errors. More specifically /data cannot be mounted.

Josvaz said:
While at recovery do u have testbend?
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Yes , in stock recovery I do. Was not sure what that did.

Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)

kable said:
Looking at my partitions via adb it looks like /dev/block/mmcblk0p10 is empty. Perhaps this is the issue? If so, does anyone know how to recreate?
~ # parted /dev/block/mmcblk0p10
parted /dev/block/mmcblk0p10
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p10
Welcome to GNU Parted! Type 'help' to view a list of co
(parted) print
print
print
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted) print list
print list
print list
Error: /dev/block/mmcblk0p10: unrecognised disk label
(parted)
Click to expand...
Click to collapse
its look like the /data partition is screwed... try running e2fsck -fDC0 /dev/block/mmcblk0p10 to check the partition...

this is the EXACT problem i was having. here's what i did to fix it*:
disclaimer: i am waiting for HC filefactory slow-*ss download to take another F*CKING hour.... so i have yet to FULLY recover my tab... BUT i think i'm onto something.
i COULD get a full flash from odin with no hanging up...then i corrupted my /data and /system partition... don't ask me how: i knew to stay away from wiping with 3e stock ICS recovery, i used cwm 5.8.1 temporary zip that i flashed from stock recovery, IT messed up everything.... then i started trying to follow androguide.fr's revive from superbrick guide. (will post link later)
after days and days and DAYS of frustration trying to remove and remake /data and /system, /cache eventually corrupted. i was ready to blow my brains out.... just on a whim, without having read any of this stuff, i:
1) flashed the original pit file,
2) flashed ATO-ICS firmware
3) flashed CWM 6.0.1.1
4) wiped /data /factory /dalvik SUCCESSFULLY!!!!
5)....after wiping, e2fsck checking and getting clean partitions with every ICS CM9/10 rom i could find, and STILL getting stuck on the boot animation...
i finally read in a gNote forum that people with this problem were flashing back to GB (original firmware for the Note) and solving their problem, then they could go back to ICS... if you can't i'm SORRY!!! but i'm even just trying to get ANYTHING to boot at this point. YOU'RE POST GIVES ME HOPE!!!!
so try: flashing the original pit file, flash cwm 6.0.1.1, wipe data/factory reset, wipe dalvik cache, reboot and JUST do the e2fsck section of the NOOB friendly guide to recovering your tab from superbrick. --will post link later. that should at LEAST get rid of the corrupt filesystem. e2fsck every partition that you were having trouble with.

zorbakun said:
I faced your situation before, here's what you should do
1 Install official HC 3.2 using PC odin
2 boot in to HC stock recovery
3 factory reset / Data & Cache wipe
4 do full boot into HC till you see your desktop
5 use your PC odin or Mobile odin pro to Install ICS over HC
6 Now you should be good to go.
Note if you can successfully boot into HC then your paritions are good, dont mess with them.
Click to expand...
Click to collapse
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.

nutley said:
Thank you for this, it got me working again. I didnt think to do any wipes after going back to stock HC but it was exactly what it needed.
Click to expand...
Click to collapse
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .

Fluxcore said:
You should change your topic by adding ( Resolved ) to it so others know you got it figured out .
Click to expand...
Click to collapse
It's not my topic. Just saying thanks as it sorted my own issue out

[Resolved] Resize recovery partition on Lenovo K30W

I want to increase size of recovery partition on Lenovo K30W so I can flash larger recovery image created for Lenovo A6000. I have devised a way, but I would be grateful if someone could look it over and spot possible flaws.
Here is the current partition table.
Code:
Model: MMC Q8XSAB (sd/mmc)
Disk /dev/block/mmcblk0: 15634268160B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 134217727B 67108864B fat16 modem
2 134217728B 134742015B 524288B sbl1
3 134742016B 135266303B 524288B sbl1bak
4 135266304B 136314879B 1048576B aboot
5 136314880B 137363455B 1048576B abootbak
6 137363456B 137887743B 524288B rpm
7 137887744B 138412031B 524288B rpmbak
8 138412032B 138936319B 524288B tz
9 138936320B 139460607B 524288B tzbak
10 139460608B 139984895B 524288B hyp
11 139984896B 140509183B 524288B hypbak
12 140509184B 141557759B 1048576B pad
13 141557760B 143130623B 1572864B modemst1
14 143130624B 144703487B 1572864B modemst2
15 144703488B 145752063B 1048576B misc
16 145752064B 145753087B 1024B fsc
17 145753088B 145761279B 8192B ssd
18 145761280B 156247039B 10485760B splash
19 201326592B 201359359B 32768B DDR
20 201359360B 202932223B 1572864B fsg
21 202932224B 202948607B 16384B sec
22 202948608B 219725823B 16777216B boot
23 219725824B 1830338559B 1610612736B ext4 system
24 1830338560B 1863892991B 33554432B ext4 persist
25 1863892992B 1998110719B 134217728B ext4 cache
26 1998110720B 2014887935B 16777216B recovery
27 2014887936B 15634251263B 13619363328B ext4 userdata
Luckily, recovery and data partition are next to each other. Here is the procedure, please tell me if it is viable.
1. Boot into recovery
2. Create nandroid backup of data partition
3. Make sure that data partition is unmounted in recovery
4. Using parted, delete recovery and data partitions, and then recreate them with new sizes
5. Format data partition
6. Make sure that "use rm -rf instead of formatting" is enabled in recovery settings
7. Restore nandroid backup
8. Flash new recovery
9. Reboot
These are the commands I would use:
Code:
adb shell
parted /dev/block/mmcblk0
unit b
rm 27
rm 26
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
name 26 recovery
name 27 userdata
quit
mke2fs -t ext4 /dev/block/mmcblk0p27

As there were no replies, I took a risk and went ahead with resizing the partitions. The described procedure worked without problems.

Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158

addict1337 said:
Could you make a guide on how you did this exactly for noobs?
I understand that you posted the steps you used, but i'm not familiar with what you did.
Also, what rom are you using currently?
I got a rom working for this phone, It works well, but is not ideal.
https://forum.xda-developers.com/general/help/k3-note-question-k30w-t3531158
Click to expand...
Click to collapse
Well, making an even more detailed guide will take some effort. I'll do it when I find the time.
I am using this ROM: https://forum.xda-developers.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184
It's great, but I do have problems with updating it. Hopefully it'll be resolved soon.

Here is a more detailed procedure. However, if you are not familiar with Linux command line and the Android partition layout, I strongly recommend that you stay away from this.
First, you need Android platform tools from here. Download for your platform (I am going to assume Windows) and extract to a folder of your choosing (for example C:\Android).
You also need parted utility, download from here. It's best to extract it to the same folder as Android platform tools.
Next, open Windows command prompt and go to the platform tools folder. The easiest way to do it is to open the folder in Windows Explorer, right click in the empty space while holding shift and choose "Open command window here". Reboot your device in recovery mode and connect it to the computer USB port.
While in recovery, make a backup of your data partition.
Copy the new recovery image to external SD if you have one, or else to internal memory. You can do it using Windows Explorer.
Copy parted utility to the device.
Code:
adb push parted /.
Next, enter device shell.
Code:
adb shell
Make parted executable.
Code:
chmod a+x parted
Start parted utility.
Code:
./parted /dev/block/mmcblk0
Be extremely careful from now on. Every parted command is executed immediately, so if you type something wrong, you could brick your device.
Change size unit to byte.
Code:
unit b
Print your current partition layout. If it's not the same as in my original post, abort now as you'll mess things up.
Code:
p
Remove recovery and data partitions.
Code:
rm 27
rm 26
Recreate partitions with new sizes (recovery is now 32MB instead of previous 16MB).
Code:
mkpart primary 1998110720 2031665151
mkpart primary 2031665152 15634251263
Give partitions the same names as before.
Code:
name 26 recovery
name 27 userdata
Exit parted utility.
Code:
quit
Format the data partition.
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
Make sure that "use rm -rf instead of formatting" is enabled in recovery settings. This may not be necessary, but I've seen it in some tutorial, and it can't hurt.
Restore data partition from backup.
Flash new recovery using current recovery (go to install and choose "install image").
Reboot and hope for the best.

Thank you very much
I will give it a try.

All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen

addict1337 said:
All worked well, however I am never able to boot into recovery from my phone itself (before i attempted this, and after).
I always need to use my pc/usb to boot into recovery via a batch file.
Even if I install recovery from the recovery I just booted.
Getting into recovery is holding volume up and the power button right?
I installed the software you mentioned, however it is stuck at the bootscreen
Click to expand...
Click to collapse
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.

CrazyNik said:
To get into recovery, you need to keep BOTH up and down volume keys, and then power on. After a few seconds, you can release volume keys.
As far as the ROM is concerned, make sure you wipe data and cache before installing it. That's all I can think of.
Click to expand...
Click to collapse
Thanks.
I managed to install a CWM recovery for A6000, witch is working fine now (32MB)
I had problems with GPS on my Cyanongenmod Rom modified for K30-W, but after installing gapps all is working fine now.
Thank you for your help!

I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.

addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
You must use TWRP 3.1.0, but even with it, RR 20170403 will not install on K30W firmware, I don't know why. I managed to install it by flashing A6000 firmware first. I will post the tutorial on RR thread when I find the time.

addict1337 said:
I hate to bother you any more, but I would like to use the same rom you are using, however I can't get it to flash.
I got TWRP 2.8.6.1 working (any other version I tried will not work)
I wipe DATA DALVIK and CACHE
When I try to install: 20170403-a6000-Official it gets stuck on:
Patching system image unconditionally....
I am able to flash Cyanogenmod, but that's a much older version.
If you could help me with what I am doing wrong, that would be much appriciated.
There are not many people running this phone.
I am also interested in the recovery you are using.
Click to expand...
Click to collapse
I've posted the tutorial here.

CrazyNik said:
I've posted the tutorial here.
Click to expand...
Click to collapse
Awesome, I was waiting for it
Thank you very much.

[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

[RECOVERY][Testing][amami] TWRP 3.2.1

This one is deprecated! Please use this one instead.
Some words about...
This recovery is for amami - Sony Z1 compact.
I'm opening this thread because I was looking for an up-to-date version of TWRP recovery. After a long search i found this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
Why am I opening this thread then?
Well,
I want to built TWRP from newest android sources (not like cm12.1 that is used in the link above )
and I want to get a deeper understanding of sony's partition layout (especially concerning recovery).
I just read a comment about the possibilities to store a recovery on our device, but unfortunately I couldn't find it again. It was something like that:
fastboot flash boot boot.img (recovery uses same kernel but different ramdisk, common sony approach, after kernel boot-up hardware keys decide which ramdisk to load)
fastboot flash FOTAKernel recovery.img (recovery is stored on extra partition with own kernel and own ramdisk)
fastboot flash recovery recovery.img (recovery is stored on extra partition with own kernel and own ramdisk)
So I stumbled over https://forum.xda-developers.com/showpost.php?p=73575131&postcount=130 and followed the instruction. But an inspection of the partitions leads me to the following assumption: either the thing doesn't worked - or fastboot flash FOTAKernel recovery.img and fastboot flash recovery recovery.img are doing the same thing.
The partitions afterwards:
Code:
major minor #blocks name #label
254 0 524288 zram0
179 0 15267840 mmcblk0
179 1 2048 mmcblk0p1 TA
179 2 512 mmcblk0p2 sbl1
179 3 256 mmcblk0p3 s1sbl
179 4 64 mmcblk0p4 dbi
179 5 512 mmcblk0p5 aboot
179 6 512 mmcblk0p6 rpm
179 7 512 mmcblk0p7 tz
179 8 512 mmcblk0p8 alt_sbl1
179 9 256 mmcblk0p9 alt_s1sbl
179 10 64 mmcblk0p10 alt_dbi
179 11 512 mmcblk0p11 alt_aboot
179 12 512 mmcblk0p12 alt_rpm
179 13 512 mmcblk0p13 alt_tz
179 14 20480 mmcblk0p14 boot
179 15 10240 mmcblk0p15 ramdump
179 16 16384 mmcblk0p16 FOTAKernel
179 17 32 mmcblk0p17 DDR
179 18 16384 mmcblk0p18 lta-label
179 19 1536 mmcblk0p19 modemst1
179 20 1536 mmcblk0p20 modemst2
179 21 1536 mmcblk0p21 fsg
179 22 8192 mmcblk0p22 apps_log
179 23 2379776 mmcblk0p23 system
179 24 204800 mmcblk0p24 cache
179 25 12589039 mmcblk0p25 userdata
179 32 4096 mmcblk0rpmb
1 block == 1 kByte == 1024 Bytes
--> get actual size in Byte: #blocks*1024 Bytes
How to install
unlock bootloader
fastboot flash FOTAKernel recovery.img (this should work in any case)
OR
fastboot flash recovery recovery.img (if my findings are correct, this should only work with new bootloader from here: https://forum.xda-developers.com/showpost.php?p=73575131&postcount=130 )
remove USB cable
press and hold Vol. down and power, if device vibrates release power and keep Vol. down holding. That's it.
Feel free to test and give comments on my thougts. :silly:
Credits:
SpritCroc (and AICP team)
munjeni (new bootloader)
Micha-Btz
charles1018
Sources:
my manifest: https://github.com/115ek/manifest
forked device tree: https://github.com/115ek/device_sony_amami
original device tree and kernel sources: https://github.com/aicp
TWRP: https://github.com/omnirom/android_bootable_recovery

One thing I forgot:
The recovery.img is packed into a .zip file. Please unpack first - it's not flashable via recovery.
I saw threads with a download section. Is this only possible with devDB threads?

Flashed, booted up fine.
Seems to be working okay

USB-OTG Not working for me.

roland080 said:
USB-OTG Not working for me.
Click to expand...
Click to collapse
Well, for me it worked without problems.
What isn't working in detail? What filesystem does your OTG device uses? What exactly did you do to mount and check for the files on the USB drive?

115ek said:
Well, for me it worked without problems.
What isn't working in detail? What filesystem does your OTG device uses? What exactly did you do to mount and check for the files on the USB drive?
Click to expand...
Click to collapse
My Pendrive is formatted as NTFS. A click on Select Storage and USB OTG "says" 0MB. The Pendrive is works fine in TWRP 3.1.1.

roland080 said:
My Pendrive is formatted as NTFS. A click on Select Storage and USB OTG "says" 0MB. The Pendrive is works fine in TWRP 3.1.1.
Click to expand...
Click to collapse
Hmm. Okay. I think I didn't include ntfs support. I'll have a look on this next build.
But did you set the check mark at USB OTG under mount menu point?
Do you also have an USB drive with fat format to test?
Thanks for the info

115ek said:
Hmm. Okay. I think I didn't include ntfs support. I'll have a look on this next build.
But did you set the check mark at USB OTG under mount menu point?
Do you also have an USB drive with fat format to test?
Thanks for the info
Click to expand...
Click to collapse
Yes, I do. Formatted as FAT32 but still not working.
Edit: Clicked on the Circle, but nothing happened.

I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way

pipyakas said:
I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way
Click to expand...
Click to collapse
you can always upgrade to a new TWRP inside TWRP itself! You can flash a new img file within twrp. You need to change the filter from zip to img though.

jho55 said:
you can always upgrade to a new TWRP inside TWRP itself! You can flash a new img file within twrp. You need to change the filter from zip to img though.
Click to expand...
Click to collapse
I'm already on the latest version of TWRP given in this post - although it was through flashing in TWRP 2.8.7.0 included in a pre-rooted stock rom. I'm just not being able to boot into twrp from the rom itself - only via hardware buttons

pipyakas said:
I can only boot into TWRP by shutting down the phone and use vol- and power on at the same time, using the reboot to recovery option and adb reboot recovery command doesnt work. Is there any workaround for this? Previously I recall booting into 2 different twrp version by hardware buttons/software command that way
Click to expand...
Click to collapse
The recovery you enter while holding Vol- and power is the one stored on FOTAKernel partition (that is the "real" one, it has got own kernel and ramdisk).
The recovery you enter with power and then Vol+ when LED lights up is the combined one. It is stored inside the boot partition.
The normal case is: kernel stored in boot.img starts and checks for user input. If you do so, a special recovery ramdisk gets loaded. Otherwise the "normal" ramdisk is loaded up.
Entering the recovery from inside the android system is a problem of your ROM. The system has to set a flag that survives reboot. Then the bootloader examines this flag and does the according operation.

roland080 said:
Yes, I do. Formatted as FAT32 but still not working.
Edit: Clicked on the Circle, but nothing happened.
Click to expand...
Click to collapse
There is still one thing you can test: enable/disable MTP. You can find this option under the mount menu point, too

115ek said:
There is still one thing you can test: enable/disable MTP. You can find this option under the mount menu point, too
Click to expand...
Click to collapse
Thank you! Now working with FAT32 Pendrive.

roland080 said:
Thank you! Now working with FAT32 Pendrive.
Click to expand...
Click to collapse
Cool
Can you test with ntfs, too? Only if that doesn't create circumstances

115ek said:
The recovery you enter while holding Vol- and power is the one stored on FOTAKernel partition (that is the "real" one, it has got own kernel and ramdisk).
The recovery you enter with power and then Vol+ when LED lights up is the combined one. It is stored inside the boot partition.
The normal case is: kernel stored in boot.img starts and checks for user input. If you do so, a special recovery ramdisk gets loaded. Otherwise the "normal" ramdisk is loaded up.
Entering the recovery from inside the android system is a problem of your ROM. The system has to set a flag that survives reboot. Then the bootloader examines this flag and does the according operation.
Click to expand...
Click to collapse
Well then that "flag" surely can trigger something, because I do remember booting into a different twrp version from within the rom than the "real" one. Also, the one booted from the rom always seem to have much worse brightness, if that's saying something. I cant exactly repeat the process to get that recovery either

115ek said:
Cool
Can you test with ntfs, too? Only if that doesn't create circumstances
Click to expand...
Click to collapse
No problem with FAT32! Works fine.
Edit: Sorry I tested with TWRP 3.1.0 :C I need to flash TWRP 3.2.1
Edit 2 Flashed TWRP 3.2.1, clicked on Mount, Enable MTP, then clicked on USB OTG but nothing happened. Still not works with FAT32.

pipyakas said:
Well then that "flag" surely can trigger something, because I do remember booting into a different twrp version from within the rom than the "real" one. Also, the one booted from the rom always seem to have much worse brightness, if that's saying something. I cant exactly repeat the process to get that recovery either
Click to expand...
Click to collapse
Yes, that sounds like your reboot-to-recovery option boots to the recovery included in boot.img, which came along with the installation of your ROM.
At the end a system call passes a "recovery" argument to the kernel restart function. This restart function then sets the kernel start parameters to the recovery-ramdisk and restarts the kernel (warm reboot).
If you want to enter the "real" recovery you have to explain the bootloader that he should load the kernel from FOTAKernel partition instead of boot partition.
You can google for more details, but there's not so much info unfortunately
https://stackoverflow.com/questions/5472761/how-does-the-bootloader-pick-up-the-command-after-a-restarting-system-with-comm
Nevertheless I'll look into it - it's really interesting. Another thing that's on my list is decryption support for TWRP...

roland080 said:
No problem with FAT32! Works fine.
Edit: Sorry I tested with TWRP 3.1.0 :C I need to flash TWRP 3.2.1
Edit 2 Flashed TWRP 3.2.1, clicked on Mount, Enable MTP, then clicked on USB OTG but nothing happened. Still not works with FAT32.
Click to expand...
Click to collapse
Try to disable MTP

115ek said:
Try to disable MTP
Click to expand...
Click to collapse
Not working. Hope you fix that later.