Develop Bugs

[TUTORIAL]Howto backup whole phone and restore back in case hardbricked

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTORIAL
* before doing anything! 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.
*/
In this tutorial i'll guide howto create full phone backup and restoring back in case got hardbricked. Tested and confirmed working myself (yes i've hardbricked my phone two days ago and managed to restore back to fully working state). My phone is nokia x, so this is confirmed to be working for the nokia x. For x+ and xl should be working too because basically theres not many different between the three. The backup created using this tutorial is low level whole disk backup, different from cwm or twrp backup because those recoveries will only backup certain partitions only, can be useful to restore back from the recoveries itself but became useless if got hardbricked. This backup can be used to restore back from hardbrick state. Attempting to do this backup alone is also dangerous on its own, i've warned u :angel:
Also special thanks to nikozzzzzz and AngSanley for chatting with me, giving idea and helping me in two days my phone got bricked :good:
Click to expand...
Click to collapse
PART 1 - TO BACKUP
THINGS THAT U NEED
Many spare times to read and follow this tutorial.
Your phone with battery not below 50%.
Busybox installed already.
Custom recovery installed already. I recommend cwm 6.0.2.8.
A reliable pc with adb installed.
A reliable usb cable.
Sdcard with more than 6GB free space. Later we will backup with custom recovery first and the backup could be 1GB, then came the whole disk backup that would be 4GB, and 1GB more for safe read/write io operation. So 1GB+4GB+1GB=6GB.
Click to expand...
Click to collapse
THE STEPS
Connect phone to pc via usb cable.
Mount usb storage and copy whole data from INTERNAL SD safely somewhere in the pc.
Boot into cwm recovery. At this time u should already have the requirement from above, the sdcard with at least 6GB free space inserted into the phone.
Do the usual whole rom backup using cwm. Backup to EXTERNAL SD not INTERNAL SD because we will format internal sd in next step.
Wipe internal sd, system, data, cache and dalvik cache from cwm.
Still in cwm and your usb cable should be connected between phone and pc, open windows cmd and do
Code:
adb shell
Still in cwm, and still connected between pc and phone using usb cable and still in windows cmd, do
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
The backup process could take few minutes. The process is done when cmd showed something like
Code:
7634944+0 records in
7634944+0 records out
3909091328 bytes (3.9 GB) copied, 3367.93 s, 1.2 MB/s
The backup result is mmcblk0.img single file in root of your sdcard, around 3.9GB in size. U can transfer it to your pc and compress it if u want, after compress the size should be smaller, around 1.3GB. Make as many copy of it as u can and store it safely, in dropbox, in your sisters pc, in your grandma pc etc.
Now u can restore back your rom using previous cwm backup in step 4.
Backup process done.
Click to expand...
Click to collapse
Restore process continued to PART 2 below.

