Database Develop

rooting galaxy tab 10.1v (working)

hi, this is how i managed to get root working on my tab, everything went fine for me till it came to booting into recovery then nothing use to happen so i combined two separate guides to get it working. thanks (bcmobile and 411tecknology)
the command in "(getting root 5) )" worked for me as i was getting stuck with "fastboot flash recovery skitzandroid-recovery.img"
i unlocked the bootloader by firmware upgrade the the following
for all those people like me with no experience in dos commands or linux, hope this works for you​
PREPARE:
1) With your Tab in fastboot mode (step 1 of “GETTING ROOT” below), make sure you have a working fastboot implementation:
working dir\\fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won’t get any response.
2) Downlad the two files attached to this thread
3) create a folder in drive c naming it "root"
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!) c: root
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder( c: root) should now have 1 IMG file and one ZIP file.
6) copy fastboot files to the the folder that you are going to use as working dir ( c:root)
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
working dir or c:\root>adb push skitzandroid-10-1v-root.zip /sdcard
GETTING ROOT:
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
keep doing cd.. until you get to "c:>" then
cd/root
5) Run the following command:
c:\root> fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options)
to select “Install zip from SDCARD” (or something like that)
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
Once complete, use the Volume rocker to select “REBOOT” from the menu and press (tap!!!) the POWER button to confirm selection.
9) YOUR’RE DONE. Press the thanks button on this thread to continue
TESTING:
Check your apps menu to confirm the existence of SuperUser app.

whats wrong with this?
http://forum.xda-developers.com/showthread.php?t=1079781

Nothing!
I used it on UNLOCKED 10.1v (not from Vodafone) and had no data loss!
Great, Thanks
Frank

I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes

TNTCOSMOS said:
I do not understand: 3) Confirm you are now in fastboot mode and do a:
fastboot devices
If all is well, you should see your device serial number.
Where do I enter this data?
I mean - fastboot deviсes
Click to expand...
Click to collapse
once you start your device in fastboot mode and connect it with the computer to make sure your device is recognized by the computer you open command prompt take it to your working dir.. (ie. c:>root) in our case type fastboot devices and hit enter, if your computer recognized your device you will the serial number under it.

im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....

TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
assuming you have installed sdk if not please do so, then staying in sdk go to
(C:\android\android-sdk-windows\platform-tools ) by clicking your mouse in desktop
(not cmd prompt). above eg.. is how i installed sdk on my desktop yours may be different, now in platform-tools you will see two files called fastboot copy them both to to your folder called ..root.. and you are set to go.
bottom line is if you want to start fastboot from any folder in cmd you have to have these two files in the folder.
also if you know that your device is detected by your computer dont worry about step 3. all it does is tell you that your device is connected.

I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!

TNTCOSMOS said:
I have all turned out, the problem was the drivers. I copied the driver from pdanet and it worked!
Click to expand...
Click to collapse
Glad to hear that you finally got the root.

same problem
TNTCOSMOS said:
im sorry> can you help me?
When i write in the command line "fastboot.exe devices" nothing happens....
Click to expand...
Click to collapse
i've tried with pdanet too but it's not working....like the computer can't see the device...any ideea ???
and when i write "fastboot boot ......etc......" it says <waiting for the device>
please help

You need the drivers installed for fastboot, have you installed them? Please have a look at the [Guide] Unlock your bootloader thread. it contains all the details to get fastboot working.

thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???

zbuggy said:
thank you...finally did it
another noob question...how do i enter in cwm for installing another ROM ???
Click to expand...
Click to collapse
The easiest way if you are rooted is to install rom manager from the market. It has an option to reboot to recovery if you have CWM installed. It also allows you to update to the latest CWM recovery if there is one.

i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?

Download latest rom and instructions from samfirmware.com using odin Get ur tab into fastboot mode with 3 button recovery and start from scratch.
It should work out
Sent from my GT-P7500 using Tapatalk

