Database Develop

[Q] Can't Open My HTC One M7

Hi all. I've try to install today Android Revolution Google Edition 6.1.
So, my phone is S-OFF, i've install but after boot my phone all time restart. Not open, so, i don't have another rom in my SD card and now, i can't login my sd card for copy. So, i've try too many time from diffrent computer (windows 7 64bit, windows 8 64bit) from cmd and "adb" and i've receive all the time "device not found" error. So, i can flash recovery but "adb" is not work. I've install SDK and install everything but still not show. Any idea?
By the way so sorry for my bad English. Please help me.

soundeluxe said:
Hi all. I've try to install today Android Revolution Google Edition 6.1.
So, my phone is S-OFF, i've install but after boot my phone all time restart. Not open, so, i don't have another rom in my SD card and now, i can't login my sd card for copy. So, i've try too many time from diffrent computer (windows 7 64bit, windows 8 64bit) from cmd and "adb" and i've receive all the time "device not found" error. So, i can flash recovery but "adb" is not work. I've install SDK and install everything but still not show. Any idea?
By the way so sorry for my bad English. Please help me.
Click to expand...
Click to collapse
can you check my guide http://forum.xda-developers.com/showthread.php?t=2541082 under FAQ #2 if that's the problem with Windows Device Manager.
you can disregard the guide only check FAQ #2

nkk71 said:
can you check my guide http://forum.xda-developers.com/showthread.php?t=2541082 under FAQ #2 if that's the problem with Windows Device Manager.
you can disregard the guide only check FAQ #2
Click to expand...
Click to collapse
Thanks for you reply. Actually my drivers looks like ok. Please check image;
{
"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"
}
"flash" command its ok, but adb still not work :S I've try too many time reinstall driver.

soundeluxe said:
Thanks for you reply. Actually my drivers looks like ok. Please check image;
"flash" command its ok, but adb still not work :S I've try too many time reinstall driver.
Click to expand...
Click to collapse
fastboot commands work in bootloader
adb commands work in custom recovery (eg TWRP) or booted up ROM (with USB debugging enabled)
so if you need adb then enter custom recovery, check your device manager again, because it changes depending on where you are (bootloader, TWRP ... even version matters, or ROM)
once in TWRP, and device manager is good, adb devices should return you serial number and "recovery" -> then you can use adb commands

24945626 720
nkk71 said:
fastboot commands work in bootloader
adb commands work in custom recovery (eg TWRP) or booted up ROM (with USB debugging enabled)
so if you need adb then enter custom recovery, check your device manager again, because it changes depending on where you are (bootloader, TWRP ... even version matters, or ROM)
once in TWRP, and device manager is good, adb devices should return you serial number and "recovery" -> then you can use adb commands
Click to expand...
Click to collapse
Finally. Thank you very much for your help dear @nkk71, i've lost the adb command just work on custom recovery
I've install driver and now everythings its ok, i'm try adb sideload rom.zip

Magisk on Stock Xperia Z2 D6503 SAFETY NET PASSED

