SOLVED
I am in a situation sort of like this guy:
http://forum.xda-developers.com/showthread.php?t=1948389
Except my father was trying to fix it and wiped the virtual SD card. Any clues on how to push the zips I need onto it?
It is recognised in fastboot but not adb, so I can flash boot.img. I also have CWM recovery.
I have tried the RUUs but they fail with an unknown error.
I tried manually pushing a system.img from the RUU's rom.zip but it's too large for fastboot (Error 000000006)
In cwm use mount USB storage and connect the hox to the pc.
Now u can copy ur ZIP to the phone.
odd29 said:
In cwm use mount USB storage and connect the hox to the pc.
Now u can copy ur ZIP to the phone.
Click to expand...
Click to collapse
Doesn't work. Gimme a mo and I'll copy the error code.
Something like "E: No umsfile"
dangercrow said:
Doesn't work. Gimme a mo and I'll copy the error code.
Something like "E: No umsfile"
Click to expand...
Click to collapse
Try flashing a different recovery, TWRP should work fine
Michealtbh said:
Try flashing a different recovery, TWRP should work fine
Click to expand...
Click to collapse
The HTC One X isn't on the supported list?
EDIT: Found the recovery file, it's booting up now
Solved, thanks to Michealtbh, TWRP allowed me to mount it to push the files over.
From here it should be a piece of cake xD
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
The error I get first it gives me some sort of error which disappears once the Android system recovery menu comes up. then the only thing I'm able to see says:
Checking Module MD5RSA.. OK
Checking Module CRC.... OK
Checking Module CURVER.... OK
Checking Module VERLIST....
Huawei SD card update fail.....
cust copying files...
copy cust files successed!
===================
FAIL
===================
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
And as I said on the tittle, I will pay whoever helps me to solve this issue, I need a step by step (with a good explanation if possible) on how to fix it, I will pay $60 via paypal to the person that provides me with the solution.
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
Ok, first of all, your picture shows that you already have the KitKat recovery.
Which version of B510 have you downloaded? Is it the update.zip? I'm assuming it is...
Please download the complete update package from here: http://www.huaweidevice.ro/user/con...001C00B510_Firmware_Android 4-4_EMUI--2-3.zip
That is the official, and full firmware update from Huawei Romania.
Once your download has completed, unzip the zip file, and copy the dload folder onto your sd card.
BEFORE placing your sd card back in your phone, try the 3 button method again. You should get into recovery mode, then do a data/factory reset, and clear cache.
Once that is done, put your sd card back in your phone, reboot your device, and reboot using the 3 button method.
Hopefully this will work.
If it fails again, you need to try formatting your sd card, and do the steps above again, without doing a factory reset.
Dear op.... Did you solve your problem? How?
miz_pimp said:
Ok, first of all, your picture shows that you already have the KitKat recovery.
Which version of B510 have you downloaded? Is it the update.zip? I'm assuming it is...
Please download the complete update package from here: http://www.huaweidevice.ro/user/con...001C00B510_Firmware_Android 4-4_EMUI--2-3.zip
That is the official, and full firmware update from Huawei Romania.
Once your download has completed, unzip the zip file, and copy the dload folder onto your sd card.
BEFORE placing your sd card back in your phone, try the 3 button method again. You should get into recovery mode, then do a data/factory reset, and clear cache.
Once that is done, put your sd card back in your phone, reboot your device, and reboot using the 3 button method.
Hopefully this will work.
If it fails again, you need to try formatting your sd card, and do the steps above again, without doing a factory reset.
Click to expand...
Click to collapse
I tried it but it's still not working. :/
blackrose1 said:
Dear op.... Did you solve your problem? How?
Click to expand...
Click to collapse
I"m still looking for a solution, actually it's been so long that I'm offering to pay whoever provides me with the solution
Try what I did here to solve a similar problem that I had: http://forum.xda-developers.com/showpost.php?p=54124890&postcount=18
sko4a said:
Try what I did here to solve a similar problem that I had: http://forum.xda-developers.com/showpost.php?p=54124890&postcount=18
Click to expand...
Click to collapse
I have a question, how can I install TWRP if the adb fastboot is not recognizing my phone? I think it's because I'm missing the drivers but I haven't been able to find them.
DanRioja said:
I have a question, how can I install TWRP if the adb fastboot is not recognizing my phone? I think it's because I'm missing the drivers but I haven't been able to find them.
Click to expand...
Click to collapse
Don't you just need Hisuite, the driver who comes with the phone when you plug in your USB cable? That made asb fastboot to recognize my phone at least.
You don't need ADB, only fastboot. Shut down the phone. Then hold the Vol- button and plug in the usb cable. Release the button after the you see the AscendP6 logo - now you are in fastboot and can flash TWRP. Windows Update should install the drivers (I've never installed HiSuite), just let it search online.
First delete your sd card to FAT32 not NTFS and put update.app to dload folder. then dowbload: http://forum.xda-developers.com/showthread.php?t=2765202
Power up your phone with volume down. and use Huawei tool kit from that link. select KitKat , unlock bootleder first from dropdown menu, then install stock recovery.
And try to update from stock recovery "3 buttons method"
ADHDDHDA said:
First delete your sd card to FAT32 not NTFS and put update.app to dload folder. then dowbload: http://forum.xda-developers.com/showthread.php?t=2765202
Power up your phone with volume down. and use Huawei tool kit from that link. select KitKat , unlock bootleder first from dropdown menu, then install stock recovery.
And try to update from stock recovery "3 buttons method"
Click to expand...
Click to collapse
Hey so far this is the most promising option I've gotten, the only problem is when I go to unlock bootloader it's giving me an error that says "error phone not connected" I've tried getting the drivers from many different ways, one from the hi suite, another letting windows look for it, the other one was I downloaded a .exe named "driver tools" but it doesn't work either, when I connect the phone it does make the sound just as when you connect any device on USB but other than that it doesn't recognizes it on the huawei toolkit. Any ideas?
sko4a said:
You don't need ADB, only fastboot. Shut down the phone. Then hold the Vol- button and plug in the usb cable. Release the button after the you see the AscendP6 logo - now you are in fastboot and can flash TWRP. Windows Update should install the drivers (I've never installed HiSuite), just let it search online.
Click to expand...
Click to collapse
I only get to see this screen: http://s3.amazonaws.com/f01.justanswer.com/JACUSTOMERd2wl5hbc/2013-01-26_122110_huawei.jpg
Tungieee said:
Don't you just need Hisuite, the driver who comes with the phone when you plug in your USB cable? That made asb fastboot to recognize my phone at least.
Click to expand...
Click to collapse
I've tried with the hi suite, downloading a .exe driver named "driver tools" and having windows look for the driver, but it doesn't recognizes it, I mean when I connect the phone it does make the sound when you're connecting something but other than that the adb is not recognizing the phone.
I had a similar problem but for me it would say verlist fail. However you should try this anyway if you haven't already: http://forum.xda-developers.com/showpost.php?p=52744051&postcount=23
What is important is that you use the recovery in that specific post. That's what fixed it for me.
blacklord9 said:
I had a similar problem but for me it would say verlist fail. However you should try this anyway if you haven't already: http://forum.xda-developers.com/showpost.php?p=52744051&postcount=23
What is important is that you use the recovery in that specific post. That's what fixed it for me.
Click to expand...
Click to collapse
I have a question, how can I flash the stock recovery? I mean I have tried with the adb fastboot but it doesn't recognizes the phone :/
Try this methode, it defently works!!! I had EXACT the same problem! P.s. You dont need to flash a other recovery!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2781977
Hi guys,
I am having a problem getting Cyanogenmod on my sons phone. I have flashed ROMs to this phone before with no problems but it was a while back. Last night I downloaded all the needed files. I flashed the latest nightly recovery which was 8-5-2016. After rebooting I tried to flash the ROM and it failed. I suspect the file got corrupted. Now I can't seam to get Windows to recognize the phone anymore so I can add a ROM to flash. It doesn't show up as a drive. Also, when I try to flash or push files to the device I'm getting adb server outdated or device not found. Can someone please help me get this working again? My son is 13 and wants his phone lol.
Thanks,
Rocky
grimreaper1014 said:
Hi guys,
I am having a problem getting Cyanogenmod on my sons phone. I have flashed ROMs to this phone before with no problems but it was a while back. Last night I downloaded all the needed files. I flashed the latest nightly recovery which was 8-5-2016. After rebooting I tried to flash the ROM and it failed. I suspect the file got corrupted. Now I can't seam to get Windows to recognize the phone anymore so I can add a ROM to flash. It doesn't show up as a drive. Also, when I try to flash or push files to the device I'm getting adb server outdated or device not found. Can someone please help me get this working again? My son is 13 and wants his phone lol.
Thanks,
Rocky
Click to expand...
Click to collapse
Try pushing the files while in twrp
Skickat från min HTC One M9 via Tapatalk
It has CyanogenMod recovery installed. When I try to push files it says adb server is out if date. My PC has Windows 10 x64. Before flashing CyanogenMod recovery when I would connect my phone to the PC I would see it's drive and could copy and paste files. Now the PC makes a sound when the phone is connected and disconnected but the drive does not show up to copy and paste a new ROM.zip.
grimreaper1014 said:
It has CyanogenMod recovery installed. When I try to push files it says adb server is out if date. My PC has Windows 10 x64. Before flashing CyanogenMod recovery when I would connect my phone to the PC I would see it's drive and could copy and paste files. Now the PC makes a sound when the phone is connected and disconnected but the drive does not show up to copy and paste a new ROM.zip.
Click to expand...
Click to collapse
Try rebooting to download mode by shutting down, holding volume down am power to restart. Download latest TWRP and flash when in download mode per fastboot. Reboot to bootloader, and recovery from there. If booted to TWRP mount as MTP and push Cyanogen Nightly as well as GApps to the device install both and reboot. This should work.
Sent from my HTC 10 using XDA Labs
Good morning guys.
I'm not really new to this forum, I've known you for years and I've always followed you for small "mods" or particular problems that I had over time with my devices.
I apologize, but I would like to ask you for help because I have big problems with an ASUS Nexus WiFi 32GB Tablet
Unfortunately, I can in no way connect it to the PC in order to install any rom (I wanted to install the rom stock). I tried everything, I even formatted an old PC and installed windows XP hoping for more compatibility (nostalgic).
The first time, I managed to install a ROM from TWRP recovery 2.8, enabling the USB-OTG and buying the appropriate cable, but then unfortunately, I wanted to try to change ROM and already I was there I wanted to update the recovery to 3.3 .1.0, but I must have been wrong to click somewhere in the recovery. I was convinced that the USB-OTG could always be enabled, so I had the security that I would always be able to install a S.O.
Now the S.O is no longer present in the device and from recovery I can no longer enable USB-OTG, and obviously in the device, no image is present that can help me, probably because I have eliminated everything with different wipes.
The PC in no way manages to see the device, whatever driver I try to install, it tells me that they have no information regarding the connected device, so I can't even use adb.
Please, help me, if needed, format a PC and install Linux or anything else I can use to resurrect this damn device.
Thank you so much for existing ...
Hello, did you try to reboot your tab in bootloader mode, and then install stock factory image from Asus? Maybe After that you will be able to reinstall twrp and custom rom you want... Your tab is unlocked? Did you try the wugfresh tool? Good luck
Thanks for the reply ichi-nii, I tried to reboot the device in bootloader mode (The menu with the open heart robot, Fastboot Mode, right?), Even if it doesn't give me many options, I can only choose whether to Turn off the device, Start it in Recovery (TWRP) or restart the Bootloader, nothing more, and from here I can't install anything anyway.
I believe the device is unlocked, or at least it was, and Fastboot tells me that it is unlocked, so ...
To use the Wugfresh tool, if I didn't err I have to be able to connect this Nexus to the PC and make it see it, but as I said ... No driver allows me to recognize this device from the PC ...
I don't know what to do ...
Isn't there a TWRP terminal way to do something? Some commands that can re-enable the USB-OTG ...
I think I inadvertently (because I didn't know what I was going towards) SELinux enabled, it was after this that the USB-OTG didn't work anymore (I think) ...
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
ichi-nii said:
Sorry for you bro, so you tell me even in bootloader mode , the tab is not recognized ? Maybe try to connect it when you are in twrp, And another one thing, maybe try another usb port or cable... About otg I can't help you , maybe your connector is broken? Did you try with windows 7 or linux( just to send files to sdcard)
edit: I just try to connect my tab (twrp mode on the screen) to my computer with kali Linux and I Can access to sdcard on the tab
Click to expand...
Click to collapse
Thank you so much for your help!
I tried to connect the device, both from TWRP and from Fastoboot mode but it is not recognized by Windows ... (Both Windows XP, Windows 7 and Windows 10) I tried to change USB ports and I also tried to change the cable, but nothing ...
The OTG cable is new, I used it on this device and it worked perfectly, I tried it on another device and it works, so the cable is ok, I must have done some **** myself.
Sending any file to the device is just what I'm desperately trying to do, I don't care how, I'm interested in doing it and fixing the damn thing.
If you tell me that your computer with Kali Linux sees it and you can access the memory, I try immediately.
Thank you so much !!
I'm not at all an expert on Linux, how does it work in this case? From Linux terminal? do I have to send commands? Or is it seen as a folder? ....
Forgive my humble ignorance ...
? I'm not an expert too? just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
ichi-nii said:
I'm not an expert too just install any linux with graphic interface then open the file manager , I did this with kali just because I have it on an old computer.
Good luck
Click to expand...
Click to collapse
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
IgNuReNt said:
I have to thank you for the help, from Linux I can easily see the device, I managed to insert in the internal memory the rom that I had previously installed ... so I took a big step forward! Unfortunately the misfortune haunts me and the recovery doesn't want to know to install that damn rom. I had to fall back on a Slimroms that I found here on the forum, but I'm not exactly where I want to be. I would like to be able to install my ROM or at most something more complete and updated. Now I try to install the GApps so that I can install some apps that allow me to permanently disable SELinux, then try again to Flash my rom ...
I do not know how to thank you! You have been very helpful.
Click to expand...
Click to collapse
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
ichi-nii said:
Congratulations, like you said it's a big step. Do you use the last twrp? Maybe the problem comes from that...
Click to expand...
Click to collapse
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
IgNuReNt said:
I updated the TWRP to 3.3.1.0, I think it is quite up to date, but it is strange that this is so, because from OTG I installed it quietly without problems ... I am convinced that SELinux blocks something ...
I also tried to check the zip file before installation and it gives me an error, it can't install ...
I'm going crazy ... but at least now I have the chance to do tests!
Click to expand...
Click to collapse
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
ichi-nii said:
And now Can you connect the tab to your computer (with windows this Time) If yes you can try install the rom you want from the wugfresh tool?
Click to expand...
Click to collapse
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
Yessssss! Congratulations bro ! That's a very good news ?
IgNuReNt said:
My dear friend! You are an ace, a beast! It was only thanks to you that I was able to solve my problem. Thank you very much, now there is a little 7-year-old who can come back and have fun with this Nexus 7, and of course he also thanks you very much.
I'll tell you briefly how I had to move and the problems I encountered and how I solved it step by step, so that if it happens to someone else, it may have a path to follow eventually.
I was screwed, after I managed to copy the stock image from flash to Kali-Linux inside the Nexus 7, because that damned TWRP crashed during installation without giving me a reason, I had to restart the tablet and that's it; from linux, same speech with ADB Sideload, did not complete the installation.
So I tried to Flashare a custom image, Slimrom that gave me only problems right away, I couldn't touch anything that gave error (but it was installed .. so I was still hoping).
So I tried to flash my damned stock rom directly from Fastboot, but it gave me a thousand mistakes of every kind, from there I suspected that there was something wrong with the file system or the partitions ... something must have messed up something , it was not possible that I could not install any roms anymore, not even the wipe worked, there was something strange, I thought of starting from the base.
So from recovery I found the function that allows you to change File System in the various partitions, so one by one I restored F2FS, the Wipe worked magically, the road was the right one.
I start with the installation of the Stock Rom ... but nothing, errors concerning the lack of files or information (now unfortunately I don't remember in detail)
Reading on the forum, I realized that it could be a common problem and that you could flash the individual files contained in the "stock.img" file that I had downloaded, even individually. So I extracted the archive of the downloaded stockrom, extracted the same .img file inside it, I found myself with all those files.img (boot.img / recovery.img / userdata.img etc etc) at that point I have them flash them one by one with the special fastboot commands.
eeeeeeeeeeeeeeeeeeeee
Taaaaaaaaaaakkkkk
Now it finally starts, it works !!!!!
All this, thanks to you, with that idea of connecting it to linux you gave me hope and it worked !!
I am Italian, from Rimini, if you ever happen in Italy you have a paid fish dinner !!!!!
Thanks again!!!!
Click to expand...
Click to collapse
ichi-nii said:
Yessssss! Congratulations bro ! That's a very good news
Click to expand...
Click to collapse
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
[email protected] said:
Thanks guys, I stumbled across this thread and changed the file system of System & Data partitions to F2FS (from ext4) and everything seemed to work normally after that. Thank you!
Click to expand...
Click to collapse
Congrats