zbuggy said:
i've tried putting the TB Galaxy 1.0.9: Honeycomb 3.1 + TouchWiz UX and i made a mistake... in cwm i've uploaded the zip file only with the update and not the rom itself.since then the tab won't start...it stop's in the beggining at the "samsung galaxy tab 10.1v"...any ideea...what can i do ?
Click to expand...
Click to collapse
Do the following. If you have not yet odin.
Download the full rom.
Follow instructions in how to get into fasboot in sticky thread.
Once in fastboot you can load recovery via it, to do that download the recovery from droidbasement.com/blog, search on pershoot's website for recovery 4.0.4 if i remember correctly then type
fastboot boot recovery.img
where recovery.img is the name of the file you downloaded from droidbasement.com
Recovery will then load give it a minute or so.
Once loaded you can push the downloaded full rom via adb. That is part of the android sdk.
Like this: adb push romfile.zip /data/media/ (this will take a few minutes)
Then in cwm instal rom.
I hope it helps. Btw, remember you need to flash the wipe script of the rom before you install the rom if you are comming from stock.
Send from my GT-P7100

10x everybody it worked!!!!!!!!

Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...

DannyBiker said:
Still me, posting in yet another thread. Still can't get the proper drivers. Pda method is not working. Which version of PDanet should I use ? The latest ? This is ****ing irritating...
I'm used to have to struggle to get things work at the beginning, but with my Magic and Hd2 it was a matter of hours...not weeks ! I'm sure it's something stupid but everybody deserted these guides topics...
I'm actually considering posting in the Dev section just to get attention...
Also, pershoot blog's advices are a joke : with no tags, a not working search field, no categories, try to find an info ! Knowing that the word "Recovery" will pop about 3 times per subject, I'm good to spend the week-end searching...
Click to expand...
Click to collapse
Hello,
I have been successful with rooting on win7. With win xp - after a few day struggling - fastboot did not give a go. Hope this helps

I just can't get the "Adb Original" signature from Pdanet. I always get standard Adb. I add the galaxy tab lines in the .inf file but still...
Do you guys edit the inf file with Wordpad or another tool ?

[Q] DS7 stuck on setup wizard

Hi,
I'm using a TMobile 4G DS7 in Europe (no SIM card); last week as I restarted it (battery was very low) I started receiving error messages (Email app has stopped unexpectedly, then Gmail and you name it...) and was sent back to the setup wizard.The DS7 was running on the original setup, no OS upgrade had been done.
I tried a factory reboot which didn't change anything.
I started reading this forum and tried the 3 options which are described
1- updating with a 306 .pkg file on the SDCard
the following takes place
Booting kernel recovery Image
Blue text
Finding update package
Opening update package
Verifying update package
Install modem error . System will upgrade again. (90% bar)
Screen turns black then reboots
and back to square one !
Trying other packages results in an error message, process stops at verifying update package .
2- Fastboot mode
I downloaded and installed the drivers
I put DS7 in fastboot mode and get the fwg :
Username : cmbuild hostname : ***** buildnumber : ******
Build on Mar 11 2011 17:19:36
Starting Fastboot USB download protocol
On PC I go to the directory where the fastboot.exe is stored .
When I type < Fastboot devices>
I get <? fastboot> which seems to indicate that no device is identified ( under Config panel in Windows I can see that the device is recognized as an Android device) ....
3- NVFlash mode
I put the DS7 in NVFlash mode connected it to my PC . The config panel showed there was a prob (yellow triangle). I installed the driver .... and now the device does not even appear when I go Config panel / System
So I get nowhere under any of the 3 options ; can I just throw away my DS7 or is there still some hope ? things I haven't done correctly ?
Any help suggestion would be most appreciated.
Thx in advance to whoever wil read this thread.
FG

the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.

giveen said:
the ???? Device under fastboot is normal
ONce you put the device into NVFlash mode and you install the drivers, open up Device Manager and look under the USB section, you should see something about Nvidia recovery mode.
Click to expand...
Click to collapse
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.

FGMareil said:
You're right. I flashed everything went all right but after "pinbooting" no change still stuck.
Click to expand...
Click to collapse
You might be in read-only mode, which can only be fixed by Dell

giveen said:
You might be in read-only mode, which can only be fixed by Dell
Click to expand...
Click to collapse
The OP stated that the battery was low which is one reason some have claimed to cause this.

can anyone offer me some help

Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated

Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.

but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this

BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.

thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks

No OS on phone! OTG USB / conncetion to PC not recgonized! Seeking Help

