Database Info

Guide to fix TWRP or CWM bootloop

This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Long story, short:
For some reasons, seems like the WIPE command from TWRP and CWM recovery screw the partitions.
No partitions or microSD card can be mounted.
The tablet is now booting only in recovery mode or in fastboot mode (the screen with three icons - RTK, Android and WIPE) instead of Android.
IMPORTANT:
If your tablet reboot in fastboot mode DONT WIPE IT AGAIN! Just skip step 4.
First of all, MAKE SURE YOR BATTERY IS CHARGED!
Recharge your tablet for at least two hours.During the flashing process the tablet doesn`t charge.
Use the original Asus USB cable that came with the tablet or a high quality replacement cable. Cheap cables can and will cause problems.
Use a laptop or desktop with known good USB ports. If you have problems, try a diferent computer, some USB chips can cause troubles.
Disable the antivirus or screensaver, sleep etc...
1.Download these files:
from ASUS website: http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300TG/#support
Drivers&Tools, on the OS tab select Android
click on Utilities and download latest version of ASUS PC Sync (you will need this for drivers)
click on Firmware and download the lastest available (you will need this for BLOB file)
Minimal ADB and Fastboot: http://d-h.st/gbx
install ASUS PC Sync and Minimal ADB and Fastboot (on fastboot installer check the box that make a shortcut to desktop)
unzip the firmware file downloaded from ASUS site
you will get a second zip file, unzip this one too
the folder unzipped from the second one contain a file called blob
copy or move the folder to the root of your drive C: or D: or whatever drive letter you have
2.Installing drivers:
connect your tablet to PC
you will get a message about Windows couldnt find driver bla...bla, ignore it and keep your tablet plugged
IMPORTANT: even if you previously installed ASUS PC Sync or other drivers and Windows recognize your tablet, you still need to change the driver.
right-click on My Computer-Properties and click Device Manager
find the Asus Android device - should be with an exclamation mark on it (the driver is not installed sign)
right-click on it and choose:
Update Driver Software..., Browse my computer for driver software, Let me pick from a list of device drivers on my computer, Have disk, Browse
go to C:\Program Files or Program Files (x86), ASUS, ASUS Android USB Drivers, Android and select android_winusb.inf
Asus Android Composite ADB interface will appear in the list of device drivers - don`t hit next yet!
uncheck Show Compatible Hardware and select Asus Android Bootloader Interface from the list, now hit next
3.ADB mode:
open Minimal ADB and Fastboot from desktop - from this point, keep it open
type: adb devices - and you should see some numbers under the List of device attached - thats your tablet
if you can`t see the tablet, try this command: adb start-server
4.Booting to "fastboot":
there are two ways to do this:
a) from adb window type: adb reboot bootloader
or
b) reset and hold vol-down (didn`t work for me, but maybe will work for someone else)
the three icons will appear on screen - NOW YOU ARE IN FASTBOOT MODE
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
the credits for this part goes to buster99. He is the one who figured out the right commands for formatting partitions and flashing back the OS
here is his post: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
here we go, one at the time in adb window:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system x:\your blob folder\blob (here you enter the path to your blob file, must end with blob, to point at the file)
fastboot -i 0x0B05 reboot
THE FLASH SYSTEM COMMAND WILL TAKE SOME TIME
be pacient and wait until the progress bar is 100% full on the tablet and you get the command prompt back in the adb window.
After reboot, the Android is back on.
Cheers and good luck!!

A big thank you alexhosu,
several months ago that my tablet was blocked, but I still kept hope
a solution would be found. I'm really happy for you and thank you again for sharing.
Long live XDA

me too
Thanks from me too; was enjoying 5.0 (timduru) on my TF300 when I went to upgrade and idiotically managed to get into a TWRP bootloop(interrupted a format of \data and then used 'wipe' from the boot screen by mistake...)
Your solution has saved my tablet
Am now carefully reinstalling Katkiss

Thanks
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again

Followed the instructions.. Worked well, but getting error 963 when installing/updating anything in Play Store. Seems to be related to storage permissions. Some users are suggesting using format instead of erase. What's the difference? Could that help.
I did factory reset, reflashed and used fix permissions in TWRP but no luck...
alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
Click to expand...
Click to collapse

