the manual method of updating to 1.2 has the user place the zip (nookcolor_1_2_update.zip) onto the base drive of the nook, and then after a few minutes, it'll detect it.
anyone know how it detects it? and whether this would serve as an avenue of flashing things (for those who haven't gone to CWM and such?)
just curious...
and FYI - if you've updated to 1.2, you can revert back to 1.1 (or your previous version) by doing the 8 failed boot trick.
Related
OK - this is my fault and I'm willing to put the work in to fix it myself but I'm hoping someone knows off the top of their head.
Transformer firmware all up to date. Rooted and on MagnuSupr3m3 ROM.
I had also pushed a modified WPA_Supplicant file to enable ad-hoc tether to my HD2 - that worked great.
I applied Sheshmaru's cool win phone7 theme to check it out. see link below
http://forum.xda-developers.com/showthread.php?t=1120525
Somewhere after applying the theme I found that wifi could no longer connect at all and showed error as it's status. This problem persisted even after I rolled back to a recovery backup of prime 1.4 I had made - using SolarNZ CWM R3.
Any suggestions? I'd rather learn how the wifi stack is working and apply fixes rather than just reinstall the whole thing
I had the same Wifi Error status on my TF, but that was after I got it rooted and flashed the newer CWM on it. Toggling Airplane mode fixed the Wifi for me, no idea why lol
SOLVED
If anyone else suffers this misfortune the fix for me was this:
Followed instructions to add an eraseData file in the Solarnz CWM thread - http://forum.xda-developers.com/showthread.php?t=1093818
Reloaded my recovery.
There is most likely a better way to do this by just pushing some wifi related files into the right folder but that goes beyond me and I couldn't drum up any instructions from a quick google.
Hello there. I was wonder about about Darkys ROM so I have installed 9.5 successfully (thanks to noobish giude).
1) I have upgraded from official Samsung I9000 galaxy S (2.2) to 9.5 ROM + Dark core 1.4.
It gave perfect result - fast and stable.
2) then I did upgrade to ROM 10.1 with help of noob guide (recovery mode, no clean, update via zip file as before, disabled lag etc.). It was successfull too, BUT after install I restarted as in last instruction of upgrade and it has come:
Look at this screen in ATTACH please.
If I let it be it will boot up fine but:
1) it appears randomly inside of system (mostly when sliding notification bar up and down).
2) I cannot see recovery mode (its in there but it looks like it cannot work with display until initialization of system)
Anyone can help me please?
Then
So its solved thanks to user ceriko on official darkyrom.com.
//sorry for unfinished name of post (I am unable to edit it)
Bootloader problem. I had the same thing when I first flashed GB.
ok i originally ran a rooted version of the 1.1 nook color and today i went to flash to
nookiecomb .413 and my wifi couldnt connect after that, next i tried
cm 7.0.3 and that had the same issue, then i tried
nookie froyo 0.6.8 and the same thing.
now i had wifi with the stock rooted 1.1 that worked fine but i wanted to upgrade to a flash capable image of android for my NC. anyone else get this issue and if you did how did you fix it?
Hi,
I'm trying to use Multiboot on my defy (Red lenses and GB kernel). My original rom is the latest CM9 by Quarx.
Every ROM I installed (I tried MIUI V4, XIUI and CM10, all for Defy+) I get com.android.phone FC and, I think its because of this error, i cannot find network (yes, I tried to switch my baseband to the correct one).
I tried Multiboot v0.6.1 and v0.5.1 and get the same error. I tried v0.7 with TWRP, but with this I stuck at Motorola logo.
Its the firist time i'm trying to use multiboot, I did all the steps of more than 1 tutorial and give me the same error. Anyone know something I may have missed? I'll keep trying and if I got something i'll post here.
Thanks.
did you get multiboot working?
if not, what error does it gave??
and what steps did you followed???
Basically I instaled multiboot V0.6.1, then installed Multiboot Manager Free and created an image with cache: 150Mb, data 250Mb, and system: 350Mb. Then I flashed one of the ROMs tha I mentioned.
I get it working, I can load the system, conect via wifi, navigate and etc, but after startup I get com.android.phone FC and get no signal. This happened with all the ROMs tha I've installed.
EDIT:
It seems that I could solve it, I uninstalled Multi Boot Manager and installed Vibhinna, deleted the old system image and did everything again. Now I get no errors.
Thanks.
You should also be aware that if you have a GB base ROM you should download the Defy+ versions of the ROMs you want to use in multiboot.
Hello
as the title says, I cannot upgrade my Thinkpad Tablet to Android 4.0.
Here are some stats:
Build number: A310_02_0039_0089_US
Kernel Version: 2.6.36.3
not rooted
I tried to upgrade the tablet via the "normal" way in the settings menu (when it tries to update, the bar stops at 1/5 of the way and the tablet restarts) and i tried to update it manually via the recovery menu (tried all US Versions from download.len ovo.com/slates/think/tablet1/ (remove space in lenovo) that are higher than 0089), I attached a picture of the failed update from A310_03_0069_0130_US and A400_03_0069_0130_US
I did also perform a factory reset, but it didn't help.
thanks
Bump
Is there anyone who can help me?
Hi.
Sorry, I never found that problem. I updated to Android 4.0 over the air without problems.
I had tried to document the problems with this tablet here: http://forum.xda-developers.com/wiki/Lenovo_ThinkPad
It will be interesting if we can find out how to fix this problem and document it there too.
By the way? is your tablet rooted? Do you use the standard Android Recovery Menu or did you installed CWM ?
Regards
The tablet is not rooted. I bought it used and it came with a CWN Recovery (as you can see in the picture).
I also tried to use NVflash but it has the 0X4 error (so I guess the bootloader is locked)
Bump
Has anyone else an idea?
Bump
Anybody here?
I think, you need to full reflash your slate with backup of ics via cwm or original firmware from Lenovo to have oem recovery
i am having the same problem but mine is completely stock.