Database Users

2.37 has been rooted!

I have tested it on my phone, it works perfect!
SORRY FOR MY BAD ENGLISH. I HAVE THE CHINESE WORDS ON MY PHONE, SO I DO NOT KNOW WHAT THE ENGLISH EXACTLY IS. I TRANSLATED THEM ON MYSELF, IF YOU DONOT UNDERSTAND MESSAGE ME.
1, you should FLASH RECOVERY TO YOUR PHONE, and that will not be talked here. lots of threads can tell you how to do it.(I HAVE PLACED ONE WAY TO DO IT ON THE SECOND PAGE)
2, unpack "root.rar" into your DISK C, and the folder must be "root"
3, now mark the "debug mode"( you can find it in application Settings) , connect your phone to your computer( just CHARGING MODE)
4, press win+R on your PC keyboard, and type in "cmd".
5, now we can see dos commond, you should type in the following commond one by one.
CD C:\root
adb shell
reboot recovery
6, now your phone should reboot into recovery. select mounts and storage. there select 3 items( mount /system, mount /data, mount /sdcard)
7, disconnect your phone, and connect it again. then type the following commonds into your PC. NOTE THE SPACE
adb push su /sdcard/su
adb push superuser.apk /sdcard/superuser.apk
adb push psneuter /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter
adb shell
8, if you can see "~#" on your screen, you have made it. I have encountered a error on the 5th commond but it seems like ok, afterall I have been rooted.
9, you still have some commond to type.
cp /sdcard/su /system/bin/
cp /sdcard/Superuser.apk /system/app/
ln -s /system/bin/su /system/xbin/su
chmod 06555 /system/bin/su
10, now on your phone you should still have the recovery, unmount the /system, data, sdcard.
11, reboot your phone, and enjoy it!
Thanks very much for the help of pxw816, without him I still in dark.

is this for real? :\

adkz said:
is this for real? :\
Click to expand...
Click to collapse
Sorry for forgeting to upload the file. It works on the chinese rom, I think all rom can be rooted this way...

Anyone willing to see if this would work on a Telus Desire HD with 2.43?

Anyone tried this ?

I'm quite sure this only works on the Chinese ROM. But I might give it a try

I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.

torkaberry said:
I have tried this, but it does not seem to work with my version. The recovery boot doesn't seem to work correctly, I believe this is the problem.
Click to expand...
Click to collapse
Same problem, booting into recovery just shows this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think this is the second method posted that only works in China

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Seems like the chinese OTA's have an unpatched exploit, maybe one of the mods would like to change the title of this thread.

hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help

CuBz90 said:
Same problem, booting into recovery just shows this...
I think this is the second method posted that only works in China
Click to expand...
Click to collapse
Hey guys, you cannot use the official recovery, flash a recovery that is usually used to install a rom...My recovery is 3.0, I don't know if 2.0 is ok....

evanbigfan said:
hey man,u say u got 2.37 rooted and then when i looked at the first line u said u need to flash recovery
u can't flash recovery if u don't have s-off so u have to be rooted in the first place,
i guess u already have a rooted device with s-foof so u could install recovery
any way thanks for ur help
Click to expand...
Click to collapse
I'm not quite sure about that, for people who do not have a recovery may place the following file on your TF card( DO NOT PLACE IT INTO ANY FOLDER!), and shut down your phone(I MEAN COMPLETELY OFF, OR YOU CAN PULL OUT YOUR BATTERY). Then try to press the volume down button and the switch button at the same time to start your phone. See if the recovery can be installed automatically or not. if not, I'm afraid you have to downgrade to root and get a S-Off. If you do not know how to downgrade, post here, and see if i can give you any help or not.

This will never work, you will need Root and S-OFF to flash recovery. (thanks hawks556 for pointing that out)
closed.

NXT-L29 Partitions

