trouble rooting and running CM9 - Verizon Droid Incredible 2

After a bunch of trouble yesterday I was able to setup Revolutionary and root my phone with tacoroot, or at least I think I rooted it. Then I found CM9 that people were posting in these forums. I loaded the CM9 and the google apps market thing into the sdcard with adb and installed it. Then I restarted my phone and it couldn't make it past the CM9 welcome screen.
Then this morning I was reading online and I found something that suggested that I need to update the radio so I pushed PG32IMG.zip with adb and now it seems to be locked in a boot cycle with HBOOT. When I get into the bootloader it tires to update the radio but when I try to just load my phone it gets stuck at the CM9 welcome animation.
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-1.09.01.0722
eMMC-boot
Any ideas would be great. Thanks in advance.
Edit: Could this problem come from me not installing super user access? The tutorials I followed didn't have something that said to do it and it wasn't a step in the process. I think there is probably access because I have S-Off; however, I did buy this phone used and the previous owner could have rooted it and then reverted it back to Sense.

Plug in the phone and turn it on normally, when it gets to the boot animation use the command "adb shell rm /mnt/sdcard/PG32IMG.zip" then try redownloading and flashing the radio and flashing cm9, you don't need to worry about root, cm9 is already rooted.
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
Plug in the phone and turn it on normally, when it gets to the boot animation use the command "adb shell rm /mnt/sdcard/PG32IMG.zip" then try redownloading and flashing the radio and flashing cm9, you don't need to worry about root, cm9 is already rooted.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
It says "rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied"
C:\>adb shell rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
C:\>adb shell
[email protected]:/ $ rm /mnt/sdcard/PG32IMG.zip
rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
255|[email protected]:/ $ su
su
Permission denied
1|[email protected]:/ $ Error type 2
android.util.AndroidException: Can't connect to activity manager; is the system
running?
at com.android.commands.am.Am.run(Am.java:99)
at com.android.commands.am.Am.main(Am.java:80)
at com.android.internal.os.RuntimeInit.finishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:238)
at dalvik.system.NativeStart.main(Native Method)
rm /mnt/sdcard/PG32IMG.zip
rm /mnt/sdcard/PG32IMG.zip
rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied
Click to expand...
Click to collapse

benj123 said:
It says "rm failed for /mnt/sdcard/PG32IMG.zip, Permission denied"
Click to expand...
Click to collapse
Try this:
Code:
adb shell
su
rm /mnt/sdcard/PG32IMG.zip
Sent from my Incredible 2 using Tapatalk 2
---------- Post added at 02:35 PM ---------- Previous post was at 02:31 PM ----------
Just saw your edit, while it's bootlooping type "adb reboot recovery" then try reflashing cm9, make sure you wipe everything.
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
Just saw your edit, while it's bootlooping type "adb reboot recovery" then try reflashing cm9, make sure you wipe everything.
Click to expand...
Click to collapse
Should I wipe the SD card? When I was trying to flash I had been wiping the cache partition and the Dalvik cache. I never wiped the battery status.
Edit: Sorry I should have added that I've already tried installing CM9 a couple of times with various versions and they all seem to get stuck at the loading animation. Yesterday I downgraded from 2.3.4 to 2.3.3 and then rooted it. Then I tried to install CM9. Do I need to wipe the OS partition prior to installing?
Edit2: Do you mean I should do a "wipe data/factory reset" to wipe all the user data? I hadn't been doing that before when I had been trying to install CM9

benj123 said:
Should I wipe the SD card? When I was trying to flash I had been wiping the cache partition and the Dalvik cache. I never wiped the battery status.
Edit: Sorry I should have added that I've already tried installing CM9 a couple of times with various versions and they all seem to get stuck at the loading animation. Yesterday I downgraded from 2.3.4 to 2.3.3 and then rooted it. Then I tried to install CM9. Do I need to wipe the OS partition prior to installing?
Click to expand...
Click to collapse
What version are you installing?
Sent from my Incredible 2 using Tapatalk 2

prototype7 said:
What version are you installing?
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to install an unofficial CM9. Whatever ones I found in the forums. A lot of the links to downloads from a few months ago don't work anymore so I've had to scavenge around to find some.
I have cm-9-20120712-UNOFFICIAL-vivow.zip and cm-9-20120816-UNOFFICIAL-vivow.zip