In the past 3 months or so I noticed that my Mi5 3GB 32GB is not recognized by my PC anymore. I didn't care too much because I hardly connect my phone to PC.
I was running the lastest xiaomi.eu Rom unrooted.
So on Thursday, I deleted my OS by mistake, therefore I do not get past the Mi Logo.
I can boot into TWRP Recovery & Fastboot however, there is not code when using CMD adb/fastboot devices such as 1cwe3f23.
Also, I read about the EOL method aka test point method, to force a connection as Qualcomm driver with no success. Different PCS dont recognize any drivers.
The battery is not an issue because I can easily charge my phone to 100% and it can hold its charge, therefore I do not think it is a battery related issue.
What i did so far :
- used 3 differenct USB C cables and PC -> phone still not recognized
- Installed all lastest driver on Drivers -> phone still not recognized
- tried to use the test points method -> phone still not recognized
- tried Miflash tool -> phone is still not recognized
- tried Mi PC Guide -> didn't work either
Then I read somewhere that I can use a OTG cable with a pen drive
- OTG storage is not recognized in TWRP recovery and cannot be selected. [OTG STORAGE 0MB even if different pen drives are connected]
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Please help me out since I really struggling with this problem for the past 7 days and I'm desperate now for any kind of help.
Greetings and thanks in advance.

amando1991 said:
SO my Main problem is not the phone itself, it is that I cannot get any data onto the internal memory because I can't get past TWRP.
Click to expand...
Click to collapse
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.

Hi bro
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
goodluck
Sory bad englis

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
I did as you recommended and used Ubuntu. However also there the system didn't recognize the phone when plugged. It may because I am not fully familiar with Ubuntu. I would appreciate if you could point me in the direction of a tutorial.
same as me, 4 days ago...
system, vendor error
flashing stock rom miui9 via twrp
although the error twrap will only provoke usb computer,
if it works usb computer, try flashing by using miflash...
Click to expand...
Click to collapse
could you be more precise please? How did you overcome not having a PC conncetion?
Currently, I am not able to transfer any kind of data to the phone either by PC or OTG. Furthermore, the internal storage is completely empty after wiping everything by mistake.
I have twrp working fine, but without any data on the device, I cannot use it. Also, the device only stays in fastboot for roughly 20 secs before it turns off.
any help is welcomed. Thank you
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there

amando1991 said:
EDIT : I got Ubuntu to work but its the same process. My phone is not recognized and running the command adb devices gives me
"list of devices" .... thats not! Nothing ! usally there is the code Phones ID but nothing there
Click to expand...
Click to collapse
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.

moo113 said:
A number of different issues could be here.
#1 Firstly, ensure you've installed openvm tools and reboot. This should enable things like hardware pass through.
$ apt-get install open-vm-tools open-vm-tools-desktop
$ sudo init 6
Then, follow these instructions for the pass through (may be slightly different, but very similar) https://forum.xda-developers.com/showthread.php?t=570452
#2 Type "adb" and see what version is in use in the first line of output. If it's 1.0.0.32 or older, it might be an issue. Try installing the following packages:
$ sudo apt-get install android-tools-fastboot android-tools-adb
You might need to find a newer version elsewhere, Ubuntu repos are often old. Google around for 1.0.36 or newer. This could solve your issue.
#3 Ensure you have the necessary rules for the Mi 5. There's a few different hardware models. The Arch Wiki can walk you through it better than I can: https://wiki.archlinux.org/index.php/android#Connect_device (ignore the package hyperlinks, they're arch-specific). Only do this if you've properly configured the pass through from #1. Do F"igure out device IDs" and then "Adding udev Rules". Instead of the "udevadm" command run
$ sudo service udev restart
If you're still not detected, no idea.
Click to expand...
Click to collapse
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?

amando1991 said:
Thank you again for the help!
Unfortunately, it appears that my device is still not recognized by either Ubuntu or Win10.
I Have taken the necessary steps to install Ubuntu and update the adb drivers (1.0.39) but still no luck so far.
It really pisses me off since I was stupid enough to wipe the internal storage ☹ and not I am not able to transfer any data to the devices again.
Any other out of the box ideas?
Click to expand...
Click to collapse
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.

moo113 said:
You configured the USB pass through to your Ubuntu host? Double check you followed #3, and then run sudo fastboot devices. That step is tricky for some.
Reconnect your phone to your Ubuntu host (in fastboot) and run "dmesg -T", see what errors are present. If you have no errors, I would image it's a configuration issue. Other than that I'm out of ideas.
Click to expand...
Click to collapse
OMFG!!! First of all, thank you for support and your patience. I really appreciate it.
HOWEVER, all it was is that the USB PORT was full of dust( literally tons!) which appears to have allowed to charge the phone but seemed to have cloaked up some part of the responsibile for a usb connection to a computer.
Stupid me should have known this because the usb port was kinda wobbly which I had mistaken for degradation using the phone for almost 2 years
MANY THANKS!