part 2 - to restore
things that u need
many spare times to read and follow this tutorial. The restore process can be long upto an hour.
obviously a hardbrick phone. The phone can be turn on by pressing power button but just vibrate, no nokia logo, no recovery mode, no fastboot mode, just blackscreen. Probably the bootloader is gone missing or corrupted. The phone is not hardbricked per se, its still alive if it vibrate after pressing power button. If the phone doesn't show any sign of life, doesn't even vibrate when pressing power button then probably battery depleted. Try to charge the battery using external charger, or find the same phone and charge the battery in it. If still doesn't work even after battery charge then probably thats total lost, only nokia aka microsoft mobile can repair, or until we find another way ourselves.
a reliable pc with a linux os installed. The pc need to have stable power source too because the restoring process could be long upto an hour or so. We dont want the pc to turn off or restart halfway of the process or risking totally messed up the phone disk. So what is linux? Where could u get it? Howto install it? Google for it yourself. I recommend linuxmint. The linux should also be installed, not in live mode because live mode usually unstable, again same as previous reason, we dont want unstable linux in live mode to make pc turn off or restart halfway of the restore process.
a reliable usb cable.
the backup file from previous part 1, the mmcblk0.img file. If u compress it earlier then decompress it.
Click to expand...
Click to collapse
the steps
remove from phone the back panel, battery, simcard and sdcard. Leave it for few seconds.
boot pc into linux.
copy backup file from previous part 1, the mmcblk0.img file into root of your home folder of your pc. Dont put it into any folder, just in root of your home folder.
reinsert phone battery and back panel but not the simcard and sdcard. Leave the simcard and sdcard out of the phone when doing restore process.
connect usb cable to pc and phone.
after connect pc and phone via usb cable, the phone should vibrate and linux probably would detect many new partitions mounted and it open many window in filemanager. Close all filemanager window that opens.
open linux terminal and do
Code:
sudo fdisk -l | grep 3909091328
and the terminal will ask for password
Code:
[sudo] password for user:
type your password (which will not be displayed for security reason) and press enter and it should give output like this
Code:
disk /dev/xxx: 3909 mb, 3909091328 bytes
thats what we want, especially the xxx. Remember the xxx, usually its only three letter long eg sdb, sdc, sde, sdf etc.. It may depends on your linux configuration so it may not be the same for everyone.
for this step we need internet connection for installing a package that not installed by default. Again still in linux terminal do
Code:
sudo apt-get update && sudo apt-get -y install pv
if the terminal ask for your password then just type it and press enter. The terminal will continue to give output and finally stop, the last line should be something like
Code:
setting up pv (1.2.0-1) ...
now close all filemanager window if u got any.
still in terminal do
Code:
sudo umount /dev/xxx
the xxx will be the one from step 7 above. If it asked again for password then type again your password and press enter. It'll give just one or two line of output after that, or nothing at all.
this is the crucial step here, to restore the disk. Still in terminal and phone still connected to pc via usb cable do
Code:
sudo pv -tpreb ~/mmcblk0.img | sudo dd of=/dev/xxx
again, the xxx will be the one from step 7 above. If the terminal asked for password again just type your password and press enter. It'll give output something like
Code:
859mb 0:12:50 [1.48mb/s] [======>....................................................................] 23% eta 0:42:30
and wait for it to finish. This will take long, probably an hour. In this time dont use the pc, don't watch movie, dont surf the net, dont do anything with it. Also dont touch the phone and the usb cable. Just leave it be, go out, take your girlfriend out, feed your cats or anything in the meantime. It'll finish when the percent goes 100% and give another output, something like
Code:
3.64GB 0:56:02 [1.11MB/s] [========================================>] 100%
7634944+0 records in
7634944+0 records out
3909091328 bytes (3.9 gb) copied, 3367.93 s, 1.2 mb/s
now just remove usb cable from pc and phone, remove the phone back panel and battery. Leave it for few seconds.
now reinsert the simcard, sdcard, battery and back panel.
turn on the phone by pressing power button and volume up to boot into recovery.
wipe internal sd, system, data, cache and dalvik cache from recovery.
i strongly suggest u got b-rom flashable zip file already in sdcard. Then just flash the b-rom zip. The b-rom i think doesn't provide kernel in it so u can flash my kernel. Why did i recommend b-rom? Because its pure stock based rom. We want to be on stock rom in first boot after the restore process.
restore process done. Now u just need to boot into rom, check all, ril, wifi, bt, wifi mac, bt mac, imei, serial etc if all in correct order.
Click to expand...
Click to collapse

Reserved #2

Sent from my Nokia_X using Tapatalk

Removed System Apps and cant reinstall them.
Can u please give me a twrp or cwm backed up file which i can use to restore my phone as i can easily boot into these recoveries.
:crying:

mdfzhi said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this TUTORIAL
* before doing anything! 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.
*/
PART 1 - TO BACKUP
THINGS THAT U NEED
THE STEPS
Restore process continued to PART 2 below.
Click to expand...
Click to collapse
actually, I didn't understand many of your thread, in addition I'm tired reading by the way what I'm tryin to say is backing up doesn't need these whole steps. well, I backed up my stock Rom with few steps via CWM and the backup is only 1.73GB.please tell me the deference between mine and yours, I'm sure there's a different, but I can't notice it, and I appreciate your work.

Fikri adli supriatna
AngSanley said:
Sent from my Nokia_X using Tapatalk
Click to expand...
Click to collapse
:crying::crying::crying::crying::crying::crying::crying::crying:
how to cope with nokia x which hardbrick