I fixed it. I feel like an idiot. My problem was that I just didn't wipe the user data. I must have missed that step in the tutorials and thought that clearing it was part of the install.
Thanks!

benj123 said:
I fixed it. I feel like an idiot. My problem was that I just didn't wipe the user data. I must have missed that step in the tutorials and thought that clearing it was part of the install.
Thanks!
Click to expand...
Click to collapse
Did that fix the bootloop? I'm having a boot loop issue after following this guide. I'm S-OFF, but i get an error when I try to flash the radio in fastboot. "fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip"
I get the msg: FAILED (remote not allowed)
EDIT 1: weird. i kept getting bootloops after OS would load. I tried to flash the Radio and got the error below:
C:\miniadb_inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.312s]
writing 'zip'... FAILED (remote: not allowed)
In recovery, I wiped the data (factory reset) and cache. Then it boot fine. I turned off fast boot and turned on usb debugging (not needed for fastboot usb) and I still get the failure above. Any ideas why I can't flash the Radio.
Also, do I really need to flash the radio as the OP stated? I've currently got:
HBOOT-6.13.1002
RADIO-1.09.01.0622
EDIT 2: I just rebooted and I'm back in a bootloop. As soon as the OS loads, it reboots.
EDIT 3: I got it working. I just needed to follow scotty's guide and flash from the oem rebootRUU state.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)
fastboot reboot-bootloader (make sure your baseband changed)
fastboot reboot

Sorry man I have no clue. I just got my first android yesterday so I'm very new to this whole rooting thing. If go into the bootloader then my phone still tries to update the radio. I'm just going to manually delete the file one of these days on my computer when the sdcard is out of the phone

agapedisciple said:
Did that fix the bootloop? I'm having a boot loop issue after following this guide. I'm S-OFF, but i get an error when I try to flash the radio in fastboot. "fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip"
I get the msg: FAILED (remote not allowed)
EDIT 1: weird. i kept getting bootloops after OS would load. I tried to flash the Radio and got the error below:
C:\miniadb_inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.312s]
writing 'zip'... FAILED (remote: not allowed)
In recovery, I wiped the data (factory reset) and cache. Then it boot fine. I turned off fast boot and turned on usb debugging (not needed for fastboot usb) and I still get the failure above. Any ideas why I can't flash the Radio.
Also, do I really need to flash the radio as the OP stated? I've currently got:
HBOOT-6.13.1002
RADIO-1.09.01.0622
EDIT 2: I just rebooted and I'm back in a bootloop. As soon as the OS loads, it reboots.
Click to expand...
Click to collapse
You need to rename the file to just PG32IMG.zip and install it from hboot.
Sent from my Incredible 2 using xda app-developers app

Baloeb said:
You need to rename the file to just PG32IMG.zip and install it from hboot.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I finally got it working the other night. I guess my EDIT 3 didn't work then, so i just added it again. I try to flash everything via USB instead of sdcard now, b/c I get more reliable results and I don't have to keep swapping the sdcard. :good:

Related

E:Cant mount /cache/recovery/command

