[Q] VAPD7 stuck at splash screen - Viewsonic ViewPad 7 & Variants

I have a VPAD7. It's stuck at the viewsonic Birds flashscreen. This is not a looping boot such has has been described in other threads -- it doesn't alternate between the flash screen and brief bursts of blank screen. It just sits there at the splash screen; I've left it for hours, and it just sits.
This all started when I rebooted to FTM (holding down the power button and vol down at the same time) in order to get this information:
* SWVer=3.240
* MODEL:FM6-0001
* HWVer:107
When I rebooted (power cycled) after that, it was stuck.
I have rooted the machine in the past (months and months ago), and installed CW mod. I *can* reboot the machine into recovery mode, holding both volume buttons when pressing the little pin reset button and then quickly pressing and holding the power button. I get the "ClockworkMod Recovery v2.5.1.2" screen. From there, I've tried wiping the cache, wiping the Davlik cache (although I get an error message when doing that about how it can't mount /dev/block/mmcblk0p2), flashing the update.zip on my SD Card (which is lakehousetech's Froyo 2.2 enhanced), and "wipe data/factory reset". I've also tried restoring from some of the backups I made in the past.
No matter what I do, if I try to do a straight boot, the device just hangs there at the splash screen. I can boot to FTM mode, and I can boot to recovery mode, but nothing seems to allow me to get the thing to actually boot all the way up and run.
Does anybody have any ideas of what might be wrong and how I might do something about it?
Thanks,
-Rob

You have new version of viewpad7. Maybe lakehouse rom is not compatible, please try other.
Sent from my ViewPad7 using xda premium

To OP, Froyo ROM that you've saved should be ITE (multi-touch screen) compatible with H/W ver. 107 - I don't think the custom ROM itself is the source of the problem, unless your saved CWM files are corrupted somehow ?
Do you have another mSD card, try formatting it first and copy the CWM folder/files on it, insert into Vpad7 and boot into Recovery, then do a full dalvik, cache and system/data wipe 3 times - before doing a Restore of the Froyo ROM.
Make sure your device is fully charged and let the ROM boot up & settled down, which can take as much as 10 minutes. If you have a 3G mobile Sim card, pull it out although it should NOT affect anything - just precautionary to rule out other factors.
If still NOT good, you will have to try flashing another custom ROM from scratch, I've been very happy with EU V1.7b ITE verision since last Sept/October - the original developer Amalgation hasn't been around, I think, and his link might still be broken for the download - hopefully, you have it saved before. Otherwise, post or PM me and I can provide a secured link for the untouched, original zip file as uploaded before - so that you can try to get the device back in working order.
Or, download the factory *.nb0 file and install it with the Viewsonic utility - for stock, unrooted condition as shipped. Then, you can use SuperOneClick to root, install CWM v2.x again (I personally like it better than the newer 4.x or 5.x verisons to set up A2SD) and resume playing with the limited choice of Roms out there now ...
Good luck & post your efforts/results back here to see whether other ideas might be useful. You didn't try to install/override with any overclocking kernel as none of them work with the ITE hardware, right :fingers-crossed:
Here's a link to some of my earlier notes written about the Vpad7 - in case you missed them. Many of the links are down & sadly, no longer available.
http://forum.xda-developers.com/showthread.php?t=1264647

Related

[Q] Help with recovery on Optimus One P500?

Ok, So I've recently updated to stock gingerbread 2.3.3 with baseband .35. I rooted my phone with the SuperOneClick method. Root was successful (Finally).
I then wanted to install a custom ROM, so I installed ClockworkMod's ROM manager, flashed the clockwork recovery image and everything. I decided to make a backup image in case I didn't like the new ROM. I then selected the "Backup Current ROM" option, and left my phone to it's own devices. When I got back about 5 minutes later, I find that I have a hard reset on my hands :| To add to that, I don't even have a backup image!
I tried doing that a couple times more, once, I even held the POWER+VOL.DOWN+HOME combo and all. The same thing happened each time. The recovery backdrop and a sliding progress appeared, after about 4 seconds, the progress bar stopped moving, it shifted back to the LG boot logo. If I kept the combo pressed, it would go on and on for about 5 times, if I released it, it would just continue on to the boot and I would get another hard reset every time. I tried "Reboot into Recovery". Same thing. Once, I selected "Install ROM from SD card", with the backup option selected. Somehow or the other, due to the combo or something, I came to a screen that had four options.
1) Reboot
2) Install from SD card:update.zip
3) Wipe data
4) Wipe dalvik cache and cache
I was able to scroll up and down with the volume rocker, but the only other button that worked was the Home button, which toggled between the screen I mentioned above and a screen where all of the text was removed and there was just the recovery background. I finally popped out the battery and booted, and got yet ANOTHER hard reset.
HELP!
It seems Clockworkmod recovery was not flashed correctly. What you see is the stock android recovery. The recovery key mapping is:
volume rocker-up/down
menu (left most button)- select current option
back - go back
the behaviour you see when pressing the home button is normal.
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
mihir287 said:
After using Rom manager to install CWM recovery, it is not recommended to do further operations through rom manager, best uninstall it. Instead, boot into recovery using the three button combo and do operations from there.
I would suggest try again to re-flash CWM recovery.
Click to expand...
Click to collapse
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
snitch_95 said:
Thanks, but do you have any idea WHY using ROM manager is a bad idea? Just curious.
Click to expand...
Click to collapse
Well, one reason I've encountered is that while flashing cwm recovery, if the download fails for some reason, Rom mananger has flashed the incorrectly downloaded file without verification resulting in a fastboot semi-brick for many users.
Another reason is related to the way it operates the recovery. I'm not very sure about this point, but I've seen many people having problems with backups and flashing.
Thanks, you were brilliant. I flashed another recovery from ClockworkMod, this time with a WiFi connection, and everything worked great.
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
hardik.gcet said:
I was updating firmware of my LGP500 optimus one using kdz updater for 2.2 to 2.3.3...
battery level might be 40 to 50%.....
at the end i got an error and phone turn off.. now i tried to start it again but its not turning on....
any key combination is not working.. like home+down vol+ power_button or..
return+ up_vol+power_button,,,, what to do to get my phone turn on ??
even when i plugged in it to charger or USB cable .. it shows nothing on screen...
Click to expand...
Click to collapse
after the kdz method i think that u can do nothing, if u r under warranty then give your phone back and just say after trying to update through original lg software ur phone would not start at all. or try reading and asking in this thread
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
djdhruv said:
I am on 2.2.1 and I installed CWM recovery via ROM manager through wifi. Everything is perfect but whenever I go into recovery it just boots and resets my phone. Its my friends phone and I need help. I have tried other recoveries too but it is the same problem. Please help.
Click to expand...
Click to collapse
try to reflash recovery again and select reboot recovery from rom manager itself after flashing recovery
if still it doesnt work then flash recovery by below method
http://forum.xda-developers.com/showthread.php?t=1318750&highlight=recovery+through+lgdmp

