Database Info

Stock UI not as crappy after all

Well, I've gotten my tablet for 5 days now and have been playing with it a lot, tried all the different ROMS, anyways, upon receiving the tablet, pretty much nothing worked, e-mail app wont launch at all, a lot of the stuff in the settings crashed when I try to change them, just figured something out today after going back to stock rom, I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format. I tried the 3361 update and wow, its actually decent now, VS is definitely listening to the community when they added the ability to use the regular launcher.

Original Rom
Where can I get the Original Rom?

da-slicksta said:
Where can I get the Original Rom?
Click to expand...
Click to collapse
FAQs are your friend
http://forum.xda-developers.com/showthread.php?t=842899
For the latest version of the stock fw, check out the thread whose title ends with 3316. The first post has a link to it, and if you read through the thread you'll find posts with instructions on how to load it with or w/o clockwork mod.
http://forum.xda-developers.com/showthread.php?t=879534
For the original fw, check in the dev forum, there should be a thread with instructions on how to revert to stock fw.
http://forum.xda-developers.com/showthread.php?t=861950
http://forum.xda-developers.com/showthread.php?t=842000

Mine did not perform setup wizard as the manual said it would on first boot. As others have reported, about 20+ FC on first boot. I will try the factory reset to see if that helps like it did for you.

UnRoot
Do we need to unroot to get OTAs

eviltuna said:
I formatted the internal storage and did a factory reset. Upon startup, I notice that it went through a TnT wizzard which I never got when I first received the tablet, and e-mail and all other apps are now working, and no more FC (still crappy, but atleast it works). I really think this is the problem viewsonic has, the devices didn't come factory reset, or atleast mine didn't anyone else's tablet didn't run the setup wizzard when you first received it, or is it just me? Because I really think they would have a lot less returns if all tablets came and started the setup wizzard on boot up as mine didn't have any problems at all after the reset/format.
Click to expand...
Click to collapse
When I returned my first GTab to Sears I did a factory reset. When the person at the store opened the the box and turned it on it didn't go to the wizard. I believe that the power button can activate during shipping and after a certain amount of time it skips the wizard and then shuts off. VS should put a piece of paper inside the box with instructions on doing a factory reset FIRST. This could solve a ton of problems for new customers

There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.

roebeet said:
There's a new one out - just see the vanilla ROM's section in the faq, in my sig. I'm going to post a link to the new ROM, shortly.
Click to expand...
Click to collapse
I already gave them links to the FAQ, new stock fw, and two threads for flashing original stock fw...

To get the setup Wizzard you must first Format you Internal Storage (Settings -> Storage), then do a factory reset (Security -> Reset to Factory). Once you do this the gTablet will shut itself down, then when you start it up you will get the wizzard, just doing a factory reset alone will not do this, you must format the storage + factory reset. Anyways, all the FC I had prior to doing this are now gone, I really think that after doing Quality control at the factory, they never did these steps and so the tablet comes borked with bad softare which can easily be fixed with this 30 second format/reset.

[Q] Help - Verizon 4.0.4 OTA - Galaxy Nexus

The 4.0.4 OTA update was waiting for me when I woke up this morning. I started the install but when it went to reboot it hung up with a picture of the Android man on his back with a red error/warning triangle.
I haven't done anything with it, hoping someone might be able to help me out.
The phone is rooted but running 4.0.2 stock rom. the battery was a little low when i started the install, but i plugged it in before starting.
Thanks in advance for help,
jvoosh

the reason is that your phone is rooted ,so ... if you want OTA ,you had better unroot you rom or ruu

so can I hard reset the phone (pull the battery) without screwing anything up and then figure out how to unroot the phone?
thanks for your help,
j

Ditto
I'm in exactly the same boat, and hope someone answers this before I try a battery pull.
EDIT: I read around and found some people describing our situation, and mentioning that they did battery pulls to no avail. So I did, and nothing broke. However, the update didn't go through, and now I'm trying to figure out why this happened.