hello
usuing cwm i formatted all partitions(boot,emmc..etc) and phone didn't boot or enter flash mod but vibrated with blank screen.
it detected as Qualcomm CDMA Technologies MSM but also as storage device,i cleaned partitions and created 1 partition with FAT file system.
now there is no any sign of life except Nokia emergency connectivity.
with or without battery only detects as below:
{
"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"
}
in my case which all partitions are deleted and overwritten, how to restore?
any hope with repair boxes?

Hi
and thank you for your awesome Idea and everyone helped
10 sec after step 7 this command
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
Click to expand...
Click to collapse
Phone reboot to the System and no file on sd card
BTW Fresh system just repair it using atf box ...

never ever format partitions using windows(after phone bricked) because will cause the hard-brick and only can be fixed using atf box.
unbrick using atf box result in null imei,the only way is using another phones backup.
also using back up from another phone result in cloned imei.
if you format boot partition using CWM and reboot without installing kernel,your phone will brick.
best regard.

xsony.plus said:
never ever format partitions using windows(if bricked) because will cause hard-brick and can be fixed only using atf box.
unbrick using atf box result in null imei,the only way is using another phones backup.
also using back up from another phone result in cloned imei.
best regard.
Click to expand...
Click to collapse
Not Really i unbrick my phone using atf box and i have my original imei's :good:

murders10 said:
Not Really i unbrick my phone using atf box and i have my original imei's :good:
Click to expand...
Click to collapse
thanks but for me did:

Originally posted by mdfzhi
The backup created using this tutorial is low level whole disk backup, different from cwm or twrp backup because those recoveries will only backup certain partitions only, can be useful to restore back from the recoveries itself but became useless if got hardbricked.
Click to expand...
Click to collapse
But what is the difference between your type of backup and the CWM or TWRP type?
If your bootloader got stuck, why not reflash it (e.g. using Nokia X Flasher)?

no backup
guys what will i do if i didn't have backup as you suggested, i have a CWM backup and i have the RM-980 product images.
my ubuntu detects the partitions i just don't know which image belongs to which partition?
however all i need is the bootloader partition to be able to use fastboot which one is it and how can i write the bootloader .img to it
thank you very much

bootloader img
xWaLeEdOoOx said:
guys what will i do if i didn't have backup as you suggested, i have a CWM backup and i have the RM-980 product images.
my ubuntu detects the partitions i just don't know which image belongs to which partition?
however all i need is the bootloader partition to be able to use fastboot which one is it and how can i write the bootloader .img to it
thank you very much
Click to expand...
Click to collapse
I also do not have a backup, can anyone post an image of partitions NOKIA X derived from this statement?
Thanks in advance

kobzdik said:
I also do not have a backup, can anyone post an image of partitions NOKIA X derived from this statement?
Thanks in advance
Click to expand...
Click to collapse
You want to restore the phone to the original state?
Just flash it using this procedure: http://forum.xda-developers.com/showthread.php?t=2747262
Next, root the phone and install TWRP recovery.

Ano11 said:
You want to restore the phone to the original state?
Just flash it using this procedure: http://forum.xda-developers.com/showthread.php?t=2747262
Next, root the phone and install TWRP recovery.
Click to expand...
Click to collapse
Unfortunately the nokia x flasher does not detect the phone
The phone is defined as Qualcomm CDMA Technologies MSM

Maybe it helps to install "Nokia_Connectivity_Cable_Driver.msi" or the "nokia_x_usb_driver.zip"?
Otherwise, try the official Nokia software to do the flashing: NokiaCareSuite.

Ano11 said:
Maybe it helps to install "Nokia_Connectivity_Cable_Driver.msi" or the "nokia_x_usb_driver.zip"?
Otherwise, try the official Nokia software to do the flashing: NokiaCareSuite.
Click to expand...
Click to collapse
you still dont understand our issue my friend. nothing of that will work THERE IS NO FASTBOOT. NOKIA CARE flashes you device using FASTBOOT, if no FASTBOOT it cant detect your phone. Fastboot is located on partition mmcblk0p3 "/sys_boot" if you are willing to help and you own a NOKIA X RM-980 please head to my thread it has complete details about the issue
http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617