Big thanks from me.
I killed my tablet with an accidental restore to factory defaults while in cm12, an got stuck in an endless bootloader boot loop.
my tablet came back too life at the end of section 4 after adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3.
although getting adb to talk to the tablet was a fluke.
I just kept trying to send "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" while the tablet was loading (boot looping)

6 months of believing my tablet was dead, after letting CM12 do its own update thing, and now, thanks to the above instructions, I'm back online and its working with the stock rom.
Thank you so much for this. No idea why I couldn't find these instructions before, then I just gave up, back in business now!

Thanks a lot for your guide, this is what helped me fortunately unbrick my device, i was stuck in a boot loop with a broken recovery

Another tablet saved. Know your work is appreciated.

i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.

ajeevlal said:
i have the same problem, the system doesn't pass the ASUS logo, i tired to log into fastboot (reset + volume down) and i was able to see the three icons but adb doesn't recognize my device. i see the drivers are correctly installed but no working adb. Any help is highly appreciated.
Click to expand...
Click to collapse
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.

Act32.97 said:
Did you try entering "fastboot devices" or just "adb devices"? adb wont find your device in the bootloader, but using fastboot commands should unless it truly is not connecting for some reason.
Click to expand...
Click to collapse
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.

ajeevlal said:
yeah Fastboot devices worked but it was not letting me flashing the rom, when i push the blob file it says 'sending' and stays in the same state for days.
Click to expand...
Click to collapse
I would try moving the blob to the root of the C drive and try the 7th command "fastboot -i 0x0B05 flash system C:\blob" just to make sure sometime of file permission type issue isn't happening on the pc side. Other than that the only kind of issue I think it could be would have to be the connection with the drivers, although if erasing the partition's works fine, I don't really see what could be going on.

I followed all the steps and delete, but when loading the file update.blob I get this error:
C: \ Users \ mikel> C: \ Users \ mikel \ Android \ android-sdk \ platform-tools \ fastboot flash system update.blob
error: can not load 'update.blob'
Can someone help me out?

TF300T KissKat
Theziggy said:
This saved my (veggie) bacon too, something went wrong when flashing new ROM (most likely user error - e.g. my fault). Tablet woud go into an eternal boot wouldn't finish booting, nandroid recovery did the same. Used this technique and have a working stock ROM from which I intend to reinstall TimDuru's Lollipop.
Thanks again
Click to expand...
Click to collapse
Hey, I know that I'm a couple years late on this. But, I was just given a Asus Transformer TF300T, and attempted to install the Kisskat custom rom. I unlocked the device with little issues. Rooted with little issues. But when it came to flashing the rom. I get his error saying that "no MD5 file found" and holds it there for a couple of minutes. Then gives me the failed install. My only option is to boot into recovery and restore the stock JB 4.2. If you could point me in the right direction, I would greatly appreciate it. I've searched the forum for someone with a similar issue, and couldn't find it. I hope that I'm not alone on this one. It would kill me to be stuck with the stock rom.

Hi i made a format data from TWRP recovery, and now i am in a recovery loop and got error of mount partitions, i can access to recovery and the screen with 3 icons, but when i plug to my pc it shows as uknown usb, i install the drivers but dosent reconose as a fastboot device, in minimal adb when i write fastboot devices the result is empty pleace help me.

Muito obrigado!
I know this must seem odd, being such an old thread and all but, after several years adding apps and changing ROMs on my wife's TF300T (my gift!) only these past weeks I had the need to search for help, after installing nougatella 7.1, which I did with success, only to stumble on endless logo loops and loading processes without conclusion. Don't get me wrong, the ROM looks great and it wasn't that hard to install but, after two weeks or so, gave me this problem and after correcting it and installing again the ROM, I got in trouble again...
After some five hours googling and trying different stuff, I finally found this thread and twenty minutes ago (around 2:AM) my ASUS returned to its (Jellybean) life!
Alexhosu, thank you so very much for such a detailed, yet easy to follow guide and, if you happen to come to Portugal on vacation and visit Setúbal, I'll have a bottle of Moscatel waiting for you!
Many thanks to Droidbound (who got me off the hook the first time the tablet went nuts!), and also Kevinthefixer, Gtanner00 and some other very inteligent, patient and thoughtful people, and all the guys who shared their difficulties and in a way helped me find the people with the fix.
For anyone interested in trying this method, I would say that it's paramount that you should stick exactly with what is asked and should pay real atention to what is the correct ROM update to download and use. If anyone needs help with translation to Portuguese, just say so.
Again, thank you so much for this!
JMonteiro

