Hello, sorry for my bad english, I'm from Germany.
I have a Iconbit NT-1006T from my Dad, and it stucks at the Boot Logo.
The only thing i can do with the Tab is to boot it into Recovery mode.
But in Recovery i can't do anything. ADB Connection doesn't work, wipe cache and data doesn't help.
I want to backup the Data (if its possible) and flash a new firmware, but doesnt find any firmware files.
Perhaps someone can help me, to solve my problem
Edit:
I did a little bit process. I found some Firmware files on files.iconbit.ru including the Software (Action PAD Product Tool) to flash.
Now it seems, that my Computers have problems. I tried to connect my Tab with 2 Computers and 4 different USB-Cables, nothing works. Also a different Tab won't connect with my PC. I also tried different OS (Windows and Ubuntu).
Please help...
Related
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.
Hello
I bought a Lenovo p780 from a Chinese website 6 months ago (4gb), rooted.
I faced a problem with the signal of sim cards "invalid imei", so I tried to install TWRP recovery using a tutorial I saw online to use the recovery to install a new "modem" file. I used Mobileuncle app to do this but this step caused my phone to enter a bootloop, and the only way to get rid of this loop is to press the reset button whenever you want to turn the phone on! I tried to install other recoveries using Mobileuncle but nothing has changed too!
I also tried to flash a stock rom using sp flashtool but it just didn't work!! I tried many stock roms versions and many versions of the flash tool programs but when I press "firmware upgrade" or "download" nothing happens! believe me I tried everything to make this happen, I even tried to do this on different computers (win 7 and win 8.1) but I got the same result: nothing! No need to mention that I've already installed all the USB drivers on my computers. I read every single word in every single tutorial I found (including tutorials from this forum), but it's always the same failure!
I tried to change the modem file using Root Explorer but I missed with some folders and now even the Wifi doesn't work. All I need now is get my phone functions as normal with stock rom or with a custom rom.
I would be very appreciated if you can tell my what's wrong and why I can't flash a rom to my phone although it's not bricked at all and I can turn it on!
Hello. I'll try to explain my problem because I really need some help.
A few days ago, I was normally using my Tablet ECS TR10RS1 Intel®.... I turned it off, went to sleep and the next day when I was going to use it again, the OS didn't start, so I tried and tried until I found a forum where they led me to restore a backup file because the original firmware/rom wasn't still available.... publicly. I tried that, but in the process, I accessed the EFI Shell... That wasn't trouble at all, I just plugged the keyboard and typed "exit", and then it let me to the BIOS... And that's when my real problem began: I restored the factory setting default... and it involves "disabling USB ports".... Now, AGAIN, I'm stuck on EFI Shell. But this time, I can not type "exit" since the keyboard is not recognized by the Tablet.
Then I pressed Vol UP + Power ON and I get access to another menu "DNX".... And that's what brings me here to your forum:
I was briefly reading that one of your members managed to flash the BIOS via DNX, so I was wondering if you guys could help me do that to my tablet because I'm not planning to have a really expensive paper holder.
Thanks in advance.
Jinky.
Not sure about your case. But as your tablet use clovertrail chip like my zenfone 5 n fonepad7 170CG, then there's some methods to unbrick like via fastboot, flashtool, or intel factory flash tool... all of above are required a valid firmware, at least a IFWI package then intel FFT can unbrick anyway. So try to find your need, as i tried to help u to find it, but most of webpages use spanish, then i didn't understand anything
Sent from my ASUS_Z00AD using Tapatalk
Hello my dear fellow community of XDA
I’m asking you for help, I found myself in a tough situation because I damaged system in tablet Nexus 9. Bootloader was already unlocked in my device when I bought it. I assume that the system was original. I didn’t notice any modifications. I damaged this system by uploading a file in a fastboot mode connected by ADB. This file is for rooting. I used this guide on the YouTube:
After doing everything step by step in this guide and switching my device on there was a sign of launching - vibration. The next thing I saw was white Google logo and after that the animation of loading appeared. It was loading without any success.
Before uploading the root file I also tried to upload TWRP file via ADB but it didn’t make any difference. After uploading TWRP files system launched properly, there is no new app in the app list and no combination of buttons such as power + volume that launches TWRP. Please tell me if I’m doing something wrong…
I tried to fix this bootloop by cleaning files via Hboot - factory reset but it didn’t change anything. I was searching for guides that would help me solve my problem but I couldn’t find anything useful. Each of them was old. They were from 2014 or 2015.
I would like to have a working tablet with TWRP, root and other unofficial system (you can give me some suggestions, I was thinking about Android 9). I don’t know where to start or what should I do first. Fix bootloop or upload TWRP ? What is correct order ? How to upload TWRP eligibly ? I rooted devices only several times so please excuse me, I am not a professional. I know that guide on YouTube mentioned before was for Android „L” not „N”.
Summary:
> Tablet Nexus 9 OP82100 WiFi version 32GB
> I use PC with Windows 10
> After connecting the tablet to the PC via USB cable in fastboot mode the tablet is visible in ADB console on the list of devices.
I hope that each information I gave you is clear enough. This is my first post on this forum. I hope somebody will find some minutes for reading this post. I’m counting on you. Thank you in advance for any help.
Ok, I honestly didn't read everything, but if you have and can access fastboot, flash TWRP, transfer a ROM to the internal memory, wipe data (not storage) and flash your ROM.
Try getting Wug's Nexus Root Toolkit, it's a graphical UI for adb and fastboot, might be a little friendlier for you.
Hello, I am actually brand new to xda-developers, I have did something stupid I guess... So, I had stock firmware and I already have it rooted and installed twrp. At this point, I have tried many many things and it is telling me No OS now with TWRP (I boot-looped it by uninstalling bixby :v) and wiped the data, formatted it, and all of that and more. I keep getting errors with everything, the most common ones I seen is ERROR: 1 and ERROR: 7, I know this is useless information but I had one about updating dynamic partitions with trying to install Lineage OS. I tried installing GApps thinking that would fix it, it tells me that it is made for ROM 11.0.x and told me to download the one for my ROM: 11 (SDK 29). I have no clue what that means or anything, but to me, it seems I have pretty much screwed up my phone somehow all from uninstalling Bixby.
Odin will not work, I have installed the right Samsung drivers (my windows PC is ****ed too, majorly somehow. Might have something to do with it).
ADB will not recognize my device, in twrp recovery or download mode. ADB Sideload function of twrp does not load (sits there forever).
I really, really need help. Please.
TL;DR
Uninstalled Bixby with Lucky Patcher and System App Remover, phone decided to reboot hours later and got stuck in boot-loop.
I have not been able to do anything flashing wise. ADB does not work, so I am stuck transferring files to/from my PC with a USB stick w/ OTG Adapter. It seems to work ok, as I was successful in flashing TWRP recovery (updated it from somewhere).
I need my phone, and it does not function in its current state and I am clueless on what to do (I get all sorts of errors that seem unfixable).
I last had Android 11 (stock firmware) on my phone before it was boot-looped.
Exact Phone: [Excuse me if I am not allowed to post links, but it is just to amazon of the phone I bought if it helps anyone] https://www.amazon.com/dp/B082YF7WY5
TWRP Version: 3.5.0_10-A11_1b1
Samsung Galaxy A51 A515F 128GB DUOS GSM UnlockedUS Compatible LTEExynos 9611 Chipset
Fastest way to contact me: Cyberhound#5672 on Discord.
I will try to respond as fast as I can, but I am without a phone :/
NOTE: I have resolved this issue.
I flashed stock firmware using OTG (just the .img's) and then reinstalled Samsung USB Drivers, restarted my computer, connected an old phone that worked so I could verify if the USB Driver was working (and so ADB as well).
I reconnected in TWRP Recovery, and it worked and showed up on Odin.
I was able to flash stock firmware successfully.