Same issue
I'm having the same issue. Phone got the IMM76k update, and after downloaded, was prompted to restart and install. So i did, gets through part of the install, and then goes to the android man on his back with a red exclamation mark. Have tried multiple times, all to no avail. Now, when I click check for update, it says system up to date, but still on 4.0.2.
Non-rooted, bootloader unlocked...anyone have any luck fixing this?

After downloading update, get Android man on back with red exclamation point
I'm having some difficulty getting the update to install, along the lines of some of the comments posted before mine:
I was able to force download the OTA update (IMM76K) according to the instructions on this original post. (It took a few tries, but eventually worked.)
I select the "Restart & Install" option (which is the only option available to me), and it restarts.
I get the relatively familiar Android man with his blue-green glowing polyhedron wireframe guts spinning, and a progress bar beneath him. After getting through what looks like about 20%, it slows down significantly, and I get the Android man on his back with a red exclamation point above him where the polyhedron used to be. I don't recall seeing any specific error message any of the three times that I tried this. (The first time, I did a battery pull; the second and third times, I just waited, and it eventually restarted on its own.) Needless to say, I'm still on 4.0.2.
I'm afraid I'm not very familiar with different version names and so forth (e.g,. I don't know what yakju is), but this was a phone that Verizon sent me in December 2011 here in the US.
Here's the information from my "About phone" page:
Model number: Galaxy Nexus
Android version: 4.0.2
Baseband version: I515.09 V.EK05 / I515.EK02
Kernel version: 3.0.8-gaaa2611 [email protected] #1
Build number: ICL53F
When I first got the phone, I immediately unlocked the bootloader and rooted it. I did NOT install a custom recovery, nor did I install any custom ROM.
It sounds like there might be some kind of validation error, but I do not recall doing anything that would make my OS non-stock, except perhaps side-loading Google Wallet, but since that doesn't even require root, I can't imagine that it would have any effect. My Superuser app shows only the following apps to have ever used root permissions: BusyBox Free, Secure Settings, Superuser, Terminal Emulator, and Titanium Backup. I've only used BusyBox and Secure Settings with Tasker to automate certain tasks, but nothing crazy! Mostly, I just need root for Titanium Backup. (I cannot recall exactly what I restored from my stock Gingerbread Droid X, but I was very careful to only restore apps and their corresponding app data--and I avoided restoring any Google-provided apps.) Even my tethering is done through an app not requiring root (SVTP).
Any advice (not requiring that I do a factory reset or flash a custom recovery or ROM) would be greatly appreciated! I'd also like to hear about people who have similar circumstances, but didn't have problems updating (so that I can rule out various factors).
Thank you in advance!

same exact issue here.

A "solution", albeit less than ideal
The OTA update eventually came to my phone naturally, and it still didn't work. (No surprise there.)
I called up Verizon tech support, and they had me do the Google Services Framework workaround to try to force the update again. Of course, it didn't work.
They said "We're going to need you to reset your device." (i.e., to factory default).
I told them that was wholly unacceptable, since I want to make sure that all my settings are preserved. (I'm kind of obsessive compulsive about things being set the way I like them, and Titanium Backup, as great a program as it is, has sometimes caused some trouble for me when restoring system settings, and especially since I'd be doing a restore after upgrading the OS, I was nervous about that option.)
Verizon got Samsung on the phone. They had no advice except "We're going to need you to reset your device." Both the Verizon rep and I told him that wasn't acceptable.
So Verizon's "solution" was to send me a new device, allow me five days to get everything transferred over, and then have me return the old device.
Up side: In case there was something wrong with my hardware or something else got messed up, I get a new device that I can get set up with the exact same settings as the old one.
Down side: The "new device" is refurbished, so there could potentially be some kind of baggage.
The "new device" came with 4.0.2. I booted it up without the SIM card, skipped all the logging in to Google, and immediately started going through the steps to unlock the bootloader and root the device. (I used the Galaxy Nexus Root Toolkit, which worked like a charm on a 64-bit Windows 7 machine I had lying around.) After unlocking and rooting, I logged into the device with my Google credentials and let it restore my settings and apps that I had downloaded from Google Play.
Then, it notified me that the 4.0.4 (IMM76K) update was available, so I installed that, and it worked without a problem.
Then, I installed the SIM card and got the new device activated through Verizon's website for activation.
Then, with both devices side by side, I went through every phone setting and made sure it's what I wanted, I made sure every app was installed (and if it was a non-Google Play app, I restored it through Titanium Backup), and I restored data for apps that don't store their data in the cloud (e.g., various games) through Titanium Backup. (I made a backup of my old device with Titanium Backup and transferred it over to the new device after getting the new one up and running.)
Everything seems to be working just fine, and the "new device" runs a bit faster and smoother than the old device, and that's with both devices rebooting and then going through the exact same "click paths", side by side.
So it's a bit of a hassle, but everyone who has a Galaxy Nexus should still be under warranty, so if you're polite with your Verizon tech support representative, they may be willing to help you out.
Verizon can sometimes be infuriating with their update release schedule and keeping their customers informed, but they sure do a good job accommodating their customers in other ways.
I realize this isn't really a "solution" to the Android man on his back problem, but this seemed to be the path of least resistance for me, and I'm pretty happy with the outcome so far. (It's been less than 24 hours since I got the "new device" set up!)
Other things I realized I should have tried (and still may, before I wipe my phone and send it back):
- uninstalling BusyBox (through the app itself, since it makes modifications to the system) and Secure Settings
- unrooting
Good luck!

My friend who has a nexus has his bootloader unlocked and CWM on it. He got the OTA today on his way into work and like you guys, he has a broken android when he boots up. We can get into CMW but we are unable to mount his internal SD storage onto our computer and he has no ROM zips on his phone. Any advice as to how to get his phone up and running?
Will wiping the system/data fix it? Is there a way to get a ROM like AOKP onto the device outside of CWM?
Edit: After several reboots it decided to just boot into the stock ROM. Really strange. Anyhow, flashed AOKP and all is well now.

[Q] LGL45C factory reset problems

Hi all, I come to you all in this time of great need. I have in my possession a LG Optimus Net or LGL45C as its know technically.
I started to suffer from problems from gapps resulting from uninstalling the Google Talk app(yes doing this in retrospect was incredibly stupid). After failing to resolve my problem when trying to re-install it, I decided to take the easy way and just do a factory reset and start from scratch. Little did I know what was to meet me. I was given the "Touch to the android to begin" screen like so many others, but it was not meant to be that simple. I would touch the android, and it would light gleefully but it would not reveal to me the next step and sit there motionless. So I proceeded to the next logical step, touching each corner in succession to skip the setup process. But no matter how many times I repeated it, nothing came of it. Next I booted into recovery mode(stock I never bothered to install CWM, another one of my mistakes) and did another factory reset, clear cache, etc. This too did not work. And I thought, there was always installing CWM through ADB where then I can then just flash to a stock ROM I downloaded. But Alas!! USB debugging some how got disabled and it was all fruitless. A little google-fu later I came across a method to flash .kdz using obscure LG utilities. With renewed hope I followed the steps but to no avail. Now I come to you stranger, and plead you in somehow help me in recovering some use of this phone. I have exhausted all my options and I hope someone out there read this and comes in my time of need. Sorry for the long block of text :silly::silly::silly::silly:

Having the same problem as you, bookface.
I couldn't install CWM from the links provided in another post, all lead to a 404 Dropbox page. This sucks. And when I tried to use the installer from Play, I got a dialog saying it's not compatible. Some would say to ignore it, it would be fine...
But if something doesn't feel right, don't do it, I've always been told...
So, I was rooted, but phone started acting funny. Done a factory reset. Since I didn't have CWM, I thought it would clear that mess up.
Nope, almost all apps crash. I'm lucky that at least the browser, Gmail, and music apps work, but everything else, including Google Play Store, all crash upon launch.
Net10's forum is a lame excuse as a "forum." Seems like TracFone employees have NO concept of how a forum works. I looked at there for the same issue, and they rather take software/hardware issues to private messages?
I have NO computer, my hubby's friend who helps him says "You have an Android tablet, that is a computer!" Technically, yes and no. Since I can't root that thing, it's useless. (If you want to know, Polaroid PMID709 4.1 with Rockchip RK29xx, and impossible to root fully, it's "semi-rooted".)
And I'm lost. I and my hubby need this phone to work. Because we need it fpr work (our jobs). And I'm getting sick of TracFone screwing up Android ROMs.
Please help!

youve made much more headway than i. trying to help my neighbor with his. he set a lockscreen password on his lgl34c and then promptly forgot it.
so upon a bit of research, this model is a doozie to work with. i had intended to overdeliver by flashing him a ROM that might allow some hotspotting and the like. upon closer inspection, i dont believe that i will be able to do that. at best a towelroot...
but ONLY IF i can get past this lockscreen. i've tried to factory reset by:
1) removing/replacing battery then holding vol down+power and waiting for LG splashscreen then releasing power (still holding vol down ) and then re-pressing(holding) power again
2) turning phone off and holding home+vol up+power and holding 30-40 sec
ive repeated both methods many many times, and these are the only methods that i have seen described in my google searching. in fact, yours is the most advanced post i have found yet.
how can i factory reset this phone without access to the settings menu?

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.

