12.3 still have error massage - Omnia II Android Development

hey everybody i tried two whole days to install android os.
i read every comment here:
http://forum.xda-developers.com/showthread.php?t=918778
tried all 3 methods there and what other worte in also the korean rom
without sucsses, this device isnt support in my contry and i have no idea how install android.
the massages that i have got:
mount: mounting /dev/block/mmcblk0p5 on /sd card failed no such device or address
"cant mount internal flash!!!!!"
Until the installation process (folder o2beta) I'll get an message "can't find ext2.tar.gz on My Storage". After reboot and starting HARET.EXE from root directory it stops at the message:
Warning: unable to open an initial console.
Failed to execute /init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init=option to kernel.
help pls!!

Your question should be in the thread you linked to. You got the Android zImage from there, so that's where your question should be.
Closed.

Related

Android Boot hangs with "disabling 'sysinit'"

I've gotten Android installed (and updated) on my HTC Tilt Device. My current hang up is that when I let it boot it hangs with the message
Code:
A N D R O I D [ ] init: cannot find'/system/bin/logwrapper', disabling 'sysinit'
Did I do something wrong/what can I do to resolve this issue?
Regards,
~Jeff
Onward, upward, backward. forward, I tried installing the "Warm Donut" version instead of the "Eclair" and the system hangs with this different message are startup on this one:
Code:
init: Unable to open persistent property directory /data/property errno: 2
I think Android dislikes me (Maybe it knows my other phone runs Maemo LOL)... Suggestions?
~Jeff
So I found a thread (which I can't link to because of the forum rules) that describes my second issue but the alternate data.img file provided does not resolve the issue for me as it says it should... As always waiting patiently and open to suggestions.
~Jeff
Since you mention data.img i'll assume you are using Haret rather then Nand install.
The 'init: Unable to open persistent property directory /data/property errno: 2' means that android cannot find the data folder, usually happens if you miss the installer stage.
Even when running from haret we have to run the installer in order to unpack the 'androidinstall.tgz' and set up the data image.
To access the installer menu you must press the d-pad centre button when booting.
Note that once it is installed you do not need to enter the installer again, unless you are updating.

please help

i got error init: Unable to open persistant property directory /data/property error: 2 every time i boot android on my kaiser..iam using dual boot..i search everywhere but no solution..iam about to uninstall android please help
fast666 said:
i got error init: Unable to open persistant property directory /data/property error: 2 every time i boot android on my kaiser..iam using dual boot..i search everywhere but no solution..iam about to uninstall android please help
Click to expand...
Click to collapse
Try a different SD card or NAND if you don't mind ditching winmo.
Follow this guide (nand) or this guide (haret/SD)
Please change topic title in "Install problem: Unable to open persistant property directory"

[Q] Lost access to internal storage

Hello,
In the process of rooting and trying to install CWM Recovery in preparation to flash Cyanogenmod, I seem to have denied myself access to the phone's internal storage. In the "File Manager" app, I get the following screen:
Local: /storage
No files
No search results
In addition, any app that requires access to internal memory will not work, instead showing messages such as "Try again after scanning media files" or "Not enough storage". If I plug in the USB cable and set it to "Media sync (MTP)" mode, Windows Explorer will show the device but list the internal storage as having "0 bytes" and no files.
I already tried the following:
- Factory reset
- Flashing the official ROM through the Windows Enabler / UpTestEX tools
In both tries the phone was "reset", as in it returned to the initial Android welcome screen where you set up your Google account, but in each case I still didn't have access to internal storage.
This is what I have in the "About phone -> Software information" option:
Android version: 4.1.2
Baseband version: APQ8064T/MDM9x15M
Kernel version: 3.4.0
Build number: JZO54K
Software version: E98810b
The phone does not have Wi-Fi access either, which is why I was tinkering around with custom ROMs in the first place, so I won't be able to download anything to it as part of the solution.
Is there anything else I can try?
I'm guessing you used FreeGee to install CWM? Perhaps try restoring?
If that didn't work... Id move the EFS backups to my computer. I'd make a NAND backup in CWM. Then I'd get CM and gapps on a micro SD. I'd do a format of system, data, and cache. Then I'd install CM and gapps. Then I'd cross my fingers.
Sent from my LG-E980 using Tapatalk
ackliph,
Since I didn't have Wi-Fi access on the phone, and at the time I didn't know how to reverse tether it to the computer, I was looking for a procedure to install CWM Recovery that didn't involve downloading files directly within the phone (only transfering via USB). Right now I can't find the exact instructions I used, but it was similar to what is described by hkfriends in this thread: http://forum.xda-developers.com/showthread.php?t=2361941, the only difference being that the image I downloaded was not that one.
I rooted the phone with Universal Root, then followed those instructions to install CWM Recovery. It seemed to have worked, but when I rebooted... nothing happened! The phone booted normally, and if I tried entering recovery mode all I got was the stock LG recovery.
I continued looking for another way to install a custom recovery, but instead came upon instructions to flash KDZ files with UpTestEx. Since the immediate problem I was trying to solve was the lack of Wi-Fi access (and not really the custom ROM), I thought it couldn't hurt to try updating the stock ROM. The procedure did update my ROM, but I ended up in my current predicament: no access to internal storage, and still no Wi-Fi access! It even managed to unroot the phone.
So your suggestion would be to try installing CM via a microSD card. OK, I can get a microSD and try that. However, I do believe I will need root access to do anything of the sort. I tried Universal Root again, and got the following messages:
Beginning Root Process
/system/bin/sh: can't create /sdcard/G_security: Permission denied
Now change from Charge Only to MTP
No need to disconnect USB
Press Enter after making the change.
adbd cannot run as root in production builds
error: device not found
If uid=0(root), gid=0(root) is displayed
Press Enter to Continue
1955 KB/s (1085140 bytes in 0.542s)
mount: permission denied (are you root?)
cp: can't create '/system/xbin/busybox': Read-only file system
failed to copy 'su' to '/system/xbin/su': Read-only file system
failed to copy 'Superuser.apk' to '/system/app/Superuser.apk': Read-only file system
Unable to chown /system/xbin/su: No such file or directory
You are now properly Rooted.
Click to expand...
Click to collapse
Evidently, that didn't work.
I guess I will need some other method of rooting it.

Worst Rooting Issue

So, upon opening this you're probably thinking "this idiot needs to research and look up the forums for his common issue."
I can say that while I am new to this page, and also new to andriod dev tools, I am not new to technology or research. :silly:
I've looked at many forums, performed many searches and the like.
If you read all of this and find a simple issue or something I missed, please feel free to condescend and tut tut,
correcting me of my foolish ways.
I'll just jump right into the issue then...
So I'll start by saying that I've downloaded the proper drivers for my Nexus 2013 FLO/wifi.
(See the troubleshooting notes)
I unlocked the device, and used both TWRP and Clockwork (the latest versions per my device nexus 2013 flo)
Booting into either recovery partition, TWRP or Clockwork mod gives me the same error message log upon start.
Code:
ClockworkMod Recovery v6.0.4.7
E: Can't mount /cache/recovery/command
E: Can't open /dev/block/platform/msm_sdcc.1/by-name/misc
(No such file or directory)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Can't open /dev/block/platform/msms_sdcc.1/by-name/misc
(No such file or directory)
TWRP, in essence, gives me the same log.
Troubleshooting notes:
Understand that each of these methods have been done in combination with each
other variation in the multiple categories. It's been a maddening process.
Driver Installation
-Nexus Root Toolkit
-NetHunter Installer
-Android studio bundle
-Manually
(Each time I uninstalled the prior driver before installing the other version.)
Misc
-Attempting to push any mods/rom/img or access storage of any kind
using SDK gives me nothing.
-Typing
Code:
adb devices
gives me a blank space when booted into TWRP or Clockwork recovery.
-I've tried using either recovery image to format my devices storage to a more susceptible file structure,
but same error messages come up
Code:
Error mounting /(any directory)
Downloaded files
latest and second to latest files for
clockwork recovery touch 6.0.4.7-flo
twrp-2.8.6.0-flo
android studio bundle-141.1903250
SU
UWT
Understand simple fixes like shutting off the device and restarting it before taking a certain step or
completely starting over, locking it, formatting to factory image and trying it again have all been attempted,
multiple times in different sequences of iteration. I'm really hoping for a knowledgeable community to come
in and save me here. I bought this device for the purpose of playing with NetHunter on my deployment her in
Kuwait. I have much time, and much more to learn. Help me root this sucker!!!
Thanks guys!
Check out this thread: http://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/mount-recovery-t3064562
I think you're probably having the same issue if you've recently purchased the device, and need to try the MultiRom version of TWRP.
Thanks!
I'll try that and respond with the updates.
-EDIT
It worked!!! Thanks!
Cendrix said:
I'll try that and respond with the updates.
-EDIT
It worked!!! Thanks!
Click to expand...
Click to collapse
Nice! Hopefully the next TWRP update resolves this on the standard TWRP.
OMG thank you... this has been driving me insane, had the same experience as OP with a Nexus we just got a week ago that came pre-installed with 5.x.x... PLEASE someone add the linked info to the guide at the top of the section for this device. Following the instructions there resulted in my uttering bad words around my children because of the lack of indication of this issue.

Occur Error 7 with failuer(Failed to extract dir from "system" to "/system")

Occur Error 7 with failuer(Failed to extract dir from "system" to "/system")
Hi sir,
I try to install miui 8(miui_marshmallow_6.9.29_sprout8) in my device(micromax canvas a1 ) .I also install the twrp(3.2.2-0 somthing) recovery in my device.
But when i try to install the rom in my device, it will geting with the Updater process ended with ERROR: 7 message
I also try the patch which is given with this rom but no solution.
And one more line will be printed above the error line is:
==> Failed to extract dir from "system" to "/system"
please help me sir,
i am tired to do this many time but no solution will occurs
And sorry for any mistake in my message cause my english is not good
Image:
https://mail.google.com/mail/u/0/#inbox/KtbxLxGgKMfRsWZrCRWfSLltDBqpHDbtGq

Categories

Resources