Hello, i have a lot need of you. After a very bad bootloops, i arrived to reboot my oneplus5 but after that usb just charge and my computer don't detect it (in fastboot or not, with dev setting on ect...). I don't undertsand what the hell. Please help me. Thank's in advance.
Hi!
For fastboot, you have to have fastboot installed on your computer, of course. Make sure the command prompt runs as administrator.
For USB file transfer, make sure you select the right option from the notification area to allow file transfer.
Also make sure USB debugging is enabled in developer settings.
AlexCmb said:
Hello, i have a lot need of you. After a very bad bootloops, i arrived to reboot my oneplus5 but after that usb just charge and my computer don't detect it (in fastboot or not, with dev setting on ect...). I don't undertsand what the hell. Please help me. Thank's in advance. Alex
Click to expand...
Click to collapse
Try reinstall the Oneplus 5 drivers.
Thanks a lot guys, but it's already done. No problem with the drivers. Before that, i have a mysterious message in red who speak about the /vendor partition (Failed to mount /vendor in TWRP).
The USB OTG don't work too.
Another Idea?
PS: (It IS a good Idea to try the unbrick tool?)
AlexCmb said:
Thanks a lot guys, but it's already done. No problem with the drivers. Before that, i have a mysterious message in red who speak about the /vendor partition (Failed to mount /vendor in TWRP).
Click to expand...
Click to collapse
Is it when you're in TWRP that you encounter the issue?
When you're in TWRP, go to "Mount", and make sure the second button at the bottom says "Disable MTP" -- this means TWRP has (tried to) enabled MTP file transfer. If it says "Enable MTP", click on it to, well... enable MTP.
Also, you may want to press the third action button, as the bottom of the screen, to switch from the TWRP interface to the logging interface. There, you should see if MTP has been enabled, disabled, or if any issue happened.
(The red "Failed to mount '/vendor' (Invalid argument)" message is normal, has no link to your issue, and will only go away if you ever come to flash a Treble-compatible ROM like MoKee.)
Alexandre-P said:
Is it when you're in TWRP that you encounter the issue?
When you're in TWRP, go to "Mount", and make sure the second button at the bottom says "Disable MTP" -- this means TWRP has (tried to) enabled MTP file transfer. If it says "Enable MTP", click on it to, well... enable MTP.
Also, you may want to press the third action button, as the bottom of the screen, to switch from the TWRP interface to the logging interface. There, you should see if MTP has been enabled, disabled, or if any issue happened.
Click to expand...
Click to collapse
I have flash stock OOS on TWRP without flash magisk so my twrp was overwritten by stock recovery.
Without fastboot, impossible for me to try that.
Alexandre-P said:
(The red "Failed to mount '/vendor' (Invalid argument)" message is normal, has no link to your issue, and will only go away if you ever come to flash a Treble-compatible ROM like MoKee.)
Click to expand...
Click to collapse
Thanks for this informations ! :fingers-crossed:
Ok guys, I have tried the unbrick tool for OnePlus 5, works great (same tool than Oppo that's nice) but problem persist. No fastboot, USB OTG isn't detected on the phone (sure, I have enabled it) and no access to internal storage from computer.
AlexCmb said:
Thanks a lot guys, but it's already done. No problem with the drivers. Before that, i have a mysterious message in red who speak about the /vendor partition (Failed to mount /vendor in TWRP).
The USB OTG don't work too.
Another Idea?
PS: (It IS a good Idea to try the unbrick tool?)
Click to expand...
Click to collapse
Do you have blu spark twrp 8.74 with treble support? That's the message you get when twrp searches for vendor partition but you didn't have one. Try using blu spark twrp 8.73 instead which has no treble support
strongst said:
Do you have blu spark twrp 8.74 with treble support? That's the message you get when twrp searches for vendor partition but you didn't have one. Try using blu spark twrp 8.73 instead which has no treble support
Click to expand...
Click to collapse
So, impossible for me to try this because i have the stock recovery installed now... And without fastboot, that's complicated... ^^
Hello, After sent my oneplus to service center, they tell me that i need to change the motherboard... Lol
Related
UPDATE:
Version v15 seems to work now .. also on N preview now
Update.ZIP_TWRP_dragon_3.0.2-0_v15.zip (to be installed via TWRP)
TWRP_dragon_3.0.2-0_v15.img (to be installed via fastboot)
Download: https://onedrive.live.com/redir?res...17&authkey=!ACPxBsf1QD-Fr0M&ithint=folder,zip
Please test with encrypted data partition.
Big thanks to @NYCHitman1 for his help !
As well .. Thanks to all the encrypted Pixel C owners helping testing !
Thanks
DELETED
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
RolfFrie said:
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
Click to expand...
Click to collapse
Thanks for your test and feedback !
Not recognizing encrypted partition here either (NPD35K)
zezayer said:
Not recognizing encrypted partition here either (NPD35K)
Click to expand...
Click to collapse
Yep .. Thanks.
It's not working ... yet.
Not sure by when and by whom it will be implemented.
Will update the first page accordingly ..
EDIT:
You engage me for a new try ..
RolfFrie said:
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
Click to expand...
Click to collapse
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
followmsi said:
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
Click to expand...
Click to collapse
Failed to decrypt data.
Testing of v7:
TWRP brings up the decrypt screen on booting, asking for a password to be entered.
Unfortunately I get a "Password Failed, please try again!" on entering my password (4 digit PIN)
"Failed to decrypt data " error when attempting via command line.
This appears to be closer than the previous boots, it recognizes the encrypted partition. I will try again with a password rather than pin
Still having the bootloops when booting into TWRP forum.xda-developers.com/pixel-c/help/twrp-bootloops-t3389438
Thanks for testing .. Seen somewhere you may need to enter password twice.. Just as test, try stock kernel for bootloop issue. Thanks
followmsi said:
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
Click to expand...
Click to collapse
twrp now asks for decryption password. But always returns "passwoord failed"
I tried it three ways with the same result "Failed to decrypt data":
At start of twrp
via mount and decrypt
Last version I think there was no decrypt button and there was a check box for data partition. This could not be checked.
Now there is the decrypt button but the data partion is missing. Klciking the button the result is as mentioned above.
via terminal
So we are getting further ...
RoFrie said:
twrp now asks for decryption password. But always returns "passwoord failed"
I tried it three ways with the same result "Failed to decrypt data":
At start of twrp
via mount and decrypt
Last version I think there was no decrypt button and there was a check box for data partition. This could not be checked.
Now there is the decrypt button but the data partion is missing. Klciking the button the result is as mentioned above.
via terminal
So we are getting further ...
Click to expand...
Click to collapse
Are you able to post the recovery.log of your steps ?
Maybe on pastebin.com ...
Thanks
followmsi said:
Are you able to post the recovery.log of your steps ?
Maybe on pastebin.com ...
Thanks
Click to expand...
Click to collapse
Thanks !
New version compiled today .. v8 ...
Code:
could not find any keystore module
Failed to init keymaster
Please mount /system partition before your start to decrypt via terminal ..
Is the recovery.log changing -> ... "could not open keymaster device in keystore .. "
Ot still "could not find kestore module" ?
Thanks for testing ..
NYChitman made also a new Version for encryption... pls test as well. .. http://forum.xda-developers.com/showthread.php?p=67138209
v10 is my last try on encryption .. makes a copy of the current dragon.keystore while starting up recovery.
This version has also a new kernel included and logcat for TWRP was compiled too.
And no bootloops while testing
Cheers
Still the usual loops on my device but only when I start from recovery. Strange thing. And it does not happen when stock recovery is installed. The funniest thing: If stock recovery is installed I can't open it if I want to. It's the red triangle droid. And if TWRP is flashed it opens if I don't want to Tried to flash the whole tablet back to start from scratch.At the moment impossible. Wiped, flashed, wiped and so on. I get the message (factory image): unable to truncate file... File too large failed to extract system.img I/o error. Installing from TWRP works fine. Tried to close and open bootloader: Not possible without stock recovery. Aaargh. I found out: There were some guys having this issue on Nexus devices who re-installed all drivers and software on their PC to solve the problem or used a different PC. That's my next step next Friday. I'm going to get everything on this stupid son of a... on this tablet working, I swear. Now, dear Pixel C, it's something personal Don't mess with an angry social worker!
GonzoKSV said:
Still the usual loops on my device but only when I start from recovery. Strange thing. And it does not happen when stock recovery is installed. The funniest thing: If stock recovery is installed I can't open it if I want to. It's the red triangle droid. And if TWRP is flashed it opens if I don't want to Tried to flash the whole tablet back to start from scratch.At the moment impossible. Wiped, flashed, wiped and so on. I get the message (factory image): unable to truncate file... File too large failed to extract system.img I/o error. Installing from TWRP works fine. Tried to close and open bootloader: Not possible without stock recovery. Aaargh. I found out: There were some guys having this issue on Nexus devices who re-installed all drivers and software on their PC to solve the problem or used a different PC. That's my next step next Friday. I'm going to get everything on this stupid son of a... on this tablet working, I swear. Now, dear Pixel C, it's something personal Don't mess with an angry social worker!
Click to expand...
Click to collapse
Did you found a solution ?
to "close/open" bootloader you need "full" stock !
Afterwards you can flash TWRP via fastboot again.
Maybe it solves your issue.
again one missing flag .. in fstab -> the very last try on encryption
Update.ZIP_TWRP_dragon_3.0.2-0_v11.zip
TWRP_dragon_3.0.2-0_v11.img
Cheers
Hi followfsi,
I tried your last build without encryption and it seems that in this build adbd doesn't accept the connexion anymore
"error: device unauthorized. Please check the confirmation dialog on your device."
That was working in the 6.0 build
Samt434 said:
Hi followfsi,
I tried your last build without encryption and it seems that in this build adbd doesn't accept the connexion anymore
"error: device unauthorized. Please check the confirmation dialog on your device."
That was working in the 6.0 build
Click to expand...
Click to collapse
Thanks for the finding ... V12 arrived
Update.ZIP_TWRP_dragon_3.0.2-0_v12.zip
TWRP_dragon_3.0.2-0_v12.img
Pls check now .. should work again..
And decryption ?
Do you get a password prompt ?
Does it work ?
Cheers
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.
I flashed my Zenfone 5 to CM 13.1. For the first few week of usage it was perfectly fine and had no issue after after a while the phone was acting weird so I rebooted it, while it was booting up it was stuck in the Cynogenmod logo and I figured out it was a bootloop. I tried many method to bring it back to stock but failed, i even tried the methods which i used when i was suing CM 12.1.
Issues I found:
I could flash from a tool called "Zenfone Assist" and could flash from adb but when I tried to wipe from TWRP it said failed to mount /cache /system etc and many other partitions.
I tried to lock the boot loader and change the recovery back to stock, it did say "okay" in the flashboot but nothing chnaged in the phone. The bootloader was not locked and the recovery was still TWRP. I tried many methods but it stays the same. The only thing that i could wipe was the /system.
I tried to restore using the jelly bean .raw file and still no luck, it showed 2 partitions failed ( one being OEM the other I'm not sure) and its still the same, the same unlocked bootlaoder and TWRP recover.
One member here suggested that my internal storage might be corrupted.
If it is , is there any alternative way out of it and is there any other methods I could use that might work.
Much thanks for responses.
Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works
leonardohenrique10 said:
Boot to TWRP > "Wipe" > "Advanced Wipe" > Mark "Data" > "Repair or change file system" > "Repair" > "Swipe to repair"
See if it works
Click to expand...
Click to collapse
didnt work, it said unable to repair /data and error repairing file system.
zaris47 said:
didnt work, it said unable to repair /data and error repairing file system.
Click to expand...
Click to collapse
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?
leonardohenrique10 said:
Try change to other file system, and if it works, change back to ext4
Also, "Format Data" option doesn't work?
Click to expand...
Click to collapse
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4
zaris47 said:
Format data says unable to mount '/cache' '/system' '/data'
Changing file system is still the same, the same message and error. Although now /datd is to ext3 and now i cant change from that :3
I could also change to ext2 but now can;t revert back to ext4
Click to expand...
Click to collapse
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
leonardohenrique10 said:
Well, try this: http://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.
zaris47 said:
Gave it a try and failed. Now the bootloader is still unlocked (which it shouldn't be since the guide repartitioned it) and when I go to recovery it shows a usb sing.
Click to expand...
Click to collapse
Well, your phone is really f*cked up
You already tried xfstk method?
leonardohenrique10 said:
Well, your phone is really f*cked up
You already tried xfstk method?
Click to expand...
Click to collapse
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?
zaris47 said:
No not that. I never heard of that. Can you tell me or give me a link to a guide of its?
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
leonardohenrique10 said:
Here: http://forum.xda-developers.com/android/development/hard-bricked-zenfone-unbrick-method-to-t3131911
Click to expand...
Click to collapse
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?
zaris47 said:
I will try that as a last resort. What I would like to know is whenever I try to re-partition with .raw file or adb there are 2 errors always showing,
one Failed cause cant partition oem and the other, Failed cause cant format spare
Another problem is the bootloader isn't locking, any clue on why any of these 3 problems occur?
Click to expand...
Click to collapse
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)
leonardohenrique10 said:
I got this error in spare partition when I tried to flash raw firmware. This partition doesn't exist in my device, so, I changed the extension of the firmware from .raw to .zip, opened "sec_update_image.bat" with Notepad++ and deleted all lines about spare partition. After edit, I replaced this file into zip and changed extension back to raw, and it flash sucessfull. I think you can do the same for oem partition.
About bootloader, try to extract "dnx_fwr_ctp_a500cg.bin" and "ifwi_ctp_a500cg.bin" from any firmware (I recommend from Lollipop .87, I always relock with these files) and flash it manually (fastboot flash dnx dnx_fwr_ctp_a500cg.bin; fastboot flash ifwi ifwi_ctp_a500cg.bin)
Click to expand...
Click to collapse
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened
zaris47 said:
:\ didnt work. As for the raw one I cant seem to do anything and I use Zenfone assist, do you know any other tool or method to flash faw file (i tried zenfone flashtool but didnt work for some reason, think its because I dont have the asus drivers for the phone , mine is windows 10 it doesnt have any drivers for that)
flashboot relocking failed, i mean it did show "Okay" but still nothing happened
Click to expand...
Click to collapse
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone
leonardohenrique10 said:
I flashed the RAW with ASUS Flash Tool, with my phone in Fastboot (Droidboot) mode. Everything worked fine.
Sorry, but I don't know how I can help you now
Good luck with your Zenfone
Click to expand...
Click to collapse
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?
zaris47 said:
May I know which os did you use? Since I dont know why but the driver for zenfone is not supported for win 10 (the one im using) so does that make a difference?
Click to expand...
Click to collapse
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.
leonardohenrique10 said:
I'm using Windows 10, all drivers works fine.
Download "adb and fastboot drivers", and install on Windows 10. It should work.
Click to expand...
Click to collapse
I had errors with that 15 sec adb install drivers but the ones I've downloaded worked too I guess, I sued that to flash to CM13.1 in the first place
@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.
zaris47 said:
@leonardohenrique10
even the xfstk method didnt work. It keep on showing error. It has got to be a problem with the drivers or my os. Since evey time there problems occur as errors some problem occur during the flashing.
Click to expand...
Click to collapse
Try from another computer, preferably using Windows 7.
leonardohenrique10 said:
Try from another computer, preferably using Windows 7.
Click to expand...
Click to collapse
tried and it showed the same error, although this time i noticed that the two drivers with the asus device in device manager, one of them has a problem, the adb one it said (altho adb worked fine)
Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
rienheuver said:
Hey all,
I have a OnePlus 2, which had Resurrection Rom (and TWRP 3.0.2-2). However, I wanted to factory reset that ROM. Problem is: I wiped too much data.
I now have no more OS (TWRP -> Reboot -> Reboot System gives a message "No OS installed!").
I do have TWRP 3.0.2-2 and can boot to it.
I have no img of an OS on the device (as far as I know, since I wiped basically everything).
If I go to TWRP -> Advanced -> ADB Sideload, it will go "Starting ADB sideload feature...", hang there for a few minutes and then give a red FAILED on the top of the screen.
I have the phone connected with USB to my pc (Ubuntu 16.10), but I can't find it with lsusb and I can't seem to transfer files that way either.
So my question is: how do I get any ROM back on there? Stock OxygenOS without a custom recovery or whatever would be fine, as long as I can boot to an OS again.
Any help is greatly appreciated, thanks in advance!
Greetings,
Rien
Click to expand...
Click to collapse
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Jitesh.saitawadekar said:
Try connecting it to windows pc and mount storage internal storage will pop up if drivers are installed properly just copy and install rom.
Click to expand...
Click to collapse
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
rienheuver said:
I tried installing the drivers I found through Google ("oneplus 2 usb drivers -> result on technobuzz).
After that I connected it to a windows pc and I got the message following message:
"USB device not recognized"
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
So I still can't access the storage.
Click to expand...
Click to collapse
Might be usb issue try with some other usb .
Jitesh.saitawadekar said:
Might be usb issue try with some other usb .
Click to expand...
Click to collapse
Wow, never thought of that one... but it was the cable indeed.
Thanks for the help!
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM
StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.
kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.