Database Users

[Q] hours for searching for nothing help plz!

I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!

There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.

let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!

alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.

alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.

If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.

It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.

downloadmode should still work. go back to any kdz for your version
also source and versions post next time

Installing twrp with locked bootloader

I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom

Nice... Did your bootloader get unlocked after you flashed the eu global ROM?

nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter

I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!

Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp

Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!

My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working

tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)

same for me!

g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.

Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.

Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.

Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded

There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.

I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!

Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post

After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB

alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk

iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix

I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.

No ADB, no Fastboot, No Boot. Please Help.

Hello everyone,
Yesterday I was trying to upgrade my supersu to newer version, my Oneplus Two is on CM13 Nightly.
After the upgrading I'm not bootloop.
The recovery is working (TWRP) but when I'm trying to turn on the adb Sideload the computer isn't recognizing it.
Else, the computer doesn't recognize the phone when I'm trying to do the Unbrick Guide as describe in the offical website.
How can I make the computer recognize my phone?
I have music/photos which really important for me so I can't wipe my internal storage.
Please help me as soon as possible,
Thanks!

https://www.androidfilehost.com/?fid=24591000424939640
try unbrick using this file..then you can enter fastboot mode and sideload any stock rom to your phone without wipe your internal storage.
i can't find the original thread make by @Naman Bhalla
good luck !

Phones in a bit of a state

Hey guys,
Yesterday I tried, after a few months of not modding my phone, to update my recovery as i was running a very old version of TWRP. Long story short I did something wrong somewhere and my phone has ended up in a bit of a weird state.
At the moment the OS is BlissRom, however it fails to boot. The loading screen runs very slowly and never actually boots the OS. The current recovery is the stock recovery.
The thing that is giving me an issue is the fact that somehow the bootloader has locked, so I am unable to flash a new OS onto my phone. I'm not able to flash anything onto my phone as it throws an error telling me the phone is locked.
Overall I aren't able to boot into the OS, however I have access to the stock recovery and fastboot. Unfortunately it looks as though the bootloader has locked some how.
Any ideas how I can fix this, or have I completely messed my phone up?
Thanks in advance.

Hi
U said u were running twrp before which means u have unlocked bootloader and flash roms already.
How did u end up with stock recovery?
Also is it phone being detected bycur PC?
Sent from my ONE A2005 using Tapatalk

I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.

colinbest2 said:
I believe it was a result of running the QualComm restoration tool. I ran this and it didn't look as though it did anything however after i rebooted into recovery I found it was stock.
I'm not sure if using this tool also re locked the bootloader however as it appears to be locked and I cant flash anything in fastboot mode.
Click to expand...
Click to collapse
Did u also tried command fastboot oem unlock
Sent from my ONE A2005 using Tapatalk

Indeed I have, I get an error saying "phone is locked".
I think the resolution will be running the restoration tool fully but i cant seem to get it to do anything. It just sits there with no progress bars appearing.
Have you ever had any experience with this tool?

No I never used recovery tools.
Can u at any point let's say u boot into recovery and connect the device to PC, will it detected the internal storage?
Sent from my ONE A2005 using Tapatalk

Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.

Dude i think you have to use recovery tool now
Here is the link first read carefully https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Thanks for the link buddy.
I've gone through this thread, I think the issue preventing this from working for me is the fact that although I have installed the relevant drivers, when I plug my phone into my PC the drivers assigned to it are "Android Bootloader Interface". When I try to target another driver, using the Update driver functionality it just refuses to change, saying the driver already assigned is the newer one.
Any ideas how I can get around this? I know ideally it should appear as Qualcomm 9008. I've tried all the methods in the "How to Make the device show as Qualcomm 9008" section without any success.

colinbest2 said:
Unfortunately not, if I boot the OS it gets stuck at the loading animation, it isn't a bootloop oddly enough.
Booting in recovery the PC doesn't detect the internal storage, however if I choose "Update from USB" I can see that ADB detects my phone in sideload mode.
Much like in fastboot mode I can see my PC detects my phone in fastboot mode.
I do have some OS zips on the internal storage which I have tried flashing in stock recovery, however these always result in "Install failed" errors.
Click to expand...
Click to collapse
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk

Brandon Indar said:
Here's what to do...
U will need to sideload the stock rom which can be downloaded from here: https://s3.amazonaws.com/oxygenos.o...4_OTA_020_all_1608262242_44a55e674a2b4bf6.zip
-Place the zip in ur adb folder and rename it to update.zip.
-Connect the Oneplus2 to the PC with USB cable and open a command prompt or terminal on your PC. To do this open the ADB folder press shift + right click and click on open command here.
-Reboot to recovery and select install from usb.
-Flash the OxygenOS on OnePlus 2 by typing:
adb sideload update.zip
-Now the update will start and this will take some time.
Hope it helped[emoji106]
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.

colinbest2 said:
Hey dude, thanks for the help! So I went through these steps and it actually appeared to sideload and update properly.
However now it looks as though my phone is stuck at the one+ logo when I go to boot the OS.
Click to expand...
Click to collapse
Try this one :
https://s3.amazonaws.com/oxygenos.o...4_OTA_019_all_1606041303_bd42fc5cc5cc4ab2.zip
If still stuck on boot logo, boot in fastboot, connect to PC and run command : fastboot erase userdata
If not work try sideload a rom u have with same steps[emoji4]
Sent from my ONE A2005 using Tapatalk

Bricked - please help !

I accidently formated everything in twrp and ended without OS and was stuck in custom twrp. I tried to flash stock recovery and that went ok. Now whatever i do i cant sideload stock zip file using adb. Fastboot is recognized but adb is not. When connected to pc shows error. I have tried to install, reinstall all sorts of drivers but all the same. Is there a way to get back to stock using fastboot commands manualy? Please help !!

Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.

himanshuladia said:
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
Click to expand...
Click to collapse
You mean stock twrp or custom because i have stock but when connected i cant copy files on device because it is not recognized by PC

Del.

TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.

himanshuladia said:
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
Click to expand...
Click to collapse
Ok will try !

Del.

Finaly i did it after a few hours of trying to find a solution and figuring out why my PC doesn't recognize phone in adb I tried on an old PC with win7 installed and sideload went smooth like butter on first attempt. I have tried on two computers with win10 installed, tried with all sorts of USB cables, usb on computer 3.0 , 2.0, tried all sorts of drivers and nothing helped. I hope that someone else will have a benefit of this post and sort of a solution if he will have the same issue. Thanks to everyone that tried to help out!