When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."

jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)

Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*

I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.

JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.

devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.

jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.

Logs or it didn't happen.

Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.

I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...

Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

Softbricked, basic usage no rooting.

Gday everyone.
I just got this phone and since it was first powered on I've had issues. I will likely be going back to the carrier tomorrow and asking for a replacement, but wanted to put my experience down here. Ive looked at a lot of other threads, but all of them involve unlocking of bootloader, flashing etc - I havent done ANY of this (yet). Its fresh out of the box.
Location: Australia
Carrier: Optus
Model: MHA-L09 (cant access extended model number)
So first up, had issues connecting to the carriers in-store wifi, which uses a captive portal.
When I finally got it going I was presented with a Chinese site - id accept this usually considering it is Huawei.
This phone is a replacement for my dead Note4 and as such I wanted to restore apps, as I had no internet, I skipped the process.
Got back to my office and connected to my wifi fine, so decided to factory reset to get a fresh start.
Noticed that after reset the initial process was in a different order. Restored from Google and all apps downloaded, happy days for a couple of hours, just waiting for my service to port over.
2 hours later, I decide to restart the phone, it gets hung up on the Optus logo which is displayed before the reboot starts.
Hard reboot.
System loads, I figure I may as well see about a firmware update. Get 'Package installer isn't responding' errors. Try again, works, no updates available.
Go to google photos, get 'Package installer isn't responding' error.
At this point I think, f**k - what is going on here.
So I reboot into recovery to wipe the cache. This processes fine, but then the option to reboot the phone doesn't work.
Hard reboot.
Boots into recovery without me touching it.
Hard reboot. - happens again.
So then I think, fine ok, I've upset the balance, lets do a factory reset.
Factory reset hangs on 99% for over 30 minutes.
Against better judgement - hard reboot.
Now I have the EMUI logo with a nice round 0% under it... and that's where its staying.
Thoughts?
I have to fly interstate on the weekend and cant really afford unreliable comms. Should I ditch the Huawei?
Thanks all.

So - it seems that nowhere did i find a mention of the fact that if i plug it into my PC and goto the recovery mode, it loads eRecovery. Whilst this didnt actually work (I believe it only works for CN firmware) It did give me a shutdown option. I shut it down and started it again and im back into a fresh install.
Lets see how I go now...

Never restore backups from other phone.

Wow, helpful.
I didn't restore the backup from another phone, just apps, ie google downloaded the apps I selected.
The device is still performing poorly, even a standard reboot does not succeed, instead it hangs on the carrier logo before actually rebooting.
Ill take it back to the store tomorrow and ask for another one, im hoping Ive just gotten a dud.