I downloaded the Fresh 2.0d Rom and all essential pieces. Followed the download and install instructions. Got past the fresh "htc quietly brialliant" screen and it froze on the htc screen with shining letters. Then I wiped data, and dalvik-cache but it wouldn't let me wipe the sd card. It kept saying that I must wipe it via adb. I looked up the issue and downloaded Fresh Pre-kitchen 0.2 and clicked auto root but that didn't work. The link on the website for the add on for pre-kitchen is dead. I tried again to wipe and nothing.
*On a side note, yes I made two different backups before wiping and before flashing.
I'm thinking I may not be using Pre-kitchen properly or I'm missing something. Any help would be appreciated.
The Fresh Pre-Kitchen has been replaced well over a month ago with Fresh Kitchen. A link to it is in the CDMA Hero ROMs.
Well I rooted the phone through Fresh kitchen successfully but the wipe still didn't work. Am I missing a step? Is there something else besides just rooting that needs to be done in order to be able to wipe SD: ext? I'm still getting the same message saying to wipe ext via adb.
Also, is it okay to do a nandroid restore after I wipe?
Which recovery are you running? If it's Amon_ra's update to 1.6.2.
It says Build: RA-heroc-v1.6.2
anything? I'm poking around but still can't out the issue
I have never flashed a "Fresh" ROM before, but I would suggest reflash.
I tried flashing again and same thing happened. It just gets stuck on the htc screen after thinking or awhile. This feels like it should be easier lol
try this restore your nandroid and reboot it will take awhile since to cleared delvick then when its booted open a cmd prompt and cd to your sdk then type
Code:
adb shell
reboot recovery
I have found that when I get an error like that that if you use adb to boot into recovery that it will usealy work after that
i can't figure out how to get into the sdk. When i tried awhile ago it was c:\android-sdk or somethin but now since it's my f drive. do i just enter these commands from the f: ?
For anyone who hasn't yet and is in ADB ever.
It makes life a lot easier if you
"add a global path to the android SDK tools. Right-click My Computer > Properties, click on Advanced, then click on Environment Variables. Doubleclick on PATH, then at the end of the Variable value, add a semi colon ";" and then c:\AndroidSDK\tools" - this is ripped of from a post in the Eris threads.
This makes things easier instead of having to CD C:\AndroidSDK\Tools
ever time, you can now just type "adb" at any Prompt path.
and Windows recognizes it.
FINALLY!
I finally got it to work and didn't have to wipe the sd. It was because I kept doing a nandroid recover after the wipes. But now, it's asking me if i want to run /system/bin/sh as root:root. Not sure what to do there
Related
I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
keen28 said:
I've tried installing roms 4 times, and each time the same thing happens:
Boot into Clockwork
Wipe everything
install zip from sd card
choose the one i want
choose yes
then the only things it does :finding update package and opening update package, and then, BOOM, back to recovery, lasted only 1 second.
then i reboot system and nothing has changed. i am really confused and quite frustrated, can anyone help or give me some tips?
Click to expand...
Click to collapse
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
i'm assuming you followed the steps in this tutorial to get rooted? did everything go as it was supposed to?
also, make sure when booting into recovery that you are not plugged in via usb.
zervic said:
Are you sure you're actually rooted? When you say "wipe everything" does that include cache/dalvik cache? If you wiped everything then rebooting the system shouldn't give the result "nothing has changed". Have you checked the MD5 of the ROM zip against the MD5 that it should "be"? If you can, boot into the phone and install terminal emulator and type "su" and tell me what it says...
Click to expand...
Click to collapse
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
keen28 said:
Hah, yes, it is rooted. i put wipe everything to shorten the steps. I just installed terminal emulator, but when i typed "su" it just forms a new line with a #
am i doing something wrong now?
also, i realized that when i downloaded cm7, my computer (mac) unzipped the file, and then i rezipped before loading to sd card. if that doesn't make a difference then disregard this
Click to expand...
Click to collapse
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
zervic said:
Okay...well try downloading it straight to your SD card from your phone browser. Also, see post above yours regarding having your phone plugged into USB when you boot into clockwork. If you've been doing this with your phone plugged in, that is your problem right there.
Click to expand...
Click to collapse
Ok, so i am not plugged in when trying to do this, so thats not the problem. i downloaded CM7 to my sd card, and i followed the instructions to install it, and now it is stuck on Installing update... but its only been here for about a couple mins, so im not sure whether its frozen or it just takes a while to install.
Ok, so it finially loaded, and it said it was complete. but now, i reboot and it goes from the HTC screen to the android intro thing, where the blue android is riding on a skateboard, but it goes about 3/4 across the screen then freezes, and a few seconds later restarts, but keeps doing the same thing over and over again. what should i do now?
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
stone_ship said:
Sounds like you are trying to flash a CM7 nightly without formatting system. In addition to wiping data, cache partition, Dalvik, you should go into Partitions menu from Clockwork Recovery and choose format system.
That was a wrinkle that tripped up many including myself when trying out the CM7 nightlies. After you have CM7 running, you don't have to format system again. ie. you can flash a more recent nightly just by clearing both caches.
Click to expand...
Click to collapse
hah, yes, that was exactly the problem. i figured it out tho. thanks, but now with cm7 i don't have Market, and i can't sync my google account to my phone. any suggestions?
Yea download the gapps package for 2.3 and flash it just like you ddid the rom minus wiping data and caches. That's if you're on CM7. Check the development section
Sent from my Liberty using XDA App
OK, so I just got my Nexus S4G two days ago, and I'm ready to root. My phone out of the box has 2.3.4 on it.
I follow this tutorial: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ the link to which was provided by a good XDA'er. I get the bootloader unlocked and install CWR (recovery-clockwork-3.0.2.4-crespo.img) and that goes fine.
That's when things stop going fine.
First, I try to create a Nandroid backup, and that process seemingly completes fine until i note that the process says it couldn't mount /data. I don't worry about it.
So, I go to Mounts and Storage to prepare to push SuperUser.zip and I tell CWR to "Mount USB Storage" and I wait as directed, but the USB storage never mounts. I try mounting USB Storage and mounting /sdcard, neither of which work, so I can't push SuperUser.zip.
Figuring I did something wrong, I decide to restore from Nandroid, only to have CWR tell me that the MD5 checksum is incorrect and now I have no clean, base Nandroid to restore to.
Then I do some digging, and discover that there's a new CWR for the NS4G at Koush's site and I download the file (recovery-clockwork-3.1.0.0-crespo4g.img) from there, push it to my phone using fastboot's recovery command and start it up.
It doesn't work.
Clicking any of the options (like mounting partitions, or restarting/powering down the phone) causes the screen to go blank and just display the CWR logo in the middle of the screen. The only solution to get out of those loops is to pull battery and restart.
So, now, I'm wondering what to do.
I go back into fastboot, relock the bootloader and I now wait for a reliable root method to root a 2.3.4 NS4G on a Mac.
My questions are:
Where can I get a stock ROM to completely start over from scratch and even remove the recovery I've installed <-- found a base ROM here: http://forum.xda-developers.com/showthread.php?t=1078213
Is there a fully reliable way to root the NS4G on a Mac, and if so how? (I've looked at this thread: http://forum.xda-developers.com/showthread.php?t=878446 and it looks problematic as well).
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
herbthehammer said:
Look in the dev section, stickies at top, the one talking about ns4g cdma. You have the su zip already. Put the cwm 3024 img file in the same directory as fastboot. You won't use adb. Boot into bootloader and do the fastboot command to unlock. Phone is wiped. Boot into phone normally and log in with gmail. On the phone, mount the device as usb so you can just copy the su zip to the root of the sd card.unmount phone on the Mac side then the phone side. Boot phone into bootloader. Do the command to fastboot the cwm into the phone again. Once finished, choose recovery on bootloader. It will boot into cwm. Choose install zip from card. Choose pick zip. Install su. Reboot into normal phone. Download busybox and a file manager you like that can handle root. With file manager, go to /system/etc and look for the sh file mentioned in the guide and add .old to the end of the file. If su pops up asking for permissions then you know everything is working. Boot into bootloader again. Install cwm again then choose recovery again. Once in cwm do wipe of caches and factory reset and dalvik. Go back and do backup with nandroid. Boot into normal phone. Sign into google again. Update profile and prl them you should be set. Pretty much that's what I did and it worked the first time around.
Follow the Mac guide in the link
Click to expand...
Click to collapse
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
My first nandroid choked. After root and final recovery install, I cleared all the caches it was *****ing about the first time, went in normally to make sure everything was okay, then went back and nandroid and no errors the second time. I probably will just stay with rooted stock but I would not flash other stuff until the dust settles and many of the bugs are worked out of the roms and kernels before jumping in.
TonyArmstrong said:
I'm going to give your method a try. Thank you for your rapid response...
I see the subtle change you suggested: simply rebooting after unlocking and pushing recovery, and moving SU to the device via USB. Wish I'd thought of that.
(I'm still concerned about the Nandroid issue I reported. But I'll have to avoid any new ROMs for the time being, until I can get an answer for my Nandroid problem...)
Click to expand...
Click to collapse
If cwm mount won't work then boot into the phone normally and copy over the file like usual is the only other quick and easy way to do it that I could think of at the moment the snafu happened. Yeah the way I did it might not have been the most efficient way but it got me past the hurdle that cwm made quickly. In the end, the result is the same so no big deal.
I don't know if cwm backs up wimax keys so I did it manually. There's a post on how to do it, I don't know if it's in this section. It might be dev?
this morning was dead at work, so i decided to go ahead and tinker with my phone. i was on 1.8.3, rooted, and running gingerblur 4.5.
i followed the instructions for the bootloader and root, everything went smoothly updating to 2.3.4 at first, but it doesnt seem to hold root. superuser kept corrupting, then when i got that settled, CWM started hanging up, and now when i try to use that, i get an error saying the path is null. aaaand now superuser says my su binaries are out of date. anyone have any idea? i tried searching, but couldnt find anything relative to my problem...
EDIT: super user is jacked up again.. so basicly my phone wont hold root...
EDIT 2: my home key doesnt seem to do anything now either...
Sounds like you did a titanium backup restore on your phone? Try doing a factory reset and try re-rooting the rom you have and give it super user access. A factory reset should work.
Sent from my MB860 using XDA App
i didnt do a titanium backup... but i did just try a factory reset, and i think it bricked my phone... i have the little android guy standing next to the yellow triangle with an exclamation point... now what? lol
can you boot into fastboot or Android Recovery?
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
PParcells said:
yes. should i use android recovery, or reflash 2.3.4 or kenn's alien rom?
Click to expand...
Click to collapse
who's recovery/CWM are you currently using?
i had the latest of tenfars CWM, but like i said, it kept botching since root wouldnt stick
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Try booting into fastboot mode and trying the command: fastboot -w
Then: fastboot reboot
Does it boot up now? Still have some more stuff to tell you.. just wanted to see if that got the phone booted first.
PParcells said:
i seem to be able to access the CWM in android recovery mode though. should i try reflashing kenn's alien rom, or start from scratch with 2.3.4?
Click to expand...
Click to collapse
Yeah, but can you still put flashable .zip files on your phone, if you can't boot?
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
PParcells said:
it booted up just fine, as if the factory reset did nothing. all my apps and stuff are still there, root still isnt working, and neither is the CWM app in the app drawer. so im not sure if i should try re-rooting again, or what to do. this is weird, i never had any issues fiddling with gingerblur or any of that stuff...
Click to expand...
Click to collapse
Ok, here we go...
1) Check to see if you have file "install-recovery.sh" @ /system/etc. If you do, delete it.
2) Uninstall Tefnar's CWM you have installed.
3) Download RomRacer's CWM/Recovery, and install via fastboot, or install via ROM Manager via the instructions in my N00B Guide thread.
4) Once you have RomRacer's CWM installed, boot into CWM and wipe dalvik cache, cache partition and format data.
5) Flash Alien ROM (not theme, just ROM). - Make sure to put this on you phone before booting into CWM and clearing everything; want to flash immediately after clearing things listed in step 4.
6) Reboot and see what you have and if everything is working correctly...
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
PParcells said:
rom manager says i need root. which i dont have. i tried installing via fastboot, but couldnt figure it out. i cant remember if im supposed to use the command prompt, or rsdlite, rsdlite says the CWM zip isnt a valid compressed file...
Click to expand...
Click to collapse
Need to use command promt for fastboot... put RomRacer's CWM .img file in the same place as your fastboot files, and then type the commands in Rom Racer's OP, except if your using fastboot, you can ignore the "moto" part of the commands and just type fastboot ....
You need Romracer's fastboot file, which is on the left side... not the flashable .zip file which is for CWM.
you are my new favorite person in the whole wide world. its currently formatting, and i'll be sure to log on in the morning to post my results. but this is far enough for the night i think. im beat. thanks for ALLLL the help and patience!
Oh. I guess I should add this piece of advice since no one else has. Don't get bored at work and try flashing roms. You don't have recovery available or another rom available. I speak from experience.
I voided my warranty.
just wanted to say i have everything up and running. super fast, super smooth, and so far, no errors or issues. thanks alot guys!
Initially tried to 'fastboot flash' the steelhead CWM, but when trying to enter the bootloader at startup, I'd get nothing.
Moved on to just using 'fastboot boot steelhead.img'. Pushed the latest CM10 and gapps. Think I did a factory reset, and cleared dalvik cache, then installed the CM from sdcard. Seemed to install good, upon reboot, all I got was the Cyanogenmod logo and a fuzzy screen.
This is where I get careless.
Instead of instantly reverting to the nandroid I have, I pushed the Quantum Singularity files to the sdcard, factory reset, wipe cache, installed it from zip. No boot. Back into cwm, tried again, but this time I formatted something that I'm not sure of.
I can fastboot into the recovery, but it can't read the sdcard or mount it. Errors on the bottom are all related to 'Can't mount /cache/recovery/' as well as 'cant mount sdcard'.
If I run shell and then 'ls' it shows the sdcard directory, but won't let me do anything to it, keeps forcing me to /data/media/.
I tried OneClickRestore, but it loads the spinning orb on the screen and just sits there.
I have these files still but not sure what to do with them;
boot.img
cache.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
Tried to fastboot boot recovery.img, but it says its too large.
I will continue to try and straighten out my situation, but any kind words would be much appreciated to give me a shortcut.
EDIT
Found a way (I think) to scan the partitions. Still trying to understand, but I think I need to repartition the sdcard (block 13?) See attached pic.
HomeR365 said:
Initially tried to 'fastboot flash' the steelhead CWM, but when trying to enter the bootloader at startup, I'd get nothing.
Moved on to just using 'fastboot boot steelhead.img'. Pushed the latest CM10 and gapps. Think I did a factory reset, and cleared dalvik cache, then installed the CM from sdcard. Seemed to install good, upon reboot, all I got was the Cyanogenmod logo and a fuzzy screen.
This is where I get careless.
Instead of instantly reverting to the nandroid I have, I pushed the Quantum Singularity files to the sdcard, factory reset, wipe cache, installed it from zip. No boot. Back into cwm, tried again, but this time I formatted something that I'm not sure of.
I can fastboot into the recovery, but it can't read the sdcard or mount it. Errors on the bottom are all related to 'Can't mount /cache/recovery/' as well as 'cant mount sdcard'.
If I run shell and then 'ls' it shows the sdcard directory, but won't let me do anything to it, keeps forcing me to /data/media/.
I tried OneClickRestore, but it loads the spinning orb on the screen and just sits there.
I have these files still but not sure what to do with them;
boot.img
cache.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
Tried to fastboot boot recovery.img, but it says its too large.
I will continue to try and straighten out my situation, but any kind words would be much appreciated to give me a shortcut.
EDIT
Found a way (I think) to scan the partitions. Still trying to understand, but I think I need to repartition the sdcard (block 13?) See attached pic.
Click to expand...
Click to collapse
Interestingly that fuzzy thing appears to be the cyanogen logo still, just without horizontal sync. Maybe your tv though it was some form of progressive scan? You have the stuff to flash directly to the processor? omapflash?
animal24 said:
Interestingly that fuzzy thing appears to be the cyanogen logo still, just without horizontal sync. Maybe your tv though it was some form of progressive scan? You have the stuff to flash directly to the processor? omapflash?
Click to expand...
Click to collapse
Thanks for your reply. You may be right about the progressive scanning, although I never had any issues before. As for the OMAP thing, I don't think I'm that deep into it yet. I still can access the bootloader, and some what function. I think I can reset the partitions straight from ADB.
I still have these Nandroid backup files that I'm sure could help out, but i think I will need to flash them with Odin, just not sure how.
http://omappedia.org/wiki/Omapboot
Found this when searching for how to create a partition on an omap
animal24 said:
http://omappedia.org/wiki/Omapboot
Found this when searching for how to create a partition on an omap
Click to expand...
Click to collapse
if you use ./flash-all.sh it will recreate your partitions from scratch, I just did that to my Q. I think the latest CM10.1 nightlies are not booting properly, I've already tried 3 nightlies and none works. flash-all will return your Q to working order as long as you have access to fastboot.
https://developers.google.com/android/nexus/images#tungsten
trschober said:
if you use ./flash-all.sh it will recreate your partitions from scratch, I just did that to my Q. I think the latest CM10.1 nightlies are not booting properly, I've already tried 3 nightlies and none works. flash-all will return your Q to working order as long as you have access to fastboot.
https://developers.google.com/android/nexus/images#tungsten
Click to expand...
Click to collapse
Ok thanks, I seem to have somewhat recovered back to stock. Manually flashed all those files through fastboot one at a time worked the best.
The battle continues, when I try to do a backup in CWM, I get 'SD Card Space Free 15MB' to which it tries to backup then fails.
The battle continues!
updated adb incase anyone needs it
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
HellaBester said:
Hey guys, I was running 4.3.x for a while with the loki twrp solution and all was well, after many attempts to flash 4.4 I finally decided to ditch twrp and go to CWM, that went without a hitch and brought me into the latest nightly of CM, yet I wanted a fresh install (No accounts, no pictures media etc etc) so I tried to do factory reset from within the OS and it wouldn't let me. so I then went into recovery and tried to format things from there...
Since then I have been unable to get past the spinning CyanogenMod boot screen and though adb sees there is a device, it is telling me it is "unauthorized". Of course since I can't get into the OS the RSA confirmation thing can't come up and I can't select any system preferences. Before I went messing around in recovery formatting things ADB was working flawlessly.
Any ideas on where to go from here?
Thanks guys,
Lokin
Click to expand...
Click to collapse
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
osugsxr said:
I had an issue with my adb, it was out dated. I updated the sdk system, and it detected the lg g2, this could possibly help you.
Click to expand...
Click to collapse
Yeah I considered that but no everything is up to date. It seems more like the RSA auth fingerprint is not being recognized. Plus it does recognize the phone, it just tells me it is unauthorized.
Get back into Recovery mode and use ADB from there
votinh said:
Get back into Recovery mode and use ADB from there
Click to expand...
Click to collapse
How do I get into recovery without being able to "adb reboot recovery"?
unomicu how
Bump. Anything guys? Really struggling here....
Can you get in recovery using button combination?
votinh said:
Can you get in recovery using button combination?
Click to expand...
Click to collapse
Nope, doesn't seem like it. Though I can get into download mode no problem.
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
HellaBester said:
Alright guys, since it seems like not many people out there know whats going on with me I'll dow what i can to keep an update.
Finally got back into Recovery using this super convenient little trick I did not know existed.
Though now I am unable to mount anything at all from recovery "E:Can't mount /cache.. etc"
Click to expand...
Click to collapse
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
super114 said:
I've never been able to mount anything using the recovery. Not sure if it because of the LG phone or of my recovery. But I've tried different ones (CWM, TWRP, Philz Touch), none was able to mount my phone from recovery. Your best bet right now is to flash the files from a OTG cable and flash drive. Also when you said you formatted the phone from the recovery, did you format the system partition as well? TWRP has that option so I assume CWM has it as well
Click to expand...
Click to collapse
Heyoo, just in the last hour or so I've got it all fixed!
I did a full system, data and cache format om CWM after that there was no OS or amnything of the sort, then I was able to mount the SD and adb push cm11 + gapps-kk to the sdcard, I flashed those two zips restarted, failed, then i did a system reset (resets everything but the OS) and I popped out in CM11 with a perfectly fresh install. got all that setup and am golden now ::
Congratz
Check the .android folder
My problem started when I tried to connect another phone which happened to be the same type of phone as the previous one. Not sure if that's actually related, but my working hypothesis is that ADB gets confused in this scenario. I tried everything listed here and in many other places, and nothing seemed to work. Finally, I did this:
1. Rename .android folder in your user directory (~/username/.android on Mac OSX) to .android_bak (for safe keeping).
2. Restart the adb daemon: "adb kill-server" followed by "adb start-server"
After that, I got the authentication confirmation on the phone (don't forget that part, of course) and all was well.
These steps merely recreate the .android folder and get rid of any authentication credentials you already have. Note of course that this will impact all other phones you may be connecting.