Develop Bugs

[Q] Unrooting: now i can not log into the system!?

Fixed! thanks guys!

Drop the toolkit and do it manually. Boot into bootloader and lock it with fastboot.
The android with the red triangle is the stock recovery.

stop being lazy with the toolkit...
http://forum.xda-developers.com/showthread.php?t=1626895

But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?

hxgni said:
But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?
Click to expand...
Click to collapse
Debugging mode has nothing to do with fast boot or custom recovery. It only applies to a booted OS.
So, no its not required.
Do some reading and comprehend what you are doing to your device.
Sent from my Galaxy Nexus

Pirateghost said:
Debugging mode has nothing to do with fast boot or custom recovery. It only applies to a booted OS.
So, no its not required.
Do some reading and comprehend what you are doing to your device.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
reading? THATS UNHEARD OF AROUND HERE! YOU SPEAK BLASPHEMY
---------- Post added at 03:31 PM ---------- Previous post was at 03:31 PM ----------
hxgni said:
But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?
Click to expand...
Click to collapse
way to not follow the guide btw

ok thanks guys, i finally got it fixed

[Q] Nexus 7 Hardbricked?!

Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!

See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582

mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?

crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.

mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!

crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.

mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.

crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.

Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?

crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs

malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.

crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links

malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!

crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?

malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).

For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.

The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.

Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/

(Soft)Bricked LG G4

While installing the latest version (6.0) which I downloaded, I also wiped the system partition.
Now when I turn it on it just stays at "LG Life's Good" and it won't leave that state unless I turn it off.
I can't enter bootloader/fastboot mode nor recovery for TWRP.
Is there anything I can do?
Note: when I try to do the combination for recovery mode I get the message if I want to go back to factory settings, TWRP doesn't come up.

you cant do nothing . just wait as a lot of people on the forum because is not possible yet to use the flashtool . for flash kdz 5.0 or 6.0

shudoha said:
you cant do nothing . just wait as a lot of people on the forum because is not possible yet to use the flashtool . for flash kdz 5.0 or 6.0
Click to expand...
Click to collapse
I can't even boot to TWRP. Now I have a 500€ brick.
**** me.

melasuda said:
I can't even boot to TWRP. Now I have a 500€ brick.
**** me.
Click to expand...
Click to collapse
its the same issue with a lot of people . you can with flashtool . not need twrp . but for the moment need to wait a update for that

You wiped your /system partition = no OS = so the system can not boot. Not a brick.
The TWRP issue is a bit interesting tough, how did you wipe it? you tried the temporary boot to TWRP via fastboot commands? Or flash it via fastboot again?

davebugyi said:
You wiped your /system partition = no OS = so the system can not boot. Not a brick.
The TWRP issue is a bit interesting tough, how did you wipe it? you tried the temporary boot to TWRP via fastboot commands? Or flash it via fastboot again?
Click to expand...
Click to collapse
its the same issue for a lot of people . as he cant go on android .. he cant put usb debugging then not adb ... and not twrp anymore . reset factory changes nothing . the only one way its flashtool but for the moment need to wait a update bcz impossible to downgrade . and kdz 6.0 doesnt work ....

Who talked about ADB here?

davebugyi said:
Who talked about ADB here?
Click to expand...
Click to collapse
fastboot . without adb on your computer and without your computer recognized your device because not usb debugging ... how you want ?

shudoha said:
fastboot . without adb on your computer and without your computer recognized your device because not usb debugging ... how you want ?
Click to expand...
Click to collapse
There is an update for the G4, where fastboot also requires debugging enabled? No other android phone I ever owned required USB debugging enabled for fastboot, not even the S6 (920F)

davebugyi said:
There is an update for the G4, where fastboot also requires debugging enabled? No other android phone I ever owned required USB debugging enabled for fastboot, not even the S6 (920F)
Click to expand...
Click to collapse
you understand nothing ... with the new 6.0 update for the moment a lot of people have a bootloop as issue ... impossible to make a hardreset ... impossible to install twrp ... impossible to use the flashtool saw the flashtool software is not updated yet ... you cant flash the 5.1 or 6.0 for the moment ... there are too much people with this issue on the website ... look all the post*
we have not access at fastboot mode or recovery mode if you prefer . when you use this option ... the hard reset its impossible and that restart the phone and bootloop again and again