External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dd command for backup partitions except /system and /userdata
dd if=/dev/block/platform/hi_mci.0/by-name/vrl of=/external_sd/backup/vrl.img
dd if=/dev/block/platform/hi_mci.0/by-name/vrl_backup of=/external_sd/backup/vrl_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_lpm3 of=/external_sd/backup/fw_lpm3.img
dd if=/dev/block/platform/hi_mci.0/by-name/frp of=/external_sd/backup/frp.img
dd if=/dev/block/platform/hi_mci.0/by-name/fastboot of=/external_sd/backup/fastboot.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_factory of=/external_sd/backup/modemnvm_factory.img
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/external_sd/backup/oeminfo.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash of=/external_sd/backup/splash.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/external_sd/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/external_sd/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/external_sd/backup/modemnvm_system.img
dd if=/dev/block/platform/hi_mci.0/by-name/secure_storage of=/external_sd/backup/secure_storage.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvm of=/external_sd/backup/3rdmodemnvm.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodemnvmbkp of=/external_sd/backup/3rdmodemnvmbkp.img
dd if=/dev/block/platform/hi_mci.0/by-name/persist of=/external_sd/backup/persist.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved1 of=/external_sd/backup/reserved1.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_om of=/external_sd/backup/modem_om.img
dd if=/dev/block/platform/hi_mci.0/by-name/splash2 of=/external_sd/backup/splash2.img
dd if=/dev/block/platform/hi_mci.0/by-name/misc of=/external_sd/backup/misc.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_update of=/external_sd/backup/modemnvm_update.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery2 of=/external_sd/backup/recovery2.img
dd if=/dev/block/platform/hi_mci.0/by-name/reserved2 of=/external_sd/backup/reserved2.img
dd if=/dev/block/platform/hi_mci.0/by-name/teeos of=/external_sd/backup/teeos.img
dd if=/dev/block/platform/hi_mci.0/by-name/trustfirmware of=/external_sd/backup/trustfirmware.img
dd if=/dev/block/platform/hi_mci.0/by-name/sensorhub of=/external_sd/backup/sensorhub.img
dd if=/dev/block/platform/hi_mci.0/by-name/fw_hifi of=/external_sd/backup/fw_hifi.img
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/external_sd/backup/boot.img
dd if=/dev/block/platform/hi_mci.0/by-name/recovery of=/external_sd/backup/recovery.img
dd if=/dev/block/platform/hi_mci.0/by-name/dts of=/external_sd/backup/dts.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem of=/external_sd/backup/modem.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dsp of=/external_sd/backup/modem_dsp.img
dd if=/dev/block/platform/hi_mci.0/by-name/modem_dtb of=/external_sd/backup/modem_dtb.img
dd if=/dev/block/platform/hi_mci.0/by-name/dfx of=/external_sd/backup/dfx.img
dd if=/dev/block/platform/hi_mci.0/by-name/3rdmodem of=/external_sd/backup/3rdmodem.img
dd if=/dev/block/platform/hi_mci.0/by-name/cache of=/external_sd/backup/cache.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest0 of=/external_sd/backup/hisitest0.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest1 of=/external_sd/backup/hisitest1.img
dd if=/dev/block/platform/hi_mci.0/by-name/cust of=/external_sd/backup/cust.img
dd if=/dev/block/platform/hi_mci.0/by-name/hisitest2 of=/external_sd/backup/hisitest2.img
Click to expand...
Click to collapse

Cheers for that. I'm on the al10 and was thinking of force flashing all partitions from the international model just to see if it worked
Sent from my NEXT using Tapatalk

sure works

How would one force flash all partitions? I have the L29 OTA's and I am trying to get my L10 debranded with fastboot as I want to keep stock recovery/unrooted/etc.

u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually

jbmc83 said:
u mean u have the AL10? theres YET no option to completely debrand it AND receive OTA updates for the "other" model ure trying to flash it to (in this case, L29)
supposedly, ud have to flash the oeminfo and make changes to build.prop and other system files, as well as flashing all partitions of a proper stock L29 firmware. people are still trying to figure things out.
in the meantime, its no biggie to crossflash roms to at least get the "other" experience manually
Click to expand...
Click to collapse
Yeah, thats what I have been doing. But there are so many .img files in the OTA's that I am not able to flash with fastboot, so I feel like I am missing stuff.

well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot

jbmc83 said:
well the number of partitions shouldnt be a problem, it would just take a while to type all commands in fastboot
Click to expand...
Click to collapse
I tried flashing them all once. Most of them failed with command not supported. The only ones that work are boot cust cache system modem recovery and a couple others.

hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?

jbmc83 said:
hm and the erecovery option with update.app in dload folder probably shows u incompatible system , hm?
Click to expand...
Click to collapse
Yeah.

Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help

jarod27 said:
Hi
I try to put my mate 8 AL10 in full L29.
I have extracted all data from update and i have flashed cache, cust, system and oeminfo, all work perfectly.
The phone is recognized in L29 but when i plug it in usb mode developer, it's write Huawei NXT-AL10.
What i need, to pass it in full L29 version ?
Flash crc ? boot ? recovery2 ?trustfirmware ?
thanks for your help
Click to expand...
Click to collapse
it could be an idea to get all partition from L29 with "dd if=/dev/block/partitonX of=partitionX.img" and flash it on L10?
can you chek yout custom.bin? is in /data partition. open it with root explorer as text file

no custom.bin in data folder

jarod27 said:
no custom.bin in data folder
Click to expand...
Click to collapse
ok.
do you think that clone all partition from l29 could be a good idea?

maybe
you can do this ?

no, I have not yet bought the mate 8. I 'm studying the situation because if I take it , I take al10 for the 64gb storage. But i prefer the international software because it has a reduced sar value.
the hardware is the same.
I have not bought it yet because I have a doubt about the size: I would not like it's too big to carry in pocket and to use it with only one hand
i thinking

ok

Did someone already tried to crossflash all the partitions?
How would you do that?
Fastboot ist not accepting all partitions.
Is it possible with dd comand from adb or twrp?
Btw. you should better not modify or crossflash NVME as it contains your SN, IMEI, MAC, ...

Backing up partitions
somboons said:
External storage path
1. TWRP : /external_sd
2. Boot to system : /storage/sdcard1
dd command for backup partitions except /system and /userdata
Click to expand...
Click to collapse
Would you mind to explain a noob (me) with a little more detail on how to locate this partitions from my computer and back some of them up?
I want to back up OEMinfo, CUST & NVME.
thanks a lot!

hi , like many other i haved a bricked mate 8 and after using dc phoenix to repair it . the phone work but no signial or network and i think because in start of flashing dc-phoenix erase this three partition modemnvm_backup/modemnvm_factory/modemnvm_system and don't reflash them only erase
so pls can you upload this three partition image if it's possible
thank you any way

OEM_NV_BACKUP The NV partition is invalid!

Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj

do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.

chintu1234 said:
do you have any back up of your EFS partition in twrp backup?? if you have restore that partition and see.
Click to expand...
Click to collapse
As said....no.
TWRP did not backed it up.
Any other method/idea, ayone?
EDIT:
Just figured out that I have EFS backed up (oem_stanvbk.emmc.win). I will restore it from twrp, lets see how it goes.

jukyO said:
Hello experts!
After updating to OOS 2.2.1 through stock updater, after reboot I get:
Code:
OEM_NV_BACKUP The NV partition is invalid!
Of course, no IMEI, no network on both SIMs.
Been googling all day, to no avail.
No root, stock recovery, EFS available.
I have tried:
This one:
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
And this one, similar to first one:
http://forum.xda-developers.com/showpost.php?p=62440352&postcount=21 (Oneplus Two - Solution for Hard Bricked Device).
Is there a hope or I need to send it to repair center?
Tagging @Zyxxeil @Lord Boeffla, maybe some ideas will pop up.
EDIT:
EFS backup restoration in TWRP does not fix it.
Thanks in advance!
Juraj
Click to expand...
Click to collapse
Any further ideas, as EFS restore from TWRp doeas not work.

Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app

jukyO said:
Can someone please check what files are inside TWRP EFS backup?
Sent from my A0001 using XDA-Developers mobile app
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here is the file that have in my EFS backup from TWRP

