** This is only needed for those that tried to apply the update and it failed. **
So I saw a tweet from our friends at WebOS Internals that people were having issues upgrading their Touchpads to WebOS 3.0.5 with Android (CM) installed. Their suggestion was to run the Android Removal utility from PreWare and reinstall after the upgrade. I didn't want to go through a reinstall of CM so I came up with the follow instructions. It worked well for me, I hope it works for you...
** As with anything you do to your device, this is done at your own risk. **
These instructions are for Windows but you should be able to easily adapt this to your OS of choice. You will need to have Palm/HP's novacom drivers installed.
Boot the Touchpad into WebOS and attach your Touchpad to your via USB in Charge only mode.
Run ->
Code:
"C:\Program Files\Palm, Inc\terminal\novaterm.bat"
From the menu File --> Connect and Accept the little pop-up.
Run these commands at the shell prompt to create a new directory on the /media partition, copy your uImages to the /media partition, remount /boot and delete the Android related uImage files from /boot. You may have an error deleting one of the files if you don't have CWM or TWRP installed.
Code:
mkdir /media/internal/uimage
cp /boot/uImage.* /media/internal/uimage/
mount -o remount,rw /boot
rm /boot/uImage.CyanogenMod
rm /boot/uImage.ClockworkMod
rm /boot/uImage.TWRP
Do the update via the WebOS System Updates app. Once the update is complete do the following:
In NovaCom do File --> Connect again.
At the shell prompt execute the following:
Code:
mount -o remount,rw /boot
cp /media/internal/uimage/uImage.CyanogenMod /boot
cp /media/internal/uimage/uImage.ClockworkMod /boot
cp /media/internal/uimage/uImage.TWRP /boot
That should do it. Once you reboot your TouchPad you should be able to get into CM/Android.
Nice post+ I will be testing this out Tom
I updated to 3.0.5, and it would not boot back into CM7 (reboot spin), so I went into recovery mode, and re-flashed the CM7 3.5 Alpha zip file, and it all worked for me.
Just did this on my touchpad, worked like a charm. Thanks!
Thanks nice information
I updated webos and had no issues. You should probably make a nandroid beforehand just incase you have to doctor. You can always restore after you put mboot and cm back on. I have mboot 0.3.5 too.
Sent from my GT-i9100 using Tapatalk
Worked great, thx for the info
Good info!!
Thanks
Personally I upgraded before seeing this and I only removed uimage.TWRP and it worked for me. (I also uninstalled UberKernel as a precaution)
Did this and it updated it but now I can't get into moboot any suggestions?
i get read only file system on first mkdir command
can;t proceed
lvpre said:
I updated webos and had no issues. You should probably make a nandroid beforehand just incase you have to doctor. You can always restore after you put mboot and cm back on. I have mboot 0.3.5 too.
Sent from my GT-i9100 using Tapatalk
Click to expand...
Click to collapse
I guess I was one of the lucky ones too because I didn't have any problems updating webos either. I did the system update from the app in webos to go from 3.0.2 to 3.0.5 and when it was done it rebooted into webos and said the update was successful. Once I powered it off and back on moboot was intact and cm7 booted normally. This thread was my backup cause I was definitely crossing my fingers lol. Now I'm off to get alpha 2!
Followed your instructions, performed the update over CM9 a2.
All is good, thank you.
With CM9 A2 released I finally took the plunge and left CM7.
I uninstalled uberkernal in webos, used webosdoctor to upgrade to 3.0.5 without any issues, and then loaded up CM9 with the latest gapps, CWM, and moboot.
Related
Okay, I've seen a few people and various threads with this problem:
1. They have a rooted Optimus V
2. they may or may not have flashed a recovery
3. they download ROM Manager and select ROM Manager's Clockwork Recovery
4. they flash a rom and reboot
5. they get stuck in a recovery loop and run around screaming.
This was me yesterday!!
What did I do, then? I downloaded the Fastbootroot tool. That got rid of the ROM Manager's CW Recovery and put in thunderc-v-1.1.0 version recovery... that looped. I tried the 1.2.0 version, which also looped, but I could flash a different recovery, finally. So I downloaded Xionia's Clockwork Recovery and THAT worked. (this next excerpt is from my androidcentral forum post)
here's exactly what I did starting from the thunderc-v-1.2.0 recovery (i'm gonna go into too much detail for other eeijits like me):
download xionia's clockwork recovery and the flash image, unzip both onto your sdcard
put your desired rom on your sdcard (zipped, omg)
get out of usb storage mode
Get ADK Tools if you don't have it (search the forum, this is the easy stuff)
Make sure you're all mounted in mounts and settings in your current recovery.
open cmd, and get into adb shell
(this next part is from zefie's post)
enter the following commands:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /sdcard/xionia_cwma_12518.6.img
# reboot recovery
it should reboot into xionia's clockwork recovery mod
clean dalvik cache and mount everything
choose 'fix recovery loop' under ... advanced IIRC, I can't check right now as I'm reloading my stuff onto the fixed phone
after the loop's fixed, get back into recovery and load whatever ROM you fancy.
WIN!
Recovery loop from ROM mgr backup restore...tried Kiona, tried mmarz, what next?
Newb here...BUT, in my defense...I DID NOT DO AN ANDROID SYSTEM RESTORE ON MY ROOTED PHONE!! which seems to be most people's problems with boot/recovery looping. My phone is stuck in a recovery loop after restoring a Clockworkmod backup.
History: I rooted my LG Optimus V running 2.2.2 with gingerbreak a couple of months ago. Per all instructions I could find, I installed SuperUser, Rom Manager, Titanium Backup, I also have another backup by Rerware, but I can't remember the name of it. I kept the stock ROM. Everything has been working fine.
I got a 32 gig micro card for Christmas. So, as per instructions found elsewhere, I made a backup to my sd card with ROM Manager, Titanium and Rerware. I copied my sd card to my hard drive, partitioned my new sd card, and loaded the new sd card with the old sd card data. At that point everything looked fine. But the instructions said to restore from my backup which I did with clockworkmod and now I am stuck in a recovery loop.
I completed Kionia CWMA install 1..4 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed Kionia CWMA install 1..6 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed the abd shell instructions "strings/dev/mtd/mtd8" and "flash_eraseall /dev/mtd/mtd8" per mmarz but it did not fix the issue.
I have recovery access. I have ADB running.
What should I do next? Everyone else seems to be fixed with mmarz's suggestion...
Thanks to whoever is out there for any help...
rom manager is mostly no good on V and the new V screen {after sept.} gets ruined alot by rom manager, so i wouldn't use it
get a compatible recovery at the iho wiki and install
then flash the rom of your choice
if that doesn't work there is lots of help for this in the optimus v "development" section
Thanks for your reply. I just wasn't sure what I should do next and your suggestion worked perfectly. And I guess I had to get over the fact that I was going to have to restore from scratch and get over my fear of installing a custom ROM. Luckily, of all the backups I had, Titanium worked BEAUTIFULLY! I was chicken to flash a custom ROM, but I flashed IHO Harmonia and it is beautiful and has been working flawlessly ever since. I shouldn't say flawlessly, I kept getting some gapps error but I was able to look it up easily and fix it.
Live and Learn.
the latest version of rom manager in market has bug... so we can use older version search on google. And it works again
Sent from my LG-P500 using xda premium
I was running Bricked Kang but installed the new build of cherry but now the old bricked rom's kernal is still a boot option, how can i remove this kernal from my touchpad and delete the entry in moboot?
I had the Bricked installed myself, and decided to go back to the stock CM9 kernel (since I was having FC issues with certain apps).
Here's what I did:
Open up Terminal Emulator
Type the following:
Code:
su <enter>
mount -t remount,rw /boot <enter>
cd /boot <enter>
rm uImage.CM <tab> <enter> (press Tab until the CM-Bricked is filled in)
echo "CyanogenMod" > moboot.default <enter> (this will set you back to defaulting CyanogenMod. If you want another, use the name of the uImage.<whatever> for Cherry (just put everything after the uImage. part)
reboot <enter>
That'll remove the Bricked Kernel from your boot options, and set your default to Cherry (or in my example, CyanogenMod). Make sure you have the proper Wifi modules installed from your Cherry install, and you should be good to go.
Hope that helps, mate.
I'm having the same problem and that proposed solution did not work...I got a Read only file error...thanks, though...
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
ve6ay said:
You have to make sure you mount the /boot partition before you try and do the changed. If it isn't mounted, you get that error.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Could you elaborate on how to do that please? The CM_Bricked thing has been bothering me as well.
Thanks in advance!
I had the exact problem and instead of playing around with the instructions I just went to a backup I had before the install.
It worked like a charm for me. If you have a recent backup on CWM don't hesitate to use it .
Basically on my moboot, I have the option to boot into about 6 different things and that's unnecessary.
I have the options to boot into:
WebOS
Cyanogenmod
AOKP
CM Bricked Kernel
Clockworkmod
WebOS Recovery
How I got it this way, I'm not entirely sure because the way the TP works is different than anything else I've used.
How can I delete all the extra boot options besides WebOS, AOKP, CWM, and Recovery?
Do I have literally like 6 partitions going on or what?
A bit lost here.
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
I would use the Terminal emulator, and issued the following commands:
Code:
- su
- mount -o rw,remount /boot
- cd /boot
- rm uImage.CM*
- rm uImage.Cyano*
- echo "AOKP" > moboot.default
- cd /sdcard
- umount /boot
- reboot
Then you'll have those two images removed, and be back to booting by default to AOKP.
haxin said:
Go into /boot and delete the uimage.* for the boot that you want to remove for example uImage.AKOP that should do the trick.
Click to expand...
Click to collapse
You should be able to do this from a root explorer in Android. This is what I do, but generally in IntrnalzPro in webOS (make sure to enable master mode). When I get too many boot items they usually fail to boot android. It might be because I have CWM and TWRP. There is only so much space for those uImage files, when that space is full they don't get created right and it won't boot. Since CM9, this has been my only reason to boot into webOS.
Sent from my Galaxy S II (i777)
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
I Am Marino said:
So all I have to do is go delete the .image in /boot?
I had messed around in there before and didn't know it was that simple.
Click to expand...
Click to collapse
Yep, that hard part is getting r/w access to the folder.
The files will be uImage.[ROM name] not *.image
Sent from my Galaxy S II (i777)
I have Root Explorer so it shouldn't be too hard I'd imagine.
I got it fixed, so thanks everyone.
moboot uimage and tga cleaner
download the moboot uimage and tga cleaner under beta on classicnerd.net then flash that. It should clean it up.
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
iman38 said:
Hello All,
I'm new here. I believe I supposed to write a reply to this thread, but I couldn't. So, sorry to all mods.
Anyway, after applying battery hack files (services.jar & systemUI.apk), my RAZR is now stuck on boot.
However, I can connect my handset to PC and access the shell via ADB. The problem is, silly me, I was so excited that I forgot to backup the services.jar & systemUI.apk in same directory. It's on the sdcard however.
How to mount the sdcard onto the android system, so that I can overwrite the files by original ones from the sdcard?
I'm using XT910, it was AsiaRetail, but I flashed using the latest eu.en.33 & deodexed, which was working fine.
Any helps are appreciated. Thanks.
Click to expand...
Click to collapse
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
sevenup30 said:
when you say stuck on boot, do you mean bootloop?
If you were on deodexed system it should work i don't see why...
Anyway if you have a backup of your file it's fine, if you don't have i'll send it to you in 2hours.
Code:
adb shell
su
cp /sdcard/SystemUI.apk /system/app/
cp /sdcard/services.jar /system/framework/
reboot
No need to mount sdcard it's mounted automatically.
Maybe the change i made, make it unworking on .33. I tried on it before the 1% just with toggle so maybe it's not working.
Click to expand...
Click to collapse
Yes, I deodexed using xUltimate 2.4.2 ; Deodexing was successful and my phone was running fine after deodexed.
So my only suspects are the services.jar and systemui.apk
It's not bootloop, it's stuck on the Motorola Animation. Normally, it would vibrate and enter the android, now it's stuck there. But as I said, I can connect using adb and access su.
The sdcard is not mounted (I guess the boot process halted somewhere before it mount the drives automatically).
So, do you know the exact command to mount the sdcard? external sd card in my case.
Btw, if I reflash using the fastboot file, SPDREM_U_01.6.7.2-180_SPU-19-TA-11.2_SIGNEuropeAustraliaEMEA_USASPDRICSRTGB_HWp2b_Service1FF_fastboot.xml.zip from droid-developers, will it work? I'm afraid it will make it worse, so I need confirmation before the last resort of re-flashing my phone.
Btw, I was using battery app and tick the 1% hack, it did show 1% decrement, but have it's own notification. If your patch works, then it's great
tia
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
sevenup30 said:
Try:
Code:
busybox mount -t vfat /dev/block/mmcblk0p1 /sdcard
or
busybox mount -t vfat /dev/block/mmcblk0 /sdcard
or try to fastboot this one:
http://forum.xda-developers.com/showthread.php?t=1747800
might be the same as you mentionned, latest fastboot ICS for EN.EU
Click to expand...
Click to collapse
Sorry for late replied. I flashed my phone using latest fastboot. At first, it was panicking since it failed in step 6 (system_signed or something) and my phone keep displaying white text of "failed fastboot" even after I powered it down. But with little hope, I tried again and it's succeeded. Thank God the flashing didn't erase anything.
Thanks anyway.
Btw, if I want to do my own mod of those files (1% battery hack), what should I do?
ok, i think i played with this too much and im stuck!
have a droid xt912, was running ICS, i rooted it, saved root via voodoo, applied the JB Leak, recovered root, and installed safestrap 3.11
i went into safe strap, made a system backup, and then F'ed up... i forgot to make a new rom slot and switch to it, so i cleared out the stock system folder, and attempted to install a rom... it didnt boot, but i could still get back into safe strap...
i recovered the stock system, but it didnt fully recover.. it gets past the boot logo, makes the boot sound but doesnt boot?
i should of stopped there but didnt, and i reapplied the JB leak... now safe strap is gone, and phone doesnt boot correctly...
i can turn it on, i can still connect via ADB, and even access shell root...
figured i messed it up enough... lol... and should probably stop and look around, found the droid utility 1.82, but thats only if i was still on ICS, since my last install was JB, probably dont want to try and install anything ICS related...
looking for ideas...
ok, i was able to do wipes via stock recovery, and it now brings back up safe strap 3.11, stock rom still will not boot, but im installing a custom rom right now...
hope, i guess now that this is kinda back, how do i fix my stock rom?
You could try and get hold of a system back up from somebody running JB restore that back to stock slot..just an idea
Sent from my XT910 using xda app-developers app
This must be my issue
NOTE: - Do NOT make a backup while su is protected by VooDoo. This will cause an incomplete restore of your system and result in booting to a black screen. Remove the su backup from within VooDoo prior to creating any backup.
Going to try the following:
http://www.droidrzr.com/index.php/topic/7701-how-to-recover-the-stock-slot-on-xt912-running-jb-ota/
Sent from my MB886 using xda premium
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
This helped me out not being by a computer. Downloaded the backup. And all is good
Sent from my DROID RAZR using xda premium
Helped me recover OTA JB 98.72.16.XT912
yoyurik said:
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
Click to expand...
Click to collapse
After receiving the latest JB soak, I immediately made a safestrap 3.11 backup while root was protected with VooDoo. After messing with some system files, I decided to just do a restore back to stock. The phone booted up and hung at a black screen. I was able to restore the backup to another slot and boot from there, but not unto the stock slot.
So I tried using the above instructions using ADB to restore /system while excluding the su-backup file but got permission errors. So I decided to use 7-Zip, open system.ext3.win and delete su-backup file from there. Then copied the "new" modified backup folder to external SD, boot into safestrap 3.11 and restore that backup into the stock slot. I was pleasantly surprised that it worked!!! And I didn't lose root either!
This will teach me never to do a safestrap backup while root is protected with VooDoo.
Thank you so much for the idea! I just implemented it a bit differently when ADB didn't cooperate.