What the heck is happening? - Fascinate Q&A, Help & Troubleshooting

So I've been trying to install the ICS roms, going from gingerbread, to installing hacksung build 2 then installing the roms and it will always goto
"Checking state of BML/MTD" and will hang then say install completed when it defintatly did not. sometimes it will add a "random offset: xxxxx"
What the heck am I doing wrong? (This happened to both MIUI and AOKP ICS roms)
and then it'll start "not able to mount blah blah blah cache data" whatever it is

So I managed to mess up somehow. My up volume button does not work, and my home button is the back button, while the back button is now the home button.
fff

sspgoolsby32 said:
So I managed to mess up somehow. My up volume button does not work, and my home button is the back button, while the back button is now the home button.
fff
Click to expand...
Click to collapse
have you tried to odin back to stock and start fresh?

I think I somewhat got it managed, but this was not only happening on my phone but another fascinate of my family's.
I did odin back to EH03, then make my way up to build 2 hacksung, then from there things get screwy. Also, the one time I managed to get the new MIUI ICS one on the other phone, it was slow as molasses.

flash aokp 32 glitched!
fyi some stock sd cards dont play nice with cm7 and cm9 mtd based roms. if you run into alot of "cant mount" errors in recovery this could very well be the problem. a class 6 or higher sd card should fix that issue. also check my guide out in the general section...refer to section 4 and follow steps to the T.

droidstyle said:
flash aokp 32 glitched!
fyi some stock sd cards dont play nice with cm7 and cm9 mtd based roms. if you run into alot of "cant mount" errors in recovery this could very well be the problem. a class 6 or higher sd card should fix that issue. also check my guide out in the general section...refer to section 4 and follow steps to the T.
Click to expand...
Click to collapse
word. That's what I'm on now, although I had to do a few wipes / reinstalls before it fully got installed. We all have the same SD (16gb) cards as well. I'll check your guide out as well, thanks!

Related