alexhosu said:
This is how i fix my TF300TG stuck on recovery. I hope the steps descried below will help.
if none of the above work try this:
in adb window type: adb reboot
wait until the tablet enter in recovery menu and type in adb window:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3
adb reboot bootloader
5. Flasing the blob
Click to expand...
Click to collapse
Thanks for your help :good: and I'm sorry for my basic English, but here is another tablet saved. Your instructions were clear and my tablet is working.
I hope this information helps, based in the next link (user sszyman): https://forum.xda-developers.com/showthread.php?t=2275035&page=9
in which he recommends using the following commands too:
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p2
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p8
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p1
With these commands and "adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3" I was able to solve my Bootloop problem.
Honestly I don't know which of the commands worked, I used all several times.

[RECOVERY][TWRP] Unofficial TWRP 3.0.3 For ZTE Nubia Z11 Mini

Unofficial TWRP For ZTE Nubia Z11 Mini​
This is vanilla TWRP and doesn't have custom "root menus" like the Russian and Chinese versions that are available.
This is currently using a prebuilt kernel and device tree blob (dt.img) extracted from my device.
The official kernel source is https://github.com/ztemt/NX529J_L_kernel but it doesn't compile with this config yet.
If you want to compile the exact same version as the attached file then you can use the manifest inside the zip to reproduce the build.
The source and build instructions are here https://github.com/opticyclic/android_device_nubia_nx529j
Instructions
Please test before replacing your stock recovery.
Load it temporarily by using fastboot boot instead of fastboot flash.
Code:
adb reboot bootloader
sudo fastboot boot recovery.img
If you are happy with it you can replace your existing recovery with
Code:
adb reboot bootloader
sudo fastboot flash recovery.img
If fastboot doesn't recognise your device then you can try forcing the vendor id like this
Code:
adb reboot bootloader
sudo fastboot -i 0x19d2 boot recovery.img
Changelog
2017-03-07
Added External SDCard as a mountable/wipeable option
Upgraded from 3.0.2.0 to 3.0.3.0

Glad to see you got TWRP up and running :good:.

hi opticyclic,
thanks for the twrp. i installed the recovery but i have not access to the external sdcard in the backup or restore menu.
please have a view on this issue.
thanks dreas

dreas74 said:
hi opticyclic,
thanks for the twrp. i installed the recovery but i have not access to the external sdcard in the backup or restore menu.
please have a view on this issue.
thanks dreas
Click to expand...
Click to collapse
Are you using TWRP to backup your external sdcard?
Or do you just need access to save the system backup to the external sdcard?

opticyclic said:
Are you using TWRP to backup your external sdcard?
Or do you just need access to save the system backup to the external sdcard?
Click to expand...
Click to collapse
hi,
the second. i will backup to the external sd and restore from the external sd.
regards
dreas

dreas74 said:
hi,
the second. i will backup to the external sd and restore from the external sd.
regards
dreas
Click to expand...
Click to collapse
Original post is updated with a newer version.

opticyclic said:
Original post is updated with a newer version.
Click to expand...
Click to collapse
hi opticyclic,
i will try it. thanks in advance.
dreas

Small problem with understanding
opticyclic said:
Unofficial TWRP For ZTE Nubia Z11 Mini​
This is vanilla TWRP and doesn't have custom "root menus" like the Russian and Chinese versions that are available.......
[/LIST]
Click to expand...
Click to collapse
Hi,
I'm new here and my problem is, that I don't know how or where could write the code like in instructions. I just rooted and flashed many roms on many phones, but Nubia is kind of high level for me and this is only one useful topic about. So I'm windows 10 user but I have Bash too, like in Linux.
Sorry guys, already SOLVED

Device not recognised
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.

teji007 said:
I was trying to install TWRP on my NX529J.
"Adb reboot bootloader command" is working but when i try to install TWRP with command "Fastboot flash recovery recovery.img", it dosent work.
It shows "waiting for devices"
Tried " fastboot devices" NO device there
I tried updating all drivers installed fastboot drivers and zte drivers but still no device found.
In developer settings OEM unlock, USB debugging is on.
and adb mode is also on with *#7678#.
Plz Help.
Click to expand...
Click to collapse
Read the first post and follow the instructions properly.
Hint : use [sudo fastboot -i 0x19d2 boot recovery.img]