[Q] Option 3 brick?

Hello all, I have what appears to be an option 3 brick, but after having searched through the Unbrick posts, I haven't been able to find a definitive answer to how to resolve this (or if it is even an option 3 brick). What happened:
1) Installed ROM Manager on the latest stock ROM (.28?)
2) Installed CWM 5.8.3.4 via ROM Manager
3) Downloaded CM10 via ROM Manager and attempted to flash
4) Realized that this required unlocking
5) Unlocked device
6) Rebooted into CWM
7) Flashed CM10
8) Reboot
9) Passes EeePad boot screen, but stays on CM10 splash screen forever
10) adb pushed a CM9 ROM on instead
11) tried flashing CM9, but same thing
From the posts in the Unbrick thread, a brick 3 isn't quite the same thing because it's a boot loop into CWM instead? I'm not sure. At any rate, it seems to have something to do with not unmounting /staging or something, but there has been no single post with a method to unbrick this. In the Unbrick thread, there are references to fixing this but those references seem to have been removed since it no longer works; a new method was hinted at in several threads, with no definitive procedure. I was also not allowed to post into the Unbrick thread as I haven't reached 10 posts yet.
Any ideas? Thanks.
li Arc
li Arc said:
Hello all, I have what appears to be an option 3 brick, but after having searched through the Unbrick posts, I haven't been able to find a definitive answer to how to resolve this (or if it is even an option 3 brick). What happened:
1) Installed ROM Manager on the latest stock ROM (.28?)
2) Installed CWM 5.8.3.4 via ROM Manager
3) Downloaded CM10 via ROM Manager and attempted to flash
4) Realized that this required unlocking
5) Unlocked device
6) Rebooted into CWM
7) Flashed CM10
8) Reboot
9) Passes EeePad boot screen, but stays on CM10 splash screen forever
10) adb pushed a CM9 ROM on instead
11) tried flashing CM9, but same thing
From the posts in the Unbrick thread, a brick 3 isn't quite the same thing because it's a boot loop into CWM instead? I'm not sure. At any rate, it seems to have something to do with not unmounting /staging or something, but there has been no single post with a method to unbrick this. In the Unbrick thread, there are references to fixing this but those references seem to have been removed since it no longer works; a new method was hinted at in several threads, with no definitive procedure. I was also not allowed to post into the Unbrick thread as I haven't reached 10 posts yet.
Any ideas? Thanks.
li Arc
Click to expand...
Click to collapse
If your getting to the boot animation it doesn't sound like any sort of brick.
It could be a few things. Try holding the volume down button while powering on. When the text appears up the top left just wait 5 seconds and you will have 3 icons on screen. press volume down to go to the wipe icon and then press volume up to select it.
If this doesn't work post back and we can try some other things.
flumpster said:
If your getting to the boot animation it doesn't sound like any sort of brick.
It could be a few things. Try holding the volume down button while powering on. When the text appears up the top left just wait 5 seconds and you will have 3 icons on screen. press volume down to go to the wipe icon and then press volume up to select it.
If this doesn't work post back and we can try some other things.
Click to expand...
Click to collapse
Yep, that did it! I didn't want to do a wipe via CWM since I thought it might destroy something else, so I was going to do the wipe upon bootup, but I guess a wipe is pretty standard whatever the ROM (I did use the wipe method you mentioned though, maybe that's not the same as the CWM wipe?). When I first tried to install via ROM Manager, I did check "Wipe data/cache", but obviously that fell through when the unit was still locked. Anyways, maybe I'll try to install something like TWRP for ease of mind later. Thanks!
li Arc