moo113 said:
What do you mean by "can't get past TWRP"? Is it that you can't flash any ROM to system?
You have fastboot and TWRP, so things are likely fine. Rather than use Windows, you might have more luck running linux inside VirtualBox (plenty of guides around XDA). If you can sudo fastboot devices in linux, you should be good to go. Otherwise, the error reporting is often richer/simpler in linux.
Click to expand...
Click to collapse
Hey , I was researching about my issue and came up to this. I'd be really glad if you can sort me out with this. I have the same mobile , by mistakenly wiped out the phone including the internal storage , my pc does not detect the device , and whenever i go to fastboot mode to try something like miflash , it goes back to twrp after 15 seconds. Also , i tried several OTG's but none of them get detected on TWRP , and I am stuck on this thing for almost a week now . Please guide me on how to sort this out . i basically just downloaded adb files , miflash , etc from the internet and never reinstalled them. also i used several usb c cables to connect to pc and even then device manager does not detect it . thank you . i would really appreciate your reply.

Question Partially bricked phone

Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast

Audoghast said:
Good evening.
I have the following equipment and an unsolvable problem:
- Oneplus Nord CE 5G
- Twrp-3.5.2_11-ebba
- Bootloader unlocked
- ADB platform tools 30.0.5, 33.0.1 and 33.0.3
For the last five months I have been trying to root the phone but nothing works. The only thing I can start is twrp in recovery mode.
System boot generates: dm-verify device corrupted Force Dump kernel_restart.
Initially, internal and OTG USB showed 0MB but I could change the file internal file system and now it is showing the correct capacity. The laptop also detects it now as internal folder but no contents.
OTG USB never shows anything and I have tried different SUB sticks and formats.
There is no way to transfer anything from the PC to the phone or vice versa.
When in twrp recovery mode, the phone accepts ADB commands but whenever I try bootloader mode or fastboot mode from the twrp menu, I cannot issue fastboot commands from my laptop (which worked before when I unlocked the bootloader).
I believe the only way is to flash the phone completely and I have extracted the files using Payloader Dump.
However, without fastboot commands there is no way to transfer anything to the phone and install.
I have not tried an SD card yet and it would be a nano type.
Does anyone have any idea? I am seriously frustrated and have seen any error message imaginable.
Thanks a lot in advance.
Audoghast
Click to expand...
Click to collapse
While your phone is in fastboot and connected to your laptop; How is it shown in device manager?

Good evening.
I found the solution to unbrick my Oneplus Nord CE 5G and here it is.
Status: - normal start leading to Qualcomm Crash Dump screen
- Recovery mode into TWRP possible but no transfer of files to/from phone
- No Fastboot possible
Procedure:
Install Qualcomm USB Drivers from
https://www.getdroidtips.com/download-qualcomm-qdloader-hs-usb-driver/
You may have to launch the command prompt as admin and type:
bcdedit /set testsigning on
I did not have to do it because the Qualcomm Driver installation did it for me.
After restart you will see the following message in the lower right side of your PC:
Testmode Windows 10 Pro + build number
To get rid of end at the very end type:
bcdedit -set testsigning off
Download the following package:
Europe: https://onepluscommunityserver.com/...BA/R/OnePlus_Nord_CE_EU_OxygenOS_11.0.9.9.zip
India:
https://onepluscommunityserver.com/...R/OnePlus_Nord_CE_India_OxygenOS_11.0.4.4.zip
These packages contain the MSM Download Tool and the respective files. Beware that you have to get the correct bundle for your phone. Other bundles contain MSM Download Tool too but will not be compatible and the tool generates a failure message.
Launch MSM and type OTHER at login.
Target was EU in my case.
Then click on start.
Now your phone needs to boot into EDL mode. It worked for me from the TWRP Reboot screen but supposedly starting the phone by holding the volume up and down buttons for 45 seconds does the same.
The screen will be totally black, no beep, no vibration, no feedback.
Then connect the USB cable and MSM will start working. After about 5 minutes the phone should be back to normal.
ADB commands worked again too (phone was being recognized as USB device under device manager). However, fastboot did not work. The device was listed as other device in the manager.
After updating the driver using the following files everything worked:
https://drive.google.com/drive/folders/1D96njoYn-n3alu3ggaK3Kw8hMGLKhJVg
Now I am back to rooting and will report about that too.
Good luck