Noob here... I get 'adb' is not recognized as an internal file or external command, operable program or batch file... What am I doing wrong? I typed the command as said.

opticyclic said:
Unofficial TWRP For ZTE Nubia Z11 Mini​
This is vanilla TWRP and doesn't have custom "root menus" like the Russian and Chinese versions that are available.
This is currently using a prebuilt kernel and device tree blob (dt.img) extracted from my device.
The official kernel source is https://github.com/ztemt/NX529J_L_kernel but it doesn't compile with this config yet.
If you want to compile the exact same version as the attached file then you can use the manifest inside the zip to reproduce the build.
The source and build instructions are here https://github.com/opticyclic/android_device_nubia_nx529j
Instructions
Please test before replacing your stock recovery.
Load it temporarily by using fastboot boot instead of fastboot flash.
Code:
adb reboot bootloader
sudo fastboot boot recovery.img
If you are happy with it you can replace your existing recovery with
Code:
adb reboot bootloader
sudo fastboot flash recovery.img
If fastboot doesn't recognise your device then you can try forcing the vendor id like this
Code:
adb reboot bootloader
sudo fastboot -i 0x19d2 boot recovery.img
Changelog
2017-03-07
Added External SDCard as a mountable/wipeable option
Upgraded from 3.0.2.0 to 3.0.3.0
Click to expand...
Click to collapse
My Nubia z11 mini is not enter into fastboot mode , it recognize only QHSUSB_Bulk mode in PC device manager and with a blank screen , please help me how to flash this device,
and i have tried through QFIL tool but always i am getting sahara error ,
View attachment 4753032

How to lock bootloader after it was unlocked