shudoha said:
you understand nothing ... with the new 6.0 update for the moment a lot of people have a bootloop as issue ... impossible to make a hardreset ... impossible to install twrp ... impossible to use the flashtool saw the flashtool software is not updated yet ... you cant flash the 5.1 or 6.0 for the moment ... there are too much people with this issue on the website ... look all the post*
we have not access at fastboot mode or recovery mode if you prefer . when you use this option ... the hard reset its impossible and that restart the phone and bootloop again and again
Click to expand...
Click to collapse
Of course I do not understand, when you are trying to tell me that fastboot needs USB debugging, rather than new bootloader is causing issues

davebugyi said:
Of course I do not understand, when you are trying to tell me that fastboot needs USB debugging, rather than new bootloader is causing issues
Click to expand...
Click to collapse
i told you just for send the commande about fasboot with adb . you need the usb debugging option that all . but only with adb on windows . if you want make that alone you can... but with this issue is not possible there are not more recovery . too much people wait a solution for that

shudoha said:
i told you just for send the commande about fasboot with adb . you need the usb debugging option that all . but only with adb on windows . if you want make that alone you can... but with this issue is not possible there are not more recovery . too much people wait a solution for that
Click to expand...
Click to collapse
Ermmm wait. So you say the G4 does not have a hardware button combo to boot into download/fastboot straight away from a power off state? That is kinda fail from LG.

davebugyi said:
Ermmm wait. So you say the G4 does not have a hardware button combo to boot into download/fastboot straight away from a power off state? That is kinda fail from LG.
Click to expand...
Click to collapse
all people with this issue after have flashed the autoprime zip etc etc have this problem . you have access at download mode but flashtool doesnt work for the moment because imposible to downgrade for 5.1 and imposible to use kdz 6.0 ... the factory reset doesnt work . whn you do it . you have again the bootloop isue . and impossible to have access at the recovery mode . we are more 100 people on xda to have this issue
then yes you have the button cmbo . and you go in factory reset . normaly after you can go in recovery mod but that doesnt work

davebugyi said:
Ermmm wait. So you say the G4 does not have a hardware button combo to boot into download/fastboot straight away from a power off state? That is kinda fail from LG.
Click to expand...
Click to collapse
It doesn't.
And also if you do the combination of volume down and power button for recovery mode, TWRP won't come up.

