Smartisan Nut Pro in Europe - Device Reviews and Information

Just a quick note to say to anyone thinking of buying the Nut Pro to use in Europe: It definitely works in the UK. I am on the PlusNet (EE) network, living in the UK and the 'phone works very well. I am getting 4G (when available) and had no problems getting the phone to register on the network, just put the SIM in, switched on and was connected straight away.
Almost everything on the 'phone appears to work correctly. The weather app looks lovely but struggles to locate me (it thinks I'm in a city 60+ miles away) but I can live with that. Many of the apps I transferred from my old 'phone that were then installed from the Smartisan app store didn't work correctly so I ended up deleting them and re-installing them from the Google Play Store which was very easy to install. They then worked without problems. The Smartisan browser has a home page that is full of Chinese news and/or links to Chinese web pages, which I can't seem to change, although it works well in all other respects. I have a preference for Opera on my 'phone so I use this in preference to the Smartisan installed one meaning this isn't a problem anyway.
Everything else? It all works really. I haven't found anything that doesn't work properly that I can recall. The music player app forgets what it was playing after a Bluetooth device has been disconnected from it which means I have to open the music player to re-start the music, again not a huge issue anyway.
If you were thinking of buying the Nuts Pro I can't recommend it more. It is one of the most wonderful 'phones I've ever had. The modifications made to the Android OS make everything more beautiful to do and add so much style to the operation of the whole 'phone. This is a wonderful device, I absolutely love it. Don't let the fact that it isn't officially supported in Europe put you off. Assuming you can speak English (no other European languages are installed) you should have no problems, network support not withstanding.

What's the camera quality like... I've heard good things about it. Is it rooted?

Sorry, as you probably can tell, I don't visit often enough to respond to questions in a timely fashion.
Regarding the camera question (probably long forgotten by the poster) the quality is good. Every 'phone I get I take some comparison shots of local landmarks to compare them too.
If I was to rate it against 'phones that you might have experienced, and score them out of ten:
Blackberry Priv. 10
Huawei P9. 9
SmartisanNut Pro. 8
Sincere apologies for not responding until six months after your question, sorry.

Since the most recent update to the software (V 6.0.0.1) my 'phone battery has been draining itself overnight, from 70% or more at bedtime to 0% by breakfast.
I have been trying for two days to downgrade the software to a previous one, with little success. I've actually today ordered an inexpensive 'phone to reluctantly replace the Smartisan (I still absolutely love the 'phone). Not an hour after I placed my order, you guessed it, I finally managed the magic combination of key presses required to enter recovery mode.
In a few steps, here's how I did it:
1. Download a full copy of the Smartisan OS, I used V 4.1.0.2 as I had a copy of this saved on my iMac already. According to the (Chinese) Smartisan Forum, 3.7.9 is favoured, but I didn't have a copy of that. File size for this file is around 1.8Gb
2. Copy the downloaded .Zip file to the root drive of the Smartisan internal storage.
3. Turn off the 'phone screen by pressing and holding the 'Home' button. [Not sure if turning off the screen using the 'Home' button is important, if it is you might have to enable this option in the button shortcuts settings]
4. Press and hold: Volume+, Volume-, Power and Home. Ignore any prompts on the screen to power down. Keep all four buttons pressed in until the 'phone switches off.
5. As soon as the boot logo (Hammer icon) appears on the screen, release all buttons.
6. Use the Volume +/- buttons to select 'Update System from SD' then press the power button.
7. Use the Volume +/- buttons to navigate to the location that you saved the update file to. [This is why it is recommended to save it in the root directory of the 'phone storage]
8. Press the Power button to start the update.
The whole time to update took about 5 minutes or so, then I had to select 'Reboot'. The boot time took a little longer than normal but once rebooted all my apps were in place, almost everything worked normally, immediately.
Some of the Google apps (including the Smartisan Mail and Calendar apps which I have linked to a Google Account) failed to sync which concerned me for a while. I simply deleted my Google account from the 'phone and then set up the account again and my Email, Contacts and Calendar all returned.
I did not wipe the cache, return to factory settings or anything else as I was hoping not to have to re-install all my apps and accounts one by one again if I could help it. As the underlying "Android" OS is still V7 between the V4 and V6 Smartisan OS versions, I hoped this wouldn't be needed. Perhaps other people won't be so lucky.
I'd already ordered a replacement 'phone so if I'd bricked the Smartisan, I'd be upset, but not I wouldn't be without a 'phone.
I would suggest you back up everything important to you, before trying this downgrade as it is possible you will be left with a totally non-working 'phone.

I do still really like the 'phone. If reinstalling a previous operating system fails to cure the problem of the excessive battery consumption I shall be really sorry.
One of the previous updates to the system added a very effective Face Unlock feature. It is possible that this isn't very secure, I have no way to tell, but it works reliably (unless the light is coming from behind me) and I've not found a way of fooling using pictures, photographs or other people.

First of all thanx to mkstevo for opening this topic. I own three Nut Pro phones and they really are wonderful devices. My story is a bit more complicated so maybe it will help someone. I gave a red Nut Pro 4/64 to my girlfirend. It was updated to the latest Smartisan OS OTA (6.X). After only a few days the phone restarted by itself and displayed only Smartisan logo. If you connected it to pc, red notification blinked for a few times (never a good sign).
With my experience with flashing i sensed the phone didn't have a hardware error but it was connected with sw. And also the thought you could never actually brick Snapdragon phones to the point of no return kept me optimistic.
I could get into recovery but couldn't load a rom onto my internal storage. The sd card and OTG usb drive were not recognized (no matter how i formatted them). I could only use adb sideload which was working but the end result was always 0. SO no progress.
It is really hard to find any info or rom about this phone, but unbrick guides are virtually non existent. After hours of Google translate I found a link on a russian site to this rom which should be QFIL flashable (pass: 5pn2) After downloading it for 2 days a lot of captchas and jdownloader sessions i got the rom from baidu.
Next challenge was to put the Nut Pro into EDL (i already had a edl cable prepared). It turns out you should press volume+, volume- and edl button when starting the device and when Smartisan logo appears - you should let them all go. The device starts blinking red constantly and you have Qualcomm Qloader 9008 in the device manager.
After that i loaded the firehouse and xml files and the flashing actually proceeded to the end with success. But the phone still didn't boot up but rather went straight into Smartisan recovery. Something told me to try and "adb sideload" one last time. Not really expecting anything I took the oldest rom i could find (3.6) and sideloaded it and this time adb sideload said success and 1. And to my surprise the device booted up normally.
I do not know what caused the crash. Maybe it was an incompatibility with some app or just a bug in the latest version of Smartisan OS. After 2 weeks of use we couldn't recreate the problem. Other 2 devices are also running fine. EDL flashing obviously reached the partitions that were messed up and couldn't be repaired otherwise.
SO if you ever run into a problem, this is probably the only source you can find about this phone. And it's a great phone, a joy to use and something totally different software wise. There are newer and better Smartisans out, but this one is fairly cheap, has a great screen, great battery, solid camera and is build like nothing on the market.
p.s.
if anybody has a hard time finding roms on bbs.smartisan or on their official site, here is a collection of Nut Pro roms.

Please send link again
The link is broken, smartisan nut pro firmware

Related

Anyone afraid of NAND flashing is a wuss. Check this out, its so easy..

These Instructions are out of date, and may not work anymore.
-CarComp
EDIT POST ON 5-5-2010
INSTRUCTIONS ARE IN BOLD!!!!!!!
EDITS AND MY OPINIONS ARE IN ITALICS
Want google and not winmo but can't wade through all of the confusion offered up by the supergeeks of android linux? Well just do these steps. It took me an evening to figure out these steps, and could whip it up instantly now.
BTW - it REALLY helps to have a computer with an SDcard slot adapter that handles the micro-sd cards. I don't really recommend trying all this with a USB cable, b/c once you get to linux only, you will kinda be screwed cause it doesn't quite work the same like windows CE. Also that and you can't format through the phone, so just get an adapter ok? Stop right here if you don't have one and just order one or go to walmart and spend 10 bucks and get one. BTW, your micro sd card should have come with one when you bought it, so go look for it.
Ok how to get the super Eclair android into NAND and live a happy life....
1, CHARGE YOUR PHONE UP ALL THE WAY BEFORE ANYTHING. When done charging, unplug whatever is in your USB port for the rest of this procedure. Having phone plugged in while flashing = BAD
2, get hard spl on your phone.
3, Install Hyperdragon IOlite on your phone to get the radio(1.65.24.36) that I recommend, which will improve battery life and possibly other things that I don't know about. Get it here -> http://sakajati.com/blogs/2009/02/hyperdragon-iv-iolite-based-on-htc-iolite/
4, format your 1+ GB sdcard using fat32 only.
5, download polyrhythmics dark / light build for nand and sdcard.
put that SINGLE FILE (androidinstall.tgz) into a folder in the root of the SD-CARD called "andboot" - Get it here -> http://forum.xda-developers.com/showthread.php?t=600154
6, go to http://sourceforge.net/projects/androidhtc/files/ and download KAISIMG-PANEL2-320-TILT.NBH if you have an ATT tilt. If you have something else, download that NBH.
7, Rename that NBH file to "KAISimg.nbh". Put it in the root of your storage card.
8. Now you are ready to install to nand. Get out your stylus, hold down the camera and power button and press the reset button with the stylus. It should go to an updating screen. If you don't get a white screen with a progress bar, but instead it still shows tri color and says "serial" then you did something wrong. Start over from step 1. Once you get to 100%, wait 20 seconds or something (just for shihtz and giggles) and then pull out the battery.
9. Now, put it back in, press power and wait for android to start booting. You will know cause all this random looking text will go by. You have to be quick to do it, but press the middle button on the d-pad when it says 'press the middle button to enter setup' or soemthing like that. (EDIT: I've been told that you have to just hold the d-pad center button down. Either way, just get that button pushed when it says to push it).
You will be presented with some options. Make sure the little asterisk is on the "NAND" option.
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.
Crap your pants at the speed NAND offers. Install some live desktops (I like the starfield warp drive one from the google market.)
BTW: If you mess up your phone doing this, blah blah its not my fault blah blah you probably shouldn't be on these forums etc. Just make sure you have HardSPL and you will be fine. I've flashed hundreds of roms hundreds of times. Just that one little step will make your life easier.
EDIT:
RADIO DETAILS:
I've heard a LOT about using the latest radio or whatever version 1.71 or soemthing. I run radio 1.65 just fine. I never upgraded it through out all of the android builds. I operate like this.. If you weren't having cell quality issues, GPS lock issues, or any other radio issues in WINMO, then android will be fine too. I've added a step to the process to install a specific winMO rom that has the radio that I use. If you don't like the fact that I'm telling people to use an older radio, so be it. I'm just spreading the word for what works REALLY well for me.
EDIT: (My thoughts on the panel 1 2 3 and the 320 or 428 or whatever...) Picking the right panel is like playing the 'cups and ball' game. if you know which one the ball is under, you will win. Well for you TILT users, the ball is under #2. I don't know why, but it is. If 2 doesn't work, use 1. Doesn't get simpler than that. As for the resolutions, just use the 320. Ya, some apps fit better on the higher res, but our screens don't support them really well, and its all blurry. Think of it like this..... using 4xx instead of 320 is like asking 3 pixels to display as 1, vs. one pixel displaying as one pixel very clearly. Polyrhymic has done a great job supporting our screen's native 320 size, so just use it.
EDIT: (An issue i've noticed with booting and having your phone plugged in). Android just won't do it on nand. You can charge your phone from a dead point for say 20 mins, unplug it, then turn it on, boot android then plug it back in. You can't plug it in, and turn it on. It gets stuck in some sort of USB status loop.
EDIT: (When your phone just sits there on the A N D R O I D text and won't boot). Seems like this has been happening a lot, for me too. I've found there are two ways to stop this, one is preventative... Don't let your phone go totally dead. The second, when you reboot your phone, press and hold dpad center, then just count to 10 and go to the QUIT option. 9 times out of 10 it will boot right up.
IF YOU HAVE ANY PROBLEMS, JUST REPEAT THE PROCESS.. Don't skip the full charge and installation of Hyperdragon first.
for may people on here, the fear of flashing isn't the problem. it's the missing features such as bluetooth, speakerphone and in some builds even camera.
I would LOVE to go nand. I hate not knowing if the problem is with the build or with the sucky sdcard.
but I need to revert back to winmo for bluetooth headset. once that or speakerphone works I am ON IT.
Nice, couldn't have said it better myself, a few small points, press and HOLD the centre button on Dpad, a quick press will not do it, I'd mention the radio version too, but those are not major issues, and can be sorted easily enough
Good advice about the card reader and adaptor, those two saved my ass a few times in the early days of Nand flashing, I keep a good stock winmo kaisimg.nbh on a spare SD card, you only need a 128Mb one for a stock rom.
Yes there are install instructions on the build posts, but a lot of the info is now spread though some 2000+ posts, so having it all in easy terms helps a load.
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
added info about panel stuff to the instructions
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Disturbed21 said:
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
Click to expand...
Click to collapse
agreed, currently no gps working map that can be rely such as garmin that can work on winmo.. 1 disadvantage of android.. need to be online to get route..
Kurt Cobain said:
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
Click to expand...
Click to collapse
320-428-480 là chỉ độ phân giải đó bạn.
320 is a resolution of 240X320 and the 480 is a resolution of 320X480
Mình biết được chừng đó thôi
Created another edit to the 1st post.
I'm not saying that android doesn't have its shortcomings, I'm just offering a quick means to get to NAND without trying to comprehend the whole thing in the traditional sense of reading 200 threads.
BTW my radio is 1.65.24.36
Maranevin, try flashing Hyperdragon IOlite first. Maybe a radio switch will prod your phone into the correct direction.
Errr, for newbs who don't know how to properly unlock their device isn't this dangerous? There IS a possibility of bricking your phone if you don't know what you're doing -- right?
Anyway, I would also mention that if you or your phone can't do 3G don't flash to NAND yet. The radio can't be instructed to use GSM only with the current poly build (and any other I have tried so far)
I totally agree with mnjm9b, the problem is not flash the phone, the problem is that there are many things that do not. In particular I am very happy with the performance of 2.1g polymod to date is the best I've worked.
carcomp thanks for the help, very good summary.
aikeru, if someone is flashing a phone, they probably know the risks. Its not my fault if they do something stupid. Is it autozone's fault if I buy specialty tools and ruin my engine changing a timing chain?
Anyways, I don't get the 3g thing. We have hardly any 2g or whatever is below 3g here in Mulberry Indiana and my android works fine.
Like I said, maybe i've found that magic mix of things that works really darn good.
BTW: major argument for using android.....
First of all, i'm not borg. I have yet to really get into bluetooth. I own two earpieces and the only good thing i've found is you can talk on the phone in freezing weather with you hands in your pockets. Bluetooth to mute car radios is cool, but I have a 20 year old car. I don't need bluetooth for file transfer cause i've got wifi, and SD CARD.
Second, as for the speakerphone, it never really was that loud anyways. I came from a hermes, which has a speaker like the voice of god, so i've never been impressed with the kaiser speakerphone.
Third, the camera... I have a nikon D60 with a speedlight for taking stills and lowlights, and a Kodak Z612 in my wife's purse most all the time for the past 3 years for video and spot shooting. All this data easily goes onto the micro sd card and into the phone.....
carcomp said:
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.[/B]
Click to expand...
Click to collapse
I've done all step above, just when i did this After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power. it started back to Step 9 when i had to 'press the middle button to enter setup'.
So, i skipped that step, and then later everytime i tried to press reset button, the phone is freeze, then i had to started over again...
In some cases, my OK button became to POWER button...
And at first time, WIFI was OK, then it showed Unable to start Wi-Fi
Any suggestion for my troubles?
Thank you!!
Great!!
Hi all, Great!! I am now running Android on my kaiser and I love it!!!
Just a couple of questions for people who can answer them:
- How to change phisycal keyboard layout? I mean, some keys that I have in blue aren't the same I have on my keyboard...
- Is there any means to connect to a pc to transfer contacts and files?
Thank you all!!
Gnatto
Maranevim said:
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Click to expand...
Click to collapse
Same problem here. Someone please help. My device is now a worthless brick!!!!
Ok when this happens (its happened to me), first of all don't panick. If you've installed hardspl you are protected, and besides, just cause your phone won't boot android doesn't mean its bricked, it just means its not booting android.
There can be a multitude of things causing this, but the #1 reason I think is "Just because thats how it is"
First of all, don't boot your phone with it plugged in. Ever. Charge it first, then boot it, or charge it enough to make it through boot then plug it in when it reaches android.
Second, sometimes during boot, it just hangs where it says A N D R O I D, or some other text. You can get around this by resetting with stylus, then pressing the center dpad button, then just counting to 10 or 20 or some random number that makes you happy, then select quit. It should boot.
Thanks. Fortunately I unbricked it by putting the KAISDIAG.NBH file onto the SD card, then booted it. This unbricked it. I also put the the KAISIMG.NBH for the Android on here and it booted into the installer. My problem now is that when I click install to NAND, it says it has an error extracting from the SD card for the android installer. It then quits back to the main install screen. I think it is a permissions error since it says on the screen something about being read only. If anyone could help me, I would greatly appreciate it. Thanks.
Oh and btw, I never had usb plugged in since mine is broken.
Ok well you are on the right track. Before you do anything else though, flash a copy of windows Mobile. Either take your pick, or use hyperdragon. Its very complete ... radio / ext rom etc. Next, try reformatting your SD card using windows. Do a complete format, not a quick one. That might help. Now reflash using the link to kaisnbh that i posted.
Remember, installing windows mobile is your NAND reset. Its lot like an sdcard where you can just erase everything. You have to put something else there that is radically different. I may be wrong about this, but it seems to be the case more often than not.
You may be one of the special case people who have a weird phone that takes one of the other KAISimg.nbh files too, so don't discount that. Also since you have hardspl, and you are flashing from the sdcard, you phone is probably NOT going to brick, and even if it does screw up royally, if you can still get to tri color, you can fix it.
Ok. That's great to know. I'll try what you stated. Do I need to partition my SD card? Thanks again. I really appreciate the help.

Possible solution to LiveView issues.

Hook it up to your PC via USB and stick it in DFU mode (from off, hold both the hardware buttons until the USB logo and "DFU" appear on screen). Let it try and find drivers (it won't) and that's it. Hold the power button for about 10 secs until it shuts down and unplug again.
I did this after someone elsewhere suggested it seemed to have sorted his problems out and lo and behold, I haven't had a dropped connection or interruption in service for about an hour since doing this and it would have dropped numerous times by now if I hadn't.
Still not getting any Facebook updates mind but music controls (stock android music app), Twitter updates, RSS feeds and texts are all coming through just fine.
Does data sync really have to be on to get all this stuff pushed through? It's just really caning the battery on both devices.
Thanks go to Rovex at Modaco for finding this out but I thought I'd better create a new thread so it didn't get lost in the mire of the main one.
Edit: Might be worth mentioning that neither of us have LiveWare installed also. That seems to be a contributing factor to the freezing/lock-up issues.
Awesome hopefully getting Sony LV soon but been hearing problems about it
(lmao at name )
Bum.
It appears my excitement got the better of me and I shot my bolt too soon. It worked fine for a couple of hours until I decided to reboot it for whatever reason.
Back to business as usual since rebooting.
Forget this entire thread. Move along.....nothing to see here..........
Go to SE website to get new update, i just bought mine, cant wait for it.
does it have a stopwatch?

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.

One V behaving erradically

Hi,
all seemed fine with my new, one week old One V. Till I installed GTA III. First the installer stuck while downloading the datafies. I canceled the download, restartet GTA III, but instead of completing the broken datafiles download (or re-downloading) it just startet the game and crashed the whole phone in the intro animation, that was without sound. I removed and reinstalled it, the download now finished, I could get the intro with sound, but it crashed the phone at the same moment. Since then my phone behaves like it would be very sick or hate me ;-/. After this crash it startet looping the reboot. It would boot, ask me for my SIMs PIN code, then be ok for a short time, then reboot again. This time it would boot into the desktop without asking me for the PIN. All seemed ok, but HTC's audio player forgot all the files I played (Last Played) and did not find any audio files (I have them on /sdcard/Music). It did not find them after several reboots, some of which were initiated by the phone all by itself. I then erased all the caches rebooted twice and it found the files along with the Last Played list. All seemed fine again, except the vibration of the tactile feedback would be less sharp and more wobbely. But only sometimes. Sometimes it was sharp. But besides that, all seemed to have healed itself and I could use the phone, maybe a bit slower, or maybe Avast and some tasker like app, I have running, made it a tad slower.
Then I installed yesterday's (today's ?) HTC update. Since that the phone reboots after two minutes. When I start the Preferences/Applications it takes ages to scan and most of the programs appear with their internal (com.foobar.someandroidapp) name. Just in order to change after a minute or so to their original name. Elixir2 crashes sporadically during use. Again I get the reboots without asking me for PIN.
Also, when I switch it off it shows the orange light for a minute, or so, instead of the green, though the phone is fully charged. It did not do this before. Oh, and in the meanwhile the HTC audio player forgets the MP3 files again I have on /sdcard/Music. Got no idea, what to do, since removing and reinserting the SD card did not help.
Also, I have the feeling, that something in the list of installed apps in the app-database crashes it. Where can I find it?
I can not even reset to factory defaults. At least I tried. It said it's doing it, then rebooted and all my stuff was there again (ie no reset).
It's crap! I need my phone's camera the next days because of some big Open Air event I am on.
See here for a little video about what happens... You need to download the vid (ca 80MB) and turn it around 90 degrees, sorry.
zmix said:
Hi,
all seemed fine with my new, one week old One V. Till I installed GTA III. First the installer stuck while downloading the datafies. I canceled the download, restartet GTA III, but instead of completing the broken datafiles download (or re-downloading) it just startet the game and crashed the whole phone in the intro animation, that was without sound. I removed and reinstalled it, the download now finished, I could get the intro with sound, but it crashed the phone at the same moment. Since then my phone behaves like it would be very sick or hate me ;-/. After this crash it startet looping the reboot. It would boot, ask me for my SIMs PIN code, then be ok for a short time, then reboot again. This time it would boot into the desktop without asking me for the PIN. All seemed ok, but HTC's audio player forgot all the files I played (Last Played) and did not find any audio files (I have them on /sdcard/Music). It did not find them after several reboots, some of which were initiated by the phone all by itself. I then erased all the caches rebooted twice and it found the files along with the Last Played list. All seemed fine again, except the vibration of the tactile feedback would be less sharp and more wobbely. But only sometimes. Sometimes it was sharp. But besides that, all seemed to have healed itself and I could use the phone, maybe a bit slower, or maybe Avast and some tasker like app, I have running, made it a tad slower.
Then I installed yesterday's (today's ?) HTC update. Since that the phone reboots after two minutes. When I start the Preferences/Applications it takes ages to scan and most of the programs appear with their internal (com.foobar.someandroidapp) name. Just in order to change after a minute or so to their original name. Elixir2 crashes sporadically during use. Again I get the reboots without asking me for PIN.
Also, when I switch it off it shows the orange light for a minute, or so, instead of the green, though the phone is fully charged. It did not do this before. Oh, and in the meanwhile the HTC audio player forgets the MP3 files again I have on /sdcard/Music. Got no idea, what to do, since removing and reinserting the SD card did not help.
Also, I have the feeling, that something in the list of installed apps in the app-database crashes it. Where can I find it?
I can not even reset to factory defaults. At least I tried. It said it's doing it, then rebooted and all my stuff was there again (ie no reset).
It's crap! I need my phone's camera the next days because of some big Open Air event I am on.
See here for a little video about what happens... You need to download the vid (ca 80MB) and turn it around 90 degrees, sorry.
Click to expand...
Click to collapse
here is what to do:
format the sdcard
factory reset your phone
Thanks, 1ceb0x, this is what I did. It all went fine. I have now applied the firmware update to 2.08.401.2, that got sent out these days. Seems to work out nicely.
What can I do, that I do not have to reformat in the future? Are there any utilities, that do snapshots of the system over time? Like Time-Machine for OS X does?
It's happening again. This is still the stock ROM, with the official (or was that two cuh?) update(s) a week ago.
I did not install any utilities, from which I think, they could go deeper into the system, like Avira and Automagic. I need a way to analyze, what my system is doing.
Oh, and it is reproducable: Mounting the phone as USB drive on a computer and, after work has been done, unmounting it on the computer, changing the USB mode on the phone. Now it starts. CPU seems to be up to 100% (UI becomes sluggish), apps behave strange (hadphone was in, speaker sounded, today appstore does not install apps, does not even connect, X-plore leaves a notification on screen after I quit, etc.). I had it two days ago, but the I rebooted a few ties, switched it off, took it from the USB cable and used it a little bit from battery. After this all was fine. But now that does not seem to help either.
zmix said:
It's happening again. This is still the stock ROM, with the official (or was that two cuh?) update(s) a week ago.
I did not install any utilities, from which I think, they could go deeper into the system, like Avira and Automagic. I need a way to analyze, what my system is doing.
Oh, and it is reproducable: Mounting the phone as USB drive on a computer and, after work has been done, unmounting it on the computer, changing the USB mode on the phone. Now it starts. CPU seems to be up to 100% (UI becomes sluggish), apps behave strange (hadphone was in, speaker sounded, today appstore does not install apps, does not even connect, X-plore leaves a notification on screen after I quit, etc.). I had it two days ago, but the I rebooted a few ties, switched it off, took it from the USB cable and used it a little bit from battery. After this all was fine. But now that does not seem to help either.
Click to expand...
Click to collapse
Wow, that's an amaizing type of error, I can assume a tad sdcard error, but I'm not sure of that.
Ken-Shi_Kun said:
Wow, that's an amaizing type of error, I can assume a tad sdcard error, but I'm not sure of that.
Click to expand...
Click to collapse
Szia
Yes, that's what I thought, too. I checked the file-system, I also ran a bad-blocks check, though, I am not sure, whether the utlity can do that reliably for an SDcard (since it has been written for a magnetic hard-disk). SDcards have a different technology. I got no reports about failures.
Now, that I hooked the phone to the debugger, I see the watchdog kicking in, but the traces.txt is being written to a directory, only root can access (and I am not). So I am still in the dark. Reports on the net have shown certain Sense devices to hace similare problems, with either too many apps installed onto SD or too many MP3s. The bugs are different. In the latter, the audio-player app of HTC is at fault, this seems to have been confirmed by HTC. Not sure, which Sense version, though, the phone was running ICS, but not a One series.
I'll hunt for the bug for a few more days, then I am going to root, custom kernel and custom ROM. Only convern I have with this, that I do not want to lose anything Sense related, because I love it so far. Ideal would be a ROM, that ported the S or X Sense, since those have more home-screens.
Yep usually clearing your caches returning your phone to factory mode should work, if not use the back nandroid.
Thread moved to.Q&A. Please keep all question related threads there. Thank you.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my HTC One X, using XDA Premium.

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen

[Q] LS980-Cloudy G3 ROM- TWRP installed&accessible- [email protected] Android is Updating screen
Hello everyone,
I would like to say first of all to the community, thank you for SHARING KNOWLEDGE. That is the key to everyone's success.
Now down to the gritty. My, now, I guess, mess of a LS980. For starters, the phone was running I would say very well considering my abuse. Big overclocks, gaming hardcore, and pushing the storage space hard. I performed a very easy and simple rooting and recovery program installation. If I remember properly, it all started with an app/.apk that sparked my interest with making the phone mine, was Autorec? (red roundish logo?) In some time I decided to install my first aftermarket ROM. I chose and installed without any issues , Cloudys G3 ROM. I cannot however remember the version number. It is by no means recent. I think I installed it last September so maybe 1.0 or 1.2 (sorry so much bad luck with stuff recently) TWRP version 2.7.0.0 is my recovery, and its functional. Unfortunately I do NOT have my apps backed up. I have no space. (just managed to get about 7GB on this PC to try to back them up but there is not external back up option, UNLESS you are OTG cable equipped I am not )
Now, I think, (this has been the state of the phone for about 3 weeks now) this all started to go south when I saw there was a Dorimanx OTA app in the play store. I used his Kernel for as long as I have had the G3 ROM installed. With no problems. So I figure this would be easier for me than button mashing trying to get into recovery mode without popping my screen out the front. LOL Upon using the app, I was informed of an update, I read the included information, and generally knew the deal. I allowed the app to download what it needed and restart and install like a good little computer. And this is where it gets a little grey for me in terms of order and symptoms. I remember checking the status of the install and it read failed! I looked into the reason why, and I was just plain full of junk. I then uninstalled painfully a bunch of rarely if that, used apps and gained back about 2.2GB of space. I ran Dorimanxs app again and let it do its thing and reboot. And again it reported fail! I looked into it more and noticed there were newer Kernels than available on his inter-web. Alpha versions. I located them on my device and rebooted into TWRP mode and selected , then flashed his 10.4.1 Kernel. Everything went fine. Phone reboots, the LG logo is no longer animated, and takes a bit longer to actually boot into a GUI. But it was, luckily.
So now, the phone would be a usable thing for about 3 minutes tops, before a power off, to a reboot. Which at first I didnt notice to be a boot loop. My battery surprisingly went from full to about 6% in no more than 15-20 minutes. I noticed the battery was getting warm like I was running the CPUs maxed under a serious load for a good half hour. Around the range to make someone pull it out their pocket wondering wth? So after the next reboot, power cycle, I jumped back into TWRP mode, and dug around for what I thought was the culprit, Xposed. I was having the worst time with my phone after a major Xposed framework error. I picked up my phone one day and out of the blue the xda framework was telling me that there were so many errors with it and my apps that ran fine, not being installed or activated. Upon looking into it, it was removed from the phone. I belive the order was , stable, 2.5/ 2.6, then I tried the beta 2.7. and thats the version that eventually , either broke, or uninstalled, I think, during those frequent Crashes! I tried to install the previous versions, even going back to the versions that came out last year like 2.4 . But none would install. And the phone grew more unstable in terms of its cooperation with its software. My normal apps and games worked fine. The phone worked the same, the music player, but there were apps that only can work with xposed that I utilize constantly, that were kaput. So I left the phone off. For a while. I had/have no time and really no resources to research and rescue a sunken ship. I come back about two weeks to it and I take a look around in the phones storage and hunt for any kind of recovery and disabler. I found xposed's disabler and flashed it. Same luck as before. About 3 minutes on, then dump.
I dig some more and found a ccc71 back up folder with some hearty backups that I didn't know were still there (no wonder I was always loosing space) and found another xposed installer.zip . I figured well , it didn't make any sense trying to disable something that wasnt enabled in the first place. (thats why I walk away and come back . fresh mind to tackle what stumps me) So I flashed the installed zip and reboot. Same thing, but now it started to loop around one minute. I power down. Found the recovery.zip that was saved on the beater PC and adb pushed it over the the phone. Im not good enough to adb install it. So TWRP'd it and rebooted, and d'oh! Now we just have the motionless LG ball, but flashing blue and green LED. And after about 2 minutes it would black screen, but be on. Not hung or anything. I connected to the PC, it never finds the right stuff but I used adb to verify state. And it said device. It still could communicate and push. I had it dump its debug, surprise! as it flashes that crap as fast as it can up the screen. But Im a PC guy so it was a fun, pause/break over and over till I found something useful. I saw some things that I could recognize like, failed starts, and longer than normal (for a speedy experience) function or call times, but nothing that slapped me with a red flag.
And that ended that nights attempts to fix thanks to the slowest no ram having box I was using to try to learn how to have the debug save to a .txt file on my PC so I could take a good look at the results.
Upon reading forum after forum, I came to something that looked promising, telling me that, that particular boot issue was due to the wrong radio being installed. So I hunted, and hunted, and laaaaaged my arse off and finally found it. Great I thought. Powered up ten or twenty times, finally get into TWRP, tried to flash it. BBBBBAAAAAANNNNT! nope. Downloaded another copy of the file and tried it again. No luck. ( I must say not until roaming around in these forums tonight did anyone bother to mention that you dont flash that radio. You instead have to inject it via LGFlashTool, which I have used before, and its a pain in the butt.
But before I go any farther, make anymore mistakes. I need some help.. I would really LOVE to be able to flash this , slap that, curse its name then hug it and get her working, without having to ditch my 492 apps. If I would have to say goodbye to happy times, I would like to say good riddance to ugly and annoying G3 ROM. I like not flat UI. My phone was depressing me every time I had to do any navigating around inside it. So I would love to go back to KK Stock LG ROM if push came to shove. But if possible I would just like to "repair, and regain access into the phones GUI system". So I could backup my apps. And eventually labor back to OEM Kitkat.
I apologize for the length of the post. But I just dont see the point of ping ponging with partial exchanges of information. I hope I have made my situation clear, and someone knows of someway, I can get my GUI/phone working again. Thanks to all in advance.
"a non functional smartphone, is an oxymoron"
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
strangely enough
siggey said:
Upgrade twrp to the blastagator last and dirty flash the same version of cloudy g3. And backup everything on the cloud. Mega give you a lot of free space.
_____________________________________Read more write less and be smart
Click to expand...
Click to collapse
strange thing,
just about 5 minutes ago, the phone, which I left on sitting at the LG screen by accident yesterday after posting the above, changed screens and presented me with the Launcher selection screen.
I immediately noticed that it looked wrong. Like if the resolution was way off. Like an old low res screen, very dull, sort of blurred looking.
I figured what the heck and tapped the screen and it of course did not immediately respond. It took its sweet time , about 30 seconds to show a change. The menu disappeared and a error message along the lines of , android system UI has crashed.
That is not the message verbatim, it was gone to fast for me to take it all in. And now its sitting at the blank powered on and repeating blue/green LED.
I havent done as you suggested yet. I kept getting results from Norway and other places and didnt understand a thing. But I found a TWRP update from Dorimanx, there was a link to it. And now I have to find my version of the OS. And to be clear, were you suggesting doing a re install, basically a file overwrite? And if so, when doing something like that, do you wipe the Dalvik cache ? Or do you just "dirty flash" it?
Thank you ,
I think that your screen is overheated. Never let the phone in bootloop for long time, it can destroy the screen.
About the cache, is better to clean it, but if I remember well the rom installer alredy do this.
_____________________________________Read more write less and be smart

Categories

Resources