Database Develop

Please Help Tried Updating to 4.4 Kitkat Bricked

Ok so I tried updating my phone that was already rooted on Android 4.3 S-OFF to 4.4 kitkat with sinless rom sense. Transferred the rom zip to my phone, then proceeded to wipe the system and data, as well as davalik cache with clockworkmod recovery. Attempted to flash the rom and it aborted. Tried a few times and nothing worked. Didn't realize till after that my phone had no OS, and now all I can do is enter the bootloader. Can't enter recovery as the phone will enter clockworkmod then abort and reboot the phone. Not sure what to do at this point as I tried one of the guides and couldn't figure it out. If anyone can help me I'd greatly appreciate it. At least I backed everything up on my computer manually and am using my iPhone 4 until I can get this fixed. Thanks in advance.

Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk

nathlynn22 said:
Try reflashing recovery then if that works ad b push or usb otg a working Rom to your phone
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks

You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk

nathlynn22 said:
You need to reflash cwm. I'll try find a link. But after recovery is working you would have to use ad b to sideload the Rom. Have you tried from bootloader fastboot erase cache?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
My biggest issue is being able to reflash clockworkmod. If I could that out of the way, I already have the rom on the phone storage, so I should in theory be able to reflash I'd think.
I don't have the option to delete cache within the bootloader under fastboot

One Hype said:
How do I reflash recovery when I can't access the filesystem? Do I need to setup ADB and connect to my phone via command line to initiate the transfer? Can you link me to a thread that explains how to setup ADB in a case like this? Thanks
Click to expand...
Click to collapse
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!

hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Gotcha. Makes sense. Will try and let you know. Thanks so much!

Htc one kiktkat 4.4 update gone wrong
hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
I did all what you said there its still takes me back to bootloader...
and that red message active cmdline overflow (1085bytes) still there...any soulutions to fix this please?

hardstuffmuc said:
How did you get your One rooted, then?
You need to install ADB/Fastboot on your computer. Best to create a folder directly on C:
In that folder you also copy the .img of the recovery (you need latest TWRP for 4.4 ROMs)
Now, once ADB/Fastboot Folder is set up, the TWRP download is copied into the same folder, you go to your bootloader and connect the One via USB and select FASTBOOT (red letters) and once connected you see (USB)
You open a CMD window (START and type cmd) , in that window you point to the fastboot folder:
cd c:\fastboot (or whatever name you choose as in link above)
fastboot erase cache (enter)
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img (enter)
fastboot erase cache (enter)
you see the commands running in the cmd window
after that you can choose inside the recovery the ADVANCED option and SIDELOAD ADB
I have not done that, so you need to search the forum on how to do that.
Njoi
Screenshot to see the Fastboot folder on my laptop with the TWRP file in it
Just saw that you still have the .zip of your ROM on your internal storage. So just choose to install that and that's it! Be careful with the wiping option and only choose factory reset or cache/dalvik and never system!
Click to expand...
Click to collapse
Just tried everything and it worked 100%! Can't thank you enough!

flash which ROM ?

Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you

intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer

when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you

you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond

My nexus will not flash correctly

Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!

Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.

Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.

If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard

Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.

Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.

Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...

Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...

coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.

You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished

dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.

Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".

dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else

Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.

Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.

dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.

hi guys..good day

last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?

jdaryl04E19 said:
last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?
Click to expand...
Click to collapse
hmm...model code?
and your device is unlocked bootloader?

Giannhs Togias said:
hmm...model code?
and your device is unlocked bootloader?
Click to expand...
Click to collapse
Che2-L11....yes it is unlocked, it was accidentally deleted using TWRP.
is it still possible to make it work again?
thank you in advance.

jdaryl04E19 said:
Che2-L11....yes it is unlocked, it was accidentally deleted using TWRP.
is it still possible to make it work again?
thank you in advance.
Click to expand...
Click to collapse
Step1: Download the ROM Package from the link
http://consumer.huawei.com/jo/support/downloads/detail/index.htm?id=87523
Step2: Extract using Winrar. (Inside dload folder you will find Update.app file)
Step3: Download Huawei Update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
Step4:: Now Run the huawei update extractor and point to the update.app file.
Now the contents of the update.app file will be displayed.
Select the Boot.img,recovery.img and System.img alone and select extract by rightclicking it.
Step5: You need the adb tool kit.
https://drive.google.com/file/d/0B8C...R3c/view?pli=1
Step6: Install and configure the Adb (yes all)
Step7: Copy the extracted recovery.img,system.img and boot.img to the adb root folder which should be in c:\adb\.
Step8: Open fastboot (connect the device to usb and press vol down) + open adb (shift+right click and select to open cmd here)
And now type in cmd:
1. "fastboot devices" -Displays some id of your device which makes sure your device is connected.
2. "fastboot flash recovery recovery.img" - Flashes stock recovery
3. "fastboot flash system system.img" - Replaces your custom rom with stock rom
4. "fastboot flash boot boot.img" - Flashes boot partition which is need to boot stock rom.
5. "fastboot reboot"
Step9: End restart your phone,open recovery and select "Wipe data/factory reset :laugh:

Giannhs Togias said:
Step1: Download the ROM Package from the link
http://consumer.huawei.com/jo/support/downloads/detail/index.htm?id=87523
Step2: Extract using Winrar. (Inside dload folder you will find Update.app file)
Step3: Download Huawei Update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
Step4:: Now Run the huawei update extractor and point to the update.app file.
Now the contents of the update.app file will be displayed.
Select the Boot.img,recovery.img and System.img alone and select extract by rightclicking it.
Step5: You need the adb tool kit.
https://drive.google.com/file/d/0B8C...R3c/view?pli=1
Step6: Install and configure the Adb (yes all)
Step7: Copy the extracted recovery.img,system.img and boot.img to the adb root folder which should be in c:\adb\.
Step8: Open fastboot (connect the device to usb and press vol down) + open adb (shift+right click and select to open cmd here)
And now type in cmd:
1. "fastboot devices" -Displays some id of your device which makes sure your device is connected.
2. "fastboot flash recovery recovery.img" - Flashes stock recovery
3. "fastboot flash system system.img" - Replaces your custom rom with stock rom
4. "fastboot flash boot boot.img" - Flashes boot partition which is need to boot stock rom.
5. "fastboot reboot"
Step9: End restart your phone,open recovery and select "Wipe data/factory reset :laugh:
Click to expand...
Click to collapse
i was in the cmd and started to type the commands but it say that the "fastboot" is not recognized as an external or internal command, operable or batch file...
my phone is open in fastboot and rescue mode and "unlocked"

jdaryl04E19 said:
i was in the cmd and started to type the commands but it say that the "fastboot" is not recognized as an external or internal command, operable or batch file...
my phone is open in fastboot and rescue mode and "unlocked"
Click to expand...
Click to collapse
you need to download minimal adb and fastboot, and run the commands from it. or, you can do it the easy way. just put your update.app file inside /dload/ folder, and do the forced upgrade. if its not working, then fallback to fastboot method.

jdaryl04E19 said:
last day i accidentally delete the os of my honor 4x..does somebody know how to install new os and where to download a new one?
Click to expand...
Click to collapse
This method is propably easiest https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702 It also has link to site that has firmwares.

keikari said:
This method is propably easiest https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702 It also has link to site that has firmwares.
Click to expand...
Click to collapse
Thank you

How To Guide [TUTORIAL] ULTIMATE How to flash GSI Trebble AND ROM and root on Xiaomi device on Windows (files needed included)

Hi, first of all, I'm not a dev or else just user who had difficulties to flash GSI on my phone... Was 7 years with a samsung galaxy Note 3, with twrp....So easy to flash....
with the help of @gr0ndpa, thanks to him.....
FLASH GSI​
Now I will explain how to flash easily with files attached
1/ first of all you need a phone and drivers installed, use xiaomi pc suite, unzip and install it
2/ you need to activate USB debug in dev options.
3/ dl platform tools folder unzip it and put in C
4/ run command and type
Code:
cd /adb
5/ then
Code:
adb devices
to check if phone recognised
6/
Code:
adb reboot bootloader
once in fast boot
7/
Code:
fastboot flash vbmeta vbmeta.img
wait finished type to enter in fastbootD
8/
Code:
fastboot reboot fastboot
9/
Code:
fastboot flash system
LiR 313.XXX.img
you will have a system error, but wait the flash begin in few seconds
at the end wait ok then
10/
Code:
fastboot reboot recovery
on stock recover
11/ wipe data and reboot with +/- and PWR
and you're done...
In case you want to flash custom kernel or patched boot image to root with magisk, you have to
12/
Code:
adb reboot bootloader
Copy kernel boot image to C drive and rename kernel boot image to boot.img.
13/
Code:
fastboot flash boot c:\boot.img
14/
Code:
fastboot reboot
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
You can check what I ve done on tuto ss...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==================================================================================================================================================================================================================++
Flash ROM​
This now how to flash ROM on your device, it's convenient for all roms like LOS, corvus, awaken...
First you need all the proper drivers installed and unlocked bootloader, USB debugging all of that stuff.
Now open up a cmd/terminal , and put the files i sent and the ROM file in the folder from where you're opening the cmd/terminal and connect the phone (you may need to put ./ as an suffix for all the commands if you're on linux)
Type
Code:
adb reboot bootloader
Then type
Code:
fastboot devices
to see if everything is ok
Then type
Code:
fastboot flash boot_ab boot.img
(you can drag and drop the file instead of typing it)
After that's done type
Code:
fastboot flash vendor_boot_ab vendor_boot.img
(you can drag and drop this too if you want)
Code:
fastboot flash dtbo dtbo.img
(you can drag and drop this too if you want)
After that's done type
Code:
fastboot reboot recovery
This will boot you into a recovery and now you need to go to wipe and format data
After that go to apply update then adb sideload then
In the cmd type
Code:
adb sideload rom.zip
for example (you put the ROM zip here you can drag and drop it)
Wait for that to finish it will go to 47% and on the phone it will show step 1/2 then step 2/2
and when it's done it's gonna show an error
adb: failed to read command: No error
Then you can reboot to system

One more

Two more

This the tuto I follow to flash renoir, who have same characteristic than all Note 12 series... Tuesday I can confirm it works

I'm having a problem that my phone can't go to fastboot via CMD after I flash vbmeta.
Is is me doing wrong or also happen to you?