[Fixed] Long post, short question on CWM/TWRP

I'll put the question first for those not wanting to read the details.
I cannot get into CWM (internal) on my 16GB nook tablet. I can boot to CWM (external), but nothing works. When I try to activate ANY menu option, it takes me to a blank screen with the CWM hat logo in the background. Pressing power returns me to the main menu. Not even "reboot device" works. Can someone help? (I want to do a backup before i flash a JB Rom (internal), and to flash a JB Rom)
Now the long part:
I purchased and rooted my NT in December 2011 (about the 21st) using the snowball root (incase you are not familiar, as I don't see any post about it now, it was a modified zerg root borrowed from Albert's root method that with one menu option allowed rooting, recovery, and removal of certain nook apps and the addition of your choice of three launchers). I used it successfully on three nooks within a month or so, but this is the only one I did the complete nook removal option to.
Root works fine, but debug does not. When I run the NT hidden settings app to turn on debug mode, the developer options are listed twice (one compete set followed by another), this did not happen until after rooting, before they were only listed once. The bottom set was correctly checked to allow debug mode, and its how I rooted; however titanium backup says debug is not enabled every time I load it. (No complaints from RTB Pro) So I go into the developer settings and found two sets, the top one not checked... When I check it I get the pop-up warning, if I uncheck the bottom one, then debug does not work, if I check the bottom one I don't get the pop-up warning. With both checked, adb works, otherwise it does not. It had been this was since December 2011, and has not really prevented me from doing anything, although as the pop-up warns somethings may not work (converting apps to/from system, merging system app updates, restoring system app backups) and cause titanium to hang, but after a manual force close of titanium, most of the time the change was successfully completed.
Now, moving on one day I was being up my phone and thought "I can't remember the last time I did a nandroid of my nook" so I used RTB to reboot into recovery, the nook booted right back up into android, no errors, no different screen than a normal boot (with the nook --> hack logo, which incidentally takes about 12 minutes to boot every time, not sure if that is normal). So I tried an adb reboot recovery, but adb said no devices were attached. I went back into NT hidden settings and due enough debug was unchecked on the top, but still checked on the bottom (I've learned it lose it every reboot), do I rechecked it, got the pop-up, and went on my way. Adb reboot recovery also restarted my nook back into the OS, not into CWM.
I started to think that I may never have installed CWM, so I checked the root package I downloaded and viewed the script, first thing it does its copy the recovery image to the device, even before rooting, then installs it right after rebooting, post root hack. I thought maybe the posh was bad flash, so I searched XDA, downloaded a newer CWM, and manually adb pushed it to the phone and dd it per the instructions in the XDA thread. Reboot recovery, still nothing.
Please note I CAN get the factory reset screen to show up, but really don't want to try it without a backup, as I've been using my nook like this for 12 months and only have a titanium backup of the apps.
So I made a CWM SD from the NT thread here on XDA and booted to it :-/ intending on flashing 6.0.12 CWM to the internal emmc, the recovery on the SD was 5 something and none of the menu options worked, as mentioned above pressing power while any are selected gives a new screen with the background image, but no options. Pressing power again takes me to the main screen (same thing when selecting reboot device).
So I found a newer CWM SD package on XDA and swapped them out, this time a newer version 5.5.x, no change in how it works, so downloaded 6.0.12 and renamed the recovery image file and booted the SD. Small change this time (beyond the new version number and the option to power off, which also does nothing), when pressing the power button to select a menu option, the screen refreshes, but continues to display the same menu choices for all options in the menu.
I have also tried pushing each of these recovery images to the device and using adb to dd them to the recovery partition. Three nook will only boot the SD clockwork image.
Yes I made sure to select internal images for dd to the nook and external images for the SD.
So last night I installed nook tab recovery flasher, it said it successfully installed, before I clicked yes to allow it root access... the pressed the reboot recovery button, no good. So I downloaded and installed goo manager from the market and had it flash TWRP, same thing, reboot recovery ignores it.
Now to repeat my question, anyone have any clue how I can get recovery working spp I can make a nandroid and flash a JB Rom? (I know I can make a backup using adb, and Iam pulling one now, but I am wanting a recovery (that works) on my nook.)
Also, I am willing to try an adb push install of the Rom, I think I can make it work (although Ihave never tried it, on any device, I might be able to do it without further help), but I do not see how a new Rom will make any difference on my recovery situation and if I screw up, it would be comforting to know I had a working recovery at least.
Sent from my VS920 4G using Tapatalk 2
For selecting an option in recovery is N button not power one
Sent from my Xperia S using my fingers to swype.
Your question belongs in Q&A with all other questions and not in development. Only work being shared belongs there.
Thanks
AvRS
Caught that, and was able to flash CWM 6.1.15 (emmc) from the SD; but still cannot get to it.
Power+ nook= regular boot
Power+ vol up+N= regular boot
Power+ vol up= regular boot
Power+ vol down+N= regular boot
Rom toolbox pro reboot recovery = regular boot
Adb reboot recovery= regular boot
However, using goo manager to reboot recovery works, sort of...
I get the cyanoboot screen, hold N, use the menu to get to emmc internal recovery and I get CWM.
Now the problem starts about 3-7 minutes later (have not tried timing it, but it seems to be the exact same length of time each time), the nook reboots, don't matter what I am doing, using it, creating a nandroid, adb push or adb pull out apparently flashing cm10...
I decided to try a flash of cm 10 from a 11-28 build with multi touch firmware for 10 points. All was good, but I had to step away for about 2 minutes... I sneaked a peek and all was well, then when I got back my nook was on the "read forever" logo and has now been that way for 20 minutes. I checked the updater script in the Rom and it does NOT have a reboot command at the end.
I'll give it another 20 before ring to get back to CWM with out goo manager...
Sent from my VS920 4G using Tapatalk 2
Update
So, no change. Hiding the power button shut it off, I also tried plugging the usb cable in to activate boot, this causes a regular boot, which at this tinge never gets to "nook" but stays on "n" "read forever" which makes me laugh as it is currently the only thing I will "read forever" until I fix it.
Next up is to try to flash from an SD.
Update to my update
Booted from the SD, wiped everything three times, flashed the Rom, rebooted and ended up with TWRP, multi-touch and JB. Reinstalling apps through the market now, hoping previous issues are gone.

[Q] Stuck in recovery boot loop midflash upgrading to KitKat 4.4.2 on dtmo SGS3

My device details: SGS3 T999, rooted, running Jellybean 4.3 on a liquid smooth ROM. Its a year old and has been a solid performer up until now.
My device is stuck in a cycle where it gives a quick vibrate, then SGS3 splash screen with white letters, then black screen, then tiny blue "Recovery booting..." words in upper left of screen, then black screen with couple vibrations, and around and around it goes in the same repeating cycle.
Just before it started I had taken the following actions: Dumped the following 2 files onto my EXTSD card (cm-11-20131217-NIGHTLY-d2tmo.zip, gapps-kk-20131119.zip) from my PC, booted phone into recovery mode using TWRP, did a factory reset wipe (success), cache wipe (success), dalvik cache wipe (success), flashed the NIGHTLY file (failed), flashed the gapps file (failed). At this point I should have sought some support. Fool! I next did a reboot step still in recovery mode. Without the reboot happening a message came up stating Superuser permission had been broken (the best I can remember) and the option to have TWRP repair the permission. I opted "yes" to repair. Then the loop started that I can't escape.
I have pulled the battery multiple times, tried a regular boot up, tried a recovery boot up (up volume+power+home) dropping the home button after a few seconds. Nothing is working. Prior to the above steps I backed up everything on the device. So I have backups to use if it can be done. My best guess is that I failed to update my CyanogenMod or TWRP to the very latest versions and it caused this hang up. Otherwise, I don't know what to do and need any help I can get.
Has anyone had this issue or heard of anyone who has and have any helpful suggestions, tips, ideas, etc..?
Thank you in advance. This is my first XDA post. Please forgive and offer tips if this thread needs any scrubbing.
I've had a few similar events for a few different reasons.
I would suggest booting into recovery but it seems you have tried that already.
If the device is plugged into a wall or pc, unplugg it, that has seemed to cause and fix boot issues for me before.
Other than that, I dunno, if you can't get to recovery or fastboot, I dunno...

Please help with rooting Galaxy S5 (g900t)

I've followed these instructions to the tee but have not had any luck with getting this to work. The flash always just results in my phone getting stuck on the "recovery booting.... recover is not seandroid enforcing - Set Warranty Bit : Recovery" screen. Odin reads as "PASS!" but my phone seems like it's just stuck. I've scoured over dozens of forums searching for answers but what works for others just doesn't seem to be working for me.
The instructions all seems so clear, and multiple forums' instructions gave me confidence that this would work no problem as long as I followed the instructions precisely. I guess that wasn't the case. I can't afford a new phone right now, but I'm sure my phone isn't completely bricked. There's gotta be a way! Can you please help me, xda community?
EDIT: I forgot to mention that I also tried the "uncheck the Auto Reboot option" method, and I'm a little confused about the last sentence. See below:
NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
I'm confused about the "This will start the install process" sentence. I flash, let it finish until Odin says "Pass!", remove the battery, boot into recovery, and then I have two options from there - I can either go into download mode again, or I can start the phone normally. Starting the phone normally just brings me right to the recovery mode which gets stuck there indefinitely. I've left it there for 15+ minutes and it still just stays stuck there.
EDIT 2: Exactly how long is it suppose to take to boot up after it's been flashed?
EDIT 3: IT WORKS. So, If you just sort of hold down all the buttons at the same time, the phone will restart a few times and eventually bring you into the TWRP menu. This is what I was unaware of before. I'm not exactly sure what the specific method or timing is for that, but just tinker with holding all the buttons, and I think you can let go when you see little blue letters on the top left that says recovery or something. Of course, being able to access the TWRP menu means you must first have flashed the TWRP thing, which I did using Odin. Just download the latest TWRP .tar file and flash it with Odin.
EDIT4: SUCCESS! I am now successfully rooted! I reflashed the twrp-3.0.2-2-klte.img.tar and then I was able to access the actual GUI. I guess what I had before was some super stripped down version of the TWRP that only gave me access to a command-line looking interphase in recovery mode, with very limited options. So there you go, if you find yourself looking at pictures on forums of a supposed TWRP with an actual GUI you can navigate, that's because it does exist! Download the one I just mentioned, flash it using Odin, and boot it up by holding VolumeUP, Home, and Power. From there you can flash Zip files, just put the zip files into an sd card. I put my zip right into the sd card, not even in it's own folder or anything.
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
goog888 said:
that version (8/26/2016) does not work at all for g900t, Maybe Chainfire wants to shut down CF_auto_root method.
you need to try the previous version (02/28/2016), I doubt you can find the old version in their website, Try google it on internet.
Click to expand...
Click to collapse
Interesting, thanks for the info! Funny enough, while I was at Best Buy last night, I decided "what the heck" and asked a Geek Squad guy about my phone, and told him how I attempted to root and now it wouldn't boot, etc. He took my phone, and just sort of held all the buttons together and it restarted a few times, and he just kept fidgeting with it until eventually it came up to the TWRP recovery menu! So, I did a factory reset and started up the phone. It is currently on 5.1.1. I have since been able to get myself into the TWRP recovery menu by fidgeting like he did, even though I'm not entirely sure what exactly the timing or button combos are. The Geek Squad guy said he just held down ALL buttons, even VolumeUp and VolumeDown at the same time. So whatever, TWRP menu IS accessible finally.
At this point, I'd prefer to flash CM13 to it, and apparently I can just put the CM13 file on my phone storage/sd card, and then flash it through the TWRP recovery menu. But since I factory reset my phone back to 5.1.1, should I first update my radios? A techy friend of mine introduced me to a new fear - that if you flash a ROM that is incompatible with an older radio, it could "hard brick" my device. So now that's where I'm at. I want to flash a rom to gain simple root access, but don't want to risk bricking my device.
Here is my phone's information:
SM-G900T
Android 5.1.1
Baseband version G900TUVU1FOG6
Build Number LMY47X.G900TUVU1FOG6
I don't know how to mark this solved, but it is, as described my my 4th edit in the original post.

Categories

Resources