Database Develop

[Q] Help with Honeycomb Nook please...

Hi folks
I couldnt find a topic like this on google so i thought i'd post a thread to see what could be made of this...
After going through the Auto-Nooter rooting process, burning CWR onto a 4gb SD Card as well as the HC v4 EMMC (not version 2) and low and behold everything worked last night until...
This morning, i had selected Lock Rotation to On as Honeycomb looked better in landscape mode than it did in portrait and when i tried to unlock the Lock Rotation the screen went black. I then pressed the power button to see what's what and the usual lock screen came (the one where you swipe to unlock) however the lock screen doesn't stay on long enough for me to unlock it.
The screen switches on, shows the lock screen and just as quickly goes black/locks again. It's not a fault with the button because i thought it was clicking twice therefore regsitering an unlock then lock process quickly but it only clicks once
Any ideas? Im thinking it may be a CWR job but i'd rather ask you guys rather than wiping everything first

I cannot get my Nook Color to boot into CWR mode via the SD Card
I tried to install Honeycomb using the eMMC method however it has clearly went tits up since trying to switch off Screen Orientation Lock
Please guys, any help would be appreciated to get this restored - have tried the various recovery methods and it aint working
Thanks

No worries guys - just a mild hyper ventilating moment!! Proof is in the pudding below

Cyanogen 7.1 RC1 and Honeycomb for Nook
I have a Nook Color that has CWR 3.2.0.1 installed to the EMMC.
I am running 7.1 RC 1 - and I understand that it installed it's own uboot. When I see the Cyanogen logo, I can press the N key on the device and get a boot menu. Everything runs perfectly with this setup.
I have since tried to create a bootable 4gb Honeycomb preview SD, the newer Honeycomb Return as well. I have tried recovery to load the Honeycomb (install from ZIP). The SD card method with the original preview will lock at a black screen - requiring me to hold the power off button for 8 or so seconds. Swap back to my original SD card, and the CM7.1 boots fine again.
Not that I want Honeycomb as a daily use, I just want to play around with this OS but have not had luck with any of the Honeycomb options.
Can someone give me some pointers to get this working on this setup - is it a RC1 issue with the alternate uboot? Something I might have missed?

WebOS bootloop after resizing!

Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.

spica123 said:
Hey guys!
I recently resized the partitions of my touchpad via the recommended cwm zips, in order to install latest 4.3.1.
Everything worked as expected.
After experiencing quite high battery drain I decided to reflash the A6 firmware, as I already did several times.
When I try to boot up WebOS, I'm stuck in a bootloop. The HP sign is flashing/blinking but it never boots up!
Seems the resizing deleted an important file or similar.
Is there any safe possibility to workaround this? Android is working normal, when I connect to a PC I can only see the MTP Media device, no other partitions.
Should I use WebOS doctor?
Hope somebody has a helpful idea.
Thank you in advance.
Click to expand...
Click to collapse
EDIT: Okay. at least acmeuninstaller brought webos back to life.

[Q] Android won't boot

Hi,
I recently tried following the guide on liliputing.
I used these 4 files and everything seemed to work ok:
cm-10.1-20130804-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST
gapps-jb-20130812-signed
moboot_0.3.5
update-CWM6_tenderloin-20131019
however, when I choose Cyanogenmod from the moboot menu, it begins to boot up, I get to the screen with the blue alien face, the screen goes dark and the table reboots back to the moboot menu.
I'm not sure what to do. Can anyone help me out? Please let me know if I should post additional details. I can boot into webOS portion fine.
Thanks!

dont.blink. said:
Hi,
I recently tried following the guide on liliputing.
I used these 4 files and everything seemed to work ok:
cm-10.1-20130804-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST
gapps-jb-20130812-signed
moboot_0.3.5
update-CWM6_tenderloin-20131019
however, when I choose Cyanogenmod from the moboot menu, it begins to boot up, I get to the screen with the blue alien face, the screen goes dark and the table reboots back to the moboot menu.
I'm not sure what to do. Can anyone help me out? Please let me know if I should post additional details. I can boot into webOS portion fine.
Thanks!
Click to expand...
Click to collapse
Did you try any other cm roms?

