Update:
I've successfully compiled CWM Recovery for my device. If anyone is inquiring on how PM and I will create a post for it. Because of the lack of support getting to that point I will hold on to it for now.
Now that I've compiled this I really dont know what do next.
---------------------
So I've spent a majority of the day looking at this device (hipstreet flare HS-9DTB4-8GB).
What I'd like to do is compile my own ClockworkMod for this device.
I've spend most of the day working on discovering where everything is and backing up everything using ADB.
Information From Device
Current Rom: Softwinerf900_V1.1.7_20121225r587_27d8028 (Found in Current Chinese Recovery, Option 2, Displayed in Center)
Model-Number: HS-9DTB4
Android version: 4.0.4
Baseband version: 1.4rc3
Kernel version: 3.0.8+ (Tue Dec 25 18:20:41 CST 2012)
Build number: 20130118 F900
Memory: 353MB (Supposed to be 512 and is but I've read there is issues with kernel support.)
Processor: ARMv7 Proccessor rev 2 (v71) 1200MHz
Partition Layout and Confirmed Partitions
cat /proc/partitions
major minor #blocks name
Code:
93 0 16384 nanda bootloader
93 8 16384 nandb
93 16 32768 nandc
93 24 393216 nandd system
93 32 1048576 nande data
93 40 16384 nandf
93 48 32768 nandg
93 56 262144 nandh
93 64 131072 nandi
93 72 16384 nandj
93 80 5799936 nandk sdcard (Mounted by vold as /mnt/sdcard and /mnt/secure/asec)
Partition Layout from what I can see follows Allwinner as described in second table on this site:
http://linux-sunxi.org/Android/partitions
Code:
[email protected]:/ # mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 rw,nodev,noatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/vold/93:80 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:80 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.quoord.tapatalkxda.activity-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
I've backed up nanda, nandb, nandc, nandd, nandg just incase with ADB.
(If anyone would like them I have no issue with sharing. Only thing I've done so far is added ROOT and fixed Keyboard issue, which both can be reversed.)
Like I said, what I'd like to do is Compile CWM for this device. I'm currently setting up Ubuntu as a dual boot so I can do this.
My question is what exactly do I need to do to do this. I understand there are many guides on the steps envolved to do this but if someone could provide the links that are rather structured. Also I'd be interested in working on taking this to the next step to work on making a rom for this.
Update: Stage One
I'm currently following mithun46 guide to build my enviroment (installing linux) I'm installing on a tower that I was using to grow my dust farm...
Now when I get to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
What should I actually be using so I can build CWM Recovery?
CWM for Hipstreet
I have the same tablet as you Hispstreet Flare 9" ics 4.0 ...... I would love to be able to flash the CWM recovery to my device and thus be able to install custom rom ...could you please help me out
Thanks its would be much appreciated
Did anyone get anywhere with this? Would love a simple way to root and install custom rom on this. Launchers just don't give me quite the flexibility that I want and it's very laggy when I get too many apps open but hardware specs should allow this to run better. I'm not a dev and knowledge is limited but I can follow steps in order and send feedback if that would help, as long as it's not going to brick it LOL - Hubby would kill me but I am just itching to do more with it.
Lost On Off Switch Function
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
stock roms
tsbrownie said:
I was cleaning up some old installs and somehow deleted the file that controls the on off switch. You would not know which file that would be would you? (And where I might find it?)
Regards,
tsb
Click to expand...
Click to collapse
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Help with stock rom
cr3at1ve said:
Does anyone know where to find stock roms for the hip street devices? Would be greatly appreciated! thanks
Click to expand...
Click to collapse
I have been looking for a stock rom as well as my issue is that it will not boot past the hipstreet flare 2 logo, i'm really not sure what to do now I have tried to contact customer support with no avail.
Any help would be great!!
Thanks in advance
Related
This is a think tank for making 2nd init load aosp based roms. It currently loads only init.rc. Attached below is the zip file I have made of where I currently stand with 2nd init. Please only download it if you want to help fix it. It probably doesnt work yet.
2nd init is further than the attached in this build (This is a full CM build) The script that is currently being hammered out is mot_boot_mode inside of /system/bin/ Also note that I have made the update script work in the build.
http://www.multiupload.com/4QG0NHCRG7
Hope this is what you needed:
http://www.multiupload.com/X0GM6Q60S3
Here ya go extracted boot.img from cm7-atrix nightly
rename it to .tgz as it wouldnt let me upload that lol
This is the ramdisk uncompressed did you need the kernel as well?
Nope, no need for the kernel. Checking those files now.
Edit: That was exactly what I needed, thanks!
K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.
Good luck, this community can be secretive @ times
I suspect this thread will gradually decline like the other so i if can suggest, change the title to status update. And continue to update the top post with the newest info. And a mod might wanna move it to general but i personal think it should be here as it is an active dev project.
I think in this way maybe we can start to have a public dev conversation and perhaps pool efforts from others that have similar goals. I know of a few others that are tackling the same issues for different purposes.
Seems the ways things are set up here it discourages anything but releases in the dev section. Perhaps its time for a dev q&a forum lol ...
Allot of things make our situation unique which draws allot of blank stares in the general dev forums.
EDIT:
Yay 200th post lol
aceoyame said:
K im asking the X and D2G devs for help with how to make it load a hijack zip rather than what it's doing. Hopefully we have this fixed soon. I know whats wrong but I just can't get it to work right. It isn't drawing the screen when I use the wrapper because it doesnt use the task sets so I am seeing if the shell script we use to execute we could make it load a hijack zip.
Click to expand...
Click to collapse
Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?
mastafunk said:
Im not familiar with a hijack.zip this being my first android device.. Is it a zip to replace the contents of the init ramdisk?? If so why not just use some space in /system?
Click to expand...
Click to collapse
As far as I know, it loads 2nd-init via exec command, which init then loads and does a hijack.killall and KILLS everything in sight, and then remounts /system as whatever it's booting so recovery would become /system. I think that's how it works? It's all so confusing to me.
aceoyame: You might benefit from getting in touch with RevNumbers, he does nightlies for the CM 4 Droid X w/ Gingerbread Kernel, so he has a lot of experience with 2nd-init and how to make it work.
0vermind said:
As far as I know, it loads 2nd-init via exec command, which init then loads and does a hijack.killall and KILLS everything in sight, and then remounts /system as whatever it's booting so recovery would become /system. I think that's how it works? It's all so confusing to me.
Click to expand...
Click to collapse
The implementations i have seen launch second init via a bash hijack or a mount script. The other stuff you describe is a function of second init, and not of any hijack.zip. From searching elsewhere it looks like a hijack.zip is a compressed filesystem for 2ndinit potentialy containing init scripts etc.. but i could be way off..
So this may be beating a dead horse but is there source for our specific 2ndinit?
The answer to why ours functions different has to be in there..
Got it. Research indicates the hijack.zip is cm teams answer to keeping the boot image seperate for device which need 2nd-init it is just the boot filesystem should be similar to the files i posted earlier except for a specific device. The Question i am asking is since 2ndinit is up why not parse those from elsewhere, the nameless series roms limited implementation threw them in /system/etc/rootfs why not pickup from there.. or are you intent with trying to make an official port? Does cm maintain the source for the 2ndinit on supported hardware? If so diffing those to the source for ours should put us in a solid direction as far as a cm port goes...
And for anyone that doesnt know where im coming from im a long time linux dev, but fairly new to android and this is my first android device so be nice
2nd init is maintained for supported devices. As for contacting revnumbers... I already was in contact with him lol. I worked with him on the D2G for a lot of things. Really our best contact would be to see if CVPCS can figure out what we need to do exactly. All we need to do is expand that task set but I myself am not sure how it works just yet. If you look in that shell script it calls on the task set and copies init.rc into /system/etc/rootfs. Seems like we need to make ALL of the files for our hijack zip copy into there. Right now the atrix ramdisk should be enough to boot at least. We just need to get it loaded lol. Oh and I don't think CM team actually maintains the Hijack zips, I think they pull it from a seperate repo. But it is maintained for supported devices.
aceoyame said:
2nd init is maintained for supported devices. As for contacting revnumbers... I already was in contact with him lol. I worked with him on the D2G for a lot of things. Really our best contact would be to see if CVPCS can figure out what we need to do exactly. All we need to do is expand that task set but I myself am not sure how it works just yet. If you look in that shell script it calls on the task set and copies init.rc into /system/etc/rootfs. Seems like we need to make ALL of the files for our hijack zip copy into there. Right now the atrix ramdisk should be enough to boot at least. We just need to get it loaded lol. Oh and I don't think CM team actually maintains the Hijack zips, I think they pull it from a seperate repo. But it is maintained for supported devices.
Click to expand...
Click to collapse
Nathan,
CVPCS is on Twitter. I've found that to be the best stream to contact him from. He seems to be pretty responsive. Although, he hasn't posted anything in like 5 days. He seems to have dropped off the face of the earth.
I asked on IRC in #koush and this might be helpful:
(11:30:47 PM) CEnnis91: the only thing i would have to guess is that you're not starting a service that draws the screen
Click to expand...
Click to collapse
Also here is our init.rc uploaded in pastebin, with syntax highlighting. Perhaps it will be helpful, if indeed there is a service that needs to be started, it would probably be in one of these files:
init.rc: http://pastebin.com/kRmnArby
init.mapphone_cdma.rc: http://pastebin.com/qrBpqxGq
init.mapphone_umts.rc: http://pastebin.com/kRmnArby
Btw links #1 and #3 are the same.
I'd like to take a look at several files / outputs from the X2:
Files needed:
/init.rc (or fixed link above)
And the ouput of these adb / terminal commands:
cat /proc/mounts
cat /proc/partitions
cat /proc/cmdline
busybox df
Code:
$ cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mmcblk0p12 /system ext3 ro,noatime,nodiratime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,errors=continue,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p3 /pds ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/block/mmcblk0p17 /preinstall ext3 ro,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/vold/179:33 /mnt/sdcard-ext vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/mnt/sdcard-ext /mnt/sdcard-ext ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=36933d94cc9c5e9b,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
/dev/block/vold/179:18 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:18 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/mnt/sdcard /mnt/sdcard ecryptfs rw,dirsync,nosuid,nodev,noexec,relatime,ecryptfs_sig=36933d94cc9c5e9b,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_passthrough,no_new_encrypted 0 0
Code:
$ cat /proc/partitions
major minor #blocks name
179 0 7747072 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 460800 mmcblk0p12
179 13 512 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 315392 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 307200 mmcblk0p17
179 18 4516864 mmcblk0p18
179 32 15558144 mmcblk1
179 33 15554048 mmcblk1p1
Code:
# cat /proc/cmdline
[email protected] [email protected] vmalloc=224M video=tegrafb console=null usbcore.old_scheme_first=1 tegraboot=sdmmc tegrapart=mbr:1100:100:800,kpanic:2500:400:800 security=tomoyo mot_prod=1 androidboot.serialno=TA05406FDO
Code:
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 206888 56 206832 0% /dev
tmpfs 206888 0 206888 0% /mnt/asec
tmpfs 206888 0 206888 0% /mnt/obb
/dev/block/mmcblk0p12
458562 201471 257091 44% /system
/dev/block/mmcblk0p16
2064204 115632 1948572 6% /data
/dev/block/mmcblk0p15
305420 10287 295133 3% /cache
/dev/block/mmcblk0p3 1980 1139 841 58% /pds
/dev/block/mmcblk0p17
305793 130975 174818 43% /preinstall
/dev/block/vold/179:33
15549952 875136 14674816 6% /mnt/sdcard-ext
/mnt/sdcard-ext 15549952 875136 14674816 6% /mnt/sdcard-ext
/dev/block/vold/179:18
4508040 3258836 1249204 72% /mnt/sdcard
/dev/block/vold/179:18
4508040 3258836 1249204 72% /mnt/secure/asec
tmpfs 4508040 3258836 1249204 72% /mnt/sdcard/.android_secure
/mnt/sdcard 4508040 3258836 1249204 72% /mnt/sdcard
init.rc @ http://iswarm.net/init.rc
Hashcode said:
Btw links #1 and #3 are the same.
I'd like to take a look at several files / outputs from the X2:
Files needed:
/init.rc (or fixed link above)
And the ouput of these adb / terminal commands:
cat /proc/mounts
cat /proc/partitions
cat /proc/cmdline
busybox df
Click to expand...
Click to collapse
I have all those files, I had to pull them for CVPCS a while back. How do those help in making 2nd-init work right. I haven't really looked at em so sorry if it's obvious.
Sent from my DROID X2 using XDA App
Here is a PM I had from dragonzkiller about a week ago.
Hey, I've appeared to lost my old 2nd-init for CM7. I think that I may actually be able to find it later. I know that you can use mot_boot_mode. Basically if you look at the C code for the hijack that is used for the other motorola devices for CM7 it's really close, but I used a shell script instead. These are the thing that have to happen:
1.Remount the rootfs and system directories as rw
2.rename adbd to adbd.old in /sbin
3.setprop ctl.stop runtime
4.setprop ctl.stop zygote
5.setprop persist.service.adb.enable 1 (this might not work, but I have a new method that actually starts it)
6.mkdir /preinstall
7.mount -t ext3 /dev/block/mmcblk0p17 /preinstall
8./preinstall/update-binary 2 0 NAMEANDPATHOFUPDATE.zip
9.cp -f /NEWROOTPATHFROMUPDATEZIP/* / (CM7 creates a directory named /newboot and all those files will get copied to the rootfs)
10.run the hijack.killall script from the CM7 hijack. (NOTE: you must remove all the references to hijack because we're not using the standard method. just use the regular ones and you'll be fine)
11./sbin/taskset -p -c 0 1 (taskset can be in you update zip)
12./sbin/taskset -c 0 /sbin/2nd-init (this should stop 2nd-init and restart with a new init.rc that you created and copied overy after using the update zip)
Here is the way I edited my script, going to test it in a bit here.
#!/system/bin/sh
PATH=/system/xbin:/system/bin
mount -o remount,rw rootfs /
mount -o remount,rw /system
rename /sbin/adb /sbin/adb.old
setprop ctl.stop runtime
setprop ctl.stop zygote
setprop persist.service.adb.enable 1
mkdir /preinstall
mount -t ext3 /dev/block/mmcblk0p17 /preinstall
/preinstall/update-binary 2 0 /system/etc/hijack-boot.zip
cp -f /newboot/* /
/sbin/hijack.killall
/sbin taskset -p -c 0 1
sbin/taskset -c 0 /sbin/2nd-init
I think your looking for 'mv' not 'rename' ..
Can you link me to where you got your implementation of 2nd init, so i can play as well...
How would mv rename it? I didnt get that part, but rename should work I would imagine.
My system doesnt respond to rename mv is the linux equivalent you 'move' the file to a new name, mv oldfile.txt newfile.txt ..
# cd tbin
# ls
mount.sh
unmount.sh
mrw
mro
# rename mro mrx
rename: not found
# mv mro mrx
# ls
mount.sh
unmount.sh
mrw
mrx
#
Click to expand...
Click to collapse
Sorry if i open this thread here again, but i have no right to write in the development forum.
I successfully installed the lates ICS ROM on my folio but i have the same problems other users had/have about the internal SD.
I read about Victor Moreira telling :
"When i go to "Used Space" theres no internal sd card in there.. i know its there because apps thats allow to install some data in the internal SD are doing that but it's not showing, like the "Move to SD" button it's not showing. "
the user ellite gave this solution : "Victor, flash the batelgeuse recovery, then istall the old rom. Once the rom loads an icon with the sd icon will appear in the bar in the bottom, click there and select format. Then, reflash the recovery from the first post and reflash this rom. Worked for me."
I did everything as instructed, i installed the old recovery, installed the previous update-cm-9.0.0-RC0-folio100-KANG-signed-r4.zip, i run it and i was able to see the 1gb phone storage and the internal SD card, i formatted it, than i installed the new recovery and the new rom update-cm-9.0.0-RC0-2011.01.29-betelgeuse-KANG-signed.zip, but i still have the problem, in the new rom i continue to see one big 12.53GB internal storage, while wth CM7 and the old CM9 i saw a 1GB phone storage and a 12gb internal storage.
The problem is that i cannot move apps from the phone storage to the internal SD.
I used the new ICS and it is great, lot better than cm7 but untill i have a solution for this i have to use the old cm7
I hope users that had the same problem as me can contact me and tell me exactly how to proceed , maybe i have wrong files or miss a task .
Thank you
this are some commands i hope could help
df
Filesystem Size Used Free Blksize
/dev 173M 32K 173M 4096
/mnt/asec 173M 0K 173M 4096
/mnt/obb 173M 0K 173M 4096
/system 251M 165M 86M 4096
/data 1007M 20M 987M 4096
/cache 1007M 54M 953M 4096
/mnt/sdcard 12G 48K 12G 4096
/mnt/secure/asec 12G 48K 12G 4096
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p1 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p5 /data ext4 rw,noatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p2 /cache ext4 rw,noatime,user_xattr,barrier=1,data=ordered 0
0
/dev/block/vold/179:7 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:7 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Internal Sd
I have installed ICS yesterday 12/02/2012. The alpha 1 version by Derartem.
At the first installation I had a problem with internal SD. I can look at in with esexplorer or astro but when I download app from market don't install the app in the sd.
I have fix it reinstalling ICS from CWM 5.5.0.4 in this way:
1) format cache
2) format system
3) format data
4) wipe cache
5) wipe dalvik cache
6) factory reset
7) install from sd update-cm-9.0.0-RC0-2011.01.29-betelgeuse-KANG-signed.zip
8) install from sd gapps-ics-20111125-2.zip
9) factory reset
10) reboot system
If you tray it reply a post with the result.
---------- Post added at 01:52 PM ---------- Previous post was at 01:45 PM ----------
I have installed ICS yesterday 12/02/2012. The alpha 1 version by Derartem.
Sameone have problem with USB Host Port?
Before I had CM7.1 and it works perfectly. Now find a new hardware on pc (win xp) but do not install USB drivers and on Folio there is only the USB debug connected.
Sameone can help me? thank you.
ICS CM9 Alpha3 SD Card issue
I did as you told me, but i keep having the same problem.
When i try app2sd it says : The device does not have a real primary external storage, or the primary external storage is emulated. Moving app to SD function may not be supported by this device.
When i check an app that i was able to move to sd on cm7 it doesn't show the move to SD button.
I did this with the latest alpha 3 versione of CM9
Please someone help me
Hello all! I'm sorry for my english.
I am trying to port CWM into my device Huawei Vision U8850, 'recovery mode' compiling from a source code Cyanogen
and i have some errors when starting RecoveryMode
1) E: can't find misc
2) E; Can't mount /cache/recovery/command
3) E: Can't moun( and open) /cache/recovery/log
4) E: Can't mount (and open) /cache/recovery/last_log
My recovery.fstab
Code:
# mount point<->fstype device <-->[device2]
/boot mtd boot
/cache ext3 /dev/block/mmcblk0p11
/data ext3 /dev/block/mmcblk0p8
/misc emmc /data/misc
/recovery mtd recovery /dev/block/mmcblk0p1
/sdcard vfat /dev/block/mmcblk1p1
/system ext3 /dev/block/mmcblk0p7
#/sd-ext ext4 /dev/block/mmcblk0p2
in device "misc" in /data/misc
When i mount "misc ext3 /data/misc" - E: unknown fs type
"misc mtd /data/misc" - E: can't found misc
"misc emmc /data/misc" - Can't open misc
Mounts from device
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p7 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p10 /hidden ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p9 /hidden/data ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/mmcblk0p11 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/ru.dublgis.dgismobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
My partitions
Code:
major minor #blocks name
7 0 24980 loop0
7 1 27660 loop1
179 0 1867776 mmcblk0
179 1 102400 mmcblk0p1
179 2 500 mmcblk0p2
179 3 1500 mmcblk0p3
179 4 1 mmcblk0p4
179 5 8192 mmcblk0p5
179 6 8192 mmcblk0p6
179 7 253952 mmcblk0p7
179 8 1122304 mmcblk0p8
179 9 81920 mmcblk0p9
179 10 32768 mmcblk0p10
179 11 204800 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 8192 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 32 3929088 mmcblk1
179 33 3924992 mmcblk1p1
254 0 24979 dm-0
Can be corrected in the boot init.rc section, but then what rights the user and group, options set?
Please help me. Thanks...
Cant help you but good luck for you, i have that phone and i really would like cwm
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 http://yadi.sk/d/R4p2T6b30Edt
Click to expand...
Click to collapse
Anyone confirm this is working?
Anyone confirm this is working?
Click to expand...
Click to collapse
Only russian users from http://4pda.ru/forum/index.php?showtopic=257207&st=2320 and http://4pda.ru/forum/index.php?showtopic=358221&st=280 May be problem if you device sim-lock.
Ok, thanks. Im MAYBE trying this
Sent from my Vision
in this firmware original bootloader. and the possibility of obtaining brick is zero %
GriefNorth said:
in this firmware original bootloader. and the possibility of obtaining brick is zero %
Click to expand...
Click to collapse
really? have you installed it?
Sent from my Vision
yes
so is it for 2.3.5 version or 2.3.7 , cos i have 2.3.5
Sent from my Vision
this is full firmware 2.3.7
GriefNorth said:
this is full firmware 2.3.7
Click to expand...
Click to collapse
and its based china version? because on not chinese
Sent from my Vision
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
GriefNorth said:
Yes it's china version, after installing change language. China because file system ext4 switch off on my official firmware (russian), but in chaina firmware ext4 switch on in kernel and used. CWM recovery not working with ext3.
Click to expand...
Click to collapse
ok, but can i change back to original if i dont like that?
Sent from my Vision
Yes...
GriefNorth said:
I did this.
If any interested for CWM Recovery 5.0.2.8 for Huawei Vision U8850
This is firmware based on chaina firmware V100R001CHNC00B307SP20 with kernel 2.6.35.7 and i added root + CWM_recovery_5.0.2.8 ...... ...
Click to expand...
Click to collapse
I have many problems with this firmware. Keyboard isn't contained and every keyboard I install won't work - it disappears every time i write one letter.
And the second problem is that CWM is not working for me. It is there, but I can't do anything in it, because back button is not working.
Is there anybody else having the same problem?
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
GriefNorth said:
i'm sorry, this firmware not have a keyboard, you should install any keyboard from google market. And in recovery going on the last position and press Vol+andVol- (at the same time) then show @Back button menu [email protected]
Click to expand...
Click to collapse
Thanks, I'll give it a second try.
try it's all works, without keyboard *sorry* )))
Oh, the "back button" I ment was the one used for confirming an action in recovery, that one is not working for me, when I use it, the selected action will not perform, nothing will happen, so I canť do anything in it, because there's no working button for confirming actions. Do you know what I mean? I'm not that good at english, so I don't know how to express some things
I tried to downgrade to 148 to get the cm install to work. Lost access to internal storage. I was using twrp 2.8.7.0 or 2.8.0, flashed the rooted stock ROM from another post here and lost access. I've tried the su command "restorecon -v -R /data/media" and now I can see the internal storage from the settings menu but not change the location from there.
Here is my terminal command "mount" result
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /dev/frz cgroup rw,relatime,freezer 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/platform/msm_sdcc.1/by-name/log /log ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,relatime,noauto_da_alloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/vold/179:65 /storage/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard1/.android_secure tmpfs ro,seclabel,relatime,size=0k,mode=000 0 0
[email protected]:/ $
What do I do now? I want to install the cm preview
Thanks for your time
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
xordos said:
CM12 and all other ROMs require you update your phone to Lollipop, B3xx.
Click to expand...
Click to collapse
And I'm ready to do that but I'm stuck in 4.3 with no access to the internal storage when I try to flash a new ROM. I'm thinking about going back to the recovery and get the ota update again and trying the cm install from there. Opinions?
Update* I got back to stock 309 with no ability to ota upgrade or install cm via twrp. Twrp still reports "unable to mount internal SD" but I have been able to browse, read, and write to it through the preloaded file explorer, after the "returncon -v -R data/media/" command through terminal in twrp 2.8.7.0.
once you are in 309, follow the cm install thread, and no need to worry about internal storage, at least for now.
copy rom and gapp to sdcard, which is called external storage, and flash it in twrp.
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
notshure said:
Getting stuck still at install in twrp. Cannot post a link to a screenshot so I'm gonna try to type it out. "this package supports bootloaders ... This device has boot loader unknown." And "e: error executing binary inside of zip..." I've tried all three of the custom ROM zips, cm, carbon, and PAC ROM with the same results.
What now?
Click to expand...
Click to collapse
Unmount in lollipop and format it. Or re run b309.
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
xordos said:
Also that unknown bootloader error, one reason is you didn't flash the twrp recovery from that CM preview thread 1st post. You have to flash that recovery image even you already have working twrp.
Click to expand...
Click to collapse
then there was cyanogen and much rejoicing. Thanks :good:
Dear XDA-Developers members, I have acquired a Mediatek MT6572 chip phone ("Jiake M4" brand) running Android Kitkat 4.4.2, and am trying to root it or install a better ROM in order to get rid of possible malware on it. I need help understanding what to do - there are a lot of mediatek related guides, but I am unsure if any of them apply to my situation. At the end of this message I have tried to put as much information as I can find about the phone - let me know if there is anything more I could find out.
What I have already tried to do:
- The stock ROM on the phone contained malware/adware - ad overlays on the browser etc.
- I downloaded a ROM from EasyFirmware.com and installed it using the SP Flash Tool. However, it turns out the ROM is slightly incompatible: camera picture is vertically flipped. I can live with that, but I think the phone still may contain some malware apps/processes: it shows some app ads in notifications, and autodownloads some "feedback" app.
- I would like to download some other MT6572 rom and "port" it, which I understand is needed for Mediatek devices. But I am unsure how to do it: all the guides I have seen start with requiring a backup, and that in turn requires root.
- A root checker app I downloaded said the phone is rooted but I think the phone/rom does not have a "proper" root, as I do not have a visible "SuperUser" app and I am unable to run root browser/busybox/superSU without error. Details below.
- I also tried downloading a version of MT Droid Tool and pressing the "Root
I am not sure how to continue from here:
- Should I try to install a "proper" root, how could I do that?
- As far as I understand, porting another rom requires copying some files from the stock ROM to the ROM I want to install. I don't have the stock ROM, only the one I installed (link below): will the contents of that work in place of the stock ROM, since I was able to install it on the phone? I am also unsure which files to copy - basically, I am willing to try any ROM you think would work for the phone.
Basic phone details:
-------------------------------------------
Brand: Jiake M4
SoC: MediaTek MT6572
CPU: ARM Cortex-A7, 1000 MHz, Cores: 2
GPU: ARM Mali-400 MP1, 500 MHz, Cores: 1
RAM: 512 MB, 266 MHz
Storage: 2 GB
Memory cards: microSD, microSDHC
Display: 5 in, TFT, 480 x 854 pixels, 24 bit
Battery: 2800 mAh, Li-Ion
OS: Android 4.4.2 KitKat
Camera: 1600 x 1200 pixels
SIM card: Mini-SIM, Micro-SIM
Wi-Fi: b, g, n, Wi-Fi Hotspot
USB: 2.0, Micro USB
Bluetooth: 4.0
Positioning: GPS, A-GPS
-------------------------------------------
Currently installed rom: "Jiake-M4_4.4.2_MT6572_SCATTER.7Z" from https://easy-firmware.com/index.php?a=browse&b=category&id=13386
How did I install it: by using the SP Flash Tool that came with the ROM download.
Contents of the ROM:
-------------------------------------------
30-Oct-14 02:36 AM 4,216,832 boot.img
30-Oct-14 02:36 AM 6,152,400 cache.img
19-Aug-15 01:20 PM 308 Checksum.ini
04-May-13 01:21 AM 167,936 CheckSum_Gen.exe
19-Aug-15 10:26 AM <DIR> database
30-Oct-14 02:36 AM 512 EBR1
30-Oct-14 02:36 AM 264,796 lk.bin
30-Oct-14 02:36 AM 244,889 logo.bin
30-Oct-14 02:36 AM 512 MBR
30-Oct-14 02:36 AM 7,213 MT6572_Android_scatter.txt
30-Oct-14 02:36 AM 100,812 preloader_yuanda72_cwet_kk.bin
30-Oct-14 02:36 AM 4,593,664 recovery.img
30-Oct-14 02:36 AM 135,168 secro.img
30-Oct-14 04:07 AM 646,223,152 system.img
30-Oct-14 02:36 AM 24,158,776 userdata.img
Contents of the "database" subdirectory:
30-Oct-14 02:36 AM 164,284 APDB_MT6572_S01_KK1.MP7_
30-Oct-14 02:36 AM 5,562,957 BPLGUInfoCustomAppSrcP_MT6572_S00_MOLY_WR8_W1315_MD_WG_MP_V43_1_wg_n
-------------------------------------------
"About phone" details:
Model number: V9 (notice this is not the same as M4! Apparently the ROM I installed was designed for V9 instead of M4)
Android version: 4.4.2
Baseband version: MOLY.WR8.W1315.MD.WG.MP.V43, 2014/09/17 10:10
Kernel version: 3.4.6 [email protected] #1 Mon Oct 20 14:43:01 CST 2014/09/17
Build number: A100_72KK_KK_3G_EMMC_32_4_XLD_Z10 20141028-170856
Custom build version: 1414486936
Developer options: USB debugging is enabled.
Recovery details: I can enter recovery by holding the power button and volume down at bootup.
The phone has the following recovery:
Android system recovery <3e>
A100_72KK_KK_3G_EMMC_32_4_XLD_Z10 20141
Installing and opening Root Browser says: "Unfortunately, Root Browser has stopped."
Installing and opening BusyBox Free says: "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is inproperly rooted. Try removing superuser/supersu permissions, uninstalling this application, reinstalling this application, and then regranting superuser/supersu permissions for this application. You can check your device to see if it is properly rooted by downloading RootChecker from the Android market."
Installing and opening SuperSU Free says: "SU Binary occupied"
Installing "Terminal Emulator for Android" and typing 'mount' says:
-------------------------------------------
rootfs / rootfs ro,seclabel,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/secure tmpfs rw,seclabel,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,seclabel,noatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,seclabel,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:7 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:7 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
-------------------------------------------
Hi, I have a similar mobile phone, did you find a solution?