davebugyi said:
Ermmm wait. So you say the G4 does not have a hardware button combo to boot into download/fastboot straight away from a power off state? That is kinda fail from LG.
Click to expand...
Click to collapse
even you can go into fastboot mode (check this thread: http://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537/post63623844#post63623844) but that won't help unless you have an unlocked bootloader.

nipun1110 said:
even you can go into fastboot mode (check this thread: http://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537/post63623844#post63623844) but that won't help unless you have an unlocked bootloader.
Click to expand...
Click to collapse
first you take the autoprime post already on the forum ... and he is not completed . you have put the half only .

nipun1110 said:
even you can go into fastboot mode (check this thread: http://forum.xda-developers.com/g4/general/guide-how-to-enter-fastboot-mode-t3239537/post63623844#post63623844) but that won't help unless you have an unlocked bootloader.
Click to expand...
Click to collapse
I just tried that, with an unlocked bootloader, it doesn't work.

shudoha said:
first you take the autoprime post already on the forum ... and he is not completed . you have put the half only .
Click to expand...
Click to collapse
autoprime posted this? where? can u send me the link? in fact i have given all the credits to all the devs possible. if autoprime has already mentioned this guide somewhere, i will delete the post for sure.
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
melasuda said:
I just tried that, with an unlocked bootloader, it doesn't work.
Click to expand...
Click to collapse
Didn't work what? U couldn't even enter fastboot mode? upto where u could go?

nipun1110 said:
autoprime posted this? where? can u send me the link? in fact i have given all the credits to all the devs possible. if autoprime has already mentioned this guide somewhere, i will delete the post for sure.
---------- Post added at 06:07 PM ---------- Previous post was at 06:06 PM ----------
Didn't work what? U couldn't even enter fastboot mode? upto where u could go?
Click to expand...
Click to collapse
I got to
Code:
SPECIAL COMMAND : ENTER , LEAVE
#
After that, if I tried to "id" then it would say "FAIL."

Redmi Note 5 Pro dead, no fastboot, no recovery, no led

Hi all,
after waiting 15 days, I have unlocked the bootloader, flashed twrp, firmware and rom, then rebooted.
the phone is dead ever since.
I can see it in device manager as "Qualcomm HS-USB QDLoader 9008 (COM10)", but I am not able to flash a rom through miflash.
any help is welcome
*additional informations*
here are the steps i followed:
1) unlocked bootloader succesfully
2) flashed official twrp
3) wiped EVERYTHING except sd ext
4) flashed this firmware
https://sourceforge.net/projects/xiaomi-firmware-updater/files/Developer/
5) flashed this rom
https://forum.xda-developers.com/re...ment/ota-resurrection-remix-os-6-0-0-t3777375
6) rebooted, dead
I noticed now that if i try to turn on the phone, the led blinks a few times
PROBLEM SOLVED:
the phone is alive again. Here is what I have done-
1) I opened the phone and tried the test point method, but I noticed that nothing changed in the way the phone was detected by my laptop. So, it's not crucial have "COM 7" in device manager.
Then I basically followed the steps suggested by @Destrangis in post #3
2- In MiFlash Choose CLEAN ALL and install this rom: http://bigota.d.miui.com/V9.2.7.0.NE...179eb04f38.tgz
3- Installed TWRP, WIPES and flash https://androidfilehost.com/?fid=5862345805528041092 and Magisk
4- Come back TWRP, WIPES and install your favorite rom.
Click to expand...
Click to collapse

lomax84 said:
Hi all,
after waiting 15 days, I have unlocked the bootloader, flashed twrp, firmware and rom, then rebooted.
the phone is dead ever since.
I can see it in device manager as "Qualcomm HS-USB QDLoader 9008 (COM10)", but I am not able to flash a rom through miflash.
any help is welcome
Click to expand...
Click to collapse
EDL booting and flashing is your solution.
Now, only debatable is will you use EDL booting procedure which requires opening of the phone to short two contacts to be able to boot in EDL or You will use altered ADB which gives possibility to boot in EDL without case opening. This second option is somehow questionable but first, i think, if second option to enter EDL without opening is way to go!
---------- Post added at 07:37 PM ---------- Previous post was at 07:03 PM ----------
lomax84 said:
Hi all,
after waiting 15 days, I have unlocked the bootloader, flashed twrp, firmware and rom, then rebooted.
the phone is dead ever since.
I can see it in device manager as "Qualcomm HS-USB QDLoader 9008 (COM10)", but I am not able to flash a rom through miflash.
any help is welcome
Click to expand...
Click to collapse
I hope this guide will help you!

lomax84 said:
Hi all,
after waiting 15 days, I have unlocked the bootloader, flashed twrp, firmware and rom, then rebooted.
the phone is dead ever since.
I can see it in device manager as "Qualcomm HS-USB QDLoader 9008 (COM10)", but I am not able to flash a rom through miflash.
any help is welcome
Click to expand...
Click to collapse
Hard brick. I went through it. Follow these steps: https://www.youtube.com/watch?v=lfkRHAW2iXI .
1- You have to activate the EDL mode.
2- In MiFlash Choose CLEAN ALL and install this rom: http://bigota.d.miui.com/V9.2.7.0.N...EK_20180406.0000.00_7.1_global_179eb04f38.tgz
3- Installed TWRP, WIPES and flash https://androidfilehost.com/?fid=5862345805528041092 and Magisk
4- Come back TWRP, WIPES and install your favorite rom. :good:
PD: If you see "COM7" in MIFLASH, go directly to step 2.
---------- Post added at 07:59 PM ---------- Previous post was at 07:55 PM ----------
Jehonan said:
EDL booting and flashing is your solution.
Now, only debatable is will you use EDL booting procedure which requires opening of the phone to short two contacts to be able to boot in EDL or You will use altered ADB which gives possibility to boot in EDL without case opening. This second option is somehow questionable but first, i think, if second option to enter EDL without opening is way to go!
---------- Post added at 07:37 PM ---------- Previous post was at 07:03 PM ----------
I hope this guide will help you!
Click to expand...
Click to collapse
The second opcion (ADB) doesnt work in RMN5.

