I have tried installing Android on my TouchPad by using the rootzwiki, XDA, Idiots Guide 2.0 on YouTube and it just wont install. I have double-checked and triple-checked every step in the guides and it still will not install moboot.
When I go into USB mode and input the commands on CMD it wont do anything and it will stay in USB mode and wont go into double-penguin mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have installed Android on this touchpad before but I didn't like the early CM7 builds so I uninstalled Android and just used stock WebOS. Could that be the problem or are the guides outdated?
Is there a different method to installing Android on the Touchpad?
liftedngifted1 said:
I have tried installing Android on my TouchPad by using the rootzwiki, XDA, Idiots Guide 2.0 on YouTube and it just wont install. I have double-checked and triple-checked every step in the guides and it still will not install moboot.
When I go into USB mode and input the commands on CMD it wont do anything and it will stay in USB mode and wont go into double-penguin mode.
I have installed Android on this touchpad before but I didn't like the early CM7 builds so I uninstalled Android and just used stock WebOS. Could that be the problem or are the guides outdated?
Is there a different method to installing Android on the Touchpad?
Click to expand...
Click to collapse
It's been a while since I installed android, but for CM9, I think you have to use Acmeinstaller 2.
After the CM7 methods did not work, I tried the CM9 and ACMEInstaller2 methods and it still didn't work.
liftedngifted1 said:
After the CM7 methods did not work, I tried the CM9 and ACMEInstaller2 methods and it still didn't work.
Click to expand...
Click to collapse
Hmmm.. The only thing I can think of is doctor the TP and do a fresh install for android.
chicle_11 said:
Hmmm.. The only thing I can think of is doctor the TP and do a fresh install for android.
Click to expand...
Click to collapse
What do you mean by doctor? Like reset the touchpad to factory settings? Because I have done that already.
liftedngifted1 said:
What do you mean by doctor? Like reset the touchpad to factory settings? Because I have done that already.
Click to expand...
Click to collapse
WebOS Doctor. Read here : http://www.webos-internals.org/wiki/How_To_Recover
You said USB mode - do you mean in WebOS or within the USB loading screen ?
Also, try re-downloading the files from RootzWiki - ACMEInstaller2, moboot, cwm, and the Alpha2 ROM zip. Make sure they're placed in the proper folder on your /media partition (/cminstall, no spaces, no caps), and try that again.
Barring that, you can always try going to THIS THREAD and resetting your TP to factory - it's the most comprehensive way to clear it and start fresh.
Related
Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language
This is what appears on display after running ACMEInstaller3.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess the problem is the difference between the reported free space, and the the real free space on system.
How can I fix that?
Gabonjour said:
Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language
Click to expand...
Click to collapse
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244
chicle_11 said:
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Thank you very much but... I cant access to Touchpad as root user when using novaterm in windows and linux. It doesnt say [email protected] It only shows a "]" symbol. When I type "lvm lvscan" or any other command, it says "This command doesn exist"...
Hi!
I have a dual boot teclast x98 c5j6. I had problems with battery, so I tried to install android 4.4.4. During the flash I think I selected to delete partitions, and know, when I power on the tablet, in the dual boot menu I can only see android logo, and not both logos like before. How can I solve it?
thanks!!
I have the same problem. I've choosed the wrong xml file during the flash...
Enviado desde el móvil
Did you solved the problem? I have the same issue. I tried to install stock ROM, I have chosen no partiotion but my system partition size is 1GB and system.img was litte over 1GB and flashing stoped at 86% with error. Then i flashed Mirek Lolipop v6 but it is only android logo on dual boot. When i use "boot to Windows" under android it shows error like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Is there aby chance to bring Windows back?
Did you solve your partition problems
Dear friends,
did you solve your partition problems? i have the same. My android partition works perfect, but the windows partition isnt more there.
cheers
Hasan
Unfortunately no, I had to reinstall Windows
no usb boot
hello thank you for answering,
i would like to reinstall windows, but there is no more a windows partition.
I installed before windows 10 manually, but when i trying now to do the same, its not booting from the usb stick anymore. I flashed again the bios ver. 2.02. without any success. has somebody any idea?
chinahasan said:
hello thank you for answering,
i would like to reinstall windows, but there is no more a windows partition.
I installed before windows 10 manually, but when i trying now to do the same, its not booting from the usb stick anymore. I flashed again the bios ver. 2.02. without any success. has somebody any idea?
Click to expand...
Click to collapse
Use the OTG USB installation method mentioned by some fellas in the official Teclast X98 forum.
Format a FAT32 thumbdrive.
Copy the 5 *.img files, installer.cmd and partition.tbl to the root of the thumbdrive.
(Ensure u got the right installer.cmd and partition table setting files, view it to confirm).
Connect the OTG cable along with the plugged-in thumbdrive.
Bring the Tablet to Droidboot Recovery Mode (The one with a Big Green Android if original recovery image).
It will automatically start recovery and reboot.
hello kevinlaikf,
thank you for your suggestions, but didnt work. the menu still shows "entering nx mode. waiting for fastboot command". thats it. i copied all the files you mention.
cheers
hasan
Hello, have anyone found any solution to thiw problem? unfortunately it is mine too.... please help me, i need windows back...
So I have this Asus MeMO Pad 7 which I tried to flash. I can't honestly remember what I did exactly, just followed some commands from tutorials online and I got it bricked.
It looks like the image attached below, the Aptio BIOS on a tablet. Do I need to bother buying an OTG cable and plug in my keyboard? I saw a thread in 2015 with someone having the same issue, but there is no answer.
I know I bricked this tablet, went with it to the service, but I have a feeling they didn't try hard enough or are not knowledgeable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
brickedasus said:
So I have this Asus MeMO Pad 7 which I tried to flash. I can't honestly remember what I did exactly, just followed some commands from tutorials online and I got it bricked.
It looks like the image attached below, the Aptio BIOS on a tablet. Do I need to bother buying an OTG cable and plug in my keyboard? I saw a thread in 2015 with someone having the same issue, but there is no answer.
I know I bricked this tablet, went with it to the service, but I have a feeling they didn't try hard enough or are not knowledgeable.
Click to expand...
Click to collapse
Solution for next time: Don't follow random commands from tutorials online.
If you end up in the UEFI setup utility every time you start the tablet, you've likely managed to destroy your bootloader. You could try to buy an OTG cable, plug in a keyboard and an USB stick with a Linux live system and use that to restore it, but generally this is not necessary because these devices come with another recovery mechanism called "DNX mode", that allows restoring the bootloader.
With your tablet turned off, press Volume Up + Volume Down and then the power button. If it displays "Fastboot starting..." there is still hope.
Install Fastboot on your PC. If you haven't done it already, there are many tutorials out there with instructions how to install it. You can take a look at https://wiki.lineageos.org/adb_fastboot_guide.html for example.
Connect the tablet to your PC and on a command line, type "fastboot devices" and check that your tablet shows up.
Download the firmware from ASUS: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip and extract "esp.zip" and "droidboot.img" from the ZIP. Open "esp.zip" and extract "EFI/Intel/efilinux.efi".
On the command line, switch to the directory where you have extracted "efilinux.efi" and "droidboot.img", then run "fastboot flash osloader efilinux.efi" and "fastboot boot droidboot.img".
With a bit of luck that might bring up Droidboot and allow you to access the recovery to install the stock ROM correctly again... Good luck!
Hello, I am a owner of a ZUK Z2 Pro from Brazil, apologies for my english.
I tried to update the mooke rom to pie, but it wasn't working via central mooke, so I downloaded and tried to flash on TWRP, but I was possesed by a demon and instead of not deleting the internal storage, I delete all files. The problem now is that the mobile isn't reconigze in the computer and the device manager shows this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The USBView show this:
Maybe it's something related to the vendor folder that can't be mount on TRWP. I tried adb push, but don't display my device and I don't have acess to allow the usb debugging. I tried USB OTG, but the pendrive is unrecognized. I don't know what to do anymore, but I don't think the mobile is bricked. May day may day!
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
craftandbuild said:
In twrp you have to click mount otg to make it visible in the file system (if you already did this you can try different adapters/usb sticks). If you deleted the vendor partition I think you should be able to fix it by going back to stock or finding a vendor image/backup. If the only problem is that you ran the vendor to factory script and now twrp dies not find it you can just update twrp. Updating twrp could also help with the unrecognized usb issue.
Click to expand...
Click to collapse
I can't mount otg because twrp don't let me selected the option, I had install all drivers I found of zuk, lenovo and qualcomm and still unrecognizable on the computer, therefore I can flash stock or the vendor image/backup, the version of my twrp is the 3.3.0.0, the most updated. You know if there is a way to force the computer to recognize the device?
Solved doind this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
brian_says_yas said:
View attachment 5517961
I previously successfully installed and ran lingeageOS for a long time. In attempting to flash stock android, I'm getting a part-way successfully then failing to a screen titled 'fastbootd' when the flash script attempts to enter userspace fastboot. I'm running Arch Linux and have android tools installed locally as well with the android-tools package. I can start the device into fastboot mode and see it on my PC with `fastboot devices`:
$ fastboot devices
13091FDD4000GY fastboot
I would prefer to install android 11, but I've also tried android 12 with the same end failure result.
How can I troubleshoot this further? Any help is much appreciated!
Click to expand...
Click to collapse
Hi Brian, have you tried a different usb cable? I only use windows so I can help more if you get a windows PC or run windows from a usb. I also unlock the bootloader manually with the ADB tools, first before using the flash tool.
So I switched to a macbook and a different USB cable both at the same time, and it worked. I'm speechless lol. Thank you for your help! Honestly the biggest benefit here is that I don't have to use Android 12 yet which was buggy as hell on my Pixel 6 Pro before someone did me the favor of stealing it in Miami.