After flashing the latest version of CM 10.1 for the Atrix 4G, the bootloader comes up, and then the screen goes blank while trying to boot into the first instance of CM. Pull the battery, and it does the same thing. I am able to boot into recovery. Have tried reflashing from the same package, reintalling + factory reset, reinstalling + factory reset + no gapps, and same thing.
What's the problem? Moreover, how do I get stuff onto the internal SD card if I cannot boot into the OS?
I should also mention that the touch sensitive buttons light up and respond to touch via vibration after a point upon booting up, which tells me that it's booting to the OS, but the screen is remaining blank for some reason. Could be a kernel problem?
In any case, I'm going to have to push a new ROM onto the device and I have no idea how to do that in it's present state.
EDIT: Solved the above problem, ADB pushed an older version of CM 10.1 and I have the screen working again! Please close this topic.
Related
I ran Cyanogen7 for about two days after rooting, and then the Gtablet froze. When I rebooted, it hangs on the Viewsonic bird screen. I seem unable to turn off, but when I try and reboot with either the pwr + or pwr - button, I'm unable to get anything to happen other than go back to the viewsonic screen with birds. I tried connecting via usb, but can't see the internal SDCARD. Please help, the gtablet is currently only useful as a flashlight using the viewsonic screen. Thx.
nv flash it back to stock rom and try putting rom on again. and clean factory data before new rom boots up or else it will hang.
I'm a novice just knowing enough to be dangerous. How do I NV flash it back to stock ROM when I can't get it to boot and I can access the internal SD with USB?
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
I need help. I came across a Galaxy Tab 2 10.1" WIFI only GT-P7510 recently and was trying to flash AOKP 4.2.2 to it after rooting it with Odin. I was originally on 4.0.1. Now I can't get it past the boot screen, the colorful X. I can still access CWM(I'm using 5.8.3 I believe). I've tried multiple times to reflash the recommended US Bootloader and always wipe the data/cache/dalvik cache. To no avail. I stupidly didn't create a backup of the original OS image; therefore, I can't put another OS on it. There's no external SD slot on the tablet and can't get the tab to boot to use the usb cable to do it. I also have the option to get to download mode, but when it asks me if I'm sure whether or not I'm sure I want to go into download mode, I click the volume up button, it doesn't work. It just shuts back off. I can still get into the recovery, but that doesn't help if i can't put any zip files on it to reflash to stock or another rom. the tablet just stays on the boot screen until it dies. I've tried a lot of google searches but nothing directly helps me. I really hope someone here can help.
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...
My Nook HD+ bootloader won’t launch the installed OS, CM 13. The Nook screen appears, and then gives way to the Cyanogenmod Universal Bootloader. After a bit the blue android image appears. It pulses normally at first, then the pulsing pauses, and finally the process starts all over … and over, and over, and over!
At first I thought there was a problem with the OS, so I booted into recovery (TWRP 3.1.1-0) and tried to flash CM 13 for ovation. That didn’t work, so I tried flashing other ovation ROMs. None will install. They all report an ERROR 7. I’ve attempted to work around that error, but none of the methods I’ve found made any difference.
It seems that I may have to reinstall the factory/stock ROM, and I’m okay with that. But it seems I can’t do that either. The stock rom download is in a CWM backup format, and I have TWRP, not CWM. So I tried to flash CWM with TWRP, but in order to make that work one has to reboot into recovery via TWRP, The problem here is that the TWRP boot menu has just two options … System and Power Off. The Recovery option that is supposed to be there isn’t!
So I tried to replace TWRP with CWM via ADB. I can sideload a CWM zip without a problem. I then issue an ADB Reboot Recovery command. But, instead of rebooting into recovery, the bootloader launches instead. As a result, when I go into recovery it’s still TWRP. I’ve also tried powering on with the CWM bootable image file on an sd card, but no matter how many times I power off and back on, my tablet never recognizes that the file is there and my problem persists.
Is there a way to boot into CWM or swap CWM for TWRP in a situation like this? I’ve seen postings that suggest fastboot may the be solution, but that requires that debugging be enabled, and it was not enabled when my problems began. Apparently there is no way to enable debugging without launching the OS.
Help!
Update:
My Nook HD+ has not rewarded my attempts to bring it back to life Perhaps I’ve made things worse. I certainly haven’t made things better. Here’s the latest.
When booted up, little or nothing has changed. At bootup the Nook screen is followed by the Cyanoboot Universal Bootloader screen. Sometimes it gets no further, and reboots. More often the android image appears with a halo pulsing in the background. Sometimes the halo pulses a couple of times before the device reboots. Sometimes is pulses a bit longer before rebooting. Sometimes it never stops pulsing (until I press and hold the power button to shut the bloody thing down, that is).
Thinking the problem was related to the OS (I had been running android 7.1.1 (an unofficial HD+ release, but from a very reliable source), I've tried in vain to flash another OS. I've tried multiple android releases, from 7.1.1 down to 4.4.4. I've also tried flashing several versions of the HD+ factory stock OS. I’ve done all this using TWRP, and also by booting CWM from an sd card. No matter which recovery I've used or which OS I've attempted to install, the process always ended with an ERROR: 7.
So, I got my hands on a good Nook HD+ running android 5.1.1. I made unbundled TWRP backups of the System, Boot, and Apps partitions using release 3.1.1-0. The System and Boot partitions each restored without a problem. The Apps would not restore, ending with “extractTarFork() process ended in ERROR: 255." That error probably isn’t related to my problem, which is that I can’t get the system to boot up. More telling is the fact that after successfully restoring the System and Boot partitions using the backup from a good HD+, when I power up the device appears to be launching 7.1.1, not 5.1.1. The android image displays in portrait mode on the good HD+ running 5.1.1, but displays in landscape mode on my HD+ ... and the boot loop continues, of course.
At this point, at the $7.25/hour minimum wage rate I’ve spent enough time that I could have earned many times the original cost of the HD+. So, am I giving up? HELL NO! Now it’s personal!!
My HD+ boots into TWRP flawlessly, so I still have that going for me. My HD+ is not rooted and did not have USB Debugging enabled when it crashed, so any solution requiring SU or flashboot is a non-starter. Otherwise, I’m willing to give anything a try. Maybe I should be looking for an exorcist?
Thanks for reading this, and for your suggestions, words of encouragement, and expressions of sympathy.