Related
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
ianmcquinn said:
For flash_image, you need to make sure you have the binary. There is a thread all about it. (http://forum.xda-developers.com/showthread.php?t=902493)
For fastboot, is the recovery.img file located in whatever directory you are running the fastboot command from? What command are you running?
Click to expand...
Click to collapse
Yes I have flash_image in my tools folder :/
Does that answer the question?
James_Caliber said:
Yes I have flash_image in my tools folder :/
Does that answer the question?
Click to expand...
Click to collapse
Do you have an ENG. Hboot? If not, you can not use fastboot, youll have to flash recovery from terminal using flash_image.
Edit: See in your first post says you have HBoot installed, you mean ENG. Hboot right?
If you do have ENG. Hboot type
Code:
fastboot devices
Do you get a "serial # fastboot" ?
See if you have the right drivers installed. I had ADB up and running but when I tried fastboot it would not recognize my G2 so I had to install new drivers.
James_Caliber said:
SO I've been trying to install the 3.0 cwm recovery but I get errors in Android and in the FASTBOOT USB mode.
In Android is says cannot find flash_image or something like that.
and in FASTBOOT it says error: cannot load 'recovery.img/
I unplugged my device and plugged it back in, rebooted it.
Do I have to have a 2.0 recovery FIRST? or can I just do 3.0 first? Is that even the problem?
I can't figure out what the problem is and I've read like 10 different threads from different forums as well.
Of course I'm perm rooted and I've installed Hboot.
Click to expand...
Click to collapse
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
EdKeys said:
Take the .img file that you have for CM 3 and rename it to: recovery.img then place it on your sdcard. Open terminal emulator on your phone and type in the following 3 commands, hitting enter after each one:
su
flash_image recovery /sdcard/recovery.img
reboot recovery
If you need a copy of the latest CM 3 (3.0.0.5) you can download it from here:
http://phones.crackflashers.com/vision/recoveries/vision-cwm3src3.0.0.5-1-16-11.img
Click to expand...
Click to collapse
If you want to use flash_image, you need to place the binary on your phone and make it executable. The guide I linked to explains exactly what you are supposed to do.
For fastboot, do you have recovery.img in your tools directory?
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
PatrickHuey said:
I've got the same problem as the OP. How do i know if i have hboot? I have s off using the original visionary method. I try to push the image through termimal but it says the image isn't found. I need to do the entire binary method to get the path to work? this is why i want to wait for the update through rom manager, so i can flash back and forth anytime.
sent from my V I S I O N.
Click to expand...
Click to collapse
Not exactly sure what you are saying about pushing things through terminal and the binary method, but if you want to use flash_image, you should follow the guide I linked to.
If you want to use flashboot, you need to make sure you have the engineering hboot (if you boot you phone while holding volume down, the first line should say something like ENG S-OFF instead of SHIP S-OFF).
If you want yet another method to flash the recovery, there is also the sticky at the top of this forum.
i found this to be the best and easiest way to flash CWM recovery 3.0.0.5
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
Click to expand...
Click to collapse
If you rooted using rage, the flash_image kernel should be on your phone.
blackknightavalon said:
If you rooted using rage, the flash_image kernel should be on your phone.
Click to expand...
Click to collapse
I don't think that's true. Temp rooting with rage doesn't install any apps for you by itself (and the temp root to perm root guides only install Busybox, SuperUser, and the su binary). It's just that most people flash a custom rom after rooting, and many of those roms include flash_image. If you rooted and then stayed on stock for example though, you would have to get the flash_image program yourself (and it's something independent of the kernel).
Hi all,
I'm just exhausted with the following problem i'm having with my Wildfire S. I've followed various procedures with the intention of installing Cyanogen but everything just stops dead at the same point, which is where I attempt to boot my phone into recovery. I'll list below everything I've done so far:
1) Unlocked the bootloader by visiting HTCDev.com, I flashed my Hboot to the correct version, which is "1.09.0099_2.13.401.3_0210_R"
2) did the Identifier token thing successfully too, phone rebooted and factory reset itself.
3) used Unlock Root to root the phone, worked perfect. Phone rebooted and Super User was on my application list.
4) Installed Rom Manager from Google play, Proceeded to flash CWM Recovery to 5.0.2.8, Super User popup appeared asking to to grant root access and confirmed.
5) Copied CM zip file and Google apps zip file to the root of my MicroSD card.
6) Rebooted into the bootloader (Vol down + Power) and selected recovery
This is where it just stops dead, I get a white screen with the HTC logo and it just stops like this forever unless I pull battery out/in and turn on. Phone will boot into Android no problem.
No matter how many times I try booting into Recovery, it will just stop on the white screen with the HTC Logo.
Rebooting into recovery via ROM Manager does the same.
I have flashed a stock ROM back on the phone several times and a system update becomes available which resets the HBoot back to the original version which allows me to retry the entire process. I have tried various different ways to root the phone which all are successful and still the phone freezes when I try to enter recovery at the same point in the procedure.
Please, anyone, help me with this, I have no idea what is going wrong or what to do next
Thanks guys
sorry ignore this post for now
You can try here and goto post 78 for the newest version to manually install CWM or try this RZR Recovery version also sd card install.
Tera Tike said:
You can try here and goto post 78 for the newest version to manually install CWM or try this RZR Recovery version also sd card install.
Click to expand...
Click to collapse
Thanks for the info bud:
1) tried the First one, I get "Model ID incorrect!, Update Fail" error Message.
2) RZR recovery file is missing and cant be downloaded. Found the file further in the thread. Tried it and I get "CID incorrect! Update Fail" error.
Ok try these..
Remove the "cmw." from cwm.PG76IMG.zip before saving to sdcard.
Remove the "rzr." from rzr.PG76IMG.zip before saving to sdcard.
Tera Tike said:
Ok try these..
Remove the "cmw." from cwm.PG76IMG.zip before saving to sdcard.
Remove the "rzr." from rzr.PG76IMG.zip before saving to sdcard.
Click to expand...
Click to collapse
Thanks again matey:
the cmw file now says "Main Version is older!"
rzr file says "CID incorrect"
Ok, lets try again I updated the above attachments.
Tera Tike said:
Ok, lets try again I updated the above attachments.
Click to expand...
Click to collapse
Both now say "Main version is older! Update Failed"
Please try again as I uploaded another version.
Yours is a Bootloader unlocked phone.......PG76IMG.zips dont work......why dont you try this...
1)Install terminal emulator from market
2)Download CWM recovery from clockworkmod.com
2)If it's a zip file(the one you downloaded),just extract "recovery.img" from it and if the file is an img file rename it to "recovery.img" and put in on the root of sd card(no folders)
3)Open terminal emulator and type "su".Allow superuser permissions
4)Then type the following
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
See if this works
csoulr666 said:
Yours is a Bootloader unlocked phone.......PG76IMG.zips dont work......why dont you try this...
1)Install terminal emulator from market
2)Download CWM recovery from clockworkmod.com
2)If it's a zip file(the one you downloaded),just extract "recovery.img" from it and if the file is an img file rename it to "recovery.img" and put in on the root of sd card(no folders)
3)Open terminal emulator and type "su".Allow superuser permissions
4)Then type the following
See if this works
Click to expand...
Click to collapse
I'll try tonight when i get home
csoulr666 said:
Yours is a Bootloader unlocked phone.......PG76IMG.zips dont work......why dont you try this...
1)Install terminal emulator from market
2)Download CWM recovery from clockworkmod.com
2)If it's a zip file(the one you downloaded),just extract "recovery.img" from it and if the file is an img file rename it to "recovery.img" and put in on the root of sd card(no folders)
3)Open terminal emulator and type "su".Allow superuser permissions
4)Then type the following
See if this works
Click to expand...
Click to collapse
Ok, tried "su".Allow superuser permissions and I get "su.allow: permission denied"
Ok, i managed to get SU access by typing "su"
But now I get access denied when using: "flash_image recovery recovery.img"
you need to wait
I know some people already return to manufacturer to repair it,that is data base was damage.
I do not think that your phone is rooted correctly. I can access terminal as root user with no warnings. On wildfire S there is no flash_image utility so I followed these instuctions > *wiki.cyanogenmod.com/wiki/Flash_image* However when I type ./flash_image recovery /sdcard/recovery.img nothink really happens no warnings, no recovery installed. I think flash_image is not supported fo wildfire S.
I think that CWM recovery cannot be started on wildfire S with configuration:
Marvel PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.54.39.28M
ROM-2.13.401.3
Please tell me I am wrong.
I also noticed that my Baseband version is
47.23c.35.3037H_7.54.39.28M. And all stock roms that I can download are for WFS without H. So I cannot put this ROMs into my phone IT ends with error 132 wrong signature.
karfi said:
I do not think that your phone is rooted correctly. I can access terminal as root user with no warnings. On wildfire S there is no flash_image utility so I followed these instuctions > *wiki.cyanogenmod.com/wiki/Flash_image* However when I type ./flash_image recovery /sdcard/recovery.img nothink really happens no warnings, no recovery installed. I think flash_image is not supported fo wildfire S.
I think that CWM recovery cannot be started on wildfire S with configuration:
Marvel PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-0451
RADIO-7.54.39.28M
ROM-2.13.401.3
Please tell me I am wrong.
I also noticed that my Baseband version is
47.23c.35.3037H_7.54.39.28M. And all stock roms that I can download are for WFS without H. So I cannot put this ROMs into my phone IT ends with error 132 wrong signature.
Click to expand...
Click to collapse
Yours match mine perfectly so I guess your right. This particular version of Wildfire S wont allow a custom recovery from running. Its most probably HBoot 1.09.009 and 2.3.5 combo which does it.
wait？
how can we do now？we try stock recovery？
@kdparton
I have the same phone, same problem.
Did you manage to gett acces to recovery menu?
Thank you
Its not that Hard.
Download the current version of CMW on the site rename the img to "recovery.img"
Make a folder in C:/Android, put the "recovery.img" in it and in Bootloader select Fastboot with USB.
Open CMD and type:
cd: c:\android
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
And it shoud normally work.
Make sure you have the adb.exe, AdbWinApi.dll and the fastboot.exe in the Folder "Android" too.
Cold Ice said:
Its not that Hard.
Download the current version of CMW on the site rename the img to "recovery.img"
Make a folder in C:/Android, put the "recovery.img" in it and in Bootloader select Fastboot with USB.
Open CMD and type:
And it shoud normally work.
Make sure you have the adb.exe, AdbWinApi.dll and the fastboot.exe in the Folder "Android" too.
Click to expand...
Click to collapse
Ok, I just did, same result: after selecting recovery menu the HTC logo comes up then after a while blanks out and remains with the bottom icons lightining..
---------- Post added at 09:21 PM ---------- Previous post was at 09:07 PM ----------
Is there any way maybe to get the recovery menu from PC?
So I can I root it from there.
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?
sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250
efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.
efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.
sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.
would running terminal in windows with admin privileges help?
sent from my i9250
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".
bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?
I have same problem to...
sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250
i have tried way to many times to root this phone and have failed over and over. atleast once every 3 months i try with zero results. the phone is unlocked using the OneX v2.5 tool kit here. when i try to do perm root it says " User C not recognized as an external or internal command, operable program or batch file". ive tried putting the tool kit directly in C: and 86x. nothing works. what do i need to do to root this freaking phone. im fixing to get a bat to this phone!
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Bl4ckX said:
Have you tried a different version, reinstall/redownload and running it as an admin?
Sent from my EndeavorU using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no. i havent. do you have a recommendation for a different root system?
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
You have a custom recovery ? Just install the SU.zip via recovery then. Tried that ?
mrbtree98 said:
have you tried to flash a custom recovery and root package. that's how i did for mine and i was done within 10 minutes
Click to expand...
Click to collapse
ive tried the all in one unlock and root kit. didnt work. could you post a link to what you used?
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Mr Hofs said:
I never root stock rom. I'm always on a custom rom.
Just check for the superuser zip and install it in the custom recovery
Click to expand...
Click to collapse
how do you use custom recovery? i tried everything on the all in tool kit(custom recovery to) and says phone not detected or what i posted up top. this is crazy. never have i seen and android phone so hard to root!!!
MPH33 said:
both programs ive used says "phone not connected". i dont get it. ive tried debugging and recovery. i have never had an android this hard to root. samsung galaxy s2 was very easy.
Click to expand...
Click to collapse
Do you get any output with "adb devices"? When you don't (and your phone has debugging enabled), it may as well be a driver problem.
(quick tip: add the antroid-tools folder to your PATH)
I personally can't find my phone on Windows anymore after the 4.2 update, so I just use an Ubuntu liveUSB for adb/fastboot purposes.
Sent from my HTC One X using Tapatalk
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Mr Hofs said:
My opinion ? Don't use a toolkit. Straight commands from the prompt.
Download android sdk bundle, unpack it and go the the platform tools folder. Put there the recovery (recovery.img) open a command prompt there and type
Fastboot flash recovery recovery.img
Fastboot erase cache
Click to expand...
Click to collapse
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
svenvv said:
Have you already followed the instructions on htcdev.com? You have to unlock your phone first before you can flash a recovery
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
yes. the phone is unlocked. it's been unlocked for like 8 months. just cant seem to root it.
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Mr Hofs said:
Are the drivers correctly installed, download the latest HTC sync. And also check if java and .net.frameworks are installed on the pc
Click to expand...
Click to collapse
yes. sync manager is fully updated. maybe its my computer. i built it. running on windows 7 ultimate. hell, i dont know. this is weird. like i said before... my old samsung was so much easier. i just wanna root to get rid of all this bloat.
MPH33 said:
done as directed. went to cmd typed fastboot. still says internal or external not recognized. man this sux
Click to expand...
Click to collapse
That seems like you're not in the correct directory.
To get rid of that error forever just put the contents of platform-tools in your C:\windows\system32 and C:\windows\syswow64 folders
Then you can run the commands from anywhere.
Now:
Install HTC sync drivers.
Put your phone in fastboot mode.
Put a recovery image in the path that the cmd shows when you start it (eg. C/users/USER/) or "cd" to the recovery image.
Then:
fastboot flash recovery recoveryname.img
When that gives decent output we're getting somewhere.
In that case put the supersu zipfile on you phones storage and flash it from recovery.
Sent from my HTC One X using Tapatalk
Try updating or reinstalling drivers for the phone check if your cable is good and connects it to PC
[Knowledge from tegra 2 device you must have APT or NVflash driver and whne phone is off with custom key combination enters flash mode i guss is similar to this]
screw this. phone works great just wanted to root. mint condition, will sell cheap. pm me if interested.
it isn't due to the phone...it's because windows don't know for what this command is...so install again the latest java for your win7 ....you are definitely doing something wrong...you could also try to google that error which you get after typing fastboot bla bla
it works for all other ppl so should also work for you even with my non genuine win8.1 pro it's working fine
SOLVED
I can't boot into recovery (op logo displayed for about 10 seconds, then the screen became black)
ore boot the system (op logo is displayed for about 0.1 seconds, then the screen became black)
i've already tried to follow the steps in Mega Unbrick Guide, but i can't "Make the device show as Qualcomm 9008" also after have followed the
appropriate guide)
please help me!
if someone succeeds to solve the problem i'll pay him/her via paypal
Thaks!!
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
how?
Xceeder said:
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
Click to expand...
Click to collapse
i can't flash via adb sideload because i have can't boot into recovery.
How can i flash into fastboot mode? what have i to tipe?
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
What were you doing actually? And is your bootloader unlocked?
Xceeder said:
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
Click to expand...
Click to collapse
I've tried, but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
cannot read oxigenos.zip
zTweaked said:
What were you doing actually? And is your bootloader unlocked?
Click to expand...
Click to collapse
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
TheReverend98 said:
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Click to expand...
Click to collapse
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
yes, i'm running the command window from that folder where adb is,
but i've tiped
:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update oxigenos.zip
archive does not contain 'android-info.txt'
error: update package 'oxigenos.zip' has no android-info.txt
because i can operate only in fastboot mode
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Xceeder said:
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Click to expand...
Click to collapse
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
TheReverend98 said:
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Click to expand...
Click to collapse
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
AJay27 said:
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
Click to expand...
Click to collapse
yes, anyway, i solved the problem
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
solving
sahed01 said:
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
Click to expand...
Click to collapse
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
TheReverend98 said:
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
Click to expand...
Click to collapse
.
thank you for sharing this! ?
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
Hi Gary can you send me the files to email [email protected] because I'm having the same issues. Thanks