Related
I wanted to Flash a ROM and i put the .zip files in /sdcard/
in the Recovery mode in "Mounts and Storage" I format everyting that was "Format X" (so i format EVERYTHING)
if you ask why its because im an idiot
I've looking for the tutorials for a solution but i am ****ed up just because i have no way that the PC recognizes the nexus by USB, because i cannot acces to anything, there's no system, no data, nothing...
There is a solution?
dnnz said:
I wanted to Flash a ROM and i put the .zip files in /sdcard/
in the Recovery mode in "Mounts and Storage" I format everyting that was "Format X" (so i format EVERYTHING)
if you ask why its because im an idiot
I've looking for the tutorials for a solution but i am ****ed up just because i have no way that the PC recognizes the nexus by USB, because i cannot acces to anything, there's no system, no data, nothing...
There is a solution?
Click to expand...
Click to collapse
Boot it up in bootloader mode and either flash the stock rom manually or use an all in one toolkit to do it for you. As long as bootloader works you are fine.
dottat said:
Boot it up in bootloader mode and either flash the stock rom manually or use an all in one toolkit to do it for you. As long as bootloader works you are fine.
Click to expand...
Click to collapse
I look for a lot of tutorials but everyone needs the PC recognize the nexus (i think)
Thanks, i found a tutorial that doesnt need USB driver
http://www.mxdroide.com/2013/04/restaurar-nexus-7-al-firmware-original.html (in spanish)
!!
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)
I tried install a root for nougat.
I am stuck on the screen that warns that the device is unlock and the message "your device is booting now ...."
Its vns-21...
I cant off this phone
First:
Wrong forum section.
Second:
Can you access recovery?
If not, flash a suitable recovery in fastboot mode with fastboot, then restore a backup.
Schlengge said:
First:
Wrong forum section.
Second:
Can you access recovery?
If not, flash a suitable recovery in fastboot mode with fastboot, then restore a backup.
Click to expand...
Click to collapse
Yes i have, but i cant wipe "unable to locate /data partition for backup calculations"
styru111 said:
Yes i have, but i cant wipe "unable to locate /data partition for backup calculations"
Click to expand...
Click to collapse
i made a tutorial how to downgrade to MM
good luck
extract boot.img from your firmware and flash it via fastboot
I flashed the new*B336 update for EMUI 5 and when i got into it i saw that there were not any system apps, i checked why and it appeared i had to install another*full_data file or smth, is there any way i can do it now ???
Btw when i try to boot into TWRP it says Your device is booting now... and does nothing
The situation is now even worst, why can`t nobody help?
Please someone help. i really need my phone back and i can`t take it for repairs.
When i try to install stock rom of EMUI 4 the install says error code - 7
failed to mount /vendor (invalid argument)
failed to mount /product (invalid argument)
I have no OS installed and i cant use HiSuite to recover using fastboot.
dload mode says the app update package does not exist when there is a corrent update.app in the dload folder on my SD card
and*i also am sure i*used the right OEMinfo file ;(
please respond someone.
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Abdulla7 said:
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Click to expand...
Click to collapse
Okay, i will try and see what happens and report back to you. Thanks for the response
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
theAuxify said:
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
Click to expand...
Click to collapse
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Schlengge said:
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Click to expand...
Click to collapse
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
theAuxify said:
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
Click to expand...
Click to collapse
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Schlengge said:
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Click to expand...
Click to collapse
Yea, says :
Phone unlocked
FRP Unlock
And if i use the command adb devices in fastboot mode no devices appear at all*D:
EDIT : I managed to flash boot.img and recovery.img without errors with the device not showing on the list of devices.
Says everything is okay
But when i try to flash system.img it shows this
C:\Users\Auxify\Desktop\Huawei\Huawei-P9-Lite>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445202 KB)...
OKAY [ 14.775s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 14.828s
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Schlengge said:
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Click to expand...
Click to collapse
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Schlengge said:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Click to expand...
Click to collapse
Yeah.*I can boot into recovery N B9 but when i try to flash/wipe/do anything it says cant mount /vendor /product /version
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Schlengge said:
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Click to expand...
Click to collapse
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
theAuxify said:
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
Click to expand...
Click to collapse
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Schlengge said:
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Click to expand...
Click to collapse
Yea, but thats not for /vendor /product /version*xD
P.s : Happy 2017 ;P
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Schlengge said:
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Click to expand...
Click to collapse
Meh, i guess ill just drive out and get it fixed xD Its a loooong way though DD
Thanks for all your help brother ;p
theAuxify said:
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
Click to expand...
Click to collapse
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
jkmaziku said:
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
Click to expand...
Click to collapse
The best, is to try to install twrpmeticulus, wipe all except external storage property, install oeminfo.zip badwolf, go back to reboot, shut down.
Restarts Dload bxxx.
I only see her.
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.