Hi All. I have been trying to google and see if i can track this down, but not having any luck.
Im in Australia and have a Motorola Atrix. I have unlocked the bootloader, Rooted and such on the phone. I installed the AURO Rom, and that all seems to be going swell. I installed Webtop2SD, and that also passes without any problems but after a reboot, i dock the phone and look under the Diagnostics Tab and it still seems to be running the default webtop.
Tried reinstalling, tried re-romming the phone. tried nearly anything i can think of but there are no errors i can see, so no idea where to look at a fix. The webtop configurator does run and seems to work, but not having much luck with anything after that.
Webtop2sd Version: 1.1.0
Mount Executablke Version: webtop2sd/1.1.0
Custom busybox installed: n
Webtop configuration version: 12
Currently mounted webtops: mmcblk0p13
In settings i have:
Webtop Version: WT-1.2.0-110
Kernel Version: 2.6.32.9-MB860-GB-Faux123-V0.1.7
Any suggestions would be appreciated.
Thanks
Busybox fix
You could probably find this by reading through that enormous thread webtop2s discussion, but I'll save you a bit of time since I stumbled upon your question. You are still on the regular webtop since it doesn't show mmcblk1p2 under mounted partitions. I'm 98% sure it's the busybox thing which seemed to happen to a bunch of people while installing. busybox moved or something so what you need to do is this:
http://forum.xda-developers.com/showpost.php?p=16400816&postcount=464
You, My friend have made my day. I have seen the section about fixing the busybox with the ln command but just wouldn't work. but that post has all i needed, ran that and booting off the webtop. Thanks a lot
I have a Korean Tab 10.1 wifi (shw-m380w). It seems there is no development going on with this device on this side of the pond so I'm kind of on my own. There are no ROMs or updates at my disposal so I need to get the kernel off my device before I start flashing new ones onto it.
Here is what I've done and know ...
I've dumped the partitions mmcblk0p1-10. There's a system, cache, etc. which can be mounted via "mount -o loop PATH PATH" and obviously the kernel does not reside in any of those. The remaining partition dumps (mmcblk0p{2,3,6,7,9}) vary in size and I am guessing from past experience the kernel is between 6-8mb. These dumps do not mount as they are not "formatted" like system. cache, etc.
Can anyone suggest how to use the dumped data for getting a kernel that can used to extract initramfs and be flashed in the likely event my kernel does not work as expected? I have seen mention of using a hex editor to locate unique strings that match the kernel start and end points.
Currently the only other option is to wait for another update and extract the kernel from there, but I'd rather not wait and who knows if there will be a kernel in it.
No idea how to answer your question, but since you're Korean: there's a rumor that Korea got the android 3.2 update about 2 weeks ago. Can you confirm/deny? Here's the link:
http://blog.naver.com/PostView.nhn?...0126095295&viewDate=¤tPage=1&listtype=0
(BTW- I can't read it, so forgive me if it's totally wrong. Google translate seems to say that theres a 3.2 update, but maybe something is lost/wrong?)
I'm actually not Korean but don't fault me for that, just live here.
Yes, this model is on 3.2 and at the time I had no plans to work on a kernel, so, I didn't think to store a copy of the update. Kicking myself in the ass now for it.
View attachment 767848
Sent from my SHW-M380W using xda premium
!!! I don't know anything about it but is it possible to use Odin to put CWM on there, then flash an old ROM, then try updating again? I'm sure some of the Devs here would love a copy of the 3.2 update...
I am at a loss, i am at a point where my phone is no longer bound by the laws of logic.
I was running Passion 13.1 ICS
two days ago for some reason i woke up and my phone was asking for a password to decrypt the phone, i though this was weird being that i didnt encrypt the phone.
so i setup ODIN and flashed back to Eugene's Froyo that doesn't brick pre rooted w/re-partition checked.
it passes and reboots after reboot i get
Code:
"E:Cant mount /dev/block/mmcblkop1 (or /dev/block/mmcblk0)
(no such file or directory)
but it will reboot into android
so i booted into android setup adb and copied over the fs tools (Parted, e2fsck, mke2fs, resize2fs tune2fs, and sdparted)
i found that in /dev/block/ the partition files were missing completely so i created them using
Code:
mknod /dev/block/mmcblk0 b 179 0
mknod /dev/block/mmcblk0p1 b 179 1
mknod /dev/block/mmcblk0p2 b 179 2
i can see them there but when i try to partition them using
Code:
parted /dev/block/mmcblk0 mkfs ext2
it returns
Code:
Error: Error opening /dev/block/mmcblk0: No such device or address
so i tried a shot in the dark i tried to write zero's to it
Code:
dd if=/dev/zero of=/dev/block/mmcblk0
it returns
Code:
/dev/block/mmcblk0: cannot open for write: No such device or address
so i rebooted my phone, when it came back up i opened an adb shell and to my surprise the fs tools and the files i created in /dev/block were gone it was like it factory reset it self on reboot.
were i am at now is hardware failure unless the collective minds here can see something that i missed?
i really really REALLY want to save her she has been an awesome phone.
any help would be appreciated
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Instead of the froyo build, you should try 2.1 jfd odin package
Woodrube said:
Dude that sucks. You are I think the 3rd or 4th person to have this happen to. I do also believe that most of whom this happened to (at least in our forum) were running Passion (different variants though). In the Cappy threads, it was CM9 or Doc's. Seems it is totally random when it happens, but I am seriously considering going back to something else unless I get another phone.
Might want to check here for a workable solution.
Sorry for your loss.
Click to expand...
Click to collapse
I was thinking about doing this, but wouldn't it make my phone incredibly slow because of the sd latency?
Dougfresh said:
Instead of the froyo build, you should try 2.1 jfd odin package
Click to expand...
Click to collapse
i tried looking for this but i cant find it do you have a link or a copy of the files?
I'm sure it will slow down but it should boot up and you can load another ROM on there. You do lose your entire internal since it is essentially swapped out for the external. Can't hurt to try with a higher class card maybe.
It seems this is happening to everyone running ICS Passion.
Ya but on the Cappy threads it is happening to people on CM9 and Doc's too.
So I am wondering if anyone on AOKP builds are getting these. I posted in the other two threads about this (the one that you were helping that guy yesterday with and the other one) to see what ROMs/kernels they were running, JIC.
Might be a problem with the port of the AOSP code since it is essentially from NS and GNex, both Sammy products though. Anyone in your NS fora reporting this problem?
Nope, nobody. And I just flashed from 2.3.6 to 4.0.4 2 days ago
I flashed GBBOOT-T959UVJFD in an effort to fix my problem, but its just stuck in a boot loop now. is there a chance that the actual physical memory is damaged?
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Woodrube said:
Chances are your internal is completely locked up and without the encryption "key" you won't be able to use it. Since you know ADB, you still might be able to pull some stuff off it and mount to your PC.
Looks to be that you may need to repartition your external in the thread I posted above.
What Bootloader were you on before this all started?
The file I sent you had GB bootloaders included. So to get into recovery Vol- and Power. To get into download Vol+ and Power.
Click to expand...
Click to collapse
at this point i don't even care about recovering the internal partition i would like to just format it and start over clean.
It had a GB boot loader on it.
This is what is confusing me, in my mind if a partition is locked and i forget the key or in this case it encrypts itself shouldn't i be able to just fdisk or dd the partition back to cleanliness and format it?
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Big Dog KMc said:
When I installed some of the ICS roms (Cant remember which ones, Too many out now) I remember at the very beginning of the post flash setup screens that I needed to Agree to Googles update rules.
I have read that The galaxy nexus and the Nexus S is getting 4.0.? upgrades re-pushed to their phones as the First update in December had a major battery drain bug in it and was stopped.
I have also read that some members reported that They got a "Welcome to your new Nexus....." e-mails.
Could this be caused by an update being pushed to the phone and sense it is a vibrant and not a nexus it is causing these problems??
Click to expand...
Click to collapse
I thought the Nexus had ICS already, so i don't think that was what happened. plus i would think it would prompt the user to apply the update or restart the device.
at this point after reading this thread, i think its hardware failure in my case. otherwise why would it clear everything after a reboot?
TheGioDoodlesII said:
Flash the original stock rom , wipe cache and do a factory reset before and after flashing
Hope i helped :beer:
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I tried that sans the beer LOL i think i am going to need something stronger.
Anythoughts on the SGS 2? HERE
or the NEXUS HERE
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Now, when it boots, I get this options:
Boot webOS
Boot ClockworkMod
boot webOS Recovery
reboot
shutdown
NONE of the options allows me to boot into CM9. I'm missing something?
kwanbis said:
Hello guys.
I just got a brand new TouchPad 32GB. WebOS is very nice, but there are not many applications, so I'm trying to intall CM9.
I have all the drivers installed correctly, I can put the touchpad in developer mode, and USB mode
Problem is, MOST of the links on the guides are outdated. I tried guides here, guides on rootwiz, guides on XDA.
So I started looking for the files myself, and now I have.
e0664157ed69f8999e1c3ee77cdc53ae ACMEInstaller2
7b49b53a9d70315c40dccde9fc20e7a9 ACMEInstaller3
7642f3f0a8090dc52445541a94ed8164 cm-9-20120816-NIGHTLY-tenderloin.zip
980139d6b46b9cbba4db0e07ad17ba5d moboot_0.3.5.zip
1308300f38685d44afde730efd9132cc update-cwm_tenderloin-1012.zip
So I copied all the files from c:\downloads\touchpad to \cminstall on my touchad.
Rebooted into recovery, and did the:
C:\DOWNLOADS\TOUCHPAD>"C:\Program Files\Palm, Inc\novacom.exe" boot mem:// < ACMEInstaller2
The touchpad did some magic, including some linux thing/scorlling, rebooted, but now I'm back at webos.
So, did i forgot something? Should I use ACMEInstaller2 or ACMEInstaller3 (or even ACMEInstaller?).
Thanks.
EDIT: OK. I just realized that the Boot menu gives you some seconds and then it boots to WebOS.
Click to expand...
Click to collapse
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Boot into CWM and then flash the 8-16Nightly file that you have then the latest Gapps 4-29
Sent from my cm_tenderloin using XDA Premium HD app
sstar said:
Your third file should should be renamed so that it reads ,
update-cm-9-20120816-NIGHTLY-tenderloin
And yes use ACMEIinstaller2
I hope this helps
Click to expand...
Click to collapse
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
kwanbis said:
Yeah, I re-read one of the guides, and it mentioned that, so i'm trying again.
Thanks.
Click to expand...
Click to collapse
How did you get on?
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
imeem said:
i personally used this link:
http://liliputing.com/2012/01/how-to-install-android-4-0-on-the-hp-touchpad-cyanogenmod-9-alpha.html
The only thing i did different was that i used the latest version of the files.
Click to expand...
Click to collapse
I did exactly the same.
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
partition repair prior to ACMEinstall3
alienkidmj12 said:
i tried acmeinstaller3 and i was complaining of inode errors ? has anyone else experienced this ? is there anyway of checking the filesystems again for errors, as there was lots of inode fixes maybe it was due to partitian resizing ?
Click to expand...
Click to collapse
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
ACMEInstaller3 is for CM10, not CM9.
not just for CM10
ve6ay said:
ACMEInstaller3 is for CM10, not CM9.
Click to expand...
Click to collapse
As posted by Developer green, it was designed for CM10 in mind to provide a little more partition room to accomodate CM10. It can be used with no ill effects* with CM9 to get that space from the beginning flash of CM9 and then you would be CM10 ready. You are able to use the benefit of a little more system partition than what is deployed with ACMEinstaller2.
I've used ACMEinstaller3 with great success on 6 of the 15 touchpads I help support with CM9. I use ACMEinstall3 by routine now as there is no need to have either ACMEinstall or ACMEinstall2.
* - the use of a few hundred MB from the SDcard to System partition is a small sacrafice of storage space on SDcard with the potential gain of CM10 ready and more headroom for the system, even on CM9.
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
mpgrimm2 said:
I picked up a 32gb TP a few weeks ago.and have just been sitting on it. I was hoping to see some updated guides to simplify my learning curve to get android on it (i know I just need to read and learn). Can't believe I'm so hesitant to do anything with it, but the op's experience seems inline with my expectations of the device at the moment.
Sent from my "Up all night, Sleep all day" EVO3D!
Click to expand...
Click to collapse
I used the same lilliputing site linked above. Like another post said, just plug the md5sum into goo.im and you should find the files.
First time install instructions for CyanogenMod
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Jonas. said:
Just wanted to say this really helped me. And for any of the noobies, if you take the OP's MD5 codes, and plug them into Goo, you will find the files very very quick. And in order for me to download the ACMEInstaller2, I had to change it to a .zip file, and download as such, and then when plugging in the CMD code, just add .zip to the file name, and you're golden. Hope this helps!
Click to expand...
Click to collapse
ZedZardoz said:
If you are partitioned once using ACMEinstaller2, you should ACMEuninstall to remove/repair partitions. After that you can use ACMEinstaller3. Just make sure your CM9 and Gapps file names begin "update-" as you copy them into the cminstall folder.
Click to expand...
Click to collapse
ZedZardoz said:
If you haven't seen these posts by the original Touchpad CM dev, you might want to check em out.
Rootzwiki post by Dalingrin: http://rootzwiki.com/topic/33872-first-time-install-instructions-for-cyanogenmod/#entry947163
The "maintained" instructions list in that post point here: http://wiki.cyanogenmod.com/wiki/HP_Touchpad:_Full_Update_Guide
^^^ There are a couple small inconsistencies here. I'm not sure how to submit to have them corrected.
Overall, this is designated as the official source.
In the top section they list ACMEinstaller3 (although the lower section they list ACMEinstaller)
NOTE: CyanogenMod product designation for HP Touchpad = tenderloin
Click to expand...
Click to collapse
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
Re Files: You have more than enough.
move a copy of ACMEinstall3 to your PCs Palm, Inc folder
rename gapps-20120429-signed.zip to update-gapps-20120429-signed.zip
rename cm9 ROM to update-cm-9-20121007-NIGHTLY-tenderloin.zip
From webOS / USB mode connect your PC and copy your cminstall folder to the tablet. (cminstall folder should have 4 .zip files: CWM, MoBoot, gapps, cm9) when you reboot to Novacom Bootie, you are ready for your ACMEinstall invocation command. Takes about 15 min. to flash.
CyanogenMod is dependent on webOS to be present. You cannot remove webOS. If you are that concerned for space, webDoctor to ver 3.0.0 and never OTA update. That version has the smallest footprint, you might get a couple hundred MB saved, but IMHO, not worth the effort.
The default boot order selects Android after 5 seconds. You can edit this or use a preware webOS app: CyBoot to edit the default and how long to wait in MoBoot before default is loaded.
ACMEinstaller3 handles the partition chores for you. You don't have any CM or other ROM loaded? If you did, you should ACMEuninstall first or to return it to stock webOS. wiping cache is a selection that is done from CWM or TWRP on re-flash of the ROM. You could select ClockworkMod on first boot to do this step, but I have never bothered on an initial load.
I'm currently on cm-9-20121007, the latest nightly.
Good Luck
mpgrimm2 said:
Thanks to everyone who posted. I plugged the MD5's in as suggested, found the liliputin, CM, and jcsullins goo.im sites for files and read/the liliputin guide. I'm sure I will have additional questions for when I get back up later tonight to attempt this, but it looks like I have all the needed files ready plus some extras (screenshot).
For now:
- Do you have to "dual boot" android & webos, vs wiping out webos and keeping only android?
- How much space is WebOS taking up on the "dual boot" setup, ie does it have it's own partitions etc separate from android?
- Can you just turn the device on and have it automatically boot android (WAF = Wife Acceptance Factor)
- When installing roms I have been used to formatting /system, /data, & /cache first. Does AcmeInstaller do this for you. If so, you can just do new rom flashes & backups "manually" through CWM or TWRP right? I keep seeing mention of only wiping "cache" beforehand?
- How would I restore the tablet to stock WebOS, AcmeUninstaller? (I plan on going with AcmeInstaller 3)
- My impression is that the latest CM9 Nightlies are the most stable/functional ICS versions currently available for the TP as a daily driver. Is this correct?
Click to expand...
Click to collapse
The Touchpad's hard drive will show as 27.1gig before installing Android and 25.4 after if you use ACMEInstaller 3 or 25.5 with ACMEInstaller 2 .
You should not attempt to remove webos.
After installation it will automatically boot into Cyanogen/Android with a 5 second delay. To give you the option to change . Both the boot preference and time out can be changed either by installing an app called Cyboot through preware on webos , or by editing the boot folder when running Android.
Use gapps 20120429 and if using ACMEInstaller 3 rename so that it begins update- .
Yes use the latest nightly and rename so it begins update-
Acmeuninstaller will return the tablet back to webos and running Android uninstall from preware will remove moboot .
Install it have fun then you will probably have a few more questions.
Good luck
Thanks guys. I'm up and running on latest CM9.. AWESOME!
Still would like to see someone with a guide here that has up to date links. But the Lilliputin site guide was good minus links.
Sent from my "Up all night, sleep all day" HP CM9 Touchpad