dont.blink. said:
I used these 4 files and everything seemed to work ok:
cm-10.1-20130804-EXPERIMENTAL-tenderloin-BLUETOOTH_TEST
gapps-jb-20130812-signed
moboot_0.3.5
update-CWM6_tenderloin-20131019
Click to expand...
Click to collapse
Where did you find "update-CWM6_tenderloin-20131019" ?
Who produced that recovery and where is it hosted?

[Q] [S3 mini 8190L]White pixelated screen, not boot and no TWRP mode after swapper2

Im currently using a S3 Mini I8190L with Carbon latest ROM. It was all fine and great until I tried to improve a little bit by using swapper2 through this method:
http://forum.xda-developers.com/showthread.php?t=1659231&page=1
Since the ROM documentation said it provided support for swap, I went straight for the swapper2 apk configuration, set it all, HIT ok. After that part, i got 2 fail msgs, the phone froze and i had to restart it.
But it would go straight to a white pixelated screen and never boot into KK or TWRP. All it does is Download mode (btw, battery doesn't recharge, need to use a 2nd device to charge it)
I tried to reflash the ROM but got a "THERES NO PIT PARTITION" error, went on to solving that with i8190l.pit but after flashing it, nothing changes. Still cant flash ROMs, boot to KK or TWRP.
For reference, the "STOCK" firmware is this one: http://www.sammobile.com/firmwares/confirm/22769/I8190LUBAMK1_I8190LZTMAMK1_ZTM/
What should I do ?

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

[Q] TWRP won't stay -- CM replaces with its own -- bootloops if replaced...

Ok, so I got the Z3c just recently since CyanogenMod now apparently supports it (odd it's not listed in devices on the wiki, but it's on their standard build system, so this is not even an unofficial build.) I found t here's even an official TWRP build for it. I really kind of need TWRP on there as I need to be able to do all of the numerous stuff it can do without having to hook it up to a computer with adb/fastboot/etc every single time. There are a huge number of features and conveniences to TWRP that CWM and CyanogenMod recovery both lack (frankly it feels like TWRP is a modern recovery and those two still feel like they date back to the Android 2.x days. I can remember the stock recovery on my Archos 43 back in the day being practically the same as what I get with CyanogenMod recovery especially.)
Anyway, this one is a bit odd. I've also setup a Z2 Tablet for my grandmother with TWRP + CyanogenMod and there are no troubles at all there. I put TWRP on it and it works normally basically. However, on this Z3c it's going a bit wonky. CyanogenMod somehow seems to be replacing the recovery with its own. I've disabled automatic updates and the option to update the recovery was never even enabled at all. If I flash using dd directly to the partition as the official TWRP page says I once again have TWRP, but then the system either won't boot at all (staying stuck on the SONY logo) or it just boots straight to TWRP over and over as if TWRP were the normal system instead of the recovery.
I'm wondering whether something is just going really wrong or if, alternately, there's some oddity like it having some sort of "boot to recovery" flag that gets set and does not clear? Is this something I can fix, or am I just stuck with CyanogenMod putting its own recovery on there without asking?
Honestly, SONY did a lot of things great on their devices, but not having a true separate bootloader/recovery is something I will never be comfortable with.

I tried flashing to boot once with, as you know, the expected results. Most of the time I did as I said in the original post and followed those instructions exactly though.
And I would just swear at at least one point I rebooted back into TWRP and it was still there before CyanogenMod replaced it. Oh, and from the TWRP page on this device:
This utility is designed to work in conjunction with the current methods that most AOSP ROMs use for the ramdisk and can also be used on stock kernels. This setup means that you must have a kernel or boot image installed that will use the FOTAKernel method. Most AOSP based ROMs like OmniROM or CyanogenMod will support this method. Some stock kernels may also support the FOTAKernel method.
Click to expand...
Click to collapse
Note they explicitly specify that CyanogenMod supports its method.

Ok, I think I was misunderstanding something. It looks like CyanogenMod essentially has its own boot partition and this goes to a separate location. Rather than being "replaced" it's just going to CyanogenMod's separate recovery instead of TWRP. If so this begs the question of how one even gets to TWRP there (which isn't mentioned on that page at all.)
EDIT: It's a pain, but I tried fastboot flashing it to boot. It still goes straight into TWRP every time if I do that. The "recovery-from-boot" file is not present in /system. (It's a pain because I have to "reinstall" CyanogenMod and wait for it to optimize everything again now.) It's when I flash with fastboot that it gets stuck always booting straight into the recovery. Ironically, if I flash CyanogenMod's own boot image back on there manually it still gets stuck always going into recovery -- just CyanogenMod's recovery instead of TWRP.
EDIT2: I ran across this post: http://forum.xda-developers.com/showpost.php?p=58830666&postcount=206 I'm still getting CyanogenMod's own recovery though even when I follow that exactly.
EDIT3: Ok, I think I found a solution. Not sure if this is the best possible way to do it, but I found out that XZDualRecovery apparently works with CyanogenMod fine. I just have to remember to flash it after flashing CyanogenMod in the recovery and then during the bootup process I have to wait for the light to go green (instead of earlier in the process as that just gives me CyanogenMod's recovery still.) If I hold down once it goes green I get TWRP. http://forum.xda-developers.com/showthread.php?t=2261606

I tried recovery. The problem is, boot and recovery are the same thing on SONY devices like this. Anyway, that XZDualRecovery isn't perfect -- for one it ignores the setting for brightness, leaving the screen at 100% (which not only hurts my eyes, but obviously isn't good for it.) Other than that though this thing works very well.

All I can tell you here is that I tried flashing to recovery instead of boot and it didn't work. Perhaps there's some special way you have to trigger it beyond the usual methods (perhaps like the way XZDualRecovery has its own portion of the startup where the LED goes green and the motor vibrates to let you know it's time to press a button if you want it to boot one of its recoveries.) Nothing mentions this anywhere that I could find though and I definitely haven't triggered it on my own.

Given that it works at all but is determined to either utterly ignore TWRP or go straight to only its own recovery it must have some sort of check then and just simply reject TWRP I guess.
Anyway, a this point there's really nothing I can do with it. I lack the development experience, time, or knowledge to go about trying to fix it and submit patches or whatever. I'm just going to stick with XZDualRecovery since it works fine in every way except ignoring the brightness setting (I do hate that, but at least on long operations it still shuts off the display.) Just to be clear, you do understand that XZDualRecovery DOES let me boot TWRP from it? I don't know if it may be a modified version or something (the fact that it's ignoring the brightness setting makes me think it may be) but everything seems to work normally within it other than that (I'm wondering if that may be more an issue with the startup process.)

In developer options there is an option that should be unchecked. Can't remember but it's says not to update recovery or something similar

Indeed. I always uncheck that first thing and actually disable automatic updates entirely anyway (this is about updating through the standard interface. I update by downloading builds and installing through TWRP for several reasons that I won't get into right now.) Unfortunately though, that is kind of a separate thing really. It's more just in reference to the fact that CyanogenMod now has its own actual recovery so you can set it to automatically update that part as well. Just to be completely clear though, because of the way it works, TWRP would no longer come up after installing CyanogenMod at all and it can't be just simply flashed back on. I guess feherneoh has the right of it really. Perhaps it's compressed incorrectly (or shouldn't be compressed at all) or whatever. If I knew what I was doing I could probably manually do this part myself, but I don't really feel very confident about that. I'll just stick to XZDualRecovery with its TWRP 2.8.7.0 build that works great in every other way but the fact it ignores the display brightness setting.