Related
Removed all my Dropbox links because they disabled my account due to too much traffic, if you guys want them back please consider donating a buck or two for a Mediafire Pro account...I didn't develop this, just getting the word out that's it's officially available for the Nexus 7. You can either install the "normal" version or touch version from ROM Manager
UPDATE 11/16 new version posted by Koush 6.0.1.9
CWM Regular
CWM Touch
Here is the CWM ZIP by osm0sis:
Touch 6.0.1.9
Regualr 6.0.1.9
You NEED an unlocked bootloader in order to flash this check this thread on how-to unlock/root etc Nexus 7 Toolkit
If you just want to apply an OTA update and you haven't got it, you can do so by booting into CWM without installing it or having root.
first download and save OTA files from OTA 4.1.1 files and save to your /sdcard
then use
./adb reboot bootloader
./fastboot boot recovery-clockwork-touch-6.0.1.9-grouper.img
select install zip from sdcard
toggle signature verification and make sure it's disabled
select the file you downloaded earlier and install
reboot and you will be updated
Click to expand...
Click to collapse
If you want to have CWM permantly installed, first make sure you have root...use Root Explorer or any other file manager with root access and go to /system and delete recovery-from-boot.p
now use
./adb reboot bootloader
./fastboot flash recovery recovery-clockwork-touch-6.0.1.9-grouper.img
./adb reboot
Click to expand...
Click to collapse
You now have CWM installed.
I'm not responsible if you brick your tablet, it blows up mid flash etc
Make sure you know how to use ADB and have the SDK installed, you need that in order to do all of the above steps
Also make sure you have the recovery files saved to /sdk/platform-tools and also fastboot.exe has to be there also
Any commands that start with ./ are for linux/osx...just remove those when using windows
Click to expand...
Click to collapse
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
** edit 7/21/12**
Here's the zip file for the new touch recovery 6.0.1.0 http://db.tt/pLDeKXEf
Feel free to mirror!
Sent from my Nexus 7 using xda app-developers app
Flashing when I get home thanks.
Sent from my Galaxy Nexus using xda app-developers app
I flashed this from rom manager and so far have not had any of the problems I have had in some of the interim CWM's like inability to delete back ups or mounting system.
hey dude it's 6.0.0.6 not 6.0.6
mrich137 said:
If you already have CWM or another recovery installed and would like to replace it with 6.0.0.6 Touch, I have packaged this file as a flash able zip file.
Download the zip file from http://db.tt/t13uCIRV and flash in recovery. To test, go to advanced -> reboot recovery and CWM Touch 6.0.0.6 should load up.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Shano56 said:
hey dude it's 6.0.0.6 not 6.0.6
Click to expand...
Click to collapse
oops, typo...thanks, I will fix it now
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
It works as long as you're connected to a computer, so you can access recovery from bootloader you just need to be hooked to a computer.
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
JoeM01 said:
Same here. Flashed via CWM with no issues what so ever. Shocking how much faster backups are now!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
If you know how to use ADB you can always fastboot a recovery.img,,,,this thing is almost impossible to truly brick. IN order to get into fastboot just connect to your computer and run adb with these commands
adb reboot bootloader
once in fastboot mode write this
fastboot devices
that will tell you if your device is connected and reading in fastboot mode if it is you will see something like fastboot and some numbers next to it. If nothing you do not have the fastboot drivers installed.
then to fastboot flash a recovery.img write this
fastboot flash recovery r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever recovery.img you are using or have in your tools folder of you SDK location).
and in order to get right into CWM if you cant boot write this
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img
hope that helps
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
camblue said:
I know right,,,almost seems like it is not doing it right but I have went back to a previous backup and it flashed fine!
Click to expand...
Click to collapse
Flashed fine here also. Works without flaw so far.
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
Did you install the ota after you rooted and installed the recovery? I soft bricked too and I think that was the reason why. Something about the ota overwrote the recovery partition. Best thing to do is download ROM manager and click the first option to flash cwm. Then click the next button to boot into recovery. Then just flash the zip I posted to upgrade to touch.
**edit** just tried to boot into recovery from the boot loader and got stuck at the Google screen too. Holding all three buttons rebooted and started up as normal. Maybe the boot loader boot into recovery is pointing to a different partition for some reason?
Booting into recovery from ROM manager works though. That's how I've been getting in.
Sent from my Galaxy Nexus using xda app-developers app
thanks for the heads up
BCD90 said:
I am still not able to access recovery from bootloader. Just makes me kinda nervous to soft brick my nexus 7 and not be able to get into recovery to restore.
Any known fix for this?
Thanks
Click to expand...
Click to collapse
What did you try?
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
BennyJr said:
Can you adb boot into recovery from the bootloader?
Oh and you can't 'adb reboot' in fastboot just hit the power button.
Click to expand...
Click to collapse
camblue said:
yes and can do this while in fastboot (bootloader mode)
fastboot boot r3-recovery-clockwork-touch-6.0.0.4-nexus7-modaco.img (or whatever the name of your recovery.img is)
Click to expand...
Click to collapse
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Bootloader = fastboot. Any adb commands wont work
BCD90 said:
The thing is when im in bootloader mode i can not access adb. I have tried this but it will not let me.
Click to expand...
Click to collapse
Which is correct. You won't be able to do adb commands in the bootloader. The command he asked you to try was a fastboot command, which should work
Sent from my Galaxy Nexus using xda app-developers app
Make sure the drivers are installed had this problem with windows 7 download the naked driver pack and follow the instructions
Sent from my Nexus 7 using xda premium
Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
You won't be able to flash anything until you fixed your sdcard using the method in that link.
Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium
ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium
DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader
Thank you both will try that now.
Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.
fastboot only works in bootloader btw
Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X
Sent from my HTC One XL using Tapatalk 2
Hey everyone, I just went through the process of rooting my phone using the Hasoon200 tool (http://forum.xda-developers.com/showthread.php?t=1952426). Everything worked fine; I unlocked the bootloader, flashed the TWRP recovery, and installed CM10. However I couldn't get past the CM10 loading screen so I went back to recovery and wiped everything I could (cache, dalvik, system, factory restore) then rebooted. After that I can't get past the white HTC "Quietly Brilliant" splash screen. No bootloader or recovery. Hasoon2000's tool can't reach the phone to do anything. Holding Down Volume and Power buttons just reboots to the splash screen. When I plug the USB into my computer it must be recognized somehow because it connection notification sound plays but I don't see the drive. What can I do now?
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually
Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1
a box of kittens said:
Turn on, hold power 10-15 seconds, until screen goes black, let off, press n hold volume down, press power just 2-3 seconds, let off power button but continue holding vol. Down
Than select recovery
And once in bootloader check if you have hboot 1.14
---------- Post added at 03:37 AM ---------- Previous post was at 03:36 AM ----------
When you get back into recovery do the same wipe process than flash the Rom...if you have hboot 1.14 you have to flash the boot.img manually
Click to expand...
Click to collapse
Thanks for the response. I'm able to reach the bootloader now, but when I select recovery it freezes once again on the white HTC splash (but this time with the HTC Dev red text below). And I do have hboot 1.14
subarudroid said:
Yea what box of kittens says ^^^^^^^
http://forum.xda-developers.com/showthread.php?p=33303798
(This thread might help as well.= if your 1.14 hboot) And make sure your thanks button isn't broken at least for the member above who took time to help. :thumbup:
Sent from my HOX w/CM10.1
Click to expand...
Click to collapse
Thanks [email protected] reflash your recovery so fastboot flash recovery recovery.img(whatever you have it named but has to end with .img)
Reflash your recovery image. Then try again
Sent from my DROID RAZR using Tapatalk 2
Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.
If you need anything else just post here.
Sent from my HTC One X using Tapatalk 2
ltjska04 said:
Thanks everyone, I'm back to recovery! Hopefully I can figure it out from here.
Click to expand...
Click to collapse
Easy peasy...
Flash rom,
boot into boot loader,
drop the boot.img inside your adb/fastboot folder,
Right click on you adb/fastboot folder and choose open command prompt here. The type
Fastboot flash boot boot.img
Reboot that beast and enjoy the profits
Sent from my HTC One XL using Tapatalk 2
New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.
_atlien_ said:
New to this phone and was a little overeager. I unlocked bootloader, rooted, installed TWRP and flashed CM but didn't flash the boot img before flashing CM so it boots forever, of course (I'm so dumb...)
I can get back to the bootloader where I try to flash my CM boot img but adb won't detect the device (presumably because usb debugging isn't selected since I can't boot into the rom). How can I either 1) get adb to detect so that I can flash the boot img with adb or 2) flash the boot img without adb?
Stumped. Thanks in advance for any/all that can help with this.
Click to expand...
Click to collapse
Sigh you flash boot img through fastboot
Get phone into bootloader. (White screen, 3 skating droids)- make sure it says "fastboot USB" in red
Right click on your adb/fastboot folder, choose "open command prompt here"
Type--> fastboot devices
See if anything shows up.
Sent from my One X using Tapatalk 2
a box of kittens said:
Sigh you flash boot img through fastboot
Click to expand...
Click to collapse
Hey! Thanks for replying. I'm stuck here. Fastboot flash of the boot img requires the phone to be usb detected, yes? I go to fastboot but when I type 'adb devices' I gets nothing back.
I don't think I was clear in my earlier post. I have CM and gapps flashed but it won't boot into the OS because I didn't flash the boot img first but now I can't get the phone to be detected by adb so I don't know how else to flash the boot img. Thanks for taking the time to reply to me. I realize you didn't have to.
Thanks to all! My phone rides again!
_atlien_ said:
Thanks to all! My phone rides again!
Click to expand...
Click to collapse
Lol what did to do to be able to fastboot flash
Sent from my One X using Tapatalk 2
Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...
strommer666 said:
Hey,
I was stuck too... Managed to get the recovery working but the fastboot flash boot boot.img thing is not working can anyone guide me through this?
I did try the forum ways but still isn't solving the problem...
Click to expand...
Click to collapse
Drop the boot.img INSIDE of your adb/fastboot folder.
Boot into bootloader
Right click on your adb/fastboot folder. Choose "open command prompt here" type --> fastboot flash boot boot.img
Sent from my One X using Tapatalk 2
Stuck in bootloader loop
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks
singh.bobby said:
Folks, I was stuck in similar situation as well; I had missed copying the boot.img step initially and after i did a factory reset on the boot loader i got stuck in HTC logo screen with red lines warning.
I followed the directions provided on this thread and am now able to get into TWRP recovery screen. What would be the steps for me now to flash a rom onto the device again. I had flashed the ViperXL rom prior to me stupidly doing the factory reset.
Per directions on another thread, I was trying to first have the rom and boot.img loaded using the mount from TWRP. However when i do the the step of 'Mount USB storage', I get the warning that on my computer that i need to 'Format Disk drive'. Not sure why would i need to do it.
Please help!
Thanks
Click to expand...
Click to collapse
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
---------- Post added at 11:44 PM ---------- Previous post was at 11:18 PM ----------
exad said:
Doing a factory reset from the bootloader killed your SD partition. You'll need to format it as fat32 before you can access it again. You've lost everything on there.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
singh.bobby said:
I did the reformat for my SDCard; how do i proceed now? should i move the zip file for the rom to the sd card and try installing it ?What would be the next steps i would need to do to get back to the ViperXL rom i have downloaded; or is there a way for me to go back to the original HTC sense rom i had prior to flashing
Thanks
Click to expand...
Click to collapse
I was able to flash ViperXL rom again; I placed the zip file for the rom in the TWRP folder after i mounted the device. Thereafter i was able to install the rom from the recovery. All good for now . Although all my data from Sd card got wiped :crying:
My NExus S is stuck on the screen that says:
Fastboot Mode No Boot or Recovery IMg.
Product Name - Herring
HW Version - Rev34
Bootloader Version - D720SPRKC5
Baseband Version - D720SPRLCI
Carrier Inro - SPR
Serial Number 32300E25C33500EC
Lock State - Locked
options to select
Reboot Bootloader (gives me exact same screen) except it only says "Fastboot"
Reboot Back to the "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"
Recovery (Can boot to CWM but I can't mount anything)
Power OFF (That works fine)
Then the little green man and the android logo
Followed by USB Control INIT
USB Control INIT End
STANDARD_SET_CONFIGURATION
Conventional wisdom says download some files and fix via fastboot. However in fastbootI can't run ANY of the steps without running FASTBOOT OEM UNLOCK. When I run it my phone asks if I really want to unlock the bootloader. when I choose YEs and hit power it just freezes there.
My next thought Boot to recovery and restore. A restore through recovery followed by a reboot leads me back to the original no boot or recovery img.
Okay I'll just sideload a working rom by mounting usb storage. Then I can flash it with CWM and be up and running.
but when I try to do mount the USB Storage I get "E:Unable to write to ums 1unfile (No such file or directory)"
Finally, Last ditch Effort, I'll load up ODIN and use that to put on a working recovery. there's forums all over the place explaining how to do that right? Well yes, but the links to the Tar file are all broken.
What next my friends? I'd really like to get this phone working.
Wug's Nexus Root Toolkit.
ej8989 said:
Wug's Nexus Root Toolkit.
Click to expand...
Click to collapse
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
swing4thefence said:
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
Click to expand...
Click to collapse
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
ej8989 said:
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
Click to expand...
Click to collapse
No matter how I try to do it, it always freezes at the unlock bootloader step.
Did you install proper drivers?
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
swing4thefence said:
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
Click to expand...
Click to collapse
Reinstalled Drivers. Still no luck.
I have the same problem.
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
!Lür said:
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
Click to expand...
Click to collapse
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
swing4thefence said:
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
Click to expand...
Click to collapse
Solution for me:
1. Turn device on into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
5. reflash everything i wanted :good:
Requirement is a working Android-SDK!
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Im having this same issue too i can still get to CWM recovery but nothing really helps from there. I can still mount my storage and put zip files on there etc but nothing seems to fix the problem...any progress?
swing4thefence said:
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
swing4thefence said:
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
Click to expand...
Click to collapse
Was this solved by any means ??, i am myself stuck at that position
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Akbar89 said:
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Wug's Nexus toolkit ?? It is stuck on bootloader unlock menu, as unlocking bootloader makes it freeze. Without unlock it doesn't flashI anything.
If there is another tool please guide me with link.
Avoid Spells!!! "Auto correct : ON"
stuck on fastboot mode(lenovo S860)
recently i've bought lenovo s860 (2GB version).....its latest updates had bugs....so i was trying to downgrade to lower version(jelly bean).....in the way i got stuck in fastboot mode......is there any way to get out of it??
same problem in galaxy nexus i9250m
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
i have same problem in galaxy nexus i9250m
my bootloader showingh no boot or recovery img
i have working fastboot, workin adb and driver
my oem is unlocked with fastboot
bt i am unable to flash recovery and rom
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
trentarmy said:
Hi, if anyone can help me solve this, I will be eternally grateful.
So I was following the CyanogenMod guide for installing the ROM on my HTC One S, but I foolishly flashed the ROM as a .zip, instead of the boot.img.
I can access the bootloader screen, and also the TeamWin recovery screen, but I cannot seem to use flashboot.
It always comes up as <waiting on device>.
I am lost, because I obviously used flashboot to flash the recovery and the ROM across to my phone, and all the files are still in the same folder.
Basically, I cannot start my phone, other than into the recovery screen or the bootloader screen. I cannot seem to flash anything across either.
If anyone can solve this issue from this poor explanation I will be more than impressed.
Many thanks.
Click to expand...
Click to collapse
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
tivofool said:
It is waiting for device because the phone isn't in bootloader (fastboot USB) connected to pc...most likely.
So with phone in bootloader and it reads fastboot USB
from your fastboot folder press shift and right click to open command window.
fastboot flash boot boot.img
(this assumes you have put the boot.img in the fastboot folder)
Then go to recovery
install rom.zip
wipe the caches
If you don't have the rom.zip on your phone then mount usb storage in twrp and move the rom.zip from your pc to your phone.
Hopefully your Hboot is 2.15 or you will just bootloop.
Click to expand...
Click to collapse
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
trentarmy said:
So can I clarify that I need to flash both the boot.img file and the rom.zip separately. Then install the rom.zip, not the boot.img?
Because I install the rom.zip last time without the boot.img being flash, and thats when it messed up.
Basically, am I installing the .zip or the .img?
Thanks a million.
Click to expand...
Click to collapse
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
luxandroid said:
.img , you need to extract boot.img from ROM zip and than just "fastboot flash boot boot.img" ,no quotes in command -that is for boot.img and you do flash ROM as a zip
Click to expand...
Click to collapse
Thanks!
Next issue. I have flashed the boot.img to the phone, now I need to get the rom.zip onto the phone.
Everytime I click mount on TWRP, my computer tells me that I must format the disk before I can use it.
I can't seem to use adb, I always get "no device found".
Any ideas?
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
adb push ROM.zip /sdcard ,ROM needs to be in fastboot folder, are U s-off or s- on ,did U flash ROM zip before soft brick, can U see files from TWRP when U go to install from sd...some info that is important,if all fails think you'll have to run RUU to fix memory partitions
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Everything is in the same folder. adb push function still won't work.
I am s-on.
I did flash the rom.zip before the soft-brick, but when it bricked, I wiped the memory and cache, reset to factory settings. So there is currently no files on the phone.
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
trentarmy said:
I wiped it all via the TWRP recovery.
Any chance you could walk me through RUU? Or at least point me in the right direction.
It does sound like it would be easiest just to start all over again. What's the best way to do this?
Thank you for your help.
Click to expand...
Click to collapse
what happened when you tried to push the rom.zip via adb?
ThudButt said:
what happened when you tried to push the rom.zip via adb?
Click to expand...
Click to collapse
I just get "error: device not found"
Any ideas?
If not, could someone please run me through just wiping everything and starting again?
Cheers
luxandroid said:
U wiped all this in bootloader ?
Sent from my HTC One S using XDA Premium 4 mobile app
---------- Post added at 07:49 PM ---------- Previous post was at 07:47 PM ----------
Anyway best thing is to flash RUU and do all over again...
Sent from my HTC One S using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not sure if this makes a difference, but when connected to my PC, my phone is called "My HTC".
I remember reading somewhere that it should be called an Android ADB Device or something similar?