I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Keuka79 said:
I am on vacation and my fassy decided to stay in recovery upon boot. It gets stuck in boot loop. I'm running AOKP Build 30 w/ Glitch. My fiance has a macbook with her however, everything I've read says that we can't use Mac for rooting or restoring fassy's. Is there anyway to get out of the boot loop with an option in clockwork. From what I understand we can't use the two button hard boot with ICS roms. I could use some help, I'd rather not be without my phone for a week.
Thanks guys
Click to expand...
Click to collapse
Is there anyway to access a Windows computer? With Parallels, VMWare, a virtual computer lab, or something else?
If so, follow http://forum.xda-developers.com/showthread.php?t=1238070
If no, Hiemdall http://www.glassechidna.com.au/products/heimdall/
Goodluck
Apparently there's no driver for samsung fascinate with mac connectivity. I downloaded Heimall and the full tar package but didn't work. Does anyone know how to generically attatch my phone to the computer. Someone said something about a generic connection as a drive that works with heimall. I'm pretty pissed and can't seem to get this work. I'll pry end up just going down to a lab and hogging that for thirty minutes or so.
Heimdall has its own driver. It'll be in the driver folder in the suite. Also I'd use an older version of heimdall suite if you can. The newer version tried to streamline things but ended up being a downgrade IMO.
Sent from my SCH-I500 using xda premium
I tried to use Heimdall but couldn't locate the driver. I then located a "exitrecovery.zip" that was supposed to be flashed in cwm. I used my gf's phone to download it then switched sd cards and that didn't work. Still stuck in cwm loop. I can't get to a pc where i can download Odin software to. There's no other flashable file i can find to help me get out of this loop.
look at section 9 of my guide...I always keep a cm7 rom on my sd card just incase this happens!
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Keuka79 said:
Can I flash a cm7 rom if i'm stuck on a cm9 bootloop??
Click to expand...
Click to collapse
READ section 9 of my guide in the general section...
droidstyle said:
READ section 9 of my guide in the general section...
Click to expand...
Click to collapse
Thanks man, I got it to work. I'm surprised I didn't think of that before.
You're a life saver man.
No problem, glad to see you got things back up and running!!
Related
Well my good friend just bricked his Fascinate trying to go to the newest glitch kernel for ICS. It has been handed to me for fixing like many times before . This time though i don't think i can quite fix it. So the phone will automatically boot into ICS Recovery(5.5.0.4).
Here is what I have tried thus far from Recovery:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
This yields no results the phone just boots back into recovery. With that in mind I have/had tried this:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
Install teamhacksung_fascinatemtd-ota-eng.BUILD6.1
This too yields NO results. The phone again boots back into recovery. Actually it didn't boot straight into recovery I had to play with it for a bit.So the logical thing to do from here would be too boot into download mode and go from there either via Heimdall or Odin. Unfortunately neither are doing anything. The phone doesn't get recognized in either program. "Maybe it is your cable or your computer" I wish that were so but when hooking up my Fascinate no issues with either program. I have tried DaleV's methods for both programs and nothing. I have even tried getting the phone into download mode via the charging plug to see if there was any difference with that and no. I don't want to say it but i think the phone is completely BRICKED. So if any of you good forums members have any advice it would be greatly appreciate it.
Aali1011 said:
Well my good friend just bricked his Fascinate trying to go to the newest glitch kernel for ICS. It has been handed to me for fixing like many times before . This time though i don't think i can quite fix it. So the phone will automatically boot into ICS Recovery(5.5.0.4).
Here is what I have tried thus far from Recovery:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
This yields no results the phone just boots back into recovery. With that in mind I have/had tried this:
Wipe Cache Partition(Check)
Wipe Dalvik Cache(Check)
Wipe Data Factory Reset(Check)
Install teamhacksung_fascinatemtd-ota-eng.BUILD6.1
This too yields NO results. The phone again boots back into recovery. Actually it didn't boot straight into recovery I had to play with it for a bit.So the logical thing to do from here would be too boot into download mode and go from there either via Heimdall or Odin. Unfortunately neither are doing anything. The phone doesn't get recognized in either program. "Maybe it is your cable or your computer" I wish that were so but when hooking up my Fascinate no issues with either program. I have tried DaleV's methods for both programs and nothing. I have even tried getting the phone into download mode via the charging plug to see if there was any difference with that and no. I don't want to say it but i think the phone is completely BRICKED. So if any of you good forums members have any advice it would be greatly appreciate it.
Click to expand...
Click to collapse
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
mkuehl06 said:
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
3 fingering into recovery CAUSES a bootloop like the OP is describing.
He can try it out, but I'd be surprised if it did anything but bootloop. If I'm reading his post right, he can get into download mode, but the device won't be recognized by the computer? I'd recommend odin and starting fresh, but if the devices isn't being recognized then I don't know. Maybe look into getting/making yourself a jig? Although I thought those were more useful for getting INTO download mode..
I'm not sure, even though you said you can plug your phone in and it'll work, I'd just be trying different ports/cables and crossing my fingers
mkuehl06 said:
I had this problem yesterday too. You have to flash build 1 not 2 then flash 6.1 again. It worked for me. Flashing 1 might give you an endless boot loop with your animation, but that's normal. Just pull battery and 3 finger into recovery and flash 6.1
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
NO DICE. The phone is pretty fudged from what it looks like. I tried to install Build 2 but just the same thing. It boots into recovery and nothing.
k_nivesout said:
3 fingering into recovery CAUSES a bootloop like the OP is describing.
He can try it out, but I'd be surprised if it did anything but bootloop. If I'm reading his post right, he can get into download mode, but the device won't be recognized by the computer? I'd recommend odin and starting fresh, but if the devices isn't being recognized then I don't know. Maybe look into getting/making yourself a jig? Although I thought those were more useful for getting INTO download mode..
I'm not sure, even though you said you can plug your phone in and it'll work, I'd just be trying different ports/cables and crossing my fingers
Click to expand...
Click to collapse
Yup went ahead and tried doing that as well. No other combination of cables does anything. So i believe the consensus here is.....Bricked Not cool but the upgrade deal that best buy is offering makes the Galaxy Nexus all that much more tempting.
I'm wondering how he got it bricked in the first place? If he flashed the correct kernel for his device I don't see how that could happen. Did he flash the wrong kernel for his device? If he did, maybe the you would need the drivers for that phone? Just kinda thinking out loud, that's pure speculation. Did he flash the kernel and then mess with overclocking or anything?
One other thing I've heard of that you might look into is the "unbrickable mod", but as I understand it, it's done at the hardware level so if you're not fairly comfortable with the idea of taking your phone apart I don't know if that would be an option.
Is it possible to flash CWM through ICS Recovery, then say ..stock rom, check if computer can pickup the phone and go from there??
k_nivesout said:
I'm wondering how he got it bricked in the first place? If he flashed the correct kernel for his device I don't see how that could happen. Did he flash the wrong kernel for his device? If he did, maybe the you would need the drivers for that phone? Just kinda thinking out loud, that's pure speculation. Did he flash the kernel and then mess with overclocking or anything?
One other thing I've heard of that you might look into is the "unbrickable mod", but as I understand it, it's done at the hardware level so if you're not fairly comfortable with the idea of taking your phone apart I don't know if that would be an option.
Click to expand...
Click to collapse
My apologies i forgot to mention that. The funny thing is when we first got our phones he bricked his by setting setCPU all the way up LMAO. So i think this was the time of superclean on eclair so we didn't even have any over clock kernels or anything of that nature. This time around he tried doing the same idk what method though. He tried going to 1.4ghz but i don't believe that he properly messed with the multiplier or voltages.Unbrickable mod would be awesome but it would have had to have happened before this instance i believe. Even at that though given the situation i don't think it would have helped.
Hyper_Warp said:
Is it possible to flash CWM through ICS Recovery, then say ..stock rom, check if computer can pickup the phone and go from there??
Click to expand...
Click to collapse
This seems like a good idea but just speaking to him a couple minutes ago he phone is no longer going into recovery either. If it was it may have been worth a shot but I doubt it would have done anything. I think due to his tinkering he has had a hardware failure at this point.
Ah, that makes sense, and yes I'd say you're right about the unbrickable mod. Not sure that it would've been able to help in this case where the hardware was pushed beyond its limits. Just because you have the option to max out the OC settings doesn't mean it's something you should do, lol! He might have been better off with the stock ICS kernel (which doesn't include the ability to OC).
I'm sad to hear this. I've been searching the Internet for people with the same issue. The same thing happened to mine except I have a captivate. I flashed the new ICY Glitch kernel from CWM and my phone buttons immediately went hay-wire, where all buttons performed the "back" function. So I pulled the battery and rebooted to find only a bootloop. The button recoveries nor download modes will work, so I used my jig I made to get into download mode, and just as you said no computers nor odin will recognize the device. Nothing, nada. Although it will charge the phone as it will show the big battery icon charging.. go figure. I wonder if the Glitch guys know about this yet. I would post but I'm still a noob so don't have enough posts or whatever you have to have.
jnthnmc01 said:
I'm sad to hear this. I've been searching the Internet for people with the same issue. The same thing happened to mine except I have a captivate. I flashed the new ICY Glitch kernel from CWM and my phone buttons immediately went hay-wire, where all buttons performed the "back" function. So I pulled the battery and rebooted to find only a bootloop. The button recoveries nor download modes will work, so I used my jig I made to get into download mode, and just as you said no computers nor odin will recognize the device. Nothing, nada. Although it will charge the phone as it will show the big battery icon charging.. go figure. I wonder if the Glitch guys know about this yet. I would post but I'm still a noob so don't have enough posts or whatever you have to have.
Click to expand...
Click to collapse
First, if you're on a captivate, then you could probably be better helped in those forums.
Second, can you not use the volume and power buttons to navigate in recovery?
Believe me ive checked those forums, that is why I am here, looking for any glimmer of hope. No the button recoveries wont work, ive tried a zillion times a zillion different ways.
Sent from my SGH-I897 using xda premium
Help for the love of god
Did you find a fix for this? Because I also have a fascinate that will go into download mode but not the boot mode, it was a completely stock phone and will not be recognized by Odin, help if you can please
Check out #9 in http://forum.xda-developers.com/showthread.php?t=1238070
hello everyone, Im new here...I dont have enough posts to post in the dev section apparently..lol but I have been following the dev pages for a while now...so anyways Im having this issue with getting cm9 to flash properly on my phone. cm7.2 works great and I can go back to that if i have any problems so my phones not bricked or anything, but i cant get cm9 to boot at all, i tried both beta and alpha builds and it just stays on the red Motorola logo boot screen indefinitly.. my phone is unlocked and i do have CWM installed on it, however i did a update on ROM Manager that updated cwm to 5.0.2.8 and i read a post recently saying it doesn't work right with the photon but i guess i got it to install just fine...so is that the reason im having a issue getting cm9 to flash right? cm7.2 flashes just fine with 5.0.2.8.. i did follow the right procedure to install the rom aka.. format system wipe cache and user data etc etc and i also followed qbkings video on how to flash the rom but still no luck on getting ics on this phone id appreciate it if anybody can help me get this to work thanks..
edit: also i noticed the phone now wont detect if im using ether the wall or usb to charge the phone, I do have a battery charger and 4 batteries that plugs into the wall? but what the...? lol is there a quick fix for this?
Been posted quite a bit, you can't use the newest version of CWM to flash CM9/ICS. Have to use 5.0.2.7. Search the dev section, the answer is in there.
Edit: Here's the thread with the info/file you'll need to flash to revive your phone.
forum.xda-developers.com/showpost.php?p=16654262&postcount=1
Sent from my 1.3 OC'd CM7.2 Electrify.
ah okay, noob mistake :rolleyes lol i had a feeling it was something to do with that thanks for the reply
edit: thanks it works fine now... this thread can be deleted
Asylumownz said:
edit: also i noticed the phone now wont detect if im using ether the wall or usb to charge the phone, I do have a battery charger and 4 batteries that plugs into the wall? but what the...? lol is there a quick fix for this?
Click to expand...
Click to collapse
I dont know about the other part, but I had a similar issue ATTEMPTING to flash and CWM was jacked up. RSDLite would not connect. I downloaded latest drivers to my desktop from Motorola and it connected right away!
Hope that helps!
dsims7_2000 said:
I dont know about the other part, but I had a similar issue ATTEMPTING to flash and CWM was jacked up. RSDLite would not connect. I downloaded latest drivers to my desktop from Motorola and it connected right away!
Hope that helps!
Click to expand...
Click to collapse
well idk if this helps at all but i just switched to another one of my batteries after it charged and now it detects it charging and everything...strange ... XD lolz
I had same prob. Flashed to 5.0.2.8 and had to go back to 5.0.2.7 before I could try to install CM9. But I did and it is up and running and working great.
Hi,
I want to try install the new Cyanogenmod on my Tab, read a bit about it, and tried last night to get it going. many different forums and steps were tried... none worked? Thing is, I read a lot of terms and stuff, but I'm not sure what they all mean.
My route took me through Android SDK's for drivers, Samsung drivers with escape??? no clue what that was?? Nvidia drivers? Then tried to use a program called Clockworkmod? Confusing, especially since nothing seemed to actually do anything?
What is it that I need to do exactly?
What i can say is that when I boot my Tab up, there is an unlocked padlock at the bottom of the screen.
I have the latest Cyanogenmod for my Tab "p3" downloaded, as well as the Google Apps.
Cheers
Weevil Kneevil said:
Hi,
I want to try install the new Cyanogenmod on my Tab, read a bit about it, and tried last night to get it going. many different forums and steps were tried... none worked? Thing is, I read a lot of terms and stuff, but I'm not sure what they all mean.
My route took me through Android SDK's for drivers, Samsung drivers with escape??? no clue what that was?? Nvidia drivers? Then tried to use a program called Clockworkmod? Confusing, especially since nothing seemed to actually do anything?
What is it that I need to do exactly?
What i can say is that when I boot my Tab up, there is an unlocked padlock at the bottom of the screen.
I have the latest Cyanogenmod for my Tab "p3" downloaded, as well as the Google Apps.
Cheers
Click to expand...
Click to collapse
You need to use Odin to flash Clockworkmod recovery onto your tablet.
Then you need to download the p4wifi (if yours is wifi) edition of CM9
Then boot clockworkmod recovery and flash CM9 and then Google Apps
ok, but with more in depth steps please, i got a better idea now though!! thanks
Weevil Kneevil said:
ok, but with more in depth steps please, i got a better idea now though!! thanks
Click to expand...
Click to collapse
Root http://www.androidauthority.com/galaxy-tab-10-1-root-clockworkmod-recovery-50799/ (stop after step 12.)
CM9 Flashable Zip http://download.cyanogenmod.com/get/jenkins/4709/cm-9-20120720-NIGHTLY-p4wifi.zip
Get into recovery mode, go to install zip from SD, select the zip /\ hit yes. Reboot.
Ok, no joy,
What I seem to have:
A working fastboot, fastboot devices does list my device. And when I try flash something via Odin, my Tab says "flashing mbr to device" so my action on my pc does initiate something on the tab. yet it stops there, at the flashing mbr to device screen. It does not start the recovery img.
A working adb, adb reboot recovery does reboot my tablet, but it still does not boot into recovery. It has a android sign, with a yellow exlamation mark over it.
I've tried to flash skitzandroid, clockworkmod, and the tabrooteasy one. I just cant seem to get this thing rooted?
Is there something I'm missing?
I do have an unlocked padlock on my screen when i boot it up.
He has a p7100 why are you guys sending him to flash p4wifi Wtf!
Dude go to 10.1v development section and read cm9 thread you will find everything you need there
Sent from my GT-N7000 using xda premium
msedek said:
He has a p7100 why are you guys sending him to flash p4wifi Wtf!
Click to expand...
Click to collapse
I had a good laugh about that one too But hey, all the clues I got, got me on the right trail!
I got it sorted! Thanks for the help guys!!
Cheers!
After downloading this rom and thinking everything would be just fine when moving to CM7 on my brother's rooted Photon, I come to a boot loop! I tried to use RSDLite to flash a SBF over to the phone, it fails, I try to use Android' Recovery to flash a new rom, fails, and then I try to factory reset and wipe the phone, FAILS! I have no clue what to do here.
I am so used to my Sensation 4G and everything is so much simpler on it, but I have no clue what I am doing with this Photon. Can someone please point me in the right direction of what I need to do? I need some real answers! I've tried tons of guides here on the forums but nothing seems to work!
Normally I could use CWM to fix it all up, but I never could find it for this phone!
Help!
bump. Please, need help.
ClipTy said:
After downloading this rom and thinking everything would be just fine when moving to CM7 on my brother's rooted Photon, I come to a boot loop! I tried to use RSDLite to flash a SBF over to the phone, it fails, I try to use Android' Recovery to flash a new rom, fails, and then I try to factory reset and wipe the phone, FAILS! I have no clue what to do here.
I am so used to my Sensation 4G and everything is so much simpler on it, but I have no clue what I am doing with this Photon. Can someone please point me in the right direction of what I need to do? I need some real answers! I've tried tons of guides here on the forums but nothing seems to work!
Normally I could use CWM to fix it all up, but I never could find it for this phone!
Help!
Click to expand...
Click to collapse
if you dont have cwm installed, i assume that you flashed that rom while in bootstrap recovery because you didnt state that the phones bootloader was unlocked.That particular rom is an unlocked only rom, which is why you're stuck in that loop. If I'm right and you flashed that rom via bootstrap, you should be able to get back into it by powering down the phone, holding power and volume down, then using the volume down key to cycle through the options until you hit 'android recovery', then press volume up to boot into it.
At that point, go to mounts and storage, mount usb storage while phone is plugged into your pc, and place this rom:
http://forum.xda-developers.com/showthread.php?t=1648297
On your sd card. After this, go back into mounts and storage and wipe data, system, and cache. Flash the rom you just placed onto your sd card and reboot.
Again, this is all asuming you installed bootstrap recovery, if I'm wrong let me know and ill try to help you further.
I forgot to add, you're also going to need to download a stock blur kernel and place that on your sd card aswell, flashing it after you flash the rom. I can't remember where to find the stock blur kernel but give me a second and ill try to find it for ya.
I don't find that very professional. I think the best you can do is tell me which section it belongs in. At least Acvice offered help...
Thanks you so much! I knew I would have to flash the stock stuff, but I just couldn't find it! Yes, I used bootstrap as I thought it was the only means of getting into cwm. I wont be screwing around after this. Only problem is, the phone is dead! I need to charge it again lol. Thanks for helping. Ill let you know the outcome later.
Acvice said:
*snip*
Click to expand...
Click to collapse
So I am downloading that rom you gave me, seems like a good one, now I am just waiting on the Kernel, have you found it yet? Oh, and I couldn't mount my phone through recovery, so I just took the SD card out and did it myself.
EDIT: I tried to install the rom, I got an E: signature verification failed and the installation aborted. I've also tried this with other roms before. What is making this happen?
ClipTy said:
So I am downloading that rom you gave me, seems like a good one, now I am just waiting on the Kernel, have you found it yet? Oh, and I couldn't mount my phone through recovery, so I just took the SD card out and did it myself.
EDIT: I tried to install the rom, I got an E: signature verification failed and the installation aborted. I've also tried this with other roms before. What is making this happen?
Click to expand...
Click to collapse
Meh, you just flashed something you shouldnt have is all. It honestly happens to all of us. You learn the most by screwing up your phone haha.. Figured i would have you try that method as it would have gotten you a nice fast rom and also fixed your problem. But it looks like youre just unlucky. Were just gonna have to get ya back on stock by flashing an SBF.
1) Download the Windows Moto drivers and install them. Make sure you choose 32bit or 64bit, respectively. (quick google search)
2) Download RSD Lite (quick google search)
3) Download the SBF located here and unzip it.
Use this video to guide you through. Some of his links are outdated which is why i linked the one above. If you are used to ODIN on Samsung devices, you'll probably already know what to do as it's the same kind of program. Good luck. Let me know how it goes.
I've tried RSDLite with an Sbf before, it never succeeded.
Sent from my HTC Sensation using xda app-developers app
Is it possible to flash an sbf with a low battery? If not, how can I charge this thing?
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
neonblur said:
I am ready to break something!!!
OK, after spending over a day reading and trying different things to no avail, my brain is a jumbled mess
i have a 16gb NT it was updated to the 1.4.3 when i started. I rooted it using indirect/brianf21 sd card method. everything worked fine for the little bit that i messed with it in this state. i then moved on to Veronica's CM7beta_ribbon_ICS rom for the most part everything was working. I installed a few apps from the market and on a reboot i got stuck in a bootloop. powered off, bootloop again. so i booted into CWM and tried reflashing the ROM only to be met with the 'please restart you device' screen. its all downhill from there. i can currently boot into CWM internally and have tried many different methods. so right now i dont get the 'restart' screen as it just goes into CWM. I have never worked with ABD but have been fighting drivers trying to get my nook to show up and having no luck so that i might try something there. i am new to rooting on the NT but have rooted and flashed different roms to my phone so i feel i have a basic concept. i dont know if im having so much of an issue cuz of the 1.4.3 or what **sigh**
I am now defeated and am in need of some help!!! haha! if anyone has anything to offer i would be so very thankful!
Click to expand...
Click to collapse
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
in order to get drivers working while in recocery mode you need to find the product id of the nook while its in cwm. in windows you need to go to device manager and check to see if your nook shows up in "other devices". then right click and go to properties and go to the tab that relates to hardware and find the neccessary info.
after that you should see two lines. ypu need to copy those two to the android_win.inf and modify the lines in there with notepad or something.
then try installing drivers and it shouls pick it up
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
neonblur said:
thanks for the reply. ok my nook is showing up as a mass storage device under other devices but is also showing up under android phone as 'android composite ADB interface' and also under portable devices as 2 drives G: and H: both unclickable. when i right click the android phone i get a hardware tab but all i see there is device functions and device functions summery so im not sure of the info that you are referring to that i need. i have been at this all day and apologize if i am missing something because im tired haha. the other file i found was called android_winusb.inf, is this the right one? thanks again for your help!
Click to expand...
Click to collapse
yea that inf file is the one you need to modify. but you already have adb composite interface... so that means drivers are installed.
what happens when you do adb devices after you get into cwm. what's the output?
Sent from my Nook Tablet CM7 BETA using xda premium app
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
neonblur said:
this is where i am a complete noob. i have never used ADB and have been reading threads about people using it but the light bulb has just not gone off yet. i know how to get to the command prompt, heh, so that is one thing. what program do i need to install, is it the android SDK? thanks for your quick reply, i am generally a quick learner when it comes to this stuff just need to get over the ADB hurdle
Click to expand...
Click to collapse
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
ShinnAsuka said:
did you download the drivers and adb zip from one of the threads? that archive should have all you need for adb. after extractng you need to navigate to the extracted folder and do adb devices.
try looking in thr general section for these drivers I was talking about.
there should be a thread by lavero burgos in there.
Sent from my Nook Tablet CM7 BETA using xda premium app
Click to expand...
Click to collapse
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
neonblur said:
Ha! got it going...ok so when i entered ADB devices it gives me:
2015170003944006 recovery
im feeling better about maybe getting this unbricked
Click to expand...
Click to collapse
ok well now you have adb working. now the problem is how to fix your problem lol... I'll see if I can think of something.
in the meantime can you go into detail as to how you got tto your current situation?
EDIT: do you get any errors when booting into cwm? like not being able to mount a certain drive or something?
Sent from my Nook Tablet CM7 BETA using xda premium app
no errors booting into cwm internal and never had a problem when booting into it from an sd card. i flashed it internally hoping it would be a little easier seeing as how i only have one sd card but i am going to go get another today just to work through this.
nook started on 1.4.3 i rooted it using brianf23 and indirects sd card method. market and everything worked great. so i flashed Veronica's CM7beta_ribbon_ICS rom. everything for the most part was working, tho i did notice that some menu items would not open for me but they were noting i really needed to mess with at the time. so i installed a few apps and was done for the day. turned it on the next day and got stuck in a bootloop, so powered off and rebooted but got the same bootloop. booted into recovery did the standard dalvik cache ect and reflashed the rom, hoping this might fix the loop. upon rebooting is when i got stuck at the 'please reboot your device' screen. i have tried several methods of just flashing to stock ect, formatted my sd correctly and made sure it was active to try and flash back to stock that way but my nook will not boot from sd. so 12+ hours later i hung my head and asked for help lol! thanks to you i am able to start ADB no clue what to do but hey....step in the right direction!
Happy Dance
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
neonblur said:
i got it working back to stock!! thank you so much for getting me going with ADB, without your help i would have stayed lost. i used kring789's ADB instructions and *poof* it rebooted to stock :good::good: thanks again for your help!
Click to expand...
Click to collapse
good job on the fix. glad to help
Sent from my Nook Tablet CM7 BETA using xda premium app