I got my Viewsonic GTablet on Friday (2/11/2011). I loved it and had no issues. I downloaded and installed the update from Viewsonic. I visited the Marketplace that's installed on the device and downloaded some apps, mainly games. Today (2/14/2011) I took it to my university and tried to get on the campus WiFi. I had difficulties, so I took it to the IT department on campus to get some help. They took my device, tried to get it on the network and said that my device could not get on the network because their network uses certain "secure credentials" or something like that. As soon as I get my device back from them, every time it boots up I get and error message that says that Dashboard Home has stopped unexpectedly and to try again. I called Viewsonic's Customer Service, and they determined that I was stuck in a reboot loop. I have tried rebooting the kernel more time than I can count, but it doesn't do anything to help.
Has anyone else been able to solve this problem? I would take it back to the store I bought it from (Office Depot) to get an exchange, but they don't have one in stock anywhere close to where I live, and I don't have the box the device came in anymore.
What do you suggest I do?
The device is running the stock OS with the update from Viewsonic. The only apps I have installed are from the marketplace that comes with the device. I have not tampered with the OS or settings. I am also mildly technically challenged, but I am working on educating myself.
I appreciate any and all help. Thanks in advance. I also apologize if this has issue has already been posted and answered.
vafalla,
This doesn't sound like the boot loops I had, but I guess if it doesn't get you to a screen you can work with the result is the same.
If it were me I would get on a PC and go the the Development part of this forum. I think you need to get ClockWorkMod installed. CWM is a replacement "recovery" program that gives you other functionality to restore, communicate, partition drives and a bunch of other things. There are a couple of threads in the Dev section that tell how. You can download CWM v.08 (the older one works!) and put the update.zip file on a microSD card and edit the recovery folder "command" (no .txt or other ending, just command) file in Notepad to load "sdcard2" instead of sdcard. then put the card in the gtab and reboot holding down the Vol+ key down. You'll get a message in the upper left corner of the screen that recovery is loading. After it installs, if it doesn't startup, reboot with the Vol+ key down again and you should be able to get into CWM.
From there, you can find the CWM partition command and change the two partitions to 2048 and 0.
From there, there are a bunch of threads which tell how to load either a stock recovery file to get back to stock -- or how to load VEGAn 5.1 (or now, 5.11).
Hope this helps get you started. I just didn't want you to think your tab is bricked and that all hope is lost!
Rev
P. S. --- Some of the other threads may have better instructions than mine!!!
Thanks so much for the help! I'll get right on it and see what happens.
Plug in your gtab to the power and see if it boots. Could be they ran your battery down.
Bootloop help
If you really want to learn about the gtablet, youtube ehunyadi. he has done over 10 excellent videos and his most recent is how to install CWM and TNT lite 4.2..sounds like only diereence for you is you'd install CWM to microsd.
Related
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
From bad to WORSE!
I discovered the dcom222 thread that describes my problem and details a solution. I followed it to the letter, changing the command and using my microSD as a secondary boot to reinstall the vanilla tnt ROM.
But then it just stuck on the tnt logo, faded in and out 3-4 times, and went dark! The device won't turn on or off (had a full charge when I pulled it from the wall socket a few moments ago)
Please tell me I haven't bricked this thing!
still no luck...
I was able to power the unit back up, but I've tried to recover and flash all three setup files I have (vanilla tnt, ota update tnt and tnt lite 2) but nothing works!
All of them create a loop of some sort, whether it's the viewsonic screen, gtablet screen loop, or the tnt logo screen blinking on and off, NOTHING boots to the desktop.
Going to bed before I drive my self insane. Hopefully someone in the know will reply by the time I check this at work.
thanks in advance
You have not bricked it, don't worry. This device is very hard to truly brick. If all else fails there is nvflash or the apx mode fallback. But I don't think you need that if you are still able to boot to clockwork recovery.
In clockwork go to advanced - mounts and try mounting and unmounting your partitions. I suspect your user partition may be screwed. This seems to happen fairly frequently especially the first time you flash a ROM. It happenend on my first flash and not again since. Clockwork lets you repartition though. Search the forum for partition fix, its not too big a deal.
If that fails try roebeet's thread on nvflash recovery for TNT lite. If that fails, search for APX mode.
As far as I know there are zero bricks from ROM flashing so far.
Sent from my SMB-A1002-3G using Tapatalk
Life in LA said:
Just joined to say thanks to Roebeet and everyone who is active in this forum. Because of the obvious potential of the gtablet being explored here, and discussed on phandroid.com I decided to take the plunge and purchased one tonight. I might have passed this tab by, and waited months for something else...
--and here's where I cry for help!
I carefully followed a series of step-by-step instructions I found thru google, to install the latest tnt lite found here on XDA. Everything seemed to work without a hitch, and was prouder than a pappa to have completed my first root and mod ,ever!
BUT right after I DL'ed and installed the flash 10.1 apk things went south. The browser constantly crashed to the home screen, and the market and email apps were crashing also. I rebooted and now I am greeted by the tnt setup screen that is covered in an endless wave of crash warning dialogs! I can't tap them away fast enough to see the desktop.
I've tried to do a recover, but I can't get thru the setup (that keeps crashing to the first screen also) to use the USB to mount the internal mem to my Mac.
I am insanely happy about the potential of this hardware, but I've painted myself into a corner. ANY help would be greatly appreciated.
And yes, I do look very handsome in my profile pic.
Click to expand...
Click to collapse
Scroll down to post number #869 http://forum.xda-developers.com/showthread.php?t=842004&page=87
feeling better
Thanks for the assurances that I didn't wreck the device, and pointing me to some solutions. I have a few questions:
what is clockwork mod? If I am able to recovery boot from my micro SD card, do I already have it? (I downloaded a bunch of recovery images to start, per instructions)
If it's something I still need to download, is it a PC application? How am I supposed to change settings in it (manage partitions, etc) if I can't get the tablet to boot?
-- stuck at work and dying to get home to fix this thing...
Ok, more detailed instructions:
If you press and hold down Volume + when you are pressing the Power button to boot up, and keep holding the Volume + key until you see a message that says "Detect a Recovery Key Pressed", that should get you to a text menu from which you can navigate using the volume +/- keys and the Home soft button to flash ZIP files and do other things. That menu is ClockworkMod Recovery. Since you remember installing a recovery.img, it sounds like you probably (hopefully) have ClockworkMod Recovery on there.
If you get to ClockwordMod Recovery, you can go down to the Mounts and Storage option, then you will find the "Mount USB storage" option at the end of that list. That lets you plug in and mount your internal memory area as a standard USB drive to your Windows or Mac computer to copy over new ZIP files and the like to your G Tablet.
You can also check that partitions are all mounting and unmounting successfully in that menu. If you go instead into the Advanced menu, you will see Partition SD Card, which I believe is what you might need to do at this point.
If booting with the Volume + button held down doesn't get you anywhere and you see nothing about Recovery Key Detected and don't see any text menu, then you don't seem to have a working recovery. At that point you'll have to do what phfaty suggested, read the post he referenced, and follow the link therein to the tegratab forum post to get the NVidia Tegra SDK installed on your Windows desktop and use the NVFlash tool and APK mode (where you hold the Volume - key down while booting instead of the Volume + key) to reflash your tablet.
still not working...
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Life in LA said:
The good news:
I do have clockwork mod installed. Must have been in 1 of those zips or rars I ran in the very beginning.
The bad news:
it's still caught in a boot loop. I've mounted it as an external drive 3 times now from clockwork, and tried all 3 versions of the operating system (vanilla, vanilla with the ota and tntlite 2) and NOTHING makes a difference.
Click to expand...
Click to collapse
1)Boot into clockwork.
2)Navigate to Advanced menu
3)Choose partition sdcard
4)Choose data partition desired size(1024=1GB)
5)Choose 0GB for the next selection(swap not used)
6)Do a factory reset from main menu
7)Reboot
8)If that doesn't work, then reinstall ROM, then reboot
UPDATE
partitioning the drive and wiping the user data did the trick. I'm up and running again. thanks to all who chimed in to help.
[SOLVED]
MESSAGE TO DEVELOPERS/ANYONE WHO CAN HELP
Long story short, i edited my build.prop incorrectly and reset (yes i know very stupid) now my motorola cliq opens up to the motoblur screen but repeated messages saying "Sorry! the process X has shut down" show up.
Literaly, nearly nothing can open up but i am able to enter usb mode if i fight with the endless popups. i can also enter recovery mode because my phone was rooted before this. The problem is that my recovery image doesnt have any options that could help me
(reboot, apply sd card:update.zip, and wipe data/factory reset)
i've tried putting an official motorola update.zip onto my sd card then running the apply.. but like i told you before my build.prop is messed up a little so an error shows up saying:
Installing update...
E/:Failure at line 1: assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=motorola/morrison_two_us/morrison/morrison:1.5/CUPCAKE/1.4.8:user/rel-keys" == "true" || file_contains("SYSTEM:build.prop", "ro.build.prop", "ro.build.fingerprint=MOTO/morrison_two_us/moInstallation aborted
Press Menu+Back to reboot
All i need to do is fix the line of code i messed up but i cant reach my systems files,...i attached my original build.prop and a copy of my corrupted one to show you.. I also cannot use the phone service or network service (even wifi) because like i said, nearly ALL the services are unable to stay on, they immediately shut off at startup.
Ways to fix this would be to REACH/EDIT THE SYSTEMS FILES
1. I cant use an app like root explorer since i cant access any apps on my phone even things like my settings
2. Turn on usb debugging somehow (I cant access my settings app so im lost on this one)
1. ingenious DESKTOP program that can somehow access my phone's system files without adb (if it can access the sd there has to be a way..)
3. Ive looked around to maybe find a custom image recovery that had options like editing system files (shouldn't be hard to make..) but ive found none with that option and im not sure how i would install it without adb...
What i CAN do
1. ENTER USB MODE (that has to count for something so Developers Please help me)
2. I can play with the motoblur intro screen to some degree to make it go away, then a blank black home menu appears. If i wait a while for the popups to stop at the motoblur screen, i follow the instructions but it gets stuck at registering a new account or existing one since you need network access.
3. ENTER REVOVERY MODE (but the only option that looks helpful is the sdcard update which gave me an error...) I havent tried the wipe data/factory reset because the factory reset doesnt touch the build.prop so its pointless
WHat should I do? WHoever sees this please give me advice or direct me somewhere to get it... THANK YOU
[EDIT]
BTW what i was trying to do on the build.prop was replace this line (ro.build.fingerprint=generic/sdk/generic:3.2/HTJ85B/140714:eng/test-keys)
with (ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys)
but i messd up and put
(ro.build.fingerprint=verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/rel)
youll see this in the attachments...what this does is unlock my 1.5 firmware market to ALL the apps (updating to the official 2.1 using recovery wouldve handled this but i didnt even know of this update till after my mistake)
I just thought id mention...
if you have adb abilities you can push the old build.prop. If you do not know a out this then post back and I will help you.You said you can enter recovery, but that is stock original recovery that anyone can get access to. If you ever bootstrapped your phone you can try pull the battery out, wait about 10 seconds, then plug your phone charger in without the battery in. If your bootstrappped this will pull you into a more advanced recovery mode. The last option is to use rsd lite to flash an sbf to your phone if nothing else works. If you have never done this just look up sbfing motor cliq to stock.
Good luck, and remember to thank me if this helped
SOLVED!!
I fixed my phone on my own but THANKS to rootfan for being the first to answer.
HERES HOW:
I was able to access recovery mode and from there i discovered the sd update option.
It took hours of research and work but i learned alot about adb,motorola, cliq, etc.
Anyway, i originally found the Blur_Version.2.1.5.MB200.T-Mobile.en.US.zip and i tried to put that in my sd card (i could get into it from the phone) but when i tried to update using recovery it gave me an error so i decided to try the "latest 1.5 with Blur 1.6.1" which was actually very hard to find... you can get it here
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/downgrade-to-cupcake .html
Lastly, i put that on my sd as update.zip, went into recover, and the update was SUCCESSFUL! MY PHONE REBOOTED AND NOW IS ACTING NORMAL AGAIN. Now, im trying to update to the Android™ 2.1 (Eclair):
motorola. com/staticfiles/Support/Experiences/sdcards/US-EN/tmo/cliq/2-1_index. html
but im still getting that error whether i update using recovery or the settings/about phone/system update option... Thats strange but my phone is still working normally and ill find a way to update to 2.1...
ONCE AGAIN THANKS TO ROOTFAN AND HOPEFULLY THIS POST WILL WORK FOR SOMEONE ELSE WHO MAY BE HALF-BRICKED (no adb, no usb debug, no root explorer) THERS STILL HOPE IN RECOVERY+USB DRIVE+BLUR VERSION SOFTWARES
Thanks man, now this is probabaly a redicilous reply, since im sure you would have already tried this, but you can try going into settings, about phone, and click on update and see if the 2.1 eclair ota update will work on your phone.
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
stepph said:
i've got a simila problem on my samsung Galaxy S5570...
... and i need to prepare an update.zip .
Can you help in this, or you only downloaded a new rom ?
Click to expand...
Click to collapse
You can reflash a stock rom back if you wanna get it done easily - or even a updated gingerbread one from samfirmware.com
Search for S5570 in these fora for some guides
This post doesn't seem to match others asked before.
I had a perfectly working rooted/rom'd HTC One (M8). Unfortunately, screen cracked so I sent it off to the insurer to sort. It came back looking great. However, I was now unable to access any of the internal storage. Everytime I tried to download a photo, voice clip or Mod Edit: removed mention of warez it would say 'unable to download', 'cannot save' or something along those lines.
I checked to see the device was still rooted. It was. Nevertheless, I perhaps in ignorance, ran through all the steps over again and spent 3.5 hrs doing so! I now have a wonderful adb file on my desktop and I was fiddling around doing fast reboots etc and trying to flash a customrom in the hope that this would fix the storage invisibility/lack of permissions. I tried fixing with busybox etc but I couldn't even install busybox as it didn't recognise that there was any internal storage whatsoever! I also could not load onto my storage (for the same reason!) the latest SuperSU zip to flash as a rom.
In the end, through fiddling about, I was able to find my old storage pack. It was all there and I located an old SuperSU from when I had previously rooted about 6 months ago (an old version now I assume). Flashed this and rebooted. I was still adb connected so ran a fastboot and chose to run the TeamWin Recovery Wipe (standard setting, not advanced).
When wiped, I tried to get my phone to turn back on thinking it would be factory reset and I could start again but now I literally cannot get my phone on!! It is plugged into the computer via USB (i've tried disconnecting it too) and no matter what I try I cannot get this phone to do anything now - it's just a black screen that doesn't look completely off if I look closely it looks like it is on somehow....? Tried holding down vol down and power - nothing. It has flatlined!
Any help PLEASE!!!!! ?????
Hi, thank you for using XDA Assist. The best place to get help is in your device's specific forum here, http://forum.xda-developers.com/htc-one-m8 To get help on your specific problem try asking here, http://forum.xda-developers.com/htc-one-m8/help/help-thread-htc-one-m8-questions-t2897783
I'll give you the whole story so bear with me. First off, I'm very new to the Android OS and tinkering with phones and tabs. I'm a computer network administrator and pc mechanic. I'm mainly a hardware guy though, no programming experience at all. But I'm not afraid to jump right into the inner workings though, especially if it's already broken.
And that's probably why I find myself in this position today with this device.
I recently bought this Tab 7.7 to use as a display for my new drone. When it arrived I tried to download the flight control app and it refused to install. No error messages, it just did not install. In looking, the unit was on Honeycomb 3.0. My guess was it was WAY behind in upgrades so off I went to make it bigger and better. I downloaded a zip file for Lollipop 5.1 onto my SD card and was able to load that. Upon reboot I had a screen and an OS. I went into settings and saw where it had upgraded. Success, right? Well, then I went into Wi-Fi settings to add my network. The keyboard would not come up on screen. So I did a bit more research and tripped over the fact that I needed to also load a GAPPS file to add the apps and drivers back. THAT is when I went down the rabbit hole.
The install did not go well and I somehow wound up with no OS at all. Probably after thinking I was following the correct process of resetting and clearing caches before installing the new files. Then this 3 day journey of learning began. I have downloaded Odin, Notepad++ to edit files, Minimal ADB and Fastboot, Samsung KIES and all manners of ROM builds and GAPP files. As of this moment I have absolutely no OS on the unit. Upon turn on it goes directly into the CWM Recovery v6.0.4.5 screen. I am able to boot it to the download screen and Odin can SEE the unit. But I can't get any further with that program other than seeing the unit listed as detected. I'm not able to get anywhere with KIES. No detection or anything.
Now I'm admitting I messed this unit up. I'm not blaming any written procedure or ROM developer. I'm not stupid but evidently don't know all I NEED to know about this process. So I'm here asking for guidance. I really would like to revive this unit and get it back to where I can use it as my monitor as originally planned. But one step at a time. Please give me the correct steps to do to get an OS reloaded and revive this unit.
I'm thinking that my best bet would be to use a TWRP image file to rebuild it. But I need the step by step process for that to make sure I do it correctly.
MANY thanks for this board and the help AOT!!!
Dave
Being the impatient type as well as a DIY'er, I pressed on with trying to revive it myself. I downloaded TWRP as a zip file and added it to the SD card. Booted and installed from the zip file. Screen said it loaded successfully. I rebooted and tried going into recovery (holding power and volume up) expecting it to go into the TWRP console. Instead it went into the regular CWM Recovery screen. Oh well, another frustrating dead end for me. I'll just set it aside until I get some good instructions from someone that knows what they're doing. Best I do that rather than brick it. I can at least access the recovery screen. Odin sees the unit but I cannot find the right file to load from there.
Okay, I'm truly stopping now. Another dead end. I was able to find a couple of files for restore using Odin. Loaded one and now I boot into Android system recovery <3a> instead of the CWM Recovery screen as before. I tried loading a recovery image from a zip file and it failed signature. That seemed to be telling me the tab is now not rooted. So I downloaded SuperSU to the SD card and tried to load it. No joy, it fails signature too.
Arrrggghhhh.........
Can't even shut it down.
Told you I'm impatient. Now have used Odin and installed TWRP 3.0.2-0. Going slowly now. Taking it one step at a time. This is the first positive step I've had so far in 3 days.
:silly:
Baby steps. LOL
Used TWRP to flash SuperSU. Now the unit is rooted and rebooted to TWRP. I still have no OS on there as of yet. I'm guessing my next step is finding a good stable ROM file and use TWRP to flash onto the tab.
Downloaded OmniROM Marshmallow 6.0.1 (https://androidfilehost.com/?w=file...69dc16313bf0332c8794621c6c7f505edf855e0d499d8) and the Open GApps ARM 6.0 stock file (http://opengapps.org/).
Will try to flash those through TWRP and hope for the best.
Joy...at last. The downloaded OMNI 6.0.1 worked when loaded using TWRP. The GApp file failed. Will try another one to see if it works.
https://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Booted to TWRP and was going to install the GApps file. I had left OMNI 6.0.1 on the card too and by mistake selected it. Dooohhh......
I'm an accident waiting for a place to happen. LOL
So, after REloading Android 6.0 I proceeded to load the gapps base file. Reboot and all appears to be going smooth. Apps updating and such. After about 2 minutes I get a message onscreen that unfortunately setup wizard has stopped. Hit okay but the message persists to pop up.
So.....
I guess I'll take a short break then do a wipe and reload of the OMNI and the working gap file and see what happens. At least I got to see it actually boot and let me get into setup. I went to add my Wi-Fi network, added the credentials but it never connected. Something else to look into.
More fun ahead....but at least I'm moving forward now.
A happy camper. Because I was able to revive this tab and because I had the patience to figure it out myself. And my wife swears I have no patience.
LOL
So...the key was downloading Odin and the Samsung drivers on my laptop.
Then download the TWRP.tar file to the laptop.
Boot the tab into download mode by holding power and volume down button. Select yes to continue.
Connect the tab to the laptop with the USB cable. See that Odin can communicate with the tab.
Select AP and find the TWRP file location and start. After it finished, rebooted and since there was no OS installed, TWRP recovery opened.
The next thing was download SuperSU file and drop it onto the SD card. You CAN go ahead and find the correct ROM you want and download the file as well as the GApp file. Drop all 3 onto the SD card.
Then insert it into the tab and select Install. Just be very observant WHICH file you load in what order.
You will need to install the SuperSU, reboot and then install the OS ROM followed by the GApp file.
Select SD card and the SuperSU file. Wait for it to complete then reboot.
After loading SuperSU and reboot, you need to get back into TWRP Recovery program by rebooting while holding power and volume up. This time when you select Install, pick the ROM file first then pick additional files and select the GApp. This way TWRP will first install the OS from the ROM file and immediately load the apps file. Then reboot and you are done!!!
And it took 3 days of round about to figure this out.
LOL
I just downloaded my flight control app and I'm off and running with Marshmallow.
Hope this helps at least one person that is new to this whole process as I was!!!
Dave
I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?