This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
Hi,
I could really use help with my Novo 7 basic. I recently upgraded from honeycomb to Ainol's ICS version. I accomplished this using the normal flash method with the update.zip file copied to my 16G Mini SD. After the Rom update I installed several programs using ADB shell. I was having difficulty getting titanium backup to work and decided to upgrade my Rom to 4.0.3. I used the same method to flash my device with the update.zip file on my SD card. After the power up I get the android robot then the reboot but there is no change to the version of my Rom. I did a factory reset to my device. After the reset my device no longer had any of my previous installed apps but the version indicated in the settings is still 4.0.1. I have even attempted to flash back to honeycomb but no change occurs to my device. I then try to flash using CWM but I cannot get it to install on my device. Any help or suggestions will be greatly appreciated
thanks
roniinn said:
I could really use help with my Novo 7 basic. I recently upgraded from honeycomb to Ainol's ICS version. I accomplished this using the normal flash method with the update.zip file copied to my 16G Mini SD. After the Rom update I installed several programs using ADB shell. I was having difficulty getting titanium backup to work and decided to upgrade my Rom to 4.0.3. I used the same method to flash my device with the update.zip file on my SD card. After the power up I get the android robot then the reboot but there is no change to the version of my Rom. I did a factory reset to my device. After the reset my device no longer had any of my previous installed apps but the version indicated in the settings is still 4.0.1. I have even attempted to flash back to honeycomb but no change occurs to my device. I then try to flash using CWM but I cannot get it to install on my device.
Click to expand...
Click to collapse
Sorry for being a tad late...
Please, don't use CWM. It's a nice piece of the software, but version for Novo7 Basic/Paladin is buggy and you have a good chance to mess up your device.
If you push "menu" button (three lines) next to the screen during update, you'll get to see some messages, and this might give you a clue what's wrong.
Most probably you've got broken update file and the update process aborts right after verifying the signature. Redownload the file and/or check MD5 sum.
If nothing else helps, please, try another SD card, Novo7 tablets are quite picky about them.
Hey there everybody, tried to find a solution all day long for my problem, but wasn't successful jet.
Brought uk version of ics on my tab (using P7510XXLPH) without any problems. I came from cm9 with cwm 5.5.0.4, because of the rolling recovery issue i flashed a different bootloader using isimobile's method.
To get ics working i flashed Stock HC, wiped cache and made a factory reset, both 3x. Finally flashed UK 7510 Version (everything with odin 1.85). Works great now, better then ever....
But and here is the problem, if i want to flash the zip for easy-root from internal sd card using stock recovery mode, it can't be mounted (see attached pictures).
I looked all day long on xda without finding a solution fitting for me. Maybe i'm searching with the wrong words, don't know. There are many solutions for a external sd card, also for different devices, but how can i solve my problem with a gt-p7511/7510?
Hope that someone can help me, don't want to kill the tab by using a try-and-error-method.
And please don't kill me directly, if i did something wrong, just getting started and want to learn now activ, after just reading xda for years.
Thanks for your help!
Just to avoid anybody to think i'm blind, yes i read also these two threads without beeing convinced that they would help me:
forum.xda-developers.com/showthread.php?t=1804824
forum.xda-developers.com/showthread.php?t=1808560
edit 2:
Just to prevent anyone to stick at the same trapp as i did, all stock recovery from ics and up where patched to prevent access to sdcard from there. This might be clear to many here, but it wasn't to me. Thanks to msedek, who lighted me up, my "problem" is absolutely normal and wished by devs. Just didn't delet my post becaus about 100 people seemed to be interested so there could be need to state that clear.
Sorry to post bs. If someone thinks my post isn't helpful at all it can be deleted also.
I return now back to read-only-state in the forum, there is still much more to learn...
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
gfreeman86 said:
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
Click to expand...
Click to collapse
Only method?? Once youve installed ICS, use Odin to flash CWM and then install the root zip
http://forum.xda-developers.com/showthread.php?p=14020091
Sent from my GT-P7510
gfreeman86 said:
Hi, I have the same problem on my GT-P7500 (Galaxy Tab 10.1).
If I flash with Odin the stock HoneyComb firmware, all returns working as usual.
If I flash with Odin the stock ICS firmware, I get this issue and can't install anything on recovery because it says
E:unknown volume for path [/sdcard]
by the way I'm happy that you confirm this isn't my fault on something :angel:
Anyway, now the only method to get a working root seems to be:
1) Flash HC
2) Root as usual
3) Do the OTA update to ICS
The first time I updated to ICS, I've done this way because I had original Rooted HC and after the update, Root was still present.
By
Click to expand...
Click to collapse
I flashed with mobile Odin and had the same problem. I think Samsung blocked it so we are not able to root easily. This was the case in 7510 in honeycomb also. Anyway, I used Odin to install team win recovery and rooted it!
Sent from my amazing 10.1 galaxy tab
Yes, thats what i was informed about to by msedek. It's a issue to might prevent us from flashing without custom recovery.
Obviousely it worked, thought i did something wrong and my tab didn't act normal
lesson learned
Can I fully root my nook tablet to Jellybean, and if I want, restore it to default 1.4.0 from the acclaim_update.zip file? Not dual boot, but fully root to JB?
Yes
ronsummers said:
Can I fully root my nook tablet to Jellybean, and if I want, restore it to default 1.4.0 from the acclaim_update.zip file? Not dual boot, but fully root to JB?
Click to expand...
Click to collapse
You can root to Jellybean by installing boot manager, a custom recovery (CWM is suggested), and then one of the JB images. You can restore back to the original 1.4.0, and restore the original recovery, but I am not sure that you can restore the original boot manager.
Note that some JB images are 5-touch enabled. If you want to take advantage of this, you will also need to flash a new firmware (that enables the 5-touch capability). If you've done this, you will not be able to run the original image without flashing the firmware back to the previous release. I have seen one post that describes this procedure, but I'm not sure how safe or easy it is.
I have not updated the firmware on my NT for 5-touch, but I am running a pretty stable JB from the Android Development board. The one I'm running is here: http://forum.xda-developers.com/showthread.php?t=1877217. It does have a couple of minor issues. The worst one is that when it goes into deep sleep, it unmounts the SD card (but the OS doesn't know this). When you unlock again, apps that depend on the SD card get errors because the device went away. Most of these apps don't handle this type of error very gracefully. The only way I've found to get it back is to reboot. It's annoying, but I can live with it for now. It is my understanding that the ROM here: http://forum.xda-developers.com/showthread.php?t=1966894 has this problem fixed. The other issue is that sometimes it doesn't want to wake up... you poke and prod at all of the buttons and eventually it does wake up, but it can take 10-20 seconds (which seems like an eternity ).
Once you've gone to JB, you'll probably not want to go back.
Thread moved. Please post in the correct section when posting. Also can you please use more descriptive titles as people don't just look in threads for the sake of it they tend to go by the title and only visit if they think they may be able to help, especially in the Q&A section.
Thanks
AvRS
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Thank you
asawi said:
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
That should work excellently, thank you very much.
Nookuser19 said:
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Click to expand...
Click to collapse
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
topdawg7793 said:
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
Click to expand...
Click to collapse
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
asawi said:
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
Click to expand...
Click to collapse
Just used a 4gb class4 through a memory stick reader. It's working beautifully now, except I need to repartition it.
Interesting bug though, the home button won't take it out of sleep any more. Only the power button..?