xWaLeEdOoOx said:
you still dont understand our issue my friend. nothing of that will work THERE IS NO FASTBOOT. NOKIA CARE flashes you device using FASTBOOT, if no FASTBOOT it cant detect your phone. Fastboot is located on partition mmcblk0p3 "/sys_boot" if you are willing to help and you own a NOKIA X RM-980 please head to my thread it has complete details about the issue
http://forum.xda-developers.com/nokia-x/general/fix-blank-screen-boot-format-sysboot-t3126617
Click to expand...
Click to collapse
Ok, now I read the whole thread
I have two working Nokia X's here, so I gave this command:
dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img
But then I recieve this message: /dev/block/mmcblk0: cannot open for read: Permission denied
Enable USB debugging is enabled, phone is rooted...
EDIT:
Ok, I first gave the command in normal operation mode, now in recovery mode: that seems to work.
I guess I am backupping the whole phone now (mmcblk0) which will took about 15 minutes (4.1 MB/s). A backup of the boot partition only (mmcblk0p3) just a few seconds.
Please see the attachment for the boot partition. Product code of my phone: RM-980 NDT IMEA KE - 059T9F4.
Please let me know if it helps you guys!!

[RECOVERY][3.4.0-2][hotdog]Unofficial TWRP recovery for OnePlus 7T Pro Unified(Test)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- TWRP boots;
- Fastboot boot is working;
- Decryption is working (except for Oxygen OS);
- System, Vendor and Product partitions mount is not working but it's not a big problem;
- You can flash ROMs;
- Format Data is broken;
- You can flash magisk
Install guide (Reccomended):
Acutally seems oneplus (or directly android 10) re-introduced the recovery partition so you should only flash it in recovery partition or you can try to boot it from fastboot. For now only boot it.
To flash:
Code:
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Tips:
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.4.0-2 Test by mauronofrio
TWRP 3.4.0-0 Test by mauronofrio
TWRP 3.3.1-43 Test by mauronofrio
TWRP 3.3.1-25 Test by mauronofrio
TWRP 3.3.1-5 Test by mauronofrio
OnePlus 7T Pro Stock Recovery
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_oneplus_hotdog_unified_TWRP
Kernel source: precompiled stock one
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
I want to say a big thanks to the testers @houmles and @ChrisFeiveel84
Created 2019-10-23

Well this completley messed up my phone somehow. First of all, i was not able to install twrp only boot it, but only once, after the first boot i always get an error in fastboot. Secondly i wasnt able to mount /system for example. Cant recommend it right now. @dev Do you have the stock recovery image somewhere and could upload it please?

fritzcola said:
Well this completley messed up my phone somehow. First of all, i was not able to install twrp only boot it, but only once, after the first boot i always get an error in fastboot. Secondly i wasnt able to mount /system for example. Cant recommend it right now. @dev Do you have the stock recovery image somewhere and could upload it please?
Click to expand...
Click to collapse
I'm looking for a stock from where extract it, i think in the night i will be able to extract it

Thanks to Dev for starting work on a TWRP for the OP7T Pro...
Tried the -5 version (only boot from fastboot) and for me it worked fine and also didn't ruin anything on the system.
I had the hope to be able to at least access /data in the filemanager to delete a woesome Magisk extension, but sadly /Data wasn't mounted and also could not be mounted manually. Btw I'm encrypted, but normally I should at least be able to see the folder with garbled names
@dev: should you see a way how I could help in improving TWRP just let me know

Thank you developer for work on this device from this early stage

fastboot boot -> Ok
backup stock boot -> Ok
Patch boot with Magisk Manager -> Ok
Thank

i keep getting this error when trying to do it on my 1+ 7t pro mclaren (remote: Failed to load/authenticate boot image: Load Error)

speedihb2k15 said:
i keep getting this error when trying to do it on my 1+ 7t pro mclaren (remote: Failed to load/authenticate boot image: Load Error)
Click to expand...
Click to collapse
I had the same error. Try to fastboot patched img from here or stock boot img, than try this TWRP after reboot again.

Does the back function working i just want to backup my McLaren edition goodies so i am worried about that

Can mount system partición?
Enviado desde mi GM1913 mediante Tapatalk

liver20 said:
Can mount system partición?
Enviado desde mi GM1913 mediante Tapatalk
Click to expand...
Click to collapse
No. This is also stated in the first post.
Sent from my OnePlus7TPro using XDA Labs

Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.

vtec303 said:
Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.
Click to expand...
Click to collapse
Doesn't matter if decrypted to not, TWRP is not functional on devices launched with Android 10.
Sent from my OnePlus7TPro using XDA Labs

Can i use the boot only option on my 7t pro mclaren(rooted) to flash a new kernel? Or is this only for testing?

Goku1992 said:
Can i use the boot only option on my 7t pro mclaren(rooted) to flash a new kernel? Or is this only for testing?
Click to expand...
Click to collapse
Use ex kernel manger to flash kernels no need for twrp ?

hi this twrp work to flash magisk with the mclaren version?

izimen said:
hi this twrp work to flash magisk with the mclaren version?
Click to expand...
Click to collapse
Search the thread and you'll find your answer.
Hint: 3 posts above yours.
Sent from my OnePlus7TPro using XDA Labs

ok thank you

Hi guys, i'm looking for some testers for the TWRP, if you want to join in the test group write me on telegram, the nickname is the same

vtec303 said:
Si I'm decrypted I'm presuming twrp will be able to mount system? cheers.
Click to expand...
Click to collapse
Hi. How did you manage to decrypt this device? I cannot find a way to do it permanently. Thanks.

[RECOVERY][UNOFFICIAL] TWRP 3.5.0

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Install guide:
Boot :
Code:
fastboot boot <twrp.img>
Install :
Code:
fastboot flash recovery <twrp.img>
Download:
twrp-3.5.0-0-rav-sofia.img
drive.google.com
XDA:DevDB Information
TWRP, Tool/Utility for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/TeamWin/android_bootable_recovery
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28

Thanks your a freaking God been waiting patiently for this much love...... this boots fine with adb command and flashes fine also. However i couldn't use the screen to type password had to use adb shell to decrypt. either way thanks so much thats great that its working....!!!! the screen isnt working the best but your on the right track im having to do everything thru adb shell but it is working backup and decrypt and formating.

I love u for making this, thank you so much :'))

Just an update after using it for 24hrs the touch seems to be off in some spots like the half way point of the screen is up top of the screen. However everything seems to work thru adb shell. I did have a small lock up which I was able to power off thru buttons to get the device working again. Hasn't happened since.

I'm being prompted for a decryption password. I never set a password on the phone, so what might the password be?
I tried default_password but that was incorrect. Any suggestions would be appreciated.

Do you have a screenlock PIN? I had that request for a decryption password, and my screenlock PIN worked.

Corbin Rune said:
Do you have a screenlock PIN? I had that request for a decryption password, and my screenlock PIN worked.
Click to expand...
Click to collapse
I didn't set up any password/screenlocks when I set up the phone. There shouldn't be any encryption.

Drat. Then I have no idea what might be going on. Sorry 'bout that.

Format data and that will wipe the encryption look for a verity disabler with encryption disabler and flash that after wiping you'll be good to go... anyone else having the screen issue im getting

dirtyscout said:
Format data and that will wipe the encryption look for a verity disabler with encryption disabler and flash that after wiping you'll be good to go... anyone else having the screen issue im getting
Click to expand...
Click to collapse
I tried formatting but it did nothing.
What do you mean by a "verity disabler"? I don't know what that is.
My screen doesnt function at all other than in recovery, but I can't load another ROM until I manage to decrypt my HD

I'm having the touch screen issues as well. Although twrp still mostly functions and or you can get around the issues
The following are the touch screen issues I've found:
Install = Advanced opens
Backup = Mount opens
Mount = Backup opens
Advanced = Install opens
Back button does not work
Swipe to unlock does not work. ( Reboot twrp is required)
The following seems to work okay:
Wipe ✓
Restore ✓
Settings ✓
Reboot✓
Home button✓
Menu or recent button✓

dirtyscout said:
Format data and that will wipe the encryption look for a verity disabler with encryption disabler and flash that after wiping you'll be good to go... anyone else having the screen issue im getting
Click to expand...
Click to collapse
I have absolutely no touch screen functionality after flashing twrp recovery image. I did manage to get it rooted with Magisk though. Do you think it would still help to Wipe Data and then flash the No-Verity file? TWRP does come in handy quite often.
Thanks.

I think I found the solution. I haven't tried it yet but certainly looks like it would work.
You need to run the following commands exactly as they are. Including remaining the .img file to recovery.img.
offered By https://unofficialtwrp.COM
fastboot flash recovery recovery.img
fastboot --disable-verity --disable-verification
flash vbmeta vbmeta.img
I'll let you know if it worked or not!

deleted

So did it work

Thanks so much for this! Now that Motorola has locked down their ROM downloads I can boot into TWRP, backup the boot partition, then patch the backup with Magisk to obtain root.

I cant get it to flash sadly i unlocked oem and debug everything but nothing avail oem is still locked in the bootloader

cesarj238 said:
i cant get it to flash sadly i unlocked oem and debug everything but nothing avail oem is still locked in the bootloader
Click to expand...
Click to collapse
your bootloader is still locked!

cbc0201 said:
your bootloader is still locked!
Click to expand...
Click to collapse
How do i get the bootloader unlocked i tried the command fastboot oem unlock and it doesnt work says it fails everytime and i think its due to the update im on 10 (QPRS30.80-64-6-2)

Cesarj238 said:
How do i get the bootloader unlocked i tried the command fastboot oem unlock and it doesnt work says it fails everytime and i think its due to the update im on 10 (QPRS30.80-64-6-2)
Click to expand...
Click to collapse
Check out the Motorola bootloader unlock program.

[Discussion+Guide] [Samsung A10S (A107F)] Bootloader Unlock, lock And Root

Only for Device: Samsung A10S [SM-A107F]
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will meow at you.
*
*/
I have the mentioned model and I tried some things on it. Sharing my experience with you as a guide.
Backup anything you need out of the phone before proceeding as the next steps erases the phone data.
You need a windows machine to follow this guide.
My experience with
Bootloader Unlocking [Source]
It has a relatively simple bootloader unlocking procedure.
To unlock bootloader, go to developer options and enable OEM Unlocking. Then reboot into download mode. Hold down the vol up key for oem unlocking. Quickly press the volume up button as soon as the next screen comes up. If done right, it should erase userdata automatically on the next boot. After erase, it will reboot. setup the phone with default options and go to developer options again. That's it, bootloader unlocked.
Bootloader Locking
Binary == Official? Follow This
Binary == Custom ? Follow This
Root
Summary: After rooting, phone didn't recognize IMEI anymore, so, no network. Phone storage was reduced down to 8 gb instead of 32gb.
But nevertheless, root worked.
Guide Here.
Details here:
ShaDisNX255 said:
By the way, the signal problem has been reported on other occasions.
It seems to be a problem on this Mediatek SoC
https://github.com/topjohnwu/Magisk/issues/1801
topjohnwu seems to have just brushed it off so it doesn't seem like it's going to get fixed anytime soon
Click to expand...
Click to collapse
Flashing the Rooted partitions+any GSI rom
Source:
kkoo said:
Hello, ...
Click to expand...
Click to collapse
Requirements:
7-Zip / 7-Zip ZS [How to unpack with 7-Zip?]
Odin
Null vbmeta.img
View attachment 5039569 [This needs Windows command prompt or Powershell]
Steps:
1. Download and unpack stock rom.
2. Unpack AP_*.tar.md5 to a new folder to keep them seperate.
3. ....
Discussion: If any developer is willing to make a recovery for it, I am willing to test it.

I have built a kernel for the a107f
@afrojanoon
Does anyone want to test it?

physwizz said:
I have built a kernel for the a107f
@afrojanoon
Does anyone want to test it?
Click to expand...
Click to collapse
yes please also please share how can I install it on my phone
(didn't installed twrp on it)

physwizz said:
I have built a kernel for the a107f
@afrojanoon
Does anyone want to test it?
Click to expand...
Click to collapse
I do.

[Guide] [Root] Debrand your lg v50 from carrier boot animation, apps... etc (SKT)

DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed
* 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.
So this is How I managed to get rid of all sh*t that I found in my phone
BACKUP before you start
1- (obviously) you have to root your lg v50, personally I followed this guide https://lge.fun/thread-159.htm
if you have root with older android 10 and you dont know how to update head to 2nd step
*install TWRP >> https://forum.xda-developers.com/v50-thinq/how-to/unofficial-twrp-3-3-1-0-t4140319
*reboot to TWRP by holdong Voldown+power >> when first screen showup release power then hold it back fast, keep Voldown press >> press yes on delete user data (wont actually delete anything)
2- sideload this zip file in TWRP (found in attachment)
then go to wipe> advanced> format data
reboot
3-[if you dont want to update skip to step 4] download latest patched boot image from here https://kdz.gresslg.tk then flash it to boot partition in TWRP
then in lgup software https://forum.xda-developers.com/showpost.php?p=80247013&postcount=5
tick partition dl then tick everything EXCEPT boot_a + boot_b (boot to lgup download mode by holding Volup+usb)
4- Reboot to twrp> Advanced> file manger
go to /OP
There you will find Bootup+shutdown animations and sounds
you can delete them to force the phone to use stock LG boot animation found in system/product/media or product/media
5-you can use app manager to uninstall or disable bloatware https://labs.xda-developers.com/store/app/de.realvoxel.appmanager
6-disable Dual clock with this guide https://forum.xda-developers.com/v50-thinq/how-to/guide-remove-roaming-clock-update-t4086295
7- Smash Thanks botton
Dont be shy to ask any question or share any tips

hello guys.
Im about to buy a V50 but wich carrier is the best for unlock and root...?

d_Barood said:
DISCLAIMER NOTICE
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed
* 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.
So this is How I managed to get rid of all sh*t that I found in my phone
BACKUP before you start
1- (obviously) you have to root your lg v50, personally I followed this guide https://lge.fun/thread-159.htm
if you have root with older android 10 and you dont know how to update head to 2nd step
*install TWRP >> https://forum.xda-developers.com/v50-thinq/how-to/unofficial-twrp-3-3-1-0-t4140319
*reboot to TWRP by holdong Voldown+power >> when first screen showup release power then hold it back fast, keep Voldown press >> press yes on delete user data (wont actually delete anything)
2- sideload this zip file in TWRP (found in attachment)
then go to wipe> advanced> format data
reboot
3-[if you dont want to update skip to step 4] download latest patched boot image from here https://kdz.gresslg.tk then flash it to boot partition in TWRP
then in lgup software https://forum.xda-developers.com/showpost.php?p=80247013&postcount=5
tick partition dl then tick everything EXCEPT boot_a + boot_b (boot to lgup download mode by holding Volup+usb)
4- Reboot to twrp> Advanced> file manger
go to /OP
There you will find Bootup+shutdown animations and sounds
you can delete them to force the phone to use stock LG boot animation found in system/product/media or product/media
5-you can use app manager to uninstall or disable bloatware https://labs.xda-developers.com/store/app/de.realvoxel.appmanager
6-disable Dual clock with this guide https://forum.xda-developers.com/v50-thinq/how-to/guide-remove-roaming-clock-update-t4086295
7- Smash Thanks botton
Dont be shy to ask any question or share any tips
Click to expand...
Click to collapse
with this tutorial can I convert my unlocked lg v50 Sprint to a factory unlock one?
At least in software?

yerling said:
with this tutorial can I convert my unlocked lg v50 Sprint to a factory unlock one?
At least in software?
Click to expand...
Click to collapse
If You mean debloat apps and boot screen then yes

Hi, I own a now-dead LG V30 and I'm thinking of getting an LG V50, European version, on which I would like to do bootloader unlocking.
I'm not clear if the procedure works on this phone and if TWRP works correctly. On the other post I read that the touch doesn't work (I didn't understand though only when I do reset from OS or always).
And so I ask with this procedure I have a perfectly rooted phone, can I make backups on TWRP, use Magisk, etc.?
Can I do it once, or do I lose something when I do a reset?
If then I want to update the firmware?
Thanks and regards!

HarryCustom said:
Hi, I own a now-dead LG V30 and I'm thinking of getting an LG V50, European version, on which I would like to do bootloader unlocking.
I'm not clear if the procedure works on this phone and if TWRP works correctly. On the other post I read that the touch doesn't work (I didn't understand though only when I do reset from OS or always).
And so I ask with this procedure I have a perfectly rooted phone, can I make backups on TWRP, use Magisk, etc.?
Can I do it once, or do I lose something when I do a reset?
If then I want to update the firmware?
Thanks and regards!
Click to expand...
Click to collapse
Touch problems are appeared when reboot from magisk only, with bottons combination every thing works