Have been getting this error of late after i run unrevoked, then when i go to recovery to flash rom i get this error...is there any solution to this, or is there a new version of unrevoked to solve this porblem? Im using unrevoked v3.32.
Thank you.
Phone details? recovery version? Which Rom?
davebugyi said:
Phone details? recovery version? Which Rom?
Click to expand...
Click to collapse
Unfortunately i gave the phone back to a friend who need help, so cant provide any info
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
lowkey1979 said:
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
Click to expand...
Click to collapse
Do you have a pvt4-desire? If, you have to flash amonra-recovery, because cwm is incompatible with pvt4-desires.
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
ghalalb said:
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
Click to expand...
Click to collapse
Can you tell me how to flash recovery with fastboot?
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
MatDrOiD said:
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
Click to expand...
Click to collapse
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
andrew21 said:
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
Click to expand...
Click to collapse
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
hi mates,
to flash recovery with fastboot need to be s-off.
the command are really simple.
boot in hboot, select fastboot (shoul see fastbbot usb on the phone screen)
open a command line
Code:
fastboot flash recovery c:/wheretefileis/yourecovery.img
MatDrOiD said:
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Sir,
I tried this method but i get a "flash_image: not found". It seems like i don't have the flash_image command on my phone. I've looked everywhere to find a way to get that command and i found this - http://www.villainrom.co.uk/forum/s...)
finished. total time: 1.094s
Thank you sir
chage a sd card for try!
zk7513153 said:
chage a sd card for try!
Click to expand...
Click to collapse
Already did change the sdcard sir.
On another note, whenever i tried remounting the /system for RW access to copy flash_image, free space drops to Zero Kb. To isolate, i tried remounting to just Read access, free space remained the same. Anything I'm missing here, or do I really have to S-OFF my phone before I can make changes on my /system ?
Thank you very much.
nonofficialcover said:
I also tried flashing via ADB and I get this:
C:\fastboot flash recovery c:\recovery-RA-desire-v2.0.1.img
sending 'recovery' (3936 KB)...
OKAY [ 0.687s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.094s
Thank you sir
Click to expand...
Click to collapse
For this part I think you need to disable signature verification in recovery.
I was able to solve my problem after I did S-OFF.

[Q] Dead Screen: Recover/clone DInc??

My rooted HTC Incredible screen has died, but otherwise the phone works (I think). I was running MIUI on it. I used Titanium Backup and the MIUI backup utility, but had not used them for a while, so my most recent setup was not saved. I can access the phone via USB/ADB. Is there any way to pull the currentconfiguration off the phone so that I can "clone" it to a "new" Incredible? If so, suggestions are gratefully accepted.
BM99
Tried adb pull * *?
adb shell
cat /dev/mtd/mtd0 > /sdcard/misc.img
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
cat /dev/mtd/mtd3 > /sdcard/system.img
cat /dev/mtd/mtd4 > /sdcard/cache.img
cat /dev/mtd/mtd5 > /sdcard/userdata.img
This will back up all system partitions. use flash_image or fastboot to restore the images.
cmlusco said:
adb shell
cat /dev/mtd/mtd0 > /sdcard/misc.img
cat /dev/mtd/mtd1 > /sdcard/recovery.img
cat /dev/mtd/mtd2 > /sdcard/boot.img
cat /dev/mtd/mtd3 > /sdcard/system.img
cat /dev/mtd/mtd4 > /sdcard/cache.img
cat /dev/mtd/mtd5 > /sdcard/userdata.img
This will back up all system partitions. use flash_image or fastboot to restore the images.
Click to expand...
Click to collapse
OK, so I was able to use the commands to back up muy dead phone. I am having a lot of trouble restoring the new rooted/s-off phone with flash_image or fastboot. Can someone recommend a site with step by step set of instructions, write it out here, or a GUI program that will accomplish the same thing?
Thanks,
B
bartman99 said:
OK, so I was able to use the commands to back up muy dead phone. I am having a lot of trouble restoring the new rooted/s-off phone with flash_image or fastboot. Can someone recommend a site with step by step set of instructions, write it out here, or a GUI program that will accomplish the same thing?
Thanks,
B
Click to expand...
Click to collapse
What hboot is the phone on? What problems was fastboot giving you?
cmlusco said:
What hboot is the phone on? What problems was fastboot giving you?
Click to expand...
Click to collapse
The phone was in "Fastboot USB". I used the instructions at wiki.cyanogenmod...Fastboot. The errors I got were:
c:\mini-adb_inc>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)... OKAY [ 1.108s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.123s​
Bart
bartman99 said:
The phone was in "Fastboot USB". I used the instructions at wiki.cyanogenmod...Fastboot. The errors I got were:
c:\mini-adb_inc>fastboot flash recovery recovery.img
sending 'recovery' (4608 KB)... OKAY [ 1.108s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.123s​
Bart
Click to expand...
Click to collapse
The new phone is s-off right? What hboot version is it on? Flashing images remotley (from a pc) with fastboot requires either the .77 engineering hboot or one of the new ones unlocked. I would flash the .77 hboot then restore the images with fastboot then flash back to .92 hboot. You can get the hboots here http://dinc.does-it.net/Hboots/
cmlusco said:
What hboot is the phone on? What problems was fastboot giving you?
Click to expand...
Click to collapse
cmlusco said:
The new phone is s-off right? What hboot version is it on? Flashing images remotley (from a pc) with fastboot requires either the .77 engineering hboot or one of the new ones unlocked. I would flash the .77 hboot then restore the images with fastboot then flash back to .92 hboot. You can get the hboots here
Click to expand...
Click to collapse
OK, so I flashed the .77 hboot and now the phone is stuck at the htc incredible start up screen. Tried removing battery and rebooting, etc. No luck.
bartman99 said:
OK, so I flashed the .77 hboot and now the phone is stuck at the htc incredible start up screen. Tried removing battery and rebooting, etc. No luck.
Click to expand...
Click to collapse
If you got the img's to restore with the .77 eng, then you just need to flash back to the .92 hboot and it should boot.
cmlusco said:
If you got the img's to restore with the .77 eng, then you just need to flash back to the .92 hboot and it should boot.
Click to expand...
Click to collapse
Unfortuately no. I am able to get into recovery and so did a restore.
Then I went back into recovery and delete the cache and Dalvik
Then flashed .77hboot again
Did a Fastboot flash of system, userdata, cache, recovery, but was unable to do "boot.img" FAILED (remote: image update error)
re-flashed back to .92 hboot
rebooted Incredible and frozen again at white HTC Incredible screen.
Any suggestions?
B
bartman99 said:
Unfortuately no. I am able to get into recovery and so did a restore.
Then I went back into recovery and delete the cache and Dalvik
Then flashed .77hboot again
Did a Fastboot flash of system, userdata, cache, recovery, but was unable to do "boot.img" FAILED (remote: image update error)
re-flashed back to .92 hboot
rebooted Incredible and frozen again at white HTC Incredible screen.
Any suggestions?
B
Click to expand...
Click to collapse
Did you install the .77 hboot or the eng (engineering) .77? You need the eng one, that will allow the fastboot commands. Then flash back to .92 and it should boot right up.
cmlusco said:
Did you install the .77 hboot or the eng (engineering) .77? You need the eng one, that will allow the fastboot commands. Then flash back to .92 and it should boot right up.
Click to expand...
Click to collapse
I used the ENG .77 (MD5 ends in D1) and then flashed to .92
B
Thats strange. Well im not sure then what to do to get the img's on there. Im not sure why it errors when you flash the img's. I will think on it some more.
cmlusco said:
Thats strange. Well im not sure then what to do to get the img's on there. Im not sure why it errors when you flash the img's. I will think on it some more.
Click to expand...
Click to collapse
It only errors when I try to flash the boot image. I was able to flash the recovery, userdata, and system fine.
bartman99 said:
It only errors when I try to flash the boot image. I was able to flash the recovery, userdata, and system fine.
Click to expand...
Click to collapse
Try erasing boot first " fastboot erase boot " and then try flashing the boot.img
cmlusco said:
Try erasing boot first " fastboot erase boot " and then try flashing the boot.img
Click to expand...
Click to collapse
Nope. Unfortunately it didn't work. I was able to erase the boot, but when I tried to flash the new boot.img, I still got the same error message. I tried a couple of different copies of the same file that I had stored in different places, but still the same error.
I also opened the MIUI ROM zip file (I am using MIUI) and tried to use the boot.img from there to flash. I was able to flash that boot.img, yet the Incredible still is frozen at the white "htc incredible" screen.
Ah well. Unfortunately, with the amount of time I have spent, I could have started from scratch with the base MIUI ROM and cusomized to where I wanted by now:crying:
Thanks for all your help.
B
bartman99 said:
Nope. Unfortunately it didn't work. I was able to erase the boot, but when I tried to flash the new boot.img, I still got the same error message. I tried a couple of different copies of the same file that I had stored in different places, but still the same error.
I also opened the MIUI ROM zip file (I am using MIUI) and tried to use the boot.img from there to flash. I was able to flash that boot.img, yet the Incredible still is frozen at the white "htc incredible" screen.
Ah well. Unfortunately, with the amount of time I have spent, I could have started from scratch with the base MIUI ROM and cusomized to where I wanted by now:crying:
Thanks for all your help.
B
Click to expand...
Click to collapse
No problem, had to try.

HELP. HOX is dead

Hello
Yesterday i unlocked bootloader on htc one x. Then i tried to root it but when i finished my hox did reboot and then reboot all the time. It goes on start screen of android and then reboot again. I cant do anything. Any idea or help?
How did you root it?
Did you flash a ROM without flashing its boot.img and fastboot erase cache?
Did you install a custom recovery?
What screen are you stuck on? "htc quietly brilliant"?
I remember when this happened to me when I first tried to root my phone (First Android phone actually) lol I freaked out.. In my case it's because I didn't make a full wipe after unlocking bootloader and flashing Cyanogen, just booted into Recovery, full wipe/wipe cache and it worked.
Tell us what you did like BenPope said, did you flash the boot.img for the ROM you installed?
the first i did was to unlock bootloader from htcdev. Afther that i tried to root by a guide from this forum:
ALTERNATE ROOT METHOD - 'INSECURE BOOT AND ROOT'
This zip file contains an insecure boot image to flash to your device and a script which will then push the root (SuperSU) files to your device. This is only tested on 1.27.401.2 / 1.27.401.7. USE AT YOUR OWN RISK!
Download
InsecureBootAndRoot r3 - DOWNLOAD (ROMraid) - MD5: a16bff582cb0e25fd3b422652d753ca7
How to use InsecureBootAndRoot - Windows, Linux and OSX
- Download the InsecureBootAndRoot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-insecure-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-mac.sh' followed by './install-insecure-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-insecure-linux.sh' followed by './install-insecure-linux.sh'
The device will now flash the new boot image and reboot. Keep the device attached to USB and when it has rebooted, ensure USB debugging is enabled - the SuperSU files will then be installed.
CONVENTIONAL ROOT METHOD - 'SUPERBOOT' (currently not functioning on shippping devices).
Superboot is a boot.img that when booted, will root your device the first time you boot (installing su and the superuser APK). No need to flash any partitions, no need to mess around with ADB, no messing with the contents of your data partition, no overwriting the shipped ROM on your device, just boot the boot image using the instructions below and you're done!
Download
Superboot r1 - DOWNLOAD (ROMraid) - MD5: c79821d5d75d57dff8a5ffe7493241fd
The superboot image is also 'insecure', allowing you to use 'adb remount' as well as having full ADB root access to your device until such time as you reboot after running this process (it's a non permanent ADB root as it's a 'fastboot boot' and not a 'fastboot flash' but it IS a permanent root in all other regards!).
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then turn on with the 'volume down' button pressed to enter the bootloader, then press the power button again to enter fastboot.
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
That was the steps. I didnt tried to put a custom rom yet. And the worst is that i need my number and i dont have an another device with micro sd. :/
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
BenPope said:
It's funny, because there are two methods that you've pasted there. I have to ask, why did you not go with the recommended one? The one you didn't paste here?
Try it, you might like it.
Click to expand...
Click to collapse
I tried the first one and after i saw that my hpox rr all the time i tried the second one.
You mean this method?
EASIEST ROOT METHOD - 'RECOVERY + SUPERSU'
The easiest way to get root is now to install the official ClockworkMod release and then flash the latest SuperSU zip file. This approach is highly recommended (I also recommend running a backup as soon as you've flashed clockworkmod!)
I do now and nothing. Cant get the command.
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Edit: ahh, is it "command not found" when you try to run fastboot?
BenPope said:
I don't understand what "my hpox rr all the time" means.
At the top of your hboot does it say ENDEAVORU or EVITA?
What does "can't get the command" mean?
Click to expand...
Click to collapse
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
sending 'recovery' (5790 KB)...
OKAY [ 0.770s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.590s]
finished. total time: 1.380s
c:\Android>
That was i did.
Click to expand...
Click to collapse
You could just flash a rooted rom and kernel now, it should work fine.
Flash this recovery http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Install a rom from recovery, you can mount usb from recovery to copy rom to phone.
Then flash the kernel from fastboot that acompanies the rom.
IoSpy said:
i mean it restart all the time
It says ENDEAVORU. WHat does it mean?
I tried the command again now and its done. Now i go to reboot in fast boot and do the same again. The step with SuperSU i didnt yet.
EDIT:
c:\Android>fastboot flash recovery recovery-1-28.img
Click to expand...
Click to collapse
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
BenPope said:
ENDEAVORU is good.
I kind of expected you to be flashing clockworkmod 5.8.4.0 as the recovery.
Once that's done, you take a backup, download the SuperSU zip file, boot into recovery, mount sd as USB, copy the zip onto the SD card, unmount and flash it.
Click to expand...
Click to collapse
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
RohinZaraki said:
What I dont get is why you didn't just root/unlock bootloader via htcdev.com
Click to expand...
Click to collapse
He did. Thanks for playing.
IoSpy said:
What do you mean to fl;ash as the recovery? Wasnt the command i did correct?
How i get backup? When i go to recovery under the fastboot goes to screen with the device and exclamation mark. How can i see my sdcard via usb on pc?
Sry for my question :/
Click to expand...
Click to collapse
The command you did was correct but you flashed the stock recovery, flash clockworkmod recovery to proceed.
BenPope said:
fastboot flash recovery recoveryname.img
I dont know what you flashed, but you'd be better off with the latest clockworkmod, version 5.8.4.0
Doing a backup from that recovery is easy.
Click to expand...
Click to collapse
I used that command fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
So i think i didnt something wrong.
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
BenPope said:
I'm confused, earlier you said you flashed recovery-1-28.img
You're going to have to be clearer on what you write here.
Click to expand...
Click to collapse
Ok sry. I mean i tried boath of them.
IoSpy said:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Click to expand...
Click to collapse
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
BenPope said:
Do that again.
Then:
fastboot erase cache
Then boot into recovery and tell us what you get.
Click to expand...
Click to collapse
Ok i did and i have this screen now.

[Q] I'm worried I killed my phone

I decided earlier today that I'd try to root my one X, but I wound up screwing up to the point that I'm lost. I accidentally wiped the system while in recovery, and when I rebooted, it kept looping. By pressing the power/down button, I can get into the bootloader, and from there into recovery. In the recovery, I was able to look around using a file manager but only found empty folders.
I used adb push to try to get a rom onto the phone, but I'm not able to flash it. When I go to reboot, it informs me that there's no OS installed.
If anybody has any idea what I can do, it would be much appreciated.
im assuming you already unlocked your phone
1.Enter fastboot by holding power + volm down.
2.Select fastboot
3.plug in USB
4.flash recovery with the command: 'fastboot flash recovery <name of recovery here>
5.flash the boot.img that came with the ROM, usually it's located within the zip file
6.erase cache using command: 'fastboot erase cache'
7.select Hboot to return to main menu
8. go to recovery
9. wipe data/factory reset, wipe cache, wipe dalvik from advanced options, format system from mounts and storage menu
10. in mounts and storage, select mount usb
11. copy over ROM zip
12. Install from ZIP
13. reboot system
PS. your phone is only bricked if it can't turn on. obviously it's not going to boot up if there is nothing to bootup, lol
Just ensure your recovery is a recent version, like clockworkmod 5.8.4.0, otherwise mounting won't work.
Thanks for the quick reply. I don't entirely understand how to flash the recovery, however.
I assume I'm running the command on the computer. How do I know what to type in as the recovery?
Mate, did you even do your research before attempting any of this?
Anyway,
Make sure you got HTC sync installed, also Android SDK
1/ Open to a command prompt by going: start -> type in cmd
2/ browse to your folder containing fastboot and adb using the 'cd' command
e.g. My fastboot folder is located at "C:/htc/fastboot" so I would type: 'cd C:/htc/fastboot'
If you're using the one from SDK it could look like C:\Users\Steven\AppData\Local\Android\android-sdk\platform-tools
3/ enter the commands -fastboot flash recovery ...., fastboot flash boot.... etc.
Not nearly as well as I should have. I learned the hard way I guess. Thanks for putting up with my cluelessness though.
I've done as you said, but when I tried to boot into the recovery, I got stuck on it looping the "htc quietly brilliant" screen.
You sure you flashed it Successfully?
and downloaded clockworkmod from here?
http://forum.xda-developers.com/showthread.php?t=1594819
Code:
D:\Android>fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
< waiting for device >
sending 'recovery' (5742 KB)... OKAY [ 1.021s]
writing 'recovery'... OKAY [ 1.506s]
finished. total time: 2.528s
D:\Android>fastboot flash boot boot.img
sending 'boot' (4988 KB)... OKAY [ 0.885s]
writing 'boot'... OKAY [ 1.257s]
finished. total time: 2.142s
D:\Android>fastboot erase cache
erasing 'cache'... OKAY [ 0.116s]
finished. total time: 0.116s
Could it be that I have a bad boot.img? I'm using one out of the renovate 8.1.0 ROM.
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
seaneschen said:
I was able to get my phone running again by following the video here --Nevermind, Can't post the link yet. Should anyone need it, send me a message--. Basically, I had to relock the bootloader and install the RUU.
Now, however, I'm trying again to root my phone, but whenever I try to unlock the bootloader, it still remains locked ("relocked" on the bootloader screen). I can't find anything about how to fix this. Have I lost the ability to root my phone?
Click to expand...
Click to collapse
what command are doing? to unlock i mean
or better yet run through the steps u do to unlock bootloader
ali3nfr3ak said:
what command are doing? to unlock i mean
Click to expand...
Click to collapse
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
seaneschen said:
I'm using the all in one toolkit, which uses the Xfactor exploit, and unlocking by getting the unlock code.bin from htcdev
Click to expand...
Click to collapse
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
elmonen said:
That guide is for the One xl (the us version) as it says "evita" on the topic.. the international one x is "endeavoru". Which phone do you have? There are good guides on here. how to root and a very easy tool in the developement section.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I have the US version.
seaneschen said:
I have the US version.
Click to expand...
Click to collapse
i would suggest that you post this in the in the AT&T, Rogers HTC One X, Telstra One XL forum as thiforum is for the international one x
Oh my....... never noticed. Please don't use Clockworkmod and instead use TWRP, you might brick

/sdcard not mounting

dear all
i am using GN 4.2.2 stock
at the moment i can go to fastboot and i flash clockwordmod recovery v6.0.1.9
i did this because my phone startted to reboot
at the GB logo
.
now problem is i cant flash ROM to sdcard.
here is the output
=================
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.435s
==========================
sending 'radio' (12288 KB)...
OKAY [ 1.353s]
writing 'radio'...
FAILED (status read failed (Too many links))
finished. total time: 2.060s
===================================
in recovery when i am trying to mount sdcard.
===============
Error mounting sdcard
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
amith007 said:
Are u trying to flash the rom immediately after unlocking the bootloader?? When the bootloader unlock is performed, the data is wiped completely.. Now u have to restart the device to mount the sd card again in recovery..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
zakisays said:
fastboot commands i tried are
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
i cant flash any thing
i am stuck
is my sdcard gone
????
Click to expand...
Click to collapse
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
zakisays said:
yes i unlocked bootloader, and yes all data must have been wiped out.
i restarted into recovery but with recovery i cant mount the sdcard
!!!!!
Click to expand...
Click to collapse
Perhaps you didnt read the post, so I will quote it here:
Zepius said:
1) you will never be able to mount the sdcard in recovery, so stop trying
2) what is the fastboot command you typed to generate the output?
Click to expand...
Click to collapse
Zepius said:
do you have the files in the same directory with your fastboot.exe?
you could also boot into your custom recovery and use adb to push a rom to your phone.
Click to expand...
Click to collapse
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
zakisays said:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot flash radio radio-maguro-i9250xxla02.img
can you sent me the link to the steps for custom recovery & adb push
let me try it
thanks in advance
Click to expand...
Click to collapse
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
samersh72 said:
first, flash cwm 6.0.2.3.
look in problem can happen section in my thread
Click to expand...
Click to collapse
i gave the following command
H:\Galaxy Nexus (yakju)>adb -d push "H:\Galaxy Nexus (yakju)\Stock-Unroot Jelly
Bean GNex GSM.zip" /sdcard/
its almost 2 hours now the command hasnt finished executing, hope all is going ok
ok i cancelled the previous command .
rebooted to recovery , mounted /data and /system
then reran push command.
got the zip file into sdcard
then tried installing , error generated
finding update package
opening update package
installing update
Installation aborted
!!!!!
please help
thanks
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
just do this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
well i followed the steps.
i got error as below
===================
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe flash bootloader bootloader-magu
ro-primelc03.img
sending 'bootloader' (2308 KB)...
OKAY [ 0.260s]
writing 'bootloader'...
FAILED (status read failed (Too many links))
finished. total time: 0.507s
================================
i hope now its clear what i am facing.
i can boot to fastboot and to recovery , but cant do anything else
if i flash something then the "Too many links error" comes
thanks for the help , is there anything else i can try
========================
ok i found something interesting
when i flash something i get the error " Too many links"
then when i run fastboot.exe devices , i get
???????????? fastboot
and after reboot i get
H:\brick\xda-24-3-2013\yakju-jdq39>fastboot.exe devices
My IEMI number fastboot
y is this happening
*sigh* ...
Op, uninstall all drivers, reboot your system;
Connect device in fastboot to PC, manually update drivers, disconnect device, reboot PC
Connect device again, flash recovery, after it finishes, disconnect USB, use volume keys to "reboot recovery", reconnect USB, manually update drivers again
'adb devices' should return your SN
'adb push ROM.zip /sdcard/' or if that doesn't do it, 'adb push ROM.zip /data/media/'
Sent from my Nexus

Categories

Resources