what rom caused the brick?

devcon69 said:
what rom caused the brick?
Click to expand...
Click to collapse
info updated in the first post.
Is it crucial to have COM 7 port for EDL?

so, its been over a day now, have you fixed the problem?

t.hasan1 said:
so, its been over a day now, have you fixed the problem?
Click to expand...
Click to collapse
the phone is alive again.
I am in the process of flashing a custom rom again.
I'll update you when I'm done

lomax84 said:
the phone is alive again.
I am in the process of flashing a custom rom again.
I'll update you when I'm done
Click to expand...
Click to collapse
Whats did you do?

lomax84 said:
the phone is alive again.
I am in the process of flashing a custom rom again.
I'll update you when I'm done
Click to expand...
Click to collapse
what method you solved your brick phone ?

Give the method you do

Error: Cannot read hello packet. Why solved?

following...how did you solve it ? come on

mxilil said:
what method you solved your brick phone ?
Click to expand...
Click to collapse
masjiko said:
Give the method you do
Click to expand...
Click to collapse
please see first post

I tried to test point to give flash in the rom by Miflash, the pc recognizes my device in the COM port, when initiating the process it gives an error message: CAN NOT READ HELLO PACKET. Does anyone know how I can solve this problem? my device is simply dead because of that anti-rollback that Xiaomi implemented.

Diegosdias said:
I tried to test point to give flash in the rom by Miflash, the pc recognizes my device in the COM port, when initiating the process it gives an error message: CAN NOT READ HELLO PACKET. Does anyone know how I can solve this problem? my device is simply dead because of that anti-rollback that Xiaomi implemented.
Click to expand...
Click to collapse
Did you removed the battery?

devcon69 said:
Did you removed the battery?
Click to expand...
Click to collapse
yes...

Diegosdias said:
yes...
Click to expand...
Click to collapse
Try to use usb 2.0 ports.
Maybe edl mode has timed out. Press the power button for 20-30 seconds to power cycle the phone.
Or open it up and remove battery pin for a minute. Reconnect and try again.

devcon69 said:
Try to use usb 2.0 ports.
Maybe edl mode has timed out. Press the power button for 20-30 seconds to power cycle the phone.
Or open it up and remove battery pin for a minute. Reconnect and try again.
Click to expand...
Click to collapse
I already tried on usb ports 2 and 3, and it did not work. Holding the buttons for a long time did not solve either. I opened it to test point, removed the battery, but none of it makes the phone work. The problem is that at the time of fash in Miflash it gives the following error: CAN NOT READ HELLO POCKET. I do not know what this error is or what it is about?

lomax84 said:
please see first post
Click to expand...
Click to collapse
Did you recognize what caused the hard brick to your phone?
I think you followed the right steps, yet your phone got hard bricked, is it a firmware issue or RR rom issue?!

Ahmed_HM said:
Did you recognize what caused the hard brick to your phone?
I think you followed the right steps, yet your phone got hard bricked, is it a firmware issue or RR rom issue?!
Click to expand...
Click to collapse
By following his link to the firmware file on sourceforge you will see that he flashed a note4x firmware on his note5... So guess where the issue was...

Cannot connect to adb Lineage OS 16

Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?

djramrques said:
Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?
Click to expand...
Click to collapse
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!

Deleted

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
I am note sure what happened but did you mean to reply twice?

djramrques said:
I am note sure what happened but did you mean to reply twice?
Click to expand...
Click to collapse
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
djramrques said:
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!
Click to expand...
Click to collapse
Oh, I have no experience with a/b devices like yours

kurtn said:
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
Oh, I have no experience with a/b devices like yours
Click to expand...
Click to collapse
So turns out, if I use my old cable (Which is a bit ruined at on end), it works. But if I use a new cable, that I just bought, it does not work. That is super weird right?
Thank you anyway. I am flashing Pixel Experience at the moment. ANd now I am TWRP installed.