Hi, all. I just installed webOS 3.0.4 and now I can no longer get to the Moboot bootloader for booting into CM7. I (perhaps foolishly) did the update via HP's official Update Manager instead of by Preware. Just posting here to give you guys a heads up if anyone else is running Android and is thinking about updating to 3.0.4.
This should be an easy fix, I'm going to just try and reinstall Moboot via novacom. I'm guessing Android is still there, but the HP update just changed the boot back to stock.
EDIT: Yup, reinstalling Moboot fixed the problem.
Similar issue
I have a similar issue, once I updated to 3.04, reinstalled moboot and CM7 now it just hangs at the CM7 loading screen and does nothing. I've downloaded all teh files 4 times, reinstalled after wiping everything clean, still not working.
Don't know if this will help resolve why. I just loaded moboot and cm7 on my 3.0.4 touchpad and it works great. Maybe you need to recover the webos original form, update tp 3.0.4, them do the dual boot. Dunno
edit oops, just saw the first post edit. LOL
You should always CMW backup before doing any updates.
3 0 4 Update Breaks Moboot
You need to run it after the first update, i think the update that breaks it is called librsvg or something similar. I had it aswell on a new install of Sabayon 7 gnome, but running the command mentioned above fixed it straight away.
Related
I'm not expert enough to say this is the answer to a lot of people's problem -- but I'm going to throw it out anyway and hopefully some of the "really expert" people will jump in.
Several times when I have had major problems, I have found that the file structure/files/etc. on my tablet were messed up. Before I could reinstall, I had to re-partition, wipe caches, etc.
I read a lot of posts about people having major lockups or loops and then just trying to reload and reload software assuming that is the only problem -- and not getting good results.
It seems to me that if there is a serious enough malfunction to have to nvflash or do a major recovery -- it would be good to re-partition, wipe caches, etc. in case there is corruption or other structure problems.
What I think we need is for one of the gurus to make us a procedure for "Rebuilding the /sdcard File Structure" (or something like that. Repartition to 2048 and 0 --- and then what else? Which things need to be wiped, formatted, etc.
I'm pretty good a discerning what's wrong -- and I think some of these rebuilds are failing because of this problem.
Right? Wrong? Other ideas? Procedure?
Rev
P. S. -- Enough folks are having these problems right now that this could be an important help for them if I am right......
I PM'd, but the short version for the forum.
I've obviously seen a lot of issues with the TNT Lite 5.0.0, and I've whittled it down to two major problems. First off, not everyone reads instructions. This was fine pre-TNTL 5.0.0 as the instructions really were the same for every version preceding it. But 5.0.0 changed the playing field drastically. Which leads me to the my second point....
I think that some of us have been using mods for so long now that stock was no longer an option without an nvflash. Viewsonic, for example, had a bootloader update in December and I believe a recovery change with 3588. But since a lot of us have been using mods for months, we never got those updates. So, when the time came to revert back to stock, there were problems.
In some ways, TNT Lite 5.0.0 is almost like a tablet cleanup - it's the first update I've had where a stock pre-req was required, and the first one in a very long time where I added a stock bootloader and recovery.
nvflash and tnt 5.0
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Charles77 said:
I tried to go 5.0 after i did nvflash and it instantly did an update ota so when I tried tnt 5.0 it got stuck at the birds for like 15mins, so I nvflashed again.
What am I doing wrong?
Click to expand...
Click to collapse
Not sure -- sounds like you did it correctly. nvflash to 2967, OTA to 3588 and then TNTL 5.00. You didn't install clockworkmod, correct? You need 3588 recovery for this to work.
oops yes I did. ok
Charles77 said:
oops yes I did. ok
Click to expand...
Click to collapse
That would do it. The reason why 3588 recovery is needed is because it updates the bootloader, whereas I believe clockwormod does not.
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
darthbubba said:
I'm kinda stuck here, and need some help...
A co-worker has this G-tablet, and gave it to me for the weekend, to load a custom ROM on it so she can watch Hulu and other videos on it.
I did my homework prior to touching ANYTHING, so I made sure it was at 3588 stock, then downloaded the TnT 5 images, along with nvflash and the stock image in case anything went wrong.
Got Tnt 5 up and running, but ran into the issue where it wouldn't sleep (required a reboot to work again). This wouldn't do, so I decided to downgrade to TnT 4.25. The hell started from there...
After flashing TnT 4.20, it got stuck on the birds boot screen. No worries I thought, just run nvflash and everything will be out-of-box new 'n fresh.
I have nvflashed this damned thing about 18 times now, and keep getting the problem where it will flash fine, then reboot fine. But if the unit is powered off or reboots, it gets stuck in APX mode, and won't do anything until it's nvflashed again.
Please help! At this point, I'll be happy just with getting back to status quo ante...
UPDATE: I forgot to mention: I'm accessing this G-tablet from a Win 7 laptop, to which I installed the nVidia USB driver.
Click to expand...
Click to collapse
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Deleted dupe
FIXED IT!
jimcpl said:
Hi,
I would hold off doing anything else until someone more knowledgeable posts some help, or maybe get on the irc channel.
There was another user, tcrews, who had what sound like the same problem. I don't know if he's still posting, but he had a thread "need some guidance", and I don't think he ever resolved it.
Sorry if this is not much help.
Jim
Click to expand...
Click to collapse
I FOUND A FIX!!!!
Link here: http://forum.xda-developers.com/showpost.php?p=12030351&postcount=14
I got my wish, now I'm back to status quo ante...
I sent tcrews a PM with this link, hopefully it'll fix his too...
darthbubba et all,
The files from otreblada that are in this download are the same files roebeet and others have provided -- just packaged together in one set.
To nvflash you have to have:
1. the files for the program nvflash
2. the .img, boot, etc. files
3. the USB driver files.
All of these are referenced and available in several places.
I am glad, however, that this might be a solution for some of you who seem to
have recurring problems.
Rev
I searched the forum but couldn't find an answer. I have tried several times to update my TF to 3.2.1 but the update keeps failing.
I get a system update notification. The tablet shuts down. The little green android with the gears on his stomach appears with a progress bar under it. The progress bar gets about 1/3 of the way then an exclamation mark appears in a yellow triangle. The a few minutes later the tablet restarts and it says that the update failed.
I am currently on build number HTJ85B.WW_epad-8.6.5.9-20110816. My TF is unrooted.
Is this happening to anyone else? Anyone have any suggestions besides doing a factory reset then trying the update again? Thanks in advance for any help.
Was it rooted before?
Rooting itself doesn't break updates it's what you do whilst rooted that can, so unrooting isn't necessary. I'm having this issue again as I removed some Asus apps with Titanium Backup which I now can't get back (I did them when there was a bug in TB which didn't backup apps properly). The OTA update script checks the integrity of a bunch of apps and files, which if it fails will abort the update in the way you are seeing. Very annoying.
---
Sent from my Asus Transformer using Tapatalk
Yeah it was rooted. I just realized that immediately after I rooted it, I had made a CWM backup. I'm going to try to restore the backup and see if the update goes through. (fingers crossed)
Sounds like you're running a custom ROM
baseballfanz said:
Sounds like you're running a custom ROM
Click to expand...
Click to collapse
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
yeah, I think that your kernel will cause the update to fail since it updates some of the kernel modules.
tmcquake said:
Nope, stock 3.2. The only thing that I flashed was a custom kernel.
The update still didn't work with my backup. Luckily the WW 3.2.1 update was posted in the development section, so I just re-rooted and flashed the update. Worked like a charm.
Click to expand...
Click to collapse
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Got the problem, too!
Now I use Revolver!
I flashed revolver, too. Works like a charm.
ppzoid said:
Where did you find the ww 3.2.1? Because have the same problem and haven't found the rom. Wrong serach terms, for sure.
Click to expand...
Click to collapse
I got it from here: http://forum.xda-developers.com/showthread.php?t=1281161
It's only a 3.2 to 3.2.1 update though, it's not a full ROM, so you have to already have 3.2 on your TF. Hope this helps!
i have the same problem too.
my TF101 was totally non rooted .
is there a download for this 3.2.1 update? so i can prehaps update my TF mannually ....
I didn't find one, because of that i flashed revolver.
ppzoid said:
I didn't find one, because of that i flashed revolver.
Click to expand...
Click to collapse
i wish too....the thing is ....my TF cant even load into recovery....
it is a B40...TW 8.6.5.9
is this normal ??
coz I saw people can do it with B40 with 3.2.1....
http://forum.xda-developers.com/showthread.php?t=1280796
I too have a problem with the update on my rotted tf.I got an unofficial update apk here but I still get an error message when trying to flash in CWM.I heard that this could be due to a modified system file,but I don`t remember having done such a thing thought...
Good luck.
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
DANOinSD said:
Hi All,
I'm probably one of the few here who is still using HoneyComb instead of ICS on my Xoom. I've been on 3.2.4 for some time now, and started getting the 3.2.6 update notification which I blew off until the other day when I said screw it, I'll update and go through the trouble of re-rooting, etc.
However, I attempted to use Solarnz's universal root method which I've used numerous times before and never had an issue with until now. So after pushing the recovery.img via Fastboot, everything appears to have been completed just fine, except when I reboot into recovery I get the damn android with an error.
I've tried pushing a few versions of recovery and each time it seems to work just fine, but again on reboot, I can't get into recovery like it never got pushed or somehow has been erased. I can even revert back to 3.2.2 and update to 3.2.4 and root and re-install clockwork no problem. But I keep getting that damn update notification every 5 mins, and I'm sick of it, hence why I bothered to update in the first place.
I know most people have by-passed this altogether by jumping to ICS, but I've had too many issues with the beta ICS versions out there (WIFI handoffs and disconnects mostly) and need to reliable daily driver vice ICS goodness (fortunately I have a GNex for that).
Anyway, since I hadn't seen much on this, I decided to post and see if its just me, or if this really is an issue?
I can probably go old skool and use the manual root method of pushing the SU files via ADB, but something isn't right here, and I wanted to get some feedback.
Thanks
Click to expand...
Click to collapse
Depending on what ROM your flashing if your trying to do the update from OTA then you have to have a 100% no bloatware removed rom, my suggestion is to download the one @ motodev and then flash 3.1 and update all the way to ICS (if wanted) otherwise I believe that when you get the (!) in recovery you can press once pwr+up fast (don't hold) and it will display the recovery window with the error message that's preventing you from upgrading.
after flashing the recovery, did you reboot into android and then into recovery? if yes, don't!
you have to reboot into recovery right after flashing the recovery.
Hi All,
Thanks for the feedback, I finally got recovery pushed and booted, along with root on 3.2.6.
As llama points out you must reboot into recovery upon rebooting from fastboot. I don’t believe this was a requirement previously. But once I did that, all was fine.
I’ve done this a thousand times before and even in my old notes I couldn’t find any reference to booting into recovery immediately after pushing the recovery.img. Is this something new with this update or has it always been this way? Call me crazy, but I can’t ever recall scrambling to catch the reboot and get into recovery before re-launching Android. I always rebooted in Android and made sure it actually loaded to ensure something didn’t get hosed, then I would reboot into recovery and flash the root zip.
DANOinSD said:
Is this something new with this update or has it always been this way?
Click to expand...
Click to collapse
as far as I know, this is a 'feature' introduced with every ota-update. To my knowledge: get a xoom from a store and flash recovery right away-> everything is good; have the xoom install an ota-update and flash recovery afterwards -> do it this way
Hi Guys,
Having a bit of a nightmare here.
A few months back I installed CM9 on my HTC Sensation, everything went well, chuffed to bits with its performance and stability.
However, there was one small gripe that I just couldn't fix. The Youtube application doesn't work properly. If I'm on Wi-Fi then it works as desired but when I'm not at home I have major issues.
It will let me login and pulls down my subscribed channels etc etc but then as soon as I try to watch a video I get the error message:
"Connection to server lost
Touch to retry"
I have full signal/HSDPA and it just will not work. So far I've tried:
- Cleared the app data / cache
- Un-installed Youtube and re-downloaded it from the Play Store
- Reverted to an older version of Gapps.
- Flashed my ROM to the nightly CM9 build, still nothing.
It worked fine before my previous upgrade to CM9. The Youtube mobile site works, but it's crap. It's driving me insane! Please help!
Thanks!
I found the same issue that somebody is having on their Samsung Galaxy SII:
http://forum.xda-developers.com/showthread.php?p=28319322#post28319322
It appears that they managed to fix theirs, but none of the fixes mentioned in that thread work for me. Still getting exactly the same error.
I'm guessing that nobody has had this issue before?
After trying ABSOLUTELY everything I have finally resolved the issue.
Thought I would post incase anybody else finds this thread on Google!
You need to revert back to an old version of Gapps, I tried the March 12 release but had the same problems. I reverted back to the Feb 12 release and it worked! Youtube has updated to the latest version and is now working.
I found the Feb 12 release on http://goo.im/gapps , a link to the file is:
http://goo.im/gapps/gapps-ics-20120212-signed.zip
Install the zip with CWM and it now works!!! :good:
jaffster said:
After trying ABSOLUTELY everything I have finally resolved the issue.
Thought I would post incase anybody else finds this thread on Google!
You need to revert back to an old version of Gapps, I tried the March 12 release but had the same problems. I reverted back to the Feb 12 release and it worked! Youtube has updated to the latest version and is now working.
I found the Feb 12 release on http://goo.im/gapps , a link to the file is:
http://goo.im/gapps/gapps-ics-20120212-signed.zip
Install the zip with CWM and it now works!!! :good:
Click to expand...
Click to collapse
Thanks. That solved my issue but why the quality now is just terrible on HD. HD looks just like my webcam in the black hole. :/
(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2