[Q] Need help, i'm stuck on the Viewsonic splash screen

Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
I would get nvflash set up with bekit's images and flash that to get yourself back to a working stock image. Follow the instructions in this thread:
http://forum.xda-developers.com/showthread.php?t=861950
After that, put Clockworkmod ( v .8, get it from development forum) on it and repartition your sdcard to 2048 and 0 then you should be ready to flash.
Then get a ROM from the development forum here, there are some based off cm7 (gingerbread builds).
I was hoping not to have to use NVflash cuz people report problems with the boot loop, however I havent found any other option so far so I guess i'm trying that. Thanks for the link.
Xxlgeek,
Every time I hear boot loop I think re-partition -- because most of the time that
seems to fix the problem.
I agree you should NVFlash to get a stock version working. Then install CWM so
you can partition -- and the do the Fix Permissions, Wipe Dalvik Cache, Wipe
Cache, Wipe Factory Data.
With that I would try to wind up with a stock machine and let it OTA up to 3588.
I wouldn't load another Alternate Rom until I knew my tablet is working good and
until I know a lot more about the roms and how to work with the G-Tablet.
IMHO.
Rev
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Xxlgeek,
If it didn't work, I would erase the Cyanogenmod 7 file -- and I would go back to a stock rom until I could make sure all the hardware is working right and the system
is stable.
When you know the tablet is good and stable, you can always download and re-do.
Rev
Xxlgeek said:
Hey xda forums, first time poster, long time reader. I rooted my Nook color from these forums and find them to be most informative. I just got back from hiking the Grand Canyon to find my G Tablet waiting for me from Woot.
As I did with my Nook, I immediately started to replace the stock rom with Cyanogenmod 7 beta. I followed the instructions on the Wiki, including installing Gapps, by putting them on the internal SD and using CWM to install from zip. After everything was done however I am now stuck at the Viewsonic splash screen. I tried to read thru the Googles and tried reflashing back to stock by way of some instructions on DroidPirate I think it was, to no avail. I can't even see my external SD card to load the update to recover. Please help. Anyone?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1021978
you are not alone...
it may have to do with the boot loader .... further investigation needed. CW does not replace this but the stock does I have been running the old one since december on my personal tab. but most of these woot pads are updated .... hmmmmmm
Xxlgeek said:
I can actually boot into CWM right now. I already repartitioned and wiped all the caches. But when I try to flash Cyanogenmod 7 again, which is on the root of the internal memory, it just does the same thing, won't load past splash screen.
Click to expand...
Click to collapse
Which version of CM7 are you running?
jivy26 said:
Which version of CM7 are you running?
Click to expand...
Click to collapse
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Just throwing this out there. I bought 2 from Woot myself. On my first G-Tab I had the same issue with every single ROM I tried. I finally used NVFlash to go back to stock and everything was good again. I then flashed to the G-Harmony Gingerbread ROM and it worked and still runs like a CHAMP. Now, I finally get the other G-Tab out and start to go through the same routine as the first and it's been a no go repeatedly. I have mostly been trying with the Cyanogen 7 Final ROM to no avail and even with the G-Harmony. Going to try NVFlash on number 2 tab and see what the result is and will post back in a bit with updates.
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
tunez23 said:
Ok, I said I would reply and here it is. The downside is this.... The NVFlash worked great and put me back to stock. The bad part is that I am not sure that was what actually caused the problem to occur in the first place on the second tablet. I had read right before doing this that installing the Clockwork mod from the SD card instead can be a fix as well. I did that this time through. It also shows something different on the screen when you hold down the start and vol+ buttons than it was when CWM was installed wrong.
So basically this:
Run NV Flash (Detailed here: http://forum.xda-developers.com/showthread.php?t=861950 )
Run Clockwork Mod FROM THE SD CARD!!! (Detailed here: http://forum.xda-developers.com/showthread.php?t=865245 )
Then proceed to follow those exact instructions from the same thread.
Do not skip stuff, do not think you have a better path, just do it all as described. I now have a G-Tablet running the Cyanogen Mod 7 Final release SMOOTH as glass! Hope this helps someone else out.
Click to expand...
Click to collapse
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Did you extract both archives to the same directory on your computer?
akodoreign said:
doesnt matter all the gbread roms do this when the error happens. thats why i am starting to think its the bootloader
Click to expand...
Click to collapse
2 partitions are reversed and Gingerbread roms don't like it. Using bekits original nvflash files will fix the partitioning permanently as far as flashing between froyo and gingerbread.
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Edit.....This is not all tablets. I'm guessing around 30% or so have the 2 reversed partitions but it seems 50% of the woot tabs. Helped fix many of these on irc in the last 2 weeks
KrazyOne7 said:
I too am having the same problem but when I try to run NVFlash, I get the error "nvflash configuration file error: file not found Press enter to continue:"
The tablet doesn't restart or anything. I followed the steps to re-partition and install the ROM from "http://forum.xda-developers.com/showthread.php?t=865245." After that didn't work, I tried the steps from "http://forum.xda-developers.com/showthread.php?t=861950" and I get stuck at running the nvflash_gtablet.bat file.
Any help would be appreciated.
Click to expand...
Click to collapse
Having the same problem too!! Any help would be much appreciated.
Tried wiping everything with FORMAT.zip from another thread, and get and error for unknown device when running that *.bat file.
This newbie needs some serious help!
Locked bootloader??!
thebadfrog said:
Any official updates from viewsonic past 3588 have a locked bootloader and require viewsonics kernel so you must use Gojimis fix or nvflash to go back.
Click to expand...
Click to collapse
I think I must have the locked bootloader, but tried both Gojimis's fix and nvflash fix and get the error as mentioned above.
So I am getting nowhere, won't go past the "booting..." splash screen to install any of the update.zip files from the microSD card.
Help!
K J Rad said:
Did you extract both archives to the same directory on your computer?
Click to expand...
Click to collapse
Yes, I extracted both the gtablet and the windows zip files.
KrazyOne7 said:
Yes, I extracted both the gtablet and the windows zip files.
Click to expand...
Click to collapse
Me too, and still getting the error "nvflash configuration file error: file not found Press enter to continue:"
Are they in the same directory. If they are not then nvflash can not find the files to flash. Both zips have to be unzipped in the same directory and the driver has to work. You must be able to see the tablet from the computer when you boot into apx mode. APX mode is power/vol- NOT power/vol+

[Q] Help, I have searched everything available, I promise.

So, I have the Samsung Fascinate from Verizon, had this phone when it was new and just found it again and it is much better than my blackberry, or so I thought. I am trying to install ICS build one by following http://forum.xda-developers.com/showthread.php?t=1238070: - I have been able to install PW but when I am trying to install ICS1.zip (I renamed for simplicity purposes) I get the following errors: E: Can't mount /cache/recovery/log and cache/recovery/last_log
I have read enough to know that I needed a class 6 or better SD card so I bought a Class 10 8 GB from Best Buy and gave it another shot. I have mounted and unmounted the SD card multiple times, and when installing it shows:
-- Installing: /sdcard/ICS Build 1.zo[
Finding update package...
Opening update package...
Installing the update...
Installation aborted.
Any suggestions are greatly appreciated by those with positive feedback or calling me ignorant and not finding the answer online. Again, thanks in advance.
P.S. Yes, I have installed everything up until step 19 is where it stops working
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
So you odined back to stock and then tried flashing build 1 in cwm4 fixed for mtd?
---------- Post added at 09:02 AM ---------- Previous post was at 08:59 AM ----------
kadin.zimmerman said:
Hey, i have had this problem as well when installing ICS. First off i would recommend installing build 6 instead of build 6.1 because build 6.1 actually has more problems that build 6. you can get build 6 from here : http://rootzwiki.com/topic/16630-romicsiml74k-teamhacksungs-ics-port-for-fascinate-build-61-0201/
Now to fix your sd error, you need to use the odin program and flash your phone back to any stock firmware. Here is verizon stock EH03 : http://www.multiupload.com/4LC6JFCSFD I'm sorry it is such a large file, verizon puts a bunch of crap on their firmwares lol As for your sd card, i honestly do not think it makes a difference what class it is. I am using a class 2 16gb sd card and have never ever not been able to get something to work.
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
After you have used odin and flashed a cwm recovery, please power off your phone and hold down the volume up, down, and power keys at the same time till the samsung logo comes on, so you can go into the new recovery kernel that you flashed to it. Once there, go to the option where it says wipe data/factory reset. After that has completed, do the next option that says wipe cache. Once that is all done, you will say "install zip from sd card" and navigate to the .zip
Now here is where you have two options....you can either flash build 1 first and then build 6, or you can skip straight to build 6. Personally i would skip straight to build 6!! It should work just fine as long as you have wiped data and cache. The differences between build 1 and 6 are night and day and you would have to clear data and cache anyway after you had build 1, so you should be able to go strait to build 6. Other people i have helped went fine right to build 6
After installing the .zip, navigate to the option that says "reboot system now". if you encounter a boot loop that constantly goes into the cwm recovery, let me know! I have dealt with that first hand! let me know if you have questions
Also i recommend using the magnifying glass capacitive search key to make your selections when in cwm, because for some reason i feel using the power key was partly the reason i encountered the cwm boot loop
Click to expand...
Click to collapse
Build 6 link is dead...and for most flashing build 1 or 2 first is the only way ics build 6 will install. Also many folks have had trouble with class 2 sd cards...your not doing anything special more so just lucky its working for you.
kadin.zimmerman said:
Now after that is done, and it has booted to stock verizon firmware, put the phone back into download mode and use the odin program again to flash a cwm recovery kernel. This one should do just fine, if for some reason it doesn't, let me know and i will upload mine and you can have it. http://forum.xda-developers.com/atta...2&d=1311907538
Click to expand...
Click to collapse
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
New link to build 6 : http://www.mediafire.com/?sjn6x76c48me9su
So if going right to build 6 didn't work, then you would just have to give it another try, but installing build 1 or 2 first. No big deal, however I do know people who have had it work just fine.
I never said i was doing anything special because i had a class 2 sd card. I simply find it hard to believe that the sd card would have that much of a bearing on whether or not you can install a rom on a phone. I realize some roms partition the sd card the way it wants it, but in the end, the rom is flashed onto the actual phone itself, not the sd card. I know what the difference is between different classes of sd cards so you don't have to explain.
---------- Post added at 03:58 PM ---------- Previous post was at 03:52 PM ----------
PushyFurball said:
That link does not work for me just FYI. I am currently back to stock (it's what I do when I can't get it to work because I am not to big of a powerwash fan. I have cwm4 to cm7. I believe it is 4.0.1. But I will search for the latest cwm recovery and put it on and see if that fixes any issues. I also saw somewhere a few days back that people format their SD cards on their PC but I do not remember what format so if that is completely irrelevant since the SD card is brand new (Almost 12 hours old) let me know. I will keep you posted and see it works.
Click to expand...
Click to collapse
Sorry i thought that link was working...here is the one i originally start out with when flashing from stock. : http://dl.dropbox.com/u/32493357/cwm4_fixed_for_cm7-ODIN.tar
Please don't hit me, dropbox link doesn't work either.
PushyFurball said:
Please don't hit me, dropbox link doesn't work either.
Click to expand...
Click to collapse
Give it another try, it is working for me when i click on it
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Ok, turn your phone off, remove the memory card, and flash this kernel instead : http://dl.dropbox.com/u/32493357/CWM3_Voodoo.tar.md5
Then put the memory card back in and boot to recovery
---------- Post added at 04:50 PM ---------- Previous post was at 04:32 PM ----------
PushyFurball said:
When I go to "wipe data/factory reset" I still receive the errors about opening stuff and this is what it looks like
-- Wiping data...
Formatting /data...
Formatting /cache...
Error mounting cache!
Skipping format...
Formatting /datadata...
Error mounting /datadata!
Skipping format...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
Data wipe complete.
E: Can't open/mount /cache/recovery/log & .../last_long
-Exactly what I am doing step by step including what is clicked-
From stock, I open odin, pull out the battery, connect to PC via USB cord, press vol - on the phone. Then, I click, PDA, go to ..../Downloads and find the cwm4_fixed_for_cm7-ODIN.tar file and populate that portion of odin and put alas.2.2.pit in the pit section with the re-partition clicked. After completed, I go to odin, hit reset while the phone is still connected and then disconnect the phone. I put the battery in the back, press vol +/- and power and hold that until I see Samsung (which I don't see so I hold it for about 45 seconds to a minute and it boots it CWMR 4.0.1.0) and start trying to clear stuff and that is when I get the errors. So what I have done this time, is formatted the SD card in the recovery menu which I saw was not suggested, and I am going to try to just do a fresh install and maybe it was in the wrong format, who knows.
Click to expand...
Click to collapse
Actually i have never put a pit file into odin. When ever i went back to stock i just did the stock .tar.md5 file and it worked fine. I am not sure what the pit file is used for so maybe i would not use that. Let me know if that voodoo recovery got rid of that error
So the good news first, not putting PIT on their got rid of the errors of mounting and whatnot. Bad news is...
-- Installing: /sdcard/ICS Build 1.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That is the same for Voodoo Lagfix and cwm4.
Now when I tried just the Build 6, it is constantly going to "Samsung" over, and over, and over again.
Ok good you are making progress lol. So you did try it with build 1 initially and it didnt work? Thats strange because it usually does.
So have you gone completely stock without the pit file, loaded a cwm kernel, and then wiped data and cache and still no luck?
There are two different versions of ICS for the fasciante, one by alphalulz and the much better builds from teamhacksung. No matter what i tried and it didnt work on my device (before i eventually figured it out) , alphalulz's ICS V2 always would load on my device. It also loaded its own custom kernel as well, so when it installed, i would let it boot up to confirm the V2 version was working, and then i would clear all data and cache in the new kernel it gave you, and then would switch over to teamhacksungs builds.
here is the link to download the V2 rom : http://rootzwiki.com/topic/9687-rom-aosp-ics-extreme-alphalulz-v2-1118/
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
PushyFurball said:
Oh. My. Goodness. We have a good sign that this beast is going to work with Teamhacksung's versions... I don't really know what I did, I went back to stock with the pit file, downloaded build 1 while this was processing, and booted it up after it was finished. Then from there, I put that file, original name on my SD card and turned off my phone. Pulled the battery and odin'd cwm4 to cm7 and unplugged. Put the SD card in, booted to recovery, wiped the appropriate files, clicked install zip from SD card, picked the original name, and BAM!, it worked. So now I am going to try to put on build 6 and will edit this post to let you know if it worked or not. I am so happy I could literally jump up and down screaming like a little girl.
----EDIT----
Well, that failed miserably. Stuck on Samsung screen now. So, I guess back to step one.
Click to expand...
Click to collapse
Hey your getting closer...you will get it dont worry lol
so you just had build 1 working right?? go from build 1 to build 5 (being sure to clear data and cache) and then from build 5 to 6, ONLY clearing cache. Going from build 5 to 6 does not require a data reset.
I am a new proud member of having a Samsung Fascinate with 4.0.3 . Thank you so much for your help kadin.zimmerman!
-Thread Closed- ^_^
Now download ROM manager and do a backup so you can revert back to that state in case something goes wrong! I do backups about once a week
Sent from my SCH-I500 using XDA App
I installed FA16 (2012/1/16): ODIN CWM that was listed on the first page of the developement forum. There were no issues - only took a few minutes. Afterwards - nothing seems to have changed on my phone. the firmware is still 2.3.5, the kernel is still 2.6.35.7 and the build number is sch-i500-eh03. Have I missed something? The phone seems to be working OK. Note: I installed CWM from the ZIp file after I put it on the SD card in the root directory. Thanks for your help
No you haven't missed anything - you flashed a new recovery kernel. Do you know what the purpose of the recovery kernel is? The recovery does not effect your 2.3.5 operating system, the cwm recovery allows you to boot to it (by powering the phone completely down, and then holding the up volume, down volume, and power button simultaneously) and then you will be presented with a menu to install a custom rom such as the new android 4.0 or the cm7 cyanogen mod etc...so its pretty cool
Thanks for 'learning me'. Anyway, before i started playing with my Fascinate today, I had ver 2.2.1 installed - worked fine. After all the changes, I lost the Google search box on the home page - is there anyway I can get that back? I have the icon - just like the search box better. Thanks
Well what all changes did you do other than installing a recovery? Did you flash any files?
And you have 2.3.5 now right, so how did you get it. Did you do a Verizon over-the-air update or did you flash that file as well. I am just confused as to what you did because technically if all you did was install a recovery, it wouldn't mess with you Google search
kardin - recoveries and kernels are 2 completely different things. You keep saying CWM recovery kernel, but that doesn't make any sense. I'm not saying you don't understand what a kernel or recovery is, but they're not the same thing and I think you might confuse people when you say recovery kernel.

[Q] Am I bricked?

I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.

[Q] noob with questions CM7 on NT

Title says it, im a real noob but i did manage to root and install cm7, my questions are this
Is there a build that has HD video? ( hulu plus)
When i play music ( mp3s from sdcard) i get random sd card dismounts with the built in player and/or winamp
When i power down and restart i MUST(?) Hit the "n" button or i get a load error
For the most part i have figured out this thing ( came from ios ) just wondering if i
Should have put a different build on or if im just not doin it right
CM 7 is outdated. Install CM10 or CM10.1 instead.
There are several thread on how to. I happen to have my own at hand, but I'm in no way saying it's the best!
http://forum.xda-developers.com/showthread.php?t=2081981
The ROM you find in the development section
Ok should i run the backup i made i revert to stock before i install 10?
I was reading some other site and it said 10 was not stable, thats what i getfor not comming here first i guess
CM10 is very stable. Can't speak for CM10. but according to comments I've seen here it's pretty stable too. I just happen to prefer CM10 to the 10.1 I have tried.
You do not need to revert to stoch before installing CM10.
Make sure you get the right version of CWN running before flashing CM10. (Version 6.x.x)
asawi said:
CM10 is very stable. Can't speak for CM10. but according to comments I've seen here it's pretty stable too. I just happen to prefer CM10 to the 10.1 I have tried.
You do not need to revert to stoch before installing CM10.
Make sure you get the right version of CWN running before flashing CM10. (Version 6.x.x)
Click to expand...
Click to collapse
thank you for your help btw...( should have said this on my first reply )
im am very happy to get some help ( thought i could figure it out on my own....NOT )
should i be worried about the error i currently get on boot-up
on the cynoboot screen it says
E1 <---on top left corner
loading Altboot from emmc
normal SD boot overridden. Alt boot from EMMC
booti: bad boot image magic ( in memory)
only way to get past this is to reboot and make sure to press "n" to bring up the menu and choose
internal eMMc normal
and at this stage a E2 is in the top left corner...but if i choose this all will boot and work fine...
is this something im supposed to do on boot-up? or is there a error i should be worried about before
i nuke CM7 and go for CM10?

Nook BNTV250 touchscreen on CM 10.1 suddenly stopped responding

Here is what I did, on a new Nook Color (I guess mine is Nook Tablet) 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
Did factory wipe and Dalvik wipe.
Installed cm-10.1.3-acclaim.zip
Did another quick factory wipe
Installed gapps-jb-20130812-signed.zip
Everything was perfect, booted just fine, went through set up process but at setting up google account, I went to get my password from my PC, when I got back screen was not responding. Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
hydeah said:
Here is what I did, on a new Nook Color 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
...
Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
Click to expand...
Click to collapse
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
digixmax said:
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
Click to expand...
Click to collapse
I did not do anything with the ROM on it, I simply used it to boot into CWM without having to go through partitioning the SD, etc.
PS: When I was testing above "live SD card" CM10 loaded fine and was working, a little slow but I blame the slow SD card for that..
(I booted to cwm, removed the SD card with HD-SDC and then inserted another SD with cm-10.1.3-acclaim used the CWM to install)
Everything looked like they worked just fine until suddenly touch screen stopped working. I have BNTV250. Did I just totally mess this up!
I fixed the title on 1st post, maybe I posted this in wrong section?
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Thanks Moscow for moving the thread for me.
asawi said:
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Click to expand...
Click to collapse
Asawi, no, that doesn't help. I already removed the SD card (since I flashed to 10.1, it boots into 10.1)
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
Is there anything I can do to just try again? Can I simply flash another copy of 10.1, maybe an earlier version or even a newer version like 10.2 over this?
I was so disappointed last night, I thought about this all night, couldn't go to sleep!
You can certainly flash the ROM and gApps again an see if that helps.
asawi said:
You can certainly flash the ROM and gApps again an see if that helps.
Click to expand...
Click to collapse
Thanks.
The ROM and gApps I listed above match each other, right?
cm-10.1.3-acclaim.zip (http://get.cm/?device=acclaim)
gapps-jb-20130812-signed.zip (http://goo.im/gapps/gapps-jb-20130812-signed.zip via http://wiki.cyanogenmod.org/w/Gapps)
btw, thanks for replying, in fact I followed your instructions to install 10.1, and here you are. :good:
Before installing cm and gapps, my nook was completely stock, I guess I really did not need to do anything before installing CM, right? Did I need to root it with a custom update.zip or something like that, or is that not necessary at all? Just boot into cwm and install rom+gapps, that's it?
Edit: Re-installed CM10.1 and Gapps, still have the unresponsive touchscreen..
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the info surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
asawi said:
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the onfo surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
Click to expand...
Click to collapse
Thanks for checking, I just re-installed them, still touchscreen won't respond to taps.
I can just go with what you have if it works fine. Tell me how to get them on my Nook and I will, I don't care about version of Android, just need a stable android on this device so I can buy some sesame street, disney, etc stuff for the kids since Nook OS was laggy and limited. Can I just wipe all this stuff off the nook and start over?
Is there anyway to check if touchscreen problem is physical or software issue?
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
asawi said:
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
Click to expand...
Click to collapse
Thanks, do I need to wipe anything to get rid of 10.1 before I install this?
I will follow this:
Download the updated CM10 12/25 ROM (cm-10-20121225-acclaim-HD-SDC.zip (GCC 4.6) (http://tinyurl.com/au32v2l) and also download the GApps file (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Do the usual wipes. Factory reset, cache, Dalvik
No go, I went down to CM10 ROM above, no luck, touchscreen is still not functioning.
I am going to use recovery by following these instructions to return this to stock OS and then take it back, this is ridiculous.
I can just use this, right: http://forum.xda-developers.com/showthread.php?t=1663836
Yes, that repart.img should work. I have used it on numeroud Tablets and it has never failed me.
Nook is going back, recovered using repart, worked very well, I don't see a trace of cwm.
Touchscreen has some issues, that's for sure, thanks for all your help.
hydeah said:
...
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
...
Click to expand...
Click to collapse
Sounds like you still have stock recovery.

Categories

Resources