Closed GoogleCodeExporter closed 8 years ago
In order to accept this issue please provide:
Device maker/model
Android version
Limbo App version
DSL version
Please be more specific on this issue. What files did it load? What process
loaded the files? At what part of the boot load did it stop working? Please
attach a screenshot and a logcat output.
Original comment by ideal2i...@gmail.com
on 13 Nov 2012 at 9:03
Original comment by ideal2i...@gmail.com
on 13 Nov 2012 at 9:08
Original comment by ideal2i...@gmail.com
on 13 Nov 2012 at 9:09
samsung galaxy geo gt5660
running custom rom (aurora rom
http://forum.xda-developers.com/showthread.php?t=1858633)
android kernel ver 2.3.6
newest limbo app v0.9.3
newest dsl 4.4.10
on loding the kernel it states ready and appears as a empty terminal screen
after unloading the bootloader image.nothing occures after.
Original comment by jdami...@gmail.com
on 14 Nov 2012 at 2:06
Attachments:
What happens if you go back to the Limbo Console (choose 'Limbo Console' from
menu) and then choose 'Resume'? Can you also try an external VNC client and see
if you can connect to the VM remotely to port 5901?
Original comment by ideal2i...@gmail.com
on 14 Nov 2012 at 2:41
[deleted comment]
if i exit to the limbo console and resume it wont connect.
so your saying the os might actually be loading but i just can't see it.
Original comment by jdami...@gmail.com
on 14 Nov 2012 at 1:38
Yeah, sounds like the VM hangs and you cant connect. Your device or possibly
the custom rom you have might not be compatible with Limbo.
Original comment by ideal2i...@gmail.com
on 15 Nov 2012 at 6:01
Incompatible rom
Original comment by ideal2i...@gmail.com
on 6 Jan 2013 at 11:59
I'm using Asus Zenfone 5
Android 4.4.2 ROM (Original, no custom ROM)
Limbo v. 0.9.4
I'm trying to ruin Windows 98 ISO, but I'm only getting a black screen at the
start. What should I do?
Original comment by mrittick...@gmail.com
on 23 Mar 2015 at 1:41
umm dude, this is a 2 year old issue, relating to the use of very our of date
hardware having Custom rom issues, open your OWN issue, and then try again
Original comment by jdami...@gmail.com
on 24 Mar 2015 at 11:39
Original issue reported on code.google.com by
jdami...@gmail.com
on 13 Nov 2012 at 10:53