Hello,
Firstly aplogies if posted in the wrong section..
I have being trying to root my one X and following this guide
I've managed to unlock the boot loader no problem. But when I'm trying to flash the clockwork recovery via cmd to just says "sending recovery" and hangs there....
I have followed the guide to the letter inc.
Installing Android SDK
Installing Java
Enabled USB debugging
I can adb to my phone
I've got all the upto date files.
The phone still works fine with no problem, I've searched this forum and the internet and gotten some idea's on how to get passed it but none have worked so far.
If anyone has any sloutions I would be very gratefull
*Update*
I have also tried flashing the r1-modaco img file aswell with same result.
Related
Hi
im currently in the process of trying to root my desire via this guide (MoDaco), ive got as far as putting the phone into recovery mode
# In the terminal window, enter 'step2-windows.bat'
when i try to do step 2 i get an error (see attatchement), ive searched the forums as best i can and done a few google searches but am no closer to fixing it.
help would be graet
tia
Xionic
EDIT: having gone through step1 again there is another error which i assume is causing my problem (see second attatchement).
did you have a chance to try that on another pc?
my (old) laptop had the same error, my netbook works fine.
Xionicorg said:
Hi
im currently in the process of trying to root my desire via this guide (MoDaco), ive got as far as putting the phone into recovery mode
# In the terminal window, enter 'step2-windows.bat'
when i try to do step 2 i get an error (see attatchement), ive searched the forums as best i can and done a few google searches but am no closer to fixing it.
help would be graet
tia
Xionic
EDIT: having gone through step1 again there is another error which i assume is causing my problem (see second attatchement).
Click to expand...
Click to collapse
You probably didn't install HTC sync
allla said:
You probably didn't install HTC sync
Click to expand...
Click to collapse
then he wont come so far in step1 (second picture)
Dont have another PC to test on but have re-installed HTC Sync and am now getting a different error.
HELP :/
Please help I'm in the same situation Xionicorg!
I can not I tried them all!
help !!!!!
possible causes:
1. windows 7 64bits
2. front USB which lacks of power supply
I used "-r3-tinycore_2.10 desireroot.iso" to load other roms before and everything ok ...not now!!!
but now from another computer does not go!
does not recognize the microSD when you start
have included 3
the 2GB
the 4gb
and 16 gb
does not see!!!!
I too have this problem and use 64 bit windows 7
Xionicorg said:
Dont have another PC to test on but have re-installed HTC Sync and am now getting a different error.
HELP :/
Click to expand...
Click to collapse
do it without the step1 file.
plug your desire in the pc. go in the bootloader.
now do in cmd to the folder where the fastboot-windows file ist.
now enter:
fastboot-windows.exe erase cache
fastboot-windows.exe oem rebootRUU
fastboot-windows.exe flash zip testimage.zip
if the error comes now again, wait a few seconds and write
fastboot-windows.exe flash zip testimage.zip
if it works, wirte
fastboot-windows.exe reboot-bootloader
thats the first step...
I tried unrevoked again as I had clockwork recovery mod on my desire, but it doesn't read my device anymore...trying to install RUU doesn't get me any further either. Maybe I do not have the right version of RUU, or maybe the CID no I got the very first time while creating the gold card wasn't correct, fact is that right now I have the device hooked up on my pc via usb and all I can do is boot in bootloader or recovery mode but thats it.
Trying PB99IMG.zip from sdcard results in CID fail...trying adb from console results in List of devices attached or error: device not found, or at best error remote: not allowed (this happened a while ago when I finally managed to keep adb on for more than a second and I tried pushing the recovery files)...
Oh, one more thing to add to the whole list of surprises...the USB drivers which before having these issues were working just fine, now aren't being recognized by the PC, I installed them manually but the drivers referring to Qualcomm Extra are not to be found even though I used the drivers provided on the forum, the ones provided in the reflashing packages etc etc etc...
BTW I am using W7x64...could this be also a reason why fixing this issue became such a pain in the a**?
Please help!
Another small step to fixing the desire
I found CID HTC_044...what should be the next step?...I can't still use PB99IMG.zip I can't use adb (device not found) only fastboot works for now.
fastboot oem boot error ...FAILED (command write failed Unknown Error)...just after finding HTC_044...where can I get a goldcard just with this CID?
Any help is much appreciated thank you!
Try the Desire forum for a quicker response
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
asanz00 said:
Good night.
I have to ask for help when trying to install custom recovery on this awesome machine.
I have done all steps and wen good, but when doing the final steps:
6) Use fastboot to boot CWM by running "fastboot boot /path/to/OuyaCWMrecovery6.0.3.2.img". This boots from our CWM recovery without writing to any partitions.
When writing this, says "wating for device" and dont advance.
I searched into ouya forums but i could not find the solution.
Also, drivers,sdk and su files are correctly installed.
Thanks for help
Click to expand...
Click to collapse
Usually that happens when the device isn't at the bootloader. Did you run "adb reboot bootloader" to get to the bootloader?
Sent from my Nexus 7 using xda premium
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
MIght be a driver issue. On mine the first time I booted into fastboot mode I had to go into device manager, found the android device with a yellow triangle, and had to install the drivers manually with "have disk". Hope this helps.
asanz00 said:
Yes, i followed all steps, including "adb reboot bootloader" and then waited 30 seconds, just the way its written
At this stage, ouya its switched on but not image, so i suposed i am into bootloader
Click to expand...
Click to collapse
Same thing happened to me, I never saw anything until I fastbooted the .img. And then I had to try it on 3 displays before one would show CWM. However after I flashed the .zip I have since tried all the displays and they all have worked every time.
Wow problem solved!
In devices administrator, there was one small called "fastboot" with yellow triangle.
I manually installed a driver called "android bootloader interface" and now it is working
thanks a lot!!!
No problem, always glad to help.
Now im fighting to get multi usb support via using a 5 ports usb-hub, i will write if i can ge througt
Can you post about that in the USB thread ? I just bought an active USB cable and 4 port hub, I hope they weren't a waste. I'll still get some use on my laptop, but not enough to justify the purchase.
Sent from my GT-P3113 using Tapatalk 4 Beta
Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance
NyxHouse said:
Hi! Im sort of new at this thread and Im a definite nooob when it comes to android stuff
I've tried to flash a pre rooted system.img as well as stock img which i got from a thread in this website
I've made sure to follow the guide thoroughly and have managed to flash the droidboot, recovery and boot img perfectly fine
But everytime I try to flash system.img the cmd prompt always says:
FAILED<command write failed <Invalid argument>>
The fastboot.exe I used has the latest version and Ive tried several times but still get the same result. I also placed all the img files in the same folder with the flashtools. Ive extracted system.img from its .zip as well
Does anyone know how to fix this?
Thanks a lot in advance
Click to expand...
Click to collapse
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.
vivix said:
Does
fastboot devices
gives you list with devicess connected ?
I think you havent installed properly drivers so fastboot cant install files.
I understand that everything you flash in bootloader mode on the fone.
Not in debugging mode when phone is turned on.
Click to expand...
Click to collapse
The phone is indeed in bootloader mode and properly connected and recognized by pc.
Entering
fastboot devices
Shows the phone as well.
Can you please elaborate more on the drivers I need to install? Is it for the usb connection or for something else?
Thanks a lot for the reply
try this flastool version.
So, I was trying to revert to total stock on my Zenfone 2 (Z00A), and now it will not boot into fastboot, or to system. It just boot loops. Everything I found online requires I can get into recovery or fastboot to do anything, and neither of these appear to be working for me. Am I totally screwed, or is there a way to unbrick from here?
HopelesRomantc91 said:
So, I was trying to revert to total stock on my Zenfone 2 (Z00A), and now it will not boot into fastboot, or to system. It just boot loops. Everything I found online requires I can get into recovery or fastboot to do anything, and neither of these appear to be working for me. Am I totally screwed, or is there a way to unbrick from here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
follow this link.. please search before making new thread. if you have any question plz post there
I was unable to find this while searching (must not have searched hard enough). But thanks!
guys you got to do this , i am having yureka plus5510a complete bootloop no recovery
guys bootloop no recovery access no fastboot access
its all started with the king root i wanted to flash twrp in my yu yureka plus 5510a no idead what " A" stands for then i used flashify from playstore and downloaded the twrp by the official twrp and flashed it with the flashify and boom boot stuck with no recovery some how removing battery and connecting the phone goes to the charging disp from where i did enable the fast boot but cmd was not able to identify adb devices nor the flashboot commands were working so i did same with win 10 powershell but nothing no devices , so i decided to use a method of ygdp , much hopes with this used ***** 5.1.153.00.P0.160604.8675_I02.def.CPB ******* dont know where the log file is but it was showing old bootloader error downloading and error and error and terminated at 2 % , then this one of your thread by unziping the official files and clicking on flash-all.bat file which he provided img(1) "some trials your phone will be all right " i tried with some "waiting devices error " message but then it just started something happened oem unlock blah_blah and then successful , tried to boot again but this time phone was automatically jumping into fastboot mode , then i finally tried one last time in that power shell thing by typing using cmd and applied fastboot code , even no devices was showing in powershell ,, but then i used some different code something like "fastboot ix902 recovery " and i was able to install a real old twrp recovery.. phone was showing the cyanogen loading ....but later after 1 hour i felt its stuck = + = but luckily recovery was working but but dont know why the buttons setup used to go in fastboot mode was now taking me in recovery,, and fastboot was no longer acessable , i was fine with it so i downloaded latest recovery from your respected thread file named as " twrp-3.0.2-0-20160604-UNOFFICIAL-tomato.img " i wanted to install nougat aosp so i thought its a nice idea to update the recovery first i. so i did the normal recovery update from the recovery it self , and now i guess that recovery was so old , the new one was kinda mindblower for the older one and booom no recovery , no fastboot , tried all the combination and came up with this one volume+ vol- and power shown img (2) same as boot logo but a small "official" tag
:cyclops: pls help i know this post dont suits your professional level , right now i havent slept from kinda like three days cause of exams and this sarcasm of being in trouble.. like my every devices is rooted o in onyx m in tab 2 , it frustating pls help ........i will edit this and make it more polite but if you are one who can solve this .. i am ready to donate man. cause u deserve it , it will gonna be learning experience with you i will be totally into the reply and pls dont scream for drivers i did installed coolpad driver adb drivers everything required i feel yureka is a real fake company their parts isnt distinguishable i did al the steps nicely and cleanly except the (kingroot ) and pls dont brag about the old threads , they didnt helped me much.. and probably why my phone is kinda dead