Related
Ok i know a thread of this kind has probably been made a couple of times, and i apologize for this, but i have been searching every where to find a way to make my nexus one back to stock. I know once the bootloader is locked i cant reverse that but i just want to have the original stock recovery image. I currently have amonRA 1.7.0 recovery image. I have tried everything possible that i know, and as I must mention im not a really a good adb user. I mostly know how to use custom recovery images, load roms, themes, mods, etc. I have read a couple of threads where it would help me revert back original state but i just cant figure it out. I would very much appreciate it if someone would help me out and give me a step by step procedure i can use to flash a recovery image.
I currently have my nexus on ERD79 stock rom, no mods no nothing.
Firmware is 2.1(not 2.1update1)
thanks for the help!
http://forum.xda-developers.com/showthread.php?t=614850
this puts everything back to original even recovery img.. this is full instructions
and once its "unlocked" it cant be Relocked.. it stays unlocked
http://forum.xda-developers.com/showthread.php?t=614057
the PASSIMG
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not
fastboot flash recovery recovery.img
Step 13. fastboot reboot
Thanks for this but i came across this thread and to be honest i got lost after it asked to put the unziped file where i can find it.
Can you give me an idea where i could put it?
Oh and i downloaded the passimg.zip and i couldnt extract it, my comp said file is invalid.
thanks again.
Ok ill see if i can unzip it for you sir
or you can try it this way too
http://www.mediafire.com/file/e5t4504thl2ry42/recovery.rar
there you go man recovery image from the thread posted before
1. Plug the phone into the computer
2. Reboot into fastboot by holding TrackBall + Power (you should see three Androids on skateboards and the words 'fastboot USB' in red)
3. On the computer, open a command prompt cd to the sdk/tools directory (we will assume the SDK is located in C:\android-sdk and the recovery file is in the root of the sdk/tools directory for the following steps)
4. With the phone connect via USB, open up a cmd prompt
Code:
adb reboot recovery"
5.
Code:
adb devices
A device name and 'recovery' should be returned
6.
Code:
adb push recovery.img /sdcard/recovery.img
recovery.img is located on android-sdk/tools dir
7.
Code:
adb shell flash_image recovery /sdcard/recovery.img
This permanently flashes the recovery.img to your phone, you can now boot into it by holding Vol- while powering on the device
8. Reboot
Click to expand...
Click to collapse
i apologise if this seems like a noob question, but i searched everywhere, and couldn't find the answer.
I followed the steps to flash the stock recovery to my nexus, and when i boot into the recovery mode to test it, it's just a blank screen with an error triangle and a little android standing next to it.
Is this what the stock recovery is meant to be? or did something go wrong in the process?
Yeah that should be the stock recovery, you should be able to press the power button and volume up and get a blue text list saying reboot system now, apply sdcard:update.zip.... etc.
yes, thank you very much for clearing that up for me
see my guide: [UNROOT] Unroot al android devices which was also posted on the front page. this step allows you to get a stock recover image specifically for YOUR GOOGLE NEXUS PHONE, not just generic google nexus phones
hate to revive a thread thread but im having the same delima.
i just bought a nexus one from CL and it was loaded up with a 2.3 rom. Im guessing its not using stock kernals, baseband, etc etc.
Im trying to get it back to stock EVERYTHING. i know i cant relock the bootloader but other than that, i want to revert it back to what you get right when you open the box. im not even sure what a recovery image is... but if its different when u flash different roms, i would like that stock too lol.
i know about the passingimg method but i wasn't sure if thats compatible with all roms (kind of like how unlocking iphones only works with certain basebands). i also wasn't sure if that'll return everything to stock, kernal, OS, modem, radio, recovery (?), etc.
im not very familiar with adb either. can anyone PLEASE help me out?
this is the method im talking about http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
would the passingimg get EVERYTHING back to stock? or would it leave the custom recovery, kernal, or something else etc.
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
leppricon said:
tried to install clockwork recovery and Im getting a FATAL ERROR The MD5sum of the installed recovery and the stored MD5sum do not match! DO NOT REBOOT YOUR PHONE Please contact TheCubed ASAP! So any help here would be appreciated.
I used the new one click root for ginger bread which included the Revo toolkit and i tried to install clockwork recovery using 4.0.0.2-pr1, after it failed with the aboved message i tried the revostock option and got the same message, so what do i do now?
please help me TheCubed!
Click to expand...
Click to collapse
Try the 4.0.0.2-pr1 again and again until it goes through. DO NOT REBOOT YOUR PHONE UNTIL IT SUCCEEDS, IT WILL RESULT IN YOU BEING STUCK IN FASTBOOT!!!!!
Try deleting mlk file and reinstalling recovery
Sent from my VS910 4G using XDA App
Installed rom manager
I installed rom manager to use to back up phone it rebooted to run the back up and it got stuck in fast boot, so i did some searching and found the page on fixing that. i used the second posters method instead of thecubed (because he said it was easier and thecubed agreed) and now all i get is an lg start screen. do not follow the other guys post it is for another phone completely i had to find it out the hard way. so any ideas on how i can get back to working phone?
The file you deleted was the mmcbik0p8 backup found on your ext card. When reinstalling the recovery CWM should have rewritten it with the correct version.
Try removing your card and mounting it on a pc go in and manually delete file and try to boot the phone. I had to do this to make my revolution boot.
This is how i fixed it
adrenaline_rush said:
Its not hard to fix at all, you will have to install the Java JDK, Android SDK, and three files AdbWinApi.dll, fastboot.exe, and CWMrecoveryrevolution.img which is the clockwork recovery for our phone.
Here are the files in .rar format.
http://www.mediafire.com/?eb3219cy0lbc71m
Android SDK
Java JDK
The first version should work
1. Install the Android SDK to your C: drive. Make sure the SDK and all the files are in C:\androidSDK. This will make things easier later.
2. Open the SDK and install the additional AndroidSDK platform tools package
3. Install the Java JDK
4. Unzip the .rar to c:/androidSDK/tools
5. Open command prompt, start> type "cmd"> press enter
6. Plug in phone
6. Assuming you placed everything in the right folders, type the following into the command prompt
Code:
cd c:/androidSDK/tools
7. You should now be in the correct folder, paste this command next:
Code:
fastboot erase recovery
then:
Code:
fastboot flash recovery CWMrecoveryrevolution.img
If that succeeds then type the final command:
Code:
fastboot reboot
Hopefully this works and is understandable
Click to expand...
Click to collapse
Don't work
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
leppricon said:
Yeah this method don't work any more I tried yesterday and today with the revolution file. Fast boot does not find the phone. Cmd is <waiting for device>. Going to Verizon tomorrow to get new phone.
Edit: why it doesn't work is because I used the easy method that the other user posted, i did not check the phone version of the flash file, so now my phone has the wrong firmware on it and wont boot. Also it does not get recognized by my pc.
Click to expand...
Click to collapse
You tried the volume up + power to get to the recovery?
Tried that too.
The only way the Vol. up and power button works if I have the battery out and the usb hooked up, and then the screen says do not detach download in progress. I left it this way for about two hours thinking it would magically fix it self but it didn't. Called Verizon about an hour ago and I going to get my new phone in the afternoon tomorrow. they over-nighting it to me, they said any new tech with 4g they try to get it fixed as fast as possible. I then asked when 4g would be coming to my area he said spring of 2013... lol
Oh, you could have flashed the .tot system file over, but I guess it does take some time to get the program set up, and they're already replacing it..
Tried
I had all the above programs installed and working properly, that is how i got to a non-working phone, I flashed it with the wrong firmware which bricked it. Its not detected in any of the programs because all the programs are looking for a revo and i flashed to something else.
This was posted in the revo fastboot fix thread, I followed it and it bricked my phone.
hello everyone, im pretty sure i was the first one to run into this issue since it happened twice on two different phones. but for an extremely easy fix just look here, believe me it doesn't get any easier than this. this is another way it was explained, but both are pretty much the same. im only posting this in case someone doesn't understand the directions posted by thecubed, not saying the ones i post it are better, just explained differently, not trying to step on anyone's shoes here http://forum.xda-developers.com/show....php?t=1088046
Last edited by zr0ko0l; 23rd June 2011 at 03:03 AM.
this is the reply from thecubed: Dont' worry about my toes
If you've got a better explanation, go for it! I'm not the best at writing instructions.
Still no CWM
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
Why run V6 when V7 (aka GingerBread) is out?
meandmine said:
I rooted my Revo using adb and zergrush. I'm running v6 and cannot get CWM to work using adb, RevoToolKit or even on a command line on the phone itself. So far all I've done is reload my phone. It stays rooted, but no CWM. Md5's all check out on mmcblk0p14 before I restart, using adb and a terminal on the phone. The checksum is right when I dl the recovery-cwm-pr1.img in the zip, also.
I did do an OTA update after I rooted. Could that be the problem? Should I unroot and reroot?
Click to expand...
Click to collapse
DId you manually use adb and Zergrush or use a different method? Did you use my all in one package with the root.bat? More info would be greatly appreciated.
Issues activating 4G LTE
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
cantibot said:
Hello all,
First post so woot! but, kind of bad news at the same time. My friend and I were rooting/CWM'ing/ROM'ing his phone and we hit this road block. Everything went find up to the flashing of Gingervolt. It boots up and starts the initial setup sequence, but after the step where it ask for language, it sits and spins it's wheels for a while before saying that it cannot find the SIM card. There is also a small SIM card icon with a question mark next to the signal bar meter. This step is keeping us from being able to move forward and was wondering if there is any hope to get this thing to activate.
Things we've tried:
1) Reboot, restore, wiped all the caches
2) Did a nandroid restore of before we flashed it with Gingervolt
3) Downloaded a stock/rooted ROM (and received the same results)
4) Calling Verizon's activation hotline (told us nothing)
5) Taking out/Putting back the SIM card and seeing if that maybe would reset something. (I guess not)
It would be really cool if I could figure this out so he doesn't have to bring it in to big red :3
Thanks and you all rock!
canti-sama
Click to expand...
Click to collapse
Was 4g turned on when you flashed? If nothing else you can flash the zv7 tot file through lgnspt.
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
cantibot said:
Thanks so much for your quick reply,
I think that is going to be my next option. Thanks for reassuring me that is the right direction! And yes, I did have 4g (It was called LTE, I think it's the same thing.) enabled before flash.
Click to expand...
Click to collapse
What version were you on before you flashed Gingervolt? If you were on v4 or v6 it will do that.
Sent from my Gingervolt-ed VS910 4G using xda premium
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
This is a response to post #14. I meant to post this with a quote. Instead, I posted a quick reply. Sorry.
meandmine said:
I rooted it with adb following root.bat. I run linux and am a terminal junkie. The rooting went fine. I then dl'ed recovery-cwm-pr1.img and adb'ed it over to the sdcard, ran all the checksums, from adb and on a root terminal on the phone. Then from adb, moved the image file to block mmcblk0p14, ran checksums again from both adb and the terminal on the phone. They both checked out fine, again.
After reboot, it just wiped, no CWM. It might be a permissions problem. I see no execute bit set. Should it be?
Click to expand...
Click to collapse
Not a permission problem, there are a couple of files in there that have to be removed otherwise it blocks it from booting into cwm with the key press combo. You have to boot into cwm using quick boot or the reboot into recovery option in the revotoolkit menu. If you flash GingerVolt you will then have reboot and recovery in the power menu, but also will be able to enter recovery through the button combo.
You will have to push the recovery image again first though.
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
limache said:
Hi I was rooting my HTC one and was able to do so successfully. Then I tried to flash roms and it didn't work with TWRP so I tried clockwork. That's when everything went to hell. I was stuck in the bootloader loop and it just kept booting to that. Then I tried to follow this guide
http://forum.xda-developers.com/showthread.php?t=2258809
and I did method 1 but when I ran one of the commands I saw failed. Now my HTC One is just stuck on the screen with a silver HTC logo and I can't even turn it off. I would really appreciate any insights and advice. I tried doing it on my own but clearly I kept ****ing up and could really use some help.
Click to expand...
Click to collapse
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Quis89 said:
I've got to ask. A bright light? Is he doing surgery as well? What's the reason for the light?
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Toxicoblivion said:
for some reason multiple people have reported successful reboots under bright light in which previously (sometimes within minutes) earlier would not work in a dark environment. i have no idea why it works, but ive heard it work enough times, its worth adding it in.
Click to expand...
Click to collapse
It's thought this is a safety feature so that you can't accidentally long press power and restart in dark places like your pocket.
@rider5512 Sounds right to me. Thanks for clarifying.
Toxicoblivion said:
This is a softbrick not a (hard)brick. this is fixable. Try putting it under a bright light and holding down pwr + vol dwn (dont ask just do it) and see if the soft buttons start blinking. if so, you should feel a buzz when it reboots, and then keep holding down vol dwn and that should put you into bootloader. from there you can get to fastboot (and maybe even recovery)
Click to expand...
Click to collapse
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
limache said:
Thanks Toxic!!- so I tried that and I'm back in the bootloader now! I guess the bright light made a difference as I messed up my phone last night. It didn't buzz but now I'm back in the bootloader. How should I go about fixing this now that I can access the bootloader and recovery? I really don't want to half ass this again lol.
It also says "TAMPERED" "RELOCKED" on the top as well.
I'm thinking of following the instructions for method 2 from this thread.
http://forum.xda-developers.com/showthread.php?t=2258809
Would this be correct or do I need to do anything else first?
Click to expand...
Click to collapse
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
crushalot said:
Method 2 looks good.
Just remember that you will have to unlock your bootloader again. You will probably have to request a new token at htcdev.
Then flash recovery from toolkit and sideload and install new rom.
Click to expand...
Click to collapse
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
fastboot erase cache
limache said:
Great I'm just concerned at getting this to work again.
EDIT - So I am trying method 2 right now - I am trying to boot into recovery but it just brings me back to bootloader. I cannot access recovery so when I try sideloading the rom it doesn't work. It says "error device not found" in cmd prompt but I already installed the HTC drivers though. Any advice?
So that means I have to go through the whole process of unlocking the bootloader and rooting it. So can I just use this tool by Hasoon2000 instead of going through manually typing in cmd prompts in the future?
In regards to requesting the new token, can you clarify? Are you saying that since I activated the old token, it cannot be activated anymore and I need to contact HTC Dev directly?
Click to expand...
Click to collapse
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
crushalot said:
You need to flash a new custom recovery again before you can boot into it and sideload. You won't be able to do that until you unlock your bootloader again.
You do have to do the whole process of unlocking the bootloader and installing a custom recovery from the toolkit.
You will need to get a new unlock token from htcdev (however you did it before, manually or with the toolkit) since you can only use the unlock token's once it seems. No biggie, just need to do the process again to get that new token you will need to unlock you bootloader before you will be able to do anything in recovery.
Click to expand...
Click to collapse
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
limache said:
Thank you crushalot!
So I am following this guide.
http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/
I successfully unlocked the bootloader and now I need to flash the recovery. In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?
Edit - Okay so I used Hasoon's toolkit to flash the recovery and I think it worked. However, now I am trying to sideload the rom and having issues. I selected "ADB Sideload a ROM" and i manually went into recovery and TWRP (the toolkit can't send it into recovery for some reason). I selected "sideload a rom" on the HTC and then it shows you a bar that says "Swipe to sideload". I wasn't sure if I needed to do that or not but I tried running the toolkit and sideloading the rom and i got "error: closed" in command prompt.
in TWRP there are messages saying "unable to mount /data, recreate data/media folder, internal storage etc".
Click to expand...
Click to collapse
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
crushalot said:
"In Step 23, he copies the file "CWM-SuperSU-v1.30.zip" into the internal storage. Since I cannot access the internal storage of the phone, is this step necessary to flashing recovery? Can I just skip over to step 24 and run "fastboot flash recovery openrecovery-twrp-2.4.0.0-m7.img" ?"
That is done in order to give root access to the currently installed rom. You are going to install a new rom, so you don't have to do that until you get the rom installed.
You are now the 3rd user I have run into that is having the issue where you can't mount anything in recovery and I'm not sure why. Some users report that re locking and unlocking the bootloader fixes this, but you just did that, so I'm not sure why this is happening.
Within the toolkit try the perm root option? Perhaps there is something I can't think of since I rooted mine, the day I got it awhile back.
"Rooting The Device To root your device, first make sure you have unlocked the bootloader and installed a custom recovery. Next, select the ‘Perm Root’ option (the last one) from the Extras section and follow the instructions to get root access in no time."
To any other advanced users who may be able to answer this:
Does the recovery need the installed rom to have the SU binaries before it can mount the system in recovery? Does recovery need to be granted SU though some other means before mounting?
Click to expand...
Click to collapse
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
I know it is a pain in the ass, and users not familiar with adb/fastboot commands and using the toolkit mess it up.
Flashing recovery in fastboot after you pointed to your adb/fastboot folder you need to do:
fastboot erase cache
fastboot flash recovery name-of-your-recovery.img
fastboot erase cache
As you got it flashed successfully but you have problems sideliadung it with adb, get yourself a OTG cable and a USB storage stick, put the custom ROM.zip on there and then choose 'flash .zip from external storage' or s.thing like that. I don't know if that option is available in TWRP but it is in ClockworkMod.
Once you have booted successfully up into the ROM, go back into recovery and do a Nandroid back up, and keep it on that stick and on the internal storage if your One!
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
limache said:
Okay I just tried Perm room - nothing happened except it showed 776 KB/s. I remember a few days ago there was a system update from HTC and I updated it OTA - would that affect this at all?
Just to be clear, I run the program, go into recovery, go into adb sideload, then I select the rom on the PC. Then I swipe across the bar to mount the rom and then it fails to mount and I get "error closed" in command prompt.
Click to expand...
Click to collapse
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
limache said:
Hmm so can I use the toolkit to do this? I don't have the actual recoveries of TWRP and CWM. If I have TWRP on this installed, can I flash Clockwork as well or do you have to choose one or the other?
I just want to clarify - are you saying that I should be doing this manually instead of using the toolkit to install CWM or TWRP? When I use the toolkit, does it erase the cache?
Btw, when I plug in my phone, it detects it as an F drive but I cannot access the actual internal storage. What does this mean? I have the drivers installed already.
Click to expand...
Click to collapse
crushalot said:
Yes, every user that I encountered with this issue had done an OTA update. Not exactly sure why or how that is causing these issues.
Yes, your procedure for sideload is correct, however you are unable to flash anything or use recovery at all because when in recovery the internal storage won't mount, so it can't perform any actions.
Need to do some more reading for: unable to mount in recovery
---------- Post added at 01:54 PM ---------- Previous post was at 01:49 PM ----------
I don't think the toolkit is the issue. The cache erase can also be done from the toolkit with the Erase Cache in the Commands section. Never hurts to try this, but the issue is not being able to mount storage in recovery. I think you could install either recovery and it wouldn't matter as they would both have the same issue. Generally, I prefer TWRP anyway.
You can't access the phones internal storage when connected via USB when the phone is in recovery or fastboot. So that is normal.
Click to expand...
Click to collapse
Hmmm okay so the other poster's suggestion was to get an OTG cable (a micro usb to USB cable right?) and connect the USB with the ROM directly the phone. Do you think this would be a big difference or no? I just don't know if the issue is the internal storage itself or the mode of pushing the ROM.
Otherwise, I'm pretty much scratching my head and have no idea what else I could do =/.
Just for anyone else who's having issues, I've tried using TWRP's install function with the OTG cable but it still doesn't mount. Just letting people know.
if you are noob to recover your phone you can try some services like this
i revived my HTC one by them
http://goo.gl/1DMXlq
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
A while earlier I was trying to enable tethering on my at&t N6 by editing the build.prop and after the reboot it's stuck in a boot loop. I don't imagine that this is important but it doesn't get to the dots animation; just white Google and the unlock at the bottom. I am still able to get into fastboot and recovery (stock one). I have a backup of the correct build.prop in the /system file named build.prop.back , so I'm hoping that there's a way to revert to that without needing to wipe my device again, but I'm not sure.
I found this thread, however my computer isn't recognizing the device when it's in recovery mode. I have the fastboot drivers installed (needed to root), so that may be why but, again, I'm not sure. the adb devices command shows that there is no device, I imagine because the driver is not installed.
any help would be appreciated. thanks in advance.
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
jj14 said:
Try the ADB & Fastboot installer from this thread - http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Unfortunately that didn't fix the problem.
Do you know if the fastboot driver and recovery driver would be different? As far as I can tell from my research, I think they're the same, but I could be wrong. Hopefully that's the problem and you can direct me towards the correct driver.
If I select "show hidden devices" in the device manager, it shows the phone as ADB Interface, and I tried undating the driver for that but it said it was already up to date. not sure what to do from here.
Thanks for your help.
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
jawmail said:
Install working drivers if you can. This is important on so many levels. If they are installed correctly you type ADB devices, you should see your device. If you do type adb reboot bootloader, it should reboot to bootloader. Type fastboot devices, you should see same device name. Pat self on back.
Once that is all good I'd install the latest TWRP img file for your whale, straight off TWRP website (do you know how to do this? fastboot flash recovery recovery/name.img) . Once you do that go to your new recovery by pushing vol-down twice then your power button, inside TWRP you mount system and go into the file manager inside TWRP and swap/rename build.prop files. At this point, please make a backup inside TWRP. This backup will be on your internal memory, also save a copy to your computer in case you accidentally reformat your internal memory like every noob that uses toolkits. Having a backup is very important when you are screwing around with your phone. Reboot and profit.
Click to expand...
Click to collapse
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
momo5732 said:
I though I had the working drivers... Whenever I boot into fastboot/ bootloader, I can do fastboot devices and the phone shows up, but for whatever reason adb devices returns an empty list everywhere. It's empty in fastboot and recovery and while the phone is stuck in it's bootloop...
I'm fairly confident I can flash TWRP without any problems. I had an old galxy tab 2 that i flashed cyanogen onto a while ago, however i used clockwork for that recovery. I don't imagine it would be too much different though.
edit: also might be worth noting that I'm using a windows 8.1 computer for this. not sure if it matters or not, but it might be useful
Click to expand...
Click to collapse
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
jawmail said:
You are ok w/ your problem because you can get to fastboot screen. Don'y worry about adb drivers for now. Do what I said in my earlier post in the 2nd paragraph, start w/ installing TWRP img then do the rest and it will work for you. Win 8.1 seems to have its difficulties but we'll worry about that later after you get TWRP installled.
Click to expand...
Click to collapse
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
momo5732 said:
OK. twrp is making a backup as I type. is this backup the same thing as a nandroid backup? i hadnt heard of them before I decided to root.
It should boot properly now. I'll update when it's done.
Edit: IT BOOTS! thank you so much.
Edit 2: So I'm not really sure why it works now but adb recognizes it when its in twrp... odd. I tried to reinstall the drivers with the most recent version i could find, but it didn't look like it actually updated anything. maybe stock recovery was just broken? I'm not sure...
Click to expand...
Click to collapse
Cool glad it's working. Yes backup=nandroid
It's cool now I've also noticed the computer recognizes phone in TWRP. You can drag and drop files onto the phone while it's in TWRP not just booted in android, couldn't do that before unless I'm wrong which is often. This is really cool as I always forget a file or two or its location on SD card.