lockmunk said:
View attachment 3729740
here is the file that have in my EFS backup from TWRP
Click to expand...
Click to collapse
I have exactly the same.
Why restoration of it does not solve it?
If I pull
/dev/block/mmcblk0p10
/dev/block/mmcblk0p11
with dd:
dd if=/dev/block/mmcblk0p10 of=/sdcard/modemst1.bin bs=512
dd if=/dev/block/mmcblk0p11 of=/sdcard/modemst2.bin bs=512
to sdcard, they have 1M each, whilst backup is 10M.
Can anyone try the same?
EDIT:
above mmcblk is for OPO, OPT has /dev/block/mmcblk0p20.
And size is ok if I do dd with it.

bump, anyone?

jukyO said:
bump, anyone?
Click to expand...
Click to collapse
bump #2.

got the same issue, damn x) need help, tried the 100% restore backup with qualcomm drivers etc, didnt restore 100%

bump..please help to share your modemst1 & modemst2 please......

androidbrick.com

Nothing on androidbrick...

[ROM][H818][5.1] Satan OS - Best custom rom with UX 5.0 framework

Note: This is not my work its from 4pda. Here is the link: http://4pda.ru/forum/index.php?showtopic=674632&st=4260#entry54442872
Disclaimer: I or xda will not be responsible for anything happens to your device.
Features:
firts lollipop rom with UX 5.0 framework so its like using nougat rom
rom runs on top of v10e software update
Its pre rooted
xposed and viper4android can be installed. Not pre installed
Dual Window for all apps
60fps FHD video recording
Slow Motion video recording
Mini view
and more
Download link:
https://drive.google.com/file/d/0B_qeVuuE99zhTlZ6clRmQmNTOFE/view?usp=sharing
Installation:
Extract the rar file
Move the downloading "system.img" file to the root of your phone's internal storage
Once this has been done, POWER OFF your phone normally and disconnect from PC. After LED stops blinking (OFF properly), Hold the UP VOLUME key and re-insert the USB cable from your PC to your phone. If done correctly, you should see DOWNLOAD MODE in small font in middle of the screen. it will then display another screen with text: FIRMWARE UPDATE (a USB logo) a warning to not unplug and a status bar at 0%.
On a windows PC, Start a command prompt (Start > Run > cmd) and navigate to the unzipped contents folder of LG Root (which is downloaded for LG g4 Root process). (On my PC, the command prompt line after navigation to my unzipped folder looks like C:\Users\star\Desktop\LG_Root\ ).
Let's verify the COM port your phone is connected to. double click the file "ports.bat" in LG_Root folder. Look for the COM number that corresponds to "DIAG1". **WRITE DOWN / REMEMBER THE COMM PORT NUMBER!** Let's assume it's COM3. Click any key/exit this window now...
copy/paste or type this command MAKING SURE THE RIGHT COMM NUMBER IS ENTERED: Send_Command.exe \\.\COM3
You should see Author: blog.lvu.kr and SPECIAL COMMAND : ENTER, LEAVE on 2 lines followed by a hashtag (#). If you are up to this point, type id and press ENTER
You should get back some text starting with "uid=(0)root gid=(0)root".
If it worked for you, from here run the command below (copy/paste next to the # and press ENTER)
dd if=/data/media/0/system.img bs=8192 seek=55296 count=529920 of=/dev/block/mmcblk0
If you've done this correctly, as soon as you've pressed ENTER, you'll see a blinking cursor, probably for a few minutes. Basically the pre-rooted system image you are FLASHING to your phone is being written, so it may take a few minutes. When complete, you should see #. If you see this, it's DONE! Type LEAVE (in CAPS)and press ENTER. Your phone should then restart... Here's mine, it worked like charm!
Overview of the ROM: https://youtu.be/0GZOYGbjFl4
Screenshot on 2nd post

Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

h815?why only 818 dude

[email protected] said:
h815?why only 818 dude
Click to expand...
Click to collapse
only for the dual sim model. h815 got bootloader unlock and got lot of custom rom...

looks nice.
currently im (H818p)on Nougat stock.
if i want to try this rom, how i do it?

dark.blue said:
looks nice.
currently im (H818p)on Nougat stock.
if i want to try this rom, how i do it?
Click to expand...
Click to collapse
you need to flash the marshmallow rom in the nougat thread to revert back to marshmallow after that flash lollipop kdz and follow the above instruction

I am on stock MM V20h can I upload this rom? Do I need to downgrade to LP? Can I go back to stock MM after trying this rom?
thanks for the answers

LPK_CZ said:
I am on stock MM V20h can I upload this rom? Do I need to downgrade to LP? Can I go back to stock MM after trying this rom?
thanks for the answers
Click to expand...
Click to collapse
you need to downgrade to LP to try this rom. after trying you can revert back to marshmallow

safwan ck said:
Note: This is not my work its from 4pda. Here is the link: http://4pda.ru/forum/index.php?showtopic=674632&st=4260#entry54442872
Click to expand...
Click to collapse
Excellent rom for H818,great battery life normal usage about 14hrs

Just wondering do I need to upgrade my phone to v10e first?before installing this ROM?

TWRP Serious problem after failed restore: unable to decrypt storage

So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...

yelti said:
So today I wanted to try something as I had issues with an app.
I made a full nandroid backup with twrp.
After setting up my phone and try the new app I wanted to restore to the old situation.
When restoring I got the error
createTarFork() process ended with ERROR: 255
After a reboot, no decryption password is asked, all files and folders have strange names.
As a result the phone doesn't boot any more except into recovery.
I'm on oxigen os 9.0.8, latest twrp.
Any clues on how I can fix this.
Phone is a brick now...
Click to expand...
Click to collapse
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup

strongst said:
Some treads below yours is the possible solution https://forum.xda-developers.com/oneplus-5/help/createtarfork-process-error255-t3727673
And: you should always remove pin/security before restore or before backup
Click to expand...
Click to collapse
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.

yelti said:
Thx,
I checked but not really my situation.
I don't have the 999 users issue.
I have made a screenshot of my /sdcard folder:
* it seem that my picture is not comming through, so a link to it imgur
Hopes this sheds some light.
What I got from those threads:
My backup was pretty large, 22GB.
I think I will try to flash the stock rom and see where that gets me.
Click to expand...
Click to collapse
So I tried a sideload of the factory images.
Flashing is successfull, next I reboot the phone.
It shows me the oneplus logo and reboots to recovery.
I tried installing the stock recovery, but then when I try to sideload the firmware, the usb device is not recognized.

I have an idea, but I don't know if is doable.
I would want to backup the data partition, (adb pull /dev/block/sda13 data_encrypted.img).
Next I would wipe the phone completely, setup encryption with the same pincode.
Next I would like to restore the old data, but I don't know how.
I hope this way I will ask to decrypt my data partition again.
Anyone an idea?

So an update:
I dumped the data and recovery partition.
Code:
adb pull /dev/block/sda13 data_encrypted.img
adb pull /dev/block/sde22 recovery.img
5494 KB/s (67108864 bytes in 11.927s)
Next I wiped the data partition, phone started normally.
I encrypted the phone again with the same pin code.
Next I tried a nandroid backup and restore while the phone was encrypted, no issues there.
Next I flashed an older recovery to the phone.
Now the test to restore the recovery from the image.
On the phone with an adb sheel:
Code:
dd of=/dev/block/sde22 | nc -l -p 9999
On the pc:
Code:
adb forward tcp:9999 tcp:9999
nc 127.0.0.1 9999 < recovery.img
On the phone I get a lot of data on the screen and the message
Code:
8+0 records in
8+0 records out
4096 bytes transferred in 64.155 secs (63 bytes/sec)
First thing I noticed: number of bytes transferred where not the same as the original recovery.
Next I dumped the recovery partition again to disk and compared the md5 hashes, not the same.
Rebooted the phone and it did not go into recovery.
So this process did not work.
Any ideas?

So, It didn't work with netcat, so I did the following:
connect an usb-c to usb-a coverter to the phone, and connected the external drive with the "bad" image on it.
Then dd-ed the image to the data partition.
When I rebooted the phone, it didn't ask for a pin code and the file and folders where gibbirish again.
So I was back to the starting position.
I'm affraid my data is lost forever :s.

Hello @yelti , I know it's been a long time but I'm kinda into the same issue. Have you been able to fix yours? Do you remember how? Thanks.