NOTE: This post was firstly added to the Xperia Z2 Forum and I decided to post it here as well thinking it might help someone else.
https://forum.xda-developers.com/xperia-z2/general/magisk-stock-xperia-z2-d6503-safety-net-t3700786
Firstly, I do not take any responsability in case anything happens to your device or your files. You decided to follow this guide at your own risk.
THIS WORKED FOR ME FOR MAGISK v14.3
ALSO WORKS ON MAGISK v14.5
I highly not recommend to use this guide for a different device other than the Xperia Z2 D6503.
All that aside, I managed to install magisk on my Stock Xperia Z2 and still keep ctsProfile and basicIntegrity: true.
HIGHLY RECOMMEND TO BACK EVERYTHING UP BEFORE PROCEEDING
You will need:
(OPTIONAL)Marshmallow FTF Firmware Here
(OPTIONAL)Flashtool Here
Magisk Manager Here
Rootkernel_v4.31_Windows_Linux.zip Here
ADB and Fastboot Here
Advanced Stock Kernel Here
TWRP Sirius Here
(OPTIONAL BUT HIGHLY RECOMMENDED) Use flashtool to flash the modified version of the stock ROM from above. It worked on this version but I can't really guarantee it will work on others. Can't really guarantee it will work on this either.(after you select the file there are 2 versions. pick the modified one).
1) Extract the Rootkernel_v4.31_Windows_Linux.zip and extract from the advanced stock kernel the boot.img (Rename it from boot.img to Old_boot.img)
2) Open cmd and use cd to reach the folder in which you extracted rootkernel.
Use the command "rootkernel Old_boot.img New_boot.img"
Say Yes to everything except installing TWRP.
3) Install Magisk Manager on your phone and copy "New_boot.img" to the phone.
4) Go to Magisk Manager settings , scroll to Update Channel and select Beta
5) Select install Magisk and select modify boot image. Select "New_boot.img" from the folder you copied it to
6) Extract adb to a folder
7) After patching the boot image at step 6, copy "patched_boot.img" from internal storage/MagiskManager to the folder in which you extracted adb
8) Copy TWRP to the adb folder and rename it to TWRP.img
9) Open cmd and use cd to navigate to the folder in which you copied adb. Type in the console "fastboot flash boot New_boot.img". Turn off your phone and then hold Volume Up whil plugging it into your pc(booting it into fastboot).
10) While still in fastboot, type "fastboot flash recovery TWRP.img"
11) Disconnect your phone from the pc. Wait a few seconds and then boot into TWRP (hold power button and Volume Down). A notification will pop up and select to "Keep System Readonly" (I think something like that). Reboot into system.
If everything worked as intended, a safetynet check will reveal everything in green, allowing you to both have root access and also run apps like Netflix and Android Pay
NOTE: Magisk Modules should be flashed via TWRP. For some reason, Magisk Manager is unable to install them.
EDIT: I tried to install xposed systemlessly but Safetynet was triggered. Don't think I can figure this out.
This worked for me but I can't guarantee it will work for you. (Photos at the end)
Did this guide help you? If you need any help, I will do my best to answer your questions.
I am not a developer and I do not really understand why or how everything works. I came across this method that worked for me and I thought I'd share it since I couldn't find a guide for my xperia phone when I needed it.
IN CASE SAFETY NET IS TRIGGERED, the only way to restore to everything in green is to reflash the stock rom (you don't have to format everything).
Did it work out for you? Just leave a reply saying that so I can figure out if everything works.
{
"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"
}
.

hi
Does it work for Magisk18?

Question Flashing Factory Images

I am trying to flash 11.0.0 (RD2A.211001.002, Oct 2021) factory image in windows using the flash-all bat file. I updated my fastboot drivers in windows update and downloaded the latest platforms tools from google's website. I get this error while running the bat file.
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 3.254s
Press any key to exit...
Any idea as to why?

Do you have your platform-tools folder in your PATH Variables?

kingofnice said:
Do you have your platform-tools folder in your PATH Variables?
Click to expand...
Click to collapse
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?

On Windows 10, type in the search bar "system environment variables" and open that settings menu.
{
"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"
}
Click on Environment Variables...
Edit
Add the location to your folder. Press Ok and Apply if you need.
Now try your adb and fastboot commands from a new command prompt window. They should be working from any directory you are using command prompt in.
I think that is why your flash failed, though I don't know. It sounds like it couldn't connect because it couldn't utilize fastboot to find a device/partition.
Test "fastboot devices" and if you see your device try flashing again. Also, "fastboot -w update image-xxx-xxx.zip" is in the flash-all bat. remove "-w" to stop it from wiping data. That's your call as you might need a fresh install.

Klimon5 said:
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
Click to expand...
Click to collapse
Did that help at all?

kingofnice said:
Did that help at all?
Click to expand...
Click to collapse
I ended up using Windows 10 to adb sideload the most recent android 11 OTA zip from google. I performed a factory data reset in recovery after I booted into the update first. I then was able to unlock the bootloader, re-enable the oem unlocking setting in dev options, & install the official lineage os recovery and rom for barbet. I will try your steps and see if I can flash a factory image. When I had my nexus 6p, I removed the -w prefix and immediately rebooted into recovery to factory data reset. It then booted just fine. For me I think that my platforms tools for Ubuntu are out of date.
I ran this command on my ubuntu machine.
$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
The lineage os installation instructions warns about issues with out of date platform tools.
Install LineageOS on barbet | LineageOS Wiki
wiki.lineageos.org
"Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
I want to try this on linux manjaro on my laptop. The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.

Klimon5 said:
For me I think that my platforms tools for Ubuntu are out of date.
The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Click to expand...
Click to collapse
This is the problem. Using outdated Platform Tools causes problems. Latest release is 31.0.3, Aug '21. Many other users have run into similar problems because they were using outdated Platform Tools.

[TUTORIAL] Revive your hardbricked M3 and revert back to EMUI 5/ Android 7

WARNING​
This tutorial is only for you who have hardbicked your M3 (BTV-DL09). This is the last option you have. If you still access any method or at least fastboot, please consider to use any other method.
Once again it is the last method to revive your device
As usual DO IT WITH YOUR OWN RISK. I WILL NOT RESPONSIBLE FOR ANY DAMAGE OF YOUR DEVICE
Scenario:
For some reason your device is hardbricked and nothing userfull method suitable to bringging back you device
Tools :
IDT Application can be downloaded here
Board Software can be downloaded here
ADB Software
HUAWEI APP Extractor can be downloaded here
Tools to open your device screen
USB cable
STEP 1:
Revive your device into basic firmware using IDT
Please refer to this tutorial to doing that. Your test point can be found by opening your screen device. please be careful when you open it.
{
"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"
}
This method will bring you to the basic firmware of this device (EMUI 2).
From here, your SIM will be locked. (I'm still dont know how to unlock, but everyting work well)
STEP 2
Update to EMUI 4
To do that you can use one of the following method:
a. Using dload
b. Using fastboot (I use this method because i dont have SD Card or USB OTG ), so i will explain this method.
You can download the firmware here
After downloaded, ectract UPDATE.APP from dload folder using APP Extractor.
Extract following files to your ADB folder:
- BOOT.IMG
- CUST.IMG
- SYSTEM.IMG
- FASTBOOT.IMG
- RECOVERY.IMG
Now we will flash IMG file.
* Boot into fastboot by connecting your device using USB cable
* open CMD then locate to your ADB folder
* type following command
Code:
adb devices
//to check connected devices
adb reboot fastboot
//you rdevice will reboot into fastboot mode
fastboot devices
//check connection
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash fastboot fastboot.img
fastboot reboot
Now disconnect your device. Your device should reboot system and running Android 6 EMUI 4.1
NOTE : First boot will take long time, so be patient
STEP 3
UPDATE TO EMUI 5 ANDROID 7
To do that we need to install TWRP. First you can download this version of TWRP for EMUI 4
You can refer to this tutorial to install TWRP
Download this OEM info
Copy oem info folder to SD Card or USB OTG. Place it in the folder TWRP/BACKUPS/<SERIAL NUMBER>
You can find SERIAL NUMBER on about tablet>>status>>SERIAL NUMBER
Download firmware BTV-DL09C100B307 form here and extract two zip file into SD Card/USB OTG root folder
Put in your SD Card/USB OTG
Now reboot into recovery > restore > locate your OEM info folder > restore.
Install update.zip
Install update_data_full_hw_eu.zip
Wipe
reboot system
First boot will took longer than first boot and you see Huawei logo if success
Congratulation, your device now running Android 7 EMUI 5.0.1
Optional you can install TWRP for android 7 here

Root Nokia 1 (TA-1066) (MT6737M) (Android 9 - Pie)

So, after trying more than a few methods I finally gained root on my TA-1066.
If you also wanna root, here is how:
To Root Nokia 1 (TA-1066) (Pie - Android 9) (Dual SIM)​
What you're gonna need:​
Working PC,
Some Packet Data,
Some knowledge of ADB & Fastboot commands,
Some storage space for storing Back Up of your phone,
and a Working Brain
WARNING!! ☠​I am not responsible for anything goes wrong to your phone by following the steps mentioned in this method. So, please do anything with care and if you don't know what is this, simply Stay away! ​
Make a Backup Of your phone's Data:​
Please make a Back Up of your data stored in your phone tp a safe place in your PC or somewhere in a disk. So, if anything goes wrong you can retrive it back from there.
Now Follow these steps:-​
Download attached ⬇ boot.img & keep it in your phone, we'll use it later.
Root boot.img using Magisk:
Download Magisk v25.2 from here.
Install Magisk app and open it.
Tap Install.
click Next.
click Select and Patch a File.
Select boot.img that you downloaded.
click Let's Go. (let the process complete)
Now rooted boot image will be stored in Download folder of your phone, move it your PC.
Install adb and fastboot into your PC​
Download the setup file from here.
Unzip and Run it as Admin.
Tap Next until it installs.
Enable developer options and turn on USB Debugging​
Goto Settings > System > Advance > About phone > Tap on Build number 7-8 times.
Go back and Tap Developer options > (scroll down) Turn On USB debugging.
Now connect your phone to your PC using USB Data Cable.
A prompt will appear asking permission, Tick Always allow from this computer and Tap OK.
{
"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"
}
Let the USB Data Cable connected and follow below steps.
In your PC open CMD and start typing these commands:​
Confirm that your device is connected:
adb devices
get your serial number by entring this command:
adb shell getprop ro.serialno
calculate md5 of the serial number using this site: https://passwordsgenerator.net/md5-hash-generator/
it'll look something like this D4423199AC65U1237C86D0E6BBF65243M
Reboot to bootloader:
adb reboot bootloader
Unlock using key (md5code=md5 of your serial number):
fastboot oem key md5code
Reboot and Turn on OEM Unlocking:
Settings > System > Advance > Developer options > Turn on OEM Unlocking
Reboot to bootloader:
adb reboot bootloader
Open Device Manager in your PC and follow this video below:
after doing as in video open CMD and type:
fastboot flashing unlock
Quickly press Volume Up button of your phone to unlock flashing.
Flash patched/rooted boot image. (boot.img = patched boot.img path in your PC)
fastboot flash boot boot.img
Reboot your phone to system.
fastboot reboot
Congratulations your Nokia 1 is now ROOTED!! Enjoy!!​Hit thanks button if you liked the process.
Feel free to ask any query.
​CREDITS​Method taken from this thread by @androidlover5842 , some changes made by me.​Thanks @Snoop05 for ADB and Fastboot.​Thanks @savadam for video tutorial.
and Me ​