This method was tested on P2a42 4/32 and P2c72 4/64 (both smartphones has 251 firmware installed).
Please, pay attention and read carefully:
You have a risk that P2 will go from EDL (9008) mode to 900E while you make a reconnect of connected to PC phone.
If you haven't successfully returned it by yourself into 9008 state - the only way is repair service. See details on 4Th step below the short instruction.
ADB and EDL (9008) drivers have to be pre-installed on your PC.​
For those, who faced with flashing firmware, gaining root, working with ADB and Fastboot commands, EDL mode on P2 and so on, here is the short instruction:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Wipe userdata via Fastboot: fastboot erase userdata .
4. P2 is connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
5. Flash 251 firmware as for unlocked device using START script .
6. Choose region ( ####682# ) and then make a reset ( ####7777# ).
7. That's all folks! Now you have locked P2 with a region that you want. So you can set the phone as you always do.
Below there is the same instruction, but detailed and with pictures.
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
Turn off P2.
Boot it into Fastboot mode - press and hold two buttons (Power And Volume -), on P2 screen you will see Fastboot mode: Screenshot 2.
View attachment 4358524
Connect P2 to PC (it is recommended not to use card readers; connect to USB which are situated on motherboard for PC, there is an exception for notebook (laptop)).
Press right mouse button and hold Shift on ADB folder, which is placed in the root of Disc C (С:\), choose "Open command line" - a CMD window will appear on the screen of PC.
In CMD window type fastboot erase secinfo and press Enter.
If all done properly, all drivers set properly, on the screen of your PC you will see: Screenshot 3.
View attachment 4358525
3. Wipe userdata via Fastboot: fastboot erase userdata .
Continue in CMD window. Type fastboot erase userdata and press Enter.
On the screen of your PC you will see: Screenshot 4.
View attachment 4358526
Close CMD window on PC.
4. P2 connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
blankflash folder must be placed in the root of Disc C (С:\).
On PC you must hold opened window of "Device manager" with opened string "Ports (COM and LPT)".
Your P2 must be connected to PC in EDL (9008) mode.
Use P2 very carefully without further re-connections, because there is a high risk, that P2 can go to 900E mode.
P2 connected to PC, press and hold all three buttons (Power and both Volume).
Hold buttons (phone will be rebooted twice) until you will see "Qualcomm HS-USB QDLoader9008 (COM12)" in opened window of device manager in string "Ports (COM and LPT)".
You might get another number of port (not only 12Th), it doesn't matter.
The main aim is "Qualcomm HS-USB QDLoader9008..." string in device manager.
Please, be very careful, because even little re-press of button or re-connect of cable will send your P2 to 900E mode with constant vibration and blue LED.
Try to restore phone to EDL (9008) mode by pressing and holding three buttons.
If you have no luck (from 900E to EDL) - congrats, you've got a brick.
From this point you should ask for help in repair service.
Going further, if all is going right and P2 connected to PC in EDL (9008) mode.
In device manager window on PC you will see this: Screenshot 5.
View attachment 4358527
From blankflash folder launch (double click of left mouse button) blank-flash.bat: Screenshot 6.
View attachment 4358528
You will see a CMD window which shows you a reset process of your P2.
If all done properly (without any "ERROR False"), you will see: Screenshot 7.
View attachment 4358529
In the end of reset your P2 will automatically boots from EDL (9008) mode to Fastboot mode: Screenshot 8.
View attachment 4358530
I suppose that there is no need to speak about 5Th and 6Th steps, because it is a basic knowledge, that you should know, when you are going to lock bootloader on P2.
Important notice.
You have to use original or other cable that has been already successfully used in Fastboot mode with your Р2.
The simple way to check cable is to type fastboot oem config in CMD and look what info it will give to you.
For those, who have already locked bootloader, it is strictly recommended not to flash stock ROM via flashall.bat.
For flashing stock you should use method for unlocked device, so you need to use START script.
All will go right if you will flash via flashall.bat after bootloader was locked, without any errors, Р2 will be booted as usual - Wi-Fi, SIM-cards (with names of operators), IMEI's and Serial number - all will be OK ...
But!
Calling, SMS and Mobile data will not work, you will see crosses on antenna icons in Status bar (in the string of modem firmware in "About" you will see "X" instead of "R" (Screenshot 9, 10) as it was, modems region will be defective).
View attachment 4358708View attachment 4358709
You can switch on/of Mobile data from Notification drawer, but there will be no connection, only Wi-Fi will work.
I am searching for solution of this problem.
As soon as it will be ready, it will be posted here. See post #2.
ADB folder (download, unzip) - View attachment ADB.rar
blankflash folder (download, unzip) - View attachment blankflash.rar
All thanks addresses to https://forum.xda-developers.com/member.php?u=279908.
I've just translated it from Russian to English from 4PDA site
Good luck and have a nice day!
Remember ...backup rules.

Solution.
Your phone must be unlocked and you must already have TWRP-backups of modem (NON-HLOS) and EFS from Р2.
1. Unlock bootloader.
2. Install TWRP.
3. Restore modem (NON-HLOS) and EFS in TWRP - you will get working modem, but there might be no sound in telephony.
4. You should install modem image via TWRP for Android 6 or 7 to get back to a working telephony (for additional instructions see post #3).
Later, if there will be a method which will work without TWRP-backups and possibly without unlock of bootloader, it will be posted here.
Modem download links:
Android 6 (062): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75313
Android 7 (244): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75314

How to restore a modem.
Important notice - you need to use modem with the same OS version which is installed on your phone.
Look here:
Firmware 062 - this is Android 6.
Firmware 233 and higher - this is Android 7.
Flash this:
For Android 6 - Modem_P2_062_ROW.zip
For Android 7 - Modem_P2_244_ROW.zip
Flash modem via TWRP:
1. Download zip for OS that you need (do not unzip it, rename or choose extension).
2. Copy to the phone memory (or to external micro-SD card).
3. Boot to TWRP and act as it is shown on the screenshots ...
View attachment 4358546View attachment 4358547View attachment 4358548View attachment 4358549View attachment 4358550

EDIT: did the first step wrong, now it's Locked

Do you have data and calls working?
Enviado desde mi Lenovo P2a42 mediante Tapatalk

Is the warranty back if the bootloader is relocked?

Danoz88 said:
Is the warranty back if the bootloader is relocked?
Click to expand...
Click to collapse
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
Thanks I thought the same. But in this case why should we go back to locked bootloader

Danoz88 said:
why should we go back to locked bootloader
Click to expand...
Click to collapse
It is personal decision. May be someone don't like to see "UNLOCKED" state.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
I agree... But there are some reports on this forum suggesting otherwise.
One common report is the replacement of motherboard for bricked devices, that too for unlocked devices.

Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
Oh great. Is this all it have to be done or followed by previous page? Any problems or things to be aware of?

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp

Shuvamilu said:
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp
Click to expand...
Click to collapse
First post, first picture.

Danoz88 said:
First post, first picture.
Click to expand...
Click to collapse
I don't understand

Shuvamilu said:
I don't understand
Click to expand...
Click to collapse
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
sergsinger said:
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
Click to expand...
Click to collapse

Danoz88 said:
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
Click to expand...
Click to collapse
Next process

If i unlcok bootloader, still recive system updates?

tapunger said:
If i unlcok bootloader, still recive system updates?
Click to expand...
Click to collapse
Yes, as long as you are on stock rom.

I lost my signal forever when I did a nandroid backup from another P2. I've tried it all, but nothing seems to work when it comes to restoring it.
I'm a bit confused by the first posts. OP talks about locking the bootloader and post #2 and #3 say you have to be unlocked to restore the modem? I'd have thought you wanted to lock it in order to flash the modem.

Accidentaly formatted all partions

I accidentally formatted all partition and now only have a TWRP. The TWRP only shows the start screen when i go to recovery.
Adb devices show me the device detected. I did a adb push and moved the stock rom 5.1.11 and my twrp recovery to the sdcard using the command adb push. I am struck here because i cannot get to the twrp screen which gives you option to install/wipe etc.
Can somebody please guide me if there is a way to recover or install the .zip files I have copied to sdcard. Thanks in advance

You need to fastboot flash the default stock rom, and then re root/install TWRP etc etc

Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.

SachinGopal said:
Thank you for your response. Will that be adb fastboot flash stock.zip ? I am not sure if this would mess it up hence please confirm. Also, will it work if i use the fastboot to install twrp again and then flash the stock rom using its menu.
Click to expand...
Click to collapse
You need to go to this thread... https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Download the version of OOS you want (5.1.11) and unzip the contents in to a folder and run the flash-all.bat file and let it install to all partitions. Just follow this instructions in the thread and you will be fine.

Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >

Thank you so much it worked when I tried. Grateful . Will donate the Dev for that bat script.

SachinGopal said:
Thank you so much for your response, but when I run this command I am getting " Waiting for device" option. I am only able to boot into twrp. I see the teamwin loading screen and its struck there. I am able to run adb commands and adb device shows the device details. I was also able to push the stock rom.zip through adb push command to /sdcard.
D:\OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT>flash-all-partitions-fastboot.bat
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
Click to expand...
Click to collapse
You need to be in fastboot mode.
Either adb reboot bootloader from inside android or from a powered off phone, hold Volume Up and power on.

[Guide] Backing up BlackShark (and other models too)

Hello, this guide explains how to backup your phone. This guide is intended for the BlackShark (SKR-H0), but works on other models, and other phones too.
So let's begin.
First of all, unlock your phone. This might void your warranty. Expect to lose all data on your device, so backup your internal storage to a pc or a cloud or something.
Boot your recovery (fastboot boot yourrecoveryfilename.img)
When inside the recovery (twrp example), it might ask you to enter a password, or swipe to allow modifications. Just ignore it and do nothing.
Now, connect your phone to your pc, and run the following adb command:
adb shell ls /dev/block/bootdevice/by-name/
You will get a list of files. Those are your phone partitions. You are going to back them up.
For every file (except for userdata, which contains the storage) you find, run the following command:
adb pull /dev/block/bootdevice/by-name/<filename> <filename>.img
Examples:
Code:
adb pull /dev/block/bootdevice/by-name/system_a system_a.img
adb pull /dev/block/bootdevice/by-name/system_b system_b.img
adb pull /dev/block/bootdevice/by-name/boot_a boot_a.img
....
Now you have a full backup. Enjoy it and keep it safe. When you **** up, this backup might be the only thing to save you.

I am late, I have updated to Pie and now TWRP is not working.
or do you have TWRP that works on Pie?

goonoth said:
I am late, I have updated to Pie and now TWRP is not working.
or do you have TWRP that works on Pie?
Click to expand...
Click to collapse
What do you mean it's not working?

gilbert32 said:
What do you mean it's not working?
Click to expand...
Click to collapse
when I push twrp with fastboot boot twrp.img its restart to system instead of recovery.
I think TWRP from https://forum.xda-developers.com/android/development/recovery-unofficial-twrp-recovery-t3892707 is not support on Pie yet.
Or do you have another recovery for Pie?