Related
Do not know what I did right
SD file transfer
Do
Command
Su
Sync
Reboot recovery
I pressed install file is shown getting error
Why?
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Hahaha do not understand what you record
Just realized that trying to install it.. why?
The stock recovery not install CM11 need to flash CWM or TWRP. To do this, first unlock the bootloader. Here is the topic http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
Vagelis1608 said:
CM11 is in alpha. You must expect a brick if something goes wrong.
And (no offense) from that you wrote, you don't seem to know how to restore a brick.
My recommendation is not to try it!!
Also, isn't one post enough for your problem?!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
eta82 said:
Using CM11 from 09.08.2014 and I have no problem with it. Rom a lot better and smoother than stock
Click to expand...
Click to collapse
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
He obviously doesn't know what to do if anything goes wrong (no offense).
If he bricks his phone, it's his responsibility, not ours!
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
eta82 said:
You're right. It's not our problem if you decide to take this step and unlock the bootloader must reckon with the possibility to brick your phone. On this subject is mentioned in the subject line phone unlock and flash CWM so I guess is aware of what they are reading
Click to expand...
Click to collapse
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
How do I install this example TWRP-d620.img
What do I do with this file?
I have ADB
There are all [=
Just what to do where to start an application I beg help me
Write me step by step how to do this request
You can also talk to me on Skype haimmalka85
haimmalka said:
You say my phone can be brick... brick I do not know what it is but I guess it lock Cell Phones
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
What's this? I need to do this?
You can return to its former wonder anyway? Reset?
I just want step by step how to install it did not confuse me
Or, should you? http://forum.xda-developers.com/g2-mini/development/rom-pac-rom-lg-g2-mini-d620-alpha-t2876820
Click to expand...
Click to collapse
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
eta82 said:
This means that you can spoil your phone. Already it does not run, it will be worthless :crying:
But if you're not afraid to lose a few $ no to help these subjects
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
If you do not understand what it says forsake activities
Try it on your own risk
and once you decide to unlock the bootloader then flash CWM then download CM11 upload on SD back up the rom and flash Cm11 in CWM
Click to expand...
Click to collapse
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
haimmalka said:
I understand ..
You send me a link
I went not understand what to do
I explain I consumed
Give me a direction where to start
This material misunderstood me explain a little request briefed
Click to expand...
Click to collapse
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
eta82 said:
First Unlock the bootloader of this guidance document http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748 editing aboot.img own or use this with attachet
Next flash CWM http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
in terminal emulator enter a command
su
reboot recovery to enter CWM
next use CWM to flash CM11
Click to expand...
Click to collapse
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
haimmalka said:
Thanks for attempting to help
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
I came here
I do not know what to do here
What this example
Get aboot.img and abootb.img:
Use "ADB SHELL" or a Terminal Emulator:
dd if = / dev / block / platform / msm_sdcc.1 / by-name / aboot of = / sdcard / aboot.img
dd if = / dev / block / platform / msm_sdcc.1 / by-name / abootb of = / sdcard / abootb.img
Open each with a hex editor.
Search for the byte chain 20 00 EB 00 00 50 FF FF E0 E3 0A
Make sure that it exists only once.
Replace the next 4 byte by DF FF FF EA.
You will get: 20 00 EB 00 00 50 E3 FF E0 FF FF FF DF 0A EA
Save aboot.img as aboot4.img and abootb.img as abootb4.img
Do it on your own risk!
Flash back unto them:
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
dd if = / sdcard / abootb4.img of = / dev / block / platform / msm_sdcc.1 / by-name / abootb
It also
What to do where to start
What actions do
http://forum.xda-developers.com/g2-mini/development/recovery-testing-lg-g2-mini-d620-t2835276
I think I give up I'm selling this instrument complicated
Request If you want to help spare 10 minutes of your time
Skype picks me together (haimmalka85) made this request, I brought up in front of you
Click to expand...
Click to collapse
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
eta82 said:
Make a backup of the file aboot
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img
Phone must be rooted and install busybox instal it
If you have D620r you can download the file from the first post at the bottom of the attached here you have a direct link to this file. you have to download it to your computer. Then copy the file to the phone memory (sdcard), download the terminal emulator play store and install on your phone.
OK
Next
Open terminal emulator and give root privileges type in the terminal
Code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Done
Click to expand...
Click to collapse
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Busybox is not needed
Stock includes the dd command
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
I'm going nuts who can help me it has been installed properly
https://www.youtube.com/watch?v=8aRrmxCOnQ0 It's okay to do the right directory request is made?
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
haimmalka said:
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
If you are using a terminal on the phone there is no need to connect the USB
eta82 said:
what you can see on the screenshot does not have assigned permissions root is visible stamp ($) and should be (#)
# You get when you give root privileges
If you are using a terminal on the phone there is no need to connect the USB
Click to expand...
Click to collapse
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
haimmalka said:
D620r
Yes it is my device
I need someone to help me guidance
Do it with me together
You can do this with me via Skype request?
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/sdcard/aboot.img This stage right?
Now with I understand correctly download it aboot.img - [Click for QR Code] (2.00 MB, 234 views)
Copy it to the SD memory card!??
Copy it to the SD memory card
Then this command register
su
dd if = / sdcard / aboot4.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
Then do what it will do?
Should be connected USB device?
Or after it copies a file can then install rom memory?
Click to expand...
Click to collapse
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
To access the options developers have to tap 7-10 times is an option in Settings> Info About phone> Build number
haimmalka said:
Before I make this Guide
https://www.youtube.com/watch?v=8aRrmxCOnQ0
I have a strange problem why it does not appear to me
??
I get this message
Click to expand...
Click to collapse
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Vagelis1608 said:
Google: How to activate adb
Google: Install adb in 15 seconds
Sent from my D620R [Stock 4.4.2]
Click to expand...
Click to collapse
OK I managed to figure out what to do
I'm stuck here
I did not get here just like what?
Continue?
Nexus 7 (2013) Repartition
No one is responsible for your actions except yourself. Everything written further may potentially brick your device, although risk is reduced to minimum.
This repartition package offers 1.5G /system; a /vendor partition and it is fully backward compatible with any ROM (including stock system.img).
Known-issues
HTML:
- If repartition pack says that device isn't correct,
than, if partition table wasn't modified before,
congrats! your device has different memory chip
that those I worked with. No worry, PM me and
I'll add support for it.
DO THE BACKUPs. Repartition will erase all your data
USB connection to PC is MANDATORY else you will not have opportunity to push ROM to your device
Backup
# Before processing further we highly recommend you backup persist and EFS using adb
# Or you might lose your IMEI/WIFI + BT mac addresses
Code:
adb root
adb shell
dd if=/dev/block/mmcblk0p2 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/modemst2.img
dd if=/dev/block/mmcblk0p4 of=/sdcard/persist.img
Now you can find 3 *.img files at path /sdcard. Copy them to your PC since internal memory will be erased.
Installation
HTML:
# This mod is backwards compatible with any ROM so we highly recommend NOT to reverse it if repartition went well.
# You should use ONLY recovery from this thread since other don't support all benefits of this mod.
# When installing ROM just after you flashed zip and before installing GAPPs you MUST make a resize in TWRP since all roms are build for ~800M system.
# Package is unified for flo and deb. To restore stock layout use same zip and steps as for repartition.
1. Boot into recovery (You need to allow system partition modification to be able resize /system in recovery).
2. Backup your data & Move your files from flash to your PC.
3. Flash repartition pack zip.
4. Do the actions asked by repartition pack (go to Terminal in ordinary recovery and input word that pack will tell you. Everything else will be done automatically).
5. Phone will reboot into recovery.
6. Install TWRP from below (it is build with support of new partitions layout and sizes. It can be differed from official TWRP by next format 3.x.x-1 UA).
7. Format everything. (mount errors will not affect formatting!)
- In TWRP: Wipe > Format data
- Type yes
- Once this completes go to: Wipe > Advanced Wipe
- Tick all the boxes and wipe. There should be no further mount errors. (Thanks [user=7694808]@mr_rubbish[/user] for corrections in formatting).
8. Install ROM which you like.
9. Enjoy better flash partition layout.
If something gone wrong - we recommend you NOT to do anything by yourself. Write here for help, else you may do only worse.
Downloads:
Repartitioning package: GitHub
Credits:
Special thanks to
- Unlegacy-Android team;
- Sudokamikaze;
- rlw6534 for Kingston MMC layout;
- surfrock66 for his gide for Nexus 5;
As usual, feedback is appreciated
XDA:DevDB Information
Nexus 7 (2013) Repartition, Tool/Utility for the Nexus 7 (2013)
Contributors
Clamor
Source Code: https://github.com/clamor95/android_device_unlegacy_recovery
Version Information
Status: Stable
Created 2018-09-19
Last Updated 2019-01-18
Common issues and F. A. Q.
Repartition pack should be safe for most devices. Common mistakes, issues and their solution will be published here.
1. You shouldn't flash any internal parts of repartition pack (*.sh files) only flash whole zip using TWRP. You may use my scripts for personal use or projects but authorship should to be kept.
2. If something isn't mounting after repartition try to format partitions that don't mount using Wipe -> Advanced Wipe in TWPR. Ideally you should format in that way all partitions in Advanced Wipe menu (see 5-th step of installation guide).
3. If you want to be sure that repartition went well I enclose loging zip. Flash it after repartition (when device reboots into TWRP). It won't modify anything only generates a partition.log in root of internal storage and outputs your current partition layout to screen. You should check if your layout is same as those fragments I provide under spoiler (file systems doesn't matter). If there are any differences you have to describe what you did and enclose partition.log to your post.
FLO/DEB STOCK
Code:
22 671088640B 1551892479B 880803840B system
23 1551892480B 2139095039B 587202560B cache
FLO/DEB MODIFIED
Code:
22 614429696B 2187293695B 1572864000B system
23 2187293696B 2270167039B 82873344B cache
...
30 2348843008B 2610987007B 262144000B vendor
4. After flashing most ROMs system size will reduce to stock, you need to resize /system in TWRP or use flashable resize zip for ROMs that support addon.d (automatic resize when dirty flashing updates).
5. After returning to stock partition table you won't be able to get into the Recovery from the bootloader anymore, but when you start the tablet normally it goes straight in the Recovery. It is normal state. New partition table proposes larger /recovery size (16MB) while stock gives only 10MB. During restoring stock process, it is impossible to restore larger recovery backup into new smaller partition. Whether not to leave user without recovery excess, recovery backup restores into /boot partition. Just flash ordinary TWRP and install ROMs from it.
6. Don't install the zip file from the USB OTG. Copy them into the /sdcard. Else you will get message after flashing repartition pack.
Code:
"Can not extract updater-script. Do you have it in package?
Updating partition details...
...done"
Link not working for the repartitioning package...
@rlw6534 should be fine now
Any chance you give details on backing up persist and EFS with dd command? I'm not really a noob but I also don't want to mess up my tab...
@rlw6534 You actually should't brake anything. Added an instruction how to backup EFS and persist.
OK. Tried to flash on a clean, freshly wiped system (Flo 32G), all stock, ext4 on cache and Data, TWRP 3.2.3-0. Got the following:
******Applying dark magic******
This is not a Nexus 7 (2013)
Updater process ended with ERROR: 1
How to restore files, that we copied from our tablet using dd command ? (I haven't done anything yet. Just asking)
Sent from my whyred using XDA Labs
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Clamor said:
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Click to expand...
Click to collapse
Do you mean that despite this error message:
******Applying dark magic******
This is not a Nexus 7 (2013)
Updater process ended with ERROR: 1
The partition table has been modified correctly?
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
Clamor said:
@lollyjay No it wasnt. Package has 2 step security system. It checks if partition table was modified and in what way (by package itself, by user or it is stock). Second step is that package itself doesn't modify anything, it needs manual confirmation in terminal, else no changes will be applied.
Click to expand...
Click to collapse
Thanks
So do I NOT flash the modded twrp first?
Your instructions said to flash it after reboot to recovery
@lollyjay actually it shouldn't metter, but after would be better
Clamor said:
@lollyjay actually it shouldn't metter, but after would be better
Click to expand...
Click to collapse
I'm going to do this when I get home. This might mean that flo/deb will get Android 9 Pie
@lollyjay look through UA ROM thread I wrote there about P on flo/deb
Clamor said:
@lollyjay look through UA ROM thread I wrote there about P on flo/deb
Click to expand...
Click to collapse
Sorry but can you give me a link?
Clamor said:
@rlw6534 your partition table was modified.
@MikiGry same commands, just switch paths.
Click to expand...
Click to collapse
I have previously used sysrepart.zip and sysrepartundo.zip from this thread, although not recently:
https://forum.xda-developers.com/showpost.php?p=76278047&postcount=19
I returned it to stock a while back (827MB). Perhaps I need to sgdisk a stock partition table?
@rlw6534 Every manual repartition or repartition made not by my pack needs an individual look and partition table restore.
@lollyjay here
Clamor said:
@rlw6534 Every manual repartition or repartition made not by my pack needs an individual look and partition table restore.
@lollyjay here
Click to expand...
Click to collapse
OK. Here is my partition layout. My userdata appears to be smaller than stock, but there isn't enough room on mmcblk0 to increase it to the size that your script is looking for. I have no idea how that could have been changed without bricking the tab. Everything else looks normal. Ideas?
Code:
Model: MMC MMC32G (sd/mmc)
Disk /dev/block/mmcblk0: 30937186304B
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 67108864B 156745727B 89636864B fat16 radio
2 201326592B 204472319B 3145728B modemst1
3 204472320B 207618047B 3145728B modemst2
4 268435456B 283795455B 15360000B ext4 persist
5 335544320B 336343039B 798720B m9kefs1
6 336343040B 337141759B 798720B m9kefs2
7 402653184B 403451903B 798720B m9kefs3
8 403451904B 406597631B 3145728B fsg
9 469762048B 471298047B 1536000B sbl1
10 471298048B 472834047B 1536000B sbl2
11 472834048B 474931199B 2097152B sbl3
12 474931200B 480174079B 5242880B aboot
13 480174080B 480698367B 524288B rpm
14 536870912B 553648127B 16777216B boot
15 603979776B 604504063B 524288B tz
16 604504064B 604505087B 1024B pad
17 604505088B 606041087B 1536000B sbl2b
18 606041088B 608138239B 2097152B sbl3b
19 608138240B 613381119B 5242880B abootb
20 613381120B 613905407B 524288B rpmb
21 613905408B 614429695B 524288B tzb
22 671088640B 1551892479B 880803840B ext4 system
23 1551892480B 2139095039B 587202560B ext4 cache
24 2147483648B 2148532223B 1048576B misc
25 2214592512B 2225078271B 10485760B recovery
26 2281701376B 2281709567B 8192B DDR
27 2281709568B 2281717759B 8192B ssd
28 2281717760B 2281718783B 1024B m9kefsc
29 2348810240B 2348843007B 32768B metadata
30 2415919104B 30937169407B 28521250304B ext4 userdata
@rlw6534 Thanks!
Many of 6GB RAM Nokia X6 has an issue, that you can't flash system partition properly - after 1st sparse flashed, fastboot will prompt "error flashing partition".
This guide introduces a workaround for this issue.
4GB RAM Nokia X6 / 6.1 Plus needn't to follow this guide.
And 6GB RAM Nokia 7 Plus needn't to follow this guide.
Or if your 6GB RAM Nokia X6 can flash stock firmware properly, you needn't to read this guide any further.
Click to expand...
Click to collapse
I still don't clear the pattern of 6GB RAM Nokia X6 that can't flash partitions.
Prerequisites:
- Bootloader must be completely unlocked
- You have fully unpacked firmware
- Use OST LA 6.0.4 or NOST v0.4 by @stollD
Here's how:
1. Make a copy of DRG-2XXX-0-00XX-B0X.mlf at the same directory, in this example, I made a copy of "DRG-221F-0-00CN-B03.mlf".
2. Use Notepad++ or any code editor that supports unix to open "DRG-221F-0-00CN-B03 - Copy.mlf".
3. Navigate to these codes.
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system.img"
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x40000
IMAGE_FILE = "DRG-0-221F-00CN-system_other.img"
And modify them to:
Code:
[Package Info 31]
PACKAGE_NAME = "system_a"
BOOT_NAME = "system_a"
OPTION = 0x4
IMAGE_FILE = ""
[Package Info 32]
PACKAGE_NAME = "system_b"
BOOT_NAME = "system_b"
OPTION = 0x4
IMAGE_FILE = ""
Save it.
4. Use OST LA or NOST to flash this - you'll definitely encounter C6DA error, but don't worry about that.
5. Download TWRP for Nokia 7 Plus that doesn't require flash from here (TBA) and execute these commands under OST LA installation directory:
NOTE: YOU MUST USE fastboot-android.exe included in OST LA - DO NOT USE fastboot.exe provided by Google.
Click to expand...
Click to collapse
Code:
.\fastboot-android format userdata
.\fastboot-android reboot-bootloader
.\fastboot-android boot D:\Nokia7plusv3.2.1.0-noflash.img
After your phone booted to TWRP, you may find the touch screen doesn't work, don't worry - we only need to use adb commands.
6. Execute following commands:
[QUOTE]
You can use adb.exe from both OST LA or platform tools.
[/QUOTE]
[CODE]
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\systeminfo.img /data/systeminfo.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system.img /data/system_a.img
.\adb push D:\DRG-221F-0-00CN-B03.nb0_unpacked\DRG-0-221F-00CN-system_other.img /data/system_b.img
.\adb shell
simg2img /data/system_a.img /data/system_a.img.ext4
simg2img /data/system_b.img /data/system_b.img.ext4
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_a
dd if=/data/systeminfo.img of=/dev/block/bootdevice/by-name/systeminfo_b
dd if=/data/system_a.img.ext4 of=/dev/block/bootdevice/by-name/system_a
dd if=/data/system_b.img.ext4 of=/dev/block/bootdevice/by-name/system_b
rm /data/systeminfo.img
rm /data/system_a.img
rm /data/system_b.img
reboot
That's all for the whole 6GB RAM Nokia X6 stock firmware flashing guide.
If you're a developer, 6GB RAM Nokia X6 is definitely unsuitable for developing.
Thanks for the guide, it will be very useful for me. I'm trying to flash this phone for a long time and I just can't unbrick it.
A few issues I've come over while following it:
OST_LA and NOST didn't want to flash DRG-221F-0-00CN-B03 ("you need to update your software" or something like that), so I had to unpack DRG-229D-0-00WW-B01.
I couldn't find Nokia7plusv3.2.1.0-noflash.img anywhere, so I used Twrp_N6.1plus_global_Aug.
When I try to use simg2img in adb shell, I get the following error:
Code:
~ # simg2img /data/system_a.img /data/system_a.img.ext4
error: file_write: write: Out of memory
Cannot write output file
---
Update: I've flashed 250A and it works like a charm! Just had to edit the .mlf according to this guide.
Hi @hikari_calyx,
have you tried flashing Nokia X6 6GB version to 6.1 Plus International Version (Android One)?
Anything I need to consider?
Hey I bought the Nokia x6 TA-1099 6gb Chinese variant it came with the global ROM 00WW_3_38A I believe it was flashed by the seller. When I got the phone I saw there was an OTA to update the pie to v3.45B I want to know if it's safe to update via OTA because it's meant for 6.1plus
:good: thanks
twrp fails
when iam flashing twrp it is showing that no such partiton is found recovery b
PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD
RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch
the image you made is for enable rw or not?
my phone is poco x3 nfc surya
janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image
aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !
janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test
its not working after restart didnt boot n just go to recovry
aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)
janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4
jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
now i cant install any rom :
updater process ended with error 7
pls help
aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !
janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk
Hi there
I had some problems booting into Recovery and ERecovery. It would always stay endless in the Warning screen where it says that the Device is unlocked.
I run into it because of TWRP not Formating Data properly.
https://dl.twrp.me/anne/
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 EST
This Versions get stuck at:
Code:
Formatting Data using mkfs.f2fs...
Done
After it beeing stuck I could usually reach erecovery and wipe . But at one point it wouldn't work and I couldn't reacht the two and also couldn't stop the device from endless starting after shutting down.
I tried to flash several images from this one: https://androidhost.ru/1nfK
After flashing odm.img I could access the reflashed Stock Recovery and E-Recovery.
Update: Erasing Data with fastboot also works.
Note: It would show Google instead of Huawei at startup and in fastboot FRP:Unlocked doesn't show anymore after flashing odm.img
Else:To reach erecovery or twrp recovery I retried often to hold power and volume up when the device is turned off. It then vibrates two times when it works. I hat sometimes to try for 10 Minutes to reach one of the to.
I unlocked with PotatoNV. The phone can be opened quite comfortable with a straight package plastic like from a cabel or electric device and a hairdrier.
Update: I can actually not format Data with any of these TWRPs. This was working before flashing the odm or maybe an other image.
twrp-3.5.1_9-0-anne.img14.6M 2021-03-13 15:27:54 ESTtwrp-3.5.0_9-0-anne.img13.2M 2020-12-27 21:03:29 ESTtwrp-3.4.0-1-anne.img13.2M 2020-09-26 14:58:13 EDTtwrp-3.4.0-0-anne.img13.2M 2020-08-21 17:03:57 EDT
I could format with adb shell:
anne:/etc # mkfs.f2fs /dev/block/mmcblk0pXX
F2FS-tools: mkfs.f2fs Ver: 1.10.0 (2018-01-30)
Info: Disable heap-based policy
Info: Debug level = 0
Info: Label =
Info: Trim is enabled
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 106086400 (51800 MB)
Info: zone aligned segment0 blkaddr: 512
Info: [/dev/block/mmcblk0p57] Discarding device
Info: Secure Discarded 0 MB
Info: Overprovision ratio = 0.880%
Info: Overprovision segments = 459 (GC reserved = 235)
Info: format successful
benaep said:
I can actually not format Data with any of these TWRPs.
Click to expand...
Click to collapse
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
-Alf- said:
Yes, you have installed wrong TWRP (version 3.4.0.x and 3.5.0.x is not fully compatible with our device and it's strongly NOT recommended do 'wipe data' runnig stock ROM , it may brick the phone).
Use recommended TWRP:
Recommended and tested TWRP Recovery
EMUI 8 Stock ROMs: 3.2.1-0 by pretoriano80 (with data decryption on Android 8 ) https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw EMUI 8 Custom ROMs: 3.2.1.0 by Catuva21...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
benaep said:
Thanks for the direction Alf. So for the Newest Linage OS build that would be:
Pie Custom ROMs:
3.4.0-0-emui9_eR
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
right?
Click to expand...
Click to collapse
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
-Alf- said:
If you want to flash LOS from TWRP (idk why, but it's your choice), use 3.2.1 by pretoriano80 (wiping etc.) After installing custom ROM, you can replace 3.2.1. with 3.4.0.0-emui9_eR.
Click to expand...
Click to collapse
Hi Alf
Thanks for the reply. Very gratefull for this. I'm trying since Weeks to get this running.
I just want a phone with minimal Google. I had /e/ but I didn't find a build and back in the days linage would be fine.
You think there is something which makes more sense?
benaep said:
I just want a phone with minimal Google
Click to expand...
Click to collapse
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
-Alf- said:
Then install "v" variant , e.g.
LOS 17.1-unoff.
https://sourceforge.net/projects/treblerom/files/LOSQ/2020.10.17/losq-v224-201017-arm64-bvN.img.xz/download
LOS 18.1-unoff.
https://sourceforge.net/projects/treblerom/files/LiR/2021.03.18/lir-v302-210318-arm64-bvZ.img.xz/download
and install opengapps - pico, nano, micro... , what suits you.
Click to expand...
Click to collapse
Yo Alf
Thanks for the Links to the Image files. I would never have found them myself. I tried now a few hours to make them run.
Formating and Wiping works with 3.2.1 by pretoriano80
I tried both images, but am not shure. I get an invalid zip file error when I copy it on the device. Sideload doesn't work. No connection or Success or Success 00.00 X.
I make it a zip on linux with --> unxz --> img2simg --> Create Zip Directory wit xarchiver.
I tried different combinations of this. First I forgot about simg and just made a zip out of the img.
Code:
/tmp/recovery.log: 1 f...57322 bytes in 0.010s)
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: failed to read command: Success
~ >>> adb sideload /home/bni/Downloads/losq17.zip
adb: sideload connection failed: closed
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: closed
~ >>> adb pull /tmp/recovery.log /home/bni/Downloads/recovery.log
/tmp/recovery.log: 1 f...59228 bytes in 0.007s)
Code:
~ # twrp install /image/LOS17_SIMG.zip
Installing zip file '/image/LOS17_SIMG.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Invalid zip file format!
Error installing zip file '/image/LOS17_SIMG.zip'
Done processing script file
benaep said:
I get an invalid zip file error when I copy it on the device.
Click to expand...
Click to collapse
Of course, it is not a flashable .zip file.
You have to install it as image file, unpack .zip package, transfer exctracted .img file to the SD card. In TWRP go to Install , select Install image, choose lineage .img file , mark "system image" and flash.
If you need to do a factory reset , first replace TWRP with stock recovery and perform factory reset in recovery.
Or, flash Lineage.img in fastboot,without TWRP, wipes, errors etc. (make sure to have the stock recovery flash) - https://forum.xda-developers.com/t/losq-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543