I bought a " Figo Atrium 5.5 ". The Figo website has instructions to flash the device to 6.0 Marshmallow instead of Lollipop. I believe these instructions are incomplete. Here is the link, I'll detail for you what I've tried using their recommended software SPFlash https://support.figoglobal.com/support/solutions/articles/16000047848-android-6-0-atrium-5-5
I downloaded and extracted both files on Windows 8 64 bit desktop, the SPFlash tool and the other the Atrium ROM itself. The very first instruction is installing the drivers which I do using the install.bat file from the "Driver_Auto_Installer_v1.352.00" folder. I believe my install fails at this point. Opening the Flash_Tool exe after installing the drivers (the tool does say they installed properly) I never get any information in the Chip Info in the Flash_Tool. It appears those drivers are not installed properly.
Researching this, I came across videos that suggest the drivers were not being installed properly because the drivers are Not digitally signed. I followed the instructions to fix the problem by booting to Advanced StartUp options then choosing to run the OS with digital signing checking disabled. Now on installing the drivers I get the popup asking me if I am sure I want to install the drivers I choose Install Anyway. The driver install tool just sits there for a couple of minutes doing nothing, then the popup message comes back asking again, am I sure I want to install the drivers. This is an endless loop, the application never attempts to install the drivers. The phone is plugged into the the PC at this point because I assume it must be for windows to see the phone. Note, at no time except the End of the instructions does it tell me to have the phone plugged in. This confuses me greatly. I don't know if the phone should be plugged into the pc at this point or not. Can someone who if used to doing these kinda flash jobs look over these instructions and help me figure out what I'm doing wrong. Thank you. I will do my best to answer back with more info, I'll be home all day watching this thread.
( btw, the forum on that site is moderated. I have tried over two weeks ago to post forum messages about my issues, but the moderators never posted any of my messages - it seems customer service is non existent)
Please mark this as Solved. I fixed my problem with a bit more research. Figo gives incomplete and also incorrect information on upgrading the Rom ( as you can see) Nowhere do they tell you in the instructions that you need USB Debugging Enabled or how to do it. This is a critical step or the drivers will never see the phone. The drivers did correctly install the first time as I suggested. That was the incomplete information. The incorrect information is this: They tell you to take the battery out to flash the device - which will never work because the phone needs power for the drivers to flash the device. What you have to do while the phone is On and Connected to PC is remove the battery then put it back in - then the phone will flash. This is critical step 2 they were wrong about. I suspect it has something to do with a bad Chinese translation.
Related
So I've been following the bootloader unlock instructions on the Sony-Ericsson site and when I have plugged the phone in and the instructions say it should ask me for drivers it just plays the driver install failed noise, so in device manager I have the S1Boot Fastboot listed but when I point the driver update wizard to the adb folder where the driver is it just says it cannot find it. Anyone had an issue like this or knows how to fix it or have I done something completely idiotic because it's 6am and I haven't slept for 2 days?
you need the google usb drivers (android sdk) good luck !
Yeah I got past this bit and have the phone unlocked now but during the proccess my camera, lockscreen and a couple of other bits have stopped working and I can't simply revert back to the original software as sony's tool won't allow that. Also can't find a clockworkmod recovery image for the device so have no clue how to put the cyanogenmod nightly that's out on.
Can't you use flashtool to flash a stock rom ?
Yup, all recovered now.
It would be much better if this most essential of sites for people mucking around with there android phones had a section for the Xperia Pro, there are already plenty of threads for the device but they are spread over every other Sony section and makes finding the thread that will help quite difficult.
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly:
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk
So i have a Pixel 6 (not the pro). I love it, despite it being a bit buggy at times. My girlfriend loves it too so she also got one. Her screen got damaged and we took it to a local repair place. They ordered the part (took about 5 days to come in) and the repair took about an hour. The repair seems to be of decent quality work. Then we realized that the fingerprint sensor was not being detected and the option to use fingerprints was no longer available in the settings. A little bit of research and i found that this is a common problem which google has failed to provide any kind of solution for.
I read through googles bug report page found here ( https://issuetracker.google.com/issues/218761008?pli=1 ) as well as a couple other pages on google, reddit, etc. I am creating this thread because i am fairly certain that a solution to this problem can be engineered by the community but personally lack the skills required to accomplish this single handedly...
So...
The issue is that the fingerprint sensor needs to be calibrated after being replaced using the official tool found here ( https://pixelrepair.withgoogle.com/udfps )
There are two ways to connect to your phone when you run this tool. Using fastboot (via "adb reboot bootloader) or fastbootd (via "adb reboot fastboot
When attempting to run the tool via fastboot the tool fails at the download step saying "Couldn't find the unique calibration software for this device"
when attempting to run the tool via fastbootd it fails at the installation step saying "Couldn’t install the software" (seemingly having successfully downloaded the tool but being unable to install it in fastbootd)
Certain posts on the google bug report page have claimed success by running the tool on different firmware builds. I have tried flashing the oldest 12.0 build, the current 12.1 build, and the beta 13 builds as suggested by various reports to no avail.
However, when i run this tool on my own device which has the factory original screen, it runs and completes flawlessly. This leads me to believe that reports saying the issue is with the build quality of the screen replacements being sources by boutique repair shops causing the tool to not recognize the screen may have some merit.
Now...
At the bug report page I linked to above, post #20, it shows a user who inspected the url for the command which is failing with a 404 code. I assume this is what happens when running via fastboot and it fails to download the tool...
This is where i lack the skills needed to implement a solution. Im pretty sure that there is a way to redirect the failing url to a destination of ones choosing. If so, it should be possible to extract the url used by the tool when it succeeds on the downloading step (either via the fastbootd method or when used on a device that has not been repaired). The URL could then be used as a redirection target for the tool, or possibly downloaded (or extracted from the browser cache) and run independently.
I dont know if any of my ideas here are viable, but there seems to be a disturbingly large number of users who would benefit from a solution.
Any ideas?
PS: please forgive any formatting failures on my part