This may be an issue that was previously resolved but I did not find a mention of it in my searches.
My children (3) all have the dreamtab, which I guess is the 2s. All three have experienced this problem at least once. When first booting after being off, the dreamtab hangs at the Android screen. Over the course of the last year, I've tried charging, wiping the cache partition and eventually just did the factory reset. While this method works, and I can get their device back to them quick, it is a factory reset and they loose all their saved games and completed activities.
Is this a known issue, or just something my kids happen to do? Is there anyway to prevent or correct this issue? Or at least back up their game data?
drirun said:
This may be an issue that was previously resolved but I did not find a mention of it in my searches.
My children (3) all have the dreamtab, which I guess is the 2s. All three have experienced this problem at least once. When first booting after being off, the dreamtab hangs at the Android screen. Over the course of the last year, I've tried charging, wiping the cache partition and eventually just did the factory reset. While this method works, and I can get their device back to them quick, it is a factory reset and they loose all their saved games and completed activities.
Is this a known issue, or just something my kids happen to do? Is there anyway to prevent or correct this issue? Or at least back up their game data?
Click to expand...
Click to collapse
The Dreamtabs come in 2 versions. Intel and Nvidia(IN08A and NB08B). The Nvidia Dreamtab does have the issue and it effects many not just you. The standard solution is a factory reset. I believe the issue is the missing fsck binary. If you don't know that is it's a UNIX disk check program. The Dreamtab calls for this at boot time if the file system wasn't shutdown cleanly or if I recall correctly every 20 times a partition is mounted. It checks the filesystem for errors and then continues the boot. When it doesn't find the fsck binary it hangs at that point. At least that is my theory and I provided a flashable zip that installs fsck and I haven't had the problem since. The problem is it can't help once it's happened unless you have previously unlocked the boot loader. If someone has unlocked the boot loader they could or do have TWRP on the device and can load fsck. If they haven't unlocked it then the unlocking the boot loader wipes the device(factory reset) and all personal data is lost. This could of course be done with root access as well but since the tablet doesn't boot it can't help at that point.
Edit: here is the patch and some more discussion http://forum.xda-developers.com/showpost.php?p=65713581&postcount=54
Related
This is where I am currently at with my tablet. It is an unrooted 1.4.2. I am having a problem with getting the device turned on somewhat. Using the power button does not garner instant power. Instead I have to wait approx. 10 mins. and wallah its on. Prior to this mishap. I was stuck in a boot loop where I could not get the tablet past the Nook "N" logo. Because of this I somehow was able to factory reset the tablet from the Alpha Build of ICS9. Accessing CWM has proved useless as I can not turn on the device at the precise moment of initially pressing the power button and nook logo button. I also am having trouble using any adb method as to do so would involve block OTAS and getting the firmware to 1.4.0. The only option that I have come to is taking the tablet in store for a replacement. I am just concerned due to the fact that I am unsure if the factory reset was able to wipe everything from the memory of the tablet (i.e. me rooting the device). I would just hate to have to shell out money if it is something that I am overlooking?
xsHauser said:
I am just concerned due to the fact that I am unsure if the factory reset was able to wipe everything from the memory of the tablet (i.e. me rooting the device). I would just hate to have to shell out money if it is something that I am overlooking?
Click to expand...
Click to collapse
all i can say is "wow" ! . . . did you try the Adam Outler thing ?
http://forum.xda-developers.com/showthread.php?t=1470910
big file so it will take time to see what happens after I do this. If nothing else, I will at least be able to return the device and exchange without fear of having to play for the replacement for breaching the warranty. Will post my results when done.
Thanks to oldfart and adam. What I think happened was during the boot loop and master reset, something happened to the internal file system. Everything works great and is in order. This should come in handy should this happen again though.
Here we go again.
No sooner did we do a factory reset on my son's phone, but it stopped on us again.
To refresh your memory, my son's phone is a dead stock T Mobile HTC One, never unlocked, never rooted, dead stock.
A week or so ago, it went into a boot loop from which we could not recover. We did a factory reset and everything was fine, for a moment. My son went about reassembling his contacts, music, etc., making sure they were properly backed up this time.
After the factory reset, everything seemed to work fine, for a time. But then the first time my son powered off his phone, charged it overnight while off, and tried to power on again, the PIN unlock screen won't come up, so he can't open his phone.
We can get to the bootloader and to the recovery. Tried wiping the cache from recovery mode, but that didn't help.
Is it time for another factory reset? Is there anything that would have potentially caused both problems loading Android/Sense (the boot loop from before and the failure of the unlock keypad this time) that we should investigate?
I love my own HTC One, but my son's opinion of his is quite different, and it's straining family relationships.
Any thoughts? Thanks in advance.
GenerousDad said:
After the factory reset, everything seemed to work fine, for a time. But then the first time my son powered off his phone, charged it overnight while off, and tried to power on again, the PIN unlock screen won't come up, so he can't open his phone.
Click to expand...
Click to collapse
Only info I can find on this suggests another Factory reset.
Do you have any idea what apps he may have installed? I have seen that there is some "beta" keyboard software out there that upon expiration will fail to appear, making it all but impossible to unlock. Of note regarding that is Swiftkey beta software. Their forums have quite a few posts regarding this issue.
Sorry I couldn't be more help. I know of no other way around the pin other than a factory reset.
If you can get the device into fastboot mode plugged into a Windows 7 PC perform the following:
fastboot erase cache
use the volume keys to select bootloader and power to active.
use the volume keys to select factory reset and power to activate.
I will talk to him about apps, but I believe he was using the stock HTC Sense keyboard.
If it's an offending app, will removing the app via his Google account using his laptop and then restarting the phone solve the problem?
Any thoughts as to why this might happen so fast on the heels of the boot loop problem described in my other thread?
Does the Fastboot Erase Cache command do anything different from the Wipe Cache Partition option on the stock Recovery menu? I've tried that already without success.
Thanks for your response.
PhoenixPath said:
Only info I can find on this suggests another Factory reset.
Do you have any idea what apps he may have installed? I have seen that there is some "beta" keyboard software out there that upon expiration will fail to appear, making it all but impossible to unlock. Of note regarding that is Swiftkey beta software. Their forums have quite a few posts regarding this issue.
Sorry I couldn't be more help. I know of no other way around the pin other than a factory reset.
If you can get the device into fastboot mode plugged into a Windows 7 PC perform the following:
fastboot erase cache
use the volume keys to select bootloader and power to active.
use the volume keys to select factory reset and power to activate.
Click to expand...
Click to collapse
I
GenerousDad said:
f it's an offending app, will removing the app via his Google account using his laptop and then restarting the phone solve the problem?
Click to expand...
Click to collapse
Worth a shot, I suppose. Do not know for sure.
GenerousDad said:
Any thoughts as to why this might happen so fast on the heels of the boot loop problem described in my other thread?
Click to expand...
Click to collapse
Coincidence most likely. Really really really bad luck.
GenerousDad said:
Does the Fastboot Erase Cache command do anything different from the Wipe Cache Partition option on the stock Recovery menu? I've tried that already without success.
Thanks for your response.
Click to expand...
Click to collapse
Same. Erases the /cache partition. I use fastboot personally because, well...ok, I really have no idea why I prefer it. Just one of those things, ya know?
Good luck! :good:
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
andPS2 said:
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
Click to expand...
Click to collapse
No need to double post. Regular HDX contributors will have seen your issue in the development thread. Well...at least those with some knowledge of your hardware. Unfortunately, there's not a lot of commonality with other android devices. Tough to get help elsewhere. Sorry this happened to you.
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
andPS2 said:
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
Click to expand...
Click to collapse
TWRP operates (loads) from the recovery portion. The symptoms suggest damage to another partition. The reboot likely occurs when a write operation fails or attempts to put data in a protected area. With a second (working/unlocked) device you might be able to compare storage layouts, determine differences and take corrective action...assuming it is not a HW issue. I realize that's unlikely to happen. Not even sure what to look for and the commands needed to reveal low level storage/partition details.
There is no low-level formatting available for HDX.
Since you have an error with /data there is a good reason to check this partition.
Load into TWRP recovery, attach the tablet to a PC with ADB and driver installed, unmount the data using the interface, launch the adb shell,
then try e2fsck -fpv /dev/block/platform/msm_sdcc.1/by-name/userdata
However I'm not sure that any issues with /data can cause the reboots.
Check the system partition too.
On my device Wi-Fi can't be turned on, this can be NAND issues.
thanks for the help
i can try on monday since my half brick fire hdx is at work
merry x-mas !
p.s.
checking the filesystem for userdata and system indeed showed no errors
still have the reboot problem
guess it is a nand problem then...
So i'm helping a buddy out that was having an issue with several Note 2's that were purchased from a company that restricted their employees access to a lot of things on the phone. My friend handed a couple off to me. The first one was not passcode locked and it was a breeze (Basically just enabled USB Debugging). It is up and running. The other ones are passcode locked and when you try to go into wipe the data/factory reset from recovery it says "MDM does not allow factory reset". The Note 2 I'm having issues with in particular has a locked bootloader on KitKat 4.4.2 through Verizon.
I've spent almost literally every waking moment trying to find a way around this issue. I may have compounded it though. I discovered ODIN, flashed the stock firmware in the hopes that it would clear the phone. It did not (password was still in place). I then decided to flash the stock firmware with the .Pit file for an SCH-I605 and made sure re-partition was checked as well as erase nand. After the process completed successfully and the phone rebooted it will no longer boot beyond the Verizon screen. I still have access to recovery and download mode but in recovery its throwing out a bunch of command lines such as E:failed to mount /data etc. I've tried to reflash the stock firmware with and without the .pit file to no avail.
In the mean time I've tried to unlock the bootloader, attempted auto root, and install custom recoveries to see if I could some how get around the MDM issue. I've also attempted to install or flash from ADB and its still the same deal.
Anyway I'm tired, kind of exhausted, and not really sure what avenues I have left. That's where I'm hoping some of you guys come in. If you have any questions for me let me know and I'll try to shed some more light on it for you. Data DOES NOT matter to me so if you can think of anyway I can get this thing completely wiped out it so I can start from scratch it would be greatly appreciated, Thanks.
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Droid_Nut said:
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Click to expand...
Click to collapse
Well tonight I'll be getting my hands on a couple other test SCH-i605 phones that are in the same situation (Password locked and no ability to wipe from recovery) and I'll put them through the paces to see if I wind up with the same issue and get back with you on it.
The basic issue with this phone is just after trying that repartition with the pit file it doesn't want to boot beyond the verizon logo anymore and thats when it started throwing those errors in recovery. It could be a coincidence I guess.
I've been messing with Heimdall today to see if I could get a custom recovery flashed that way but the phone fails protocol initialization. The only thing I can get to flash to this phone is 4.4.2 and the i605 pit file through ODIN. Nothing else will budge.
I guess the question I really need answered, is there another way to wipe data/factory reset without the option in the stock Samsung recovery and no access beyond the lock screen?
What I have to work with is ODIN mode and whatever is in recovery that is not wipe data/factory reset.
So I did get my hands on a couple other phones with passcode locks that have the MDM lockout within the stock recovery that still fails to flash anything in Odin except the stock 4.4.2 firmware. So I can eliminate the idea its hardware. I have 4 phones here 3 of which have the same issue and the 4th I was lucky enough to not have a passcode. Quick fix to get MDM removed that way.
Again any ideas that are slightly more outside the box would be appreciated. Thanks.
Edit: If this helps the phone that is working that I manage to clean all of that stuff off of also throws the same error in ODIN with or without USB debugging so it leads me to believe there is something I'm actually missing... Time to go read more.
Well, sound like it is more than coincidence. Maybe you should contact Samsung and see if they can help?
Yeah I might do that. I'd just hope they have a one size fits all solution because I have about 600 to 1000 phones to tackle... Hahaha.
The conundrum here is that for the MDM company to release the lock on the phone I have to be able to get beyond the lock screen for the phone to process the request. To get beyond the lock screen I need the psswords that the previous company allowed their employees to put on the phones that for some odd reason they didn't have remove.
Anyway if I get this figured out i'll let you guys know how I got it. Thanks for the suggestion.
((deleted))
I stumbled upon a peculiar message I've never faced before, right after my Note 9S has rebooted to OrangeFox recovery out of the blue. According to it, a particular thing had caused my phone to enter rescue mode (for additional information, look at the attached screenshots). I have absolutely no clue what could've been the culprit behind this disaster. All I did was trying to install an APK file that I'm convinced was not corrupted. Funny thing, the installation didn't even commence. I presume a few newer Telegram builds have a problem launching Package Installer the proper way (at least, that is on the current ROM I use). As far as I know, an app kept crashing in the foreground before the installation could've gone ahead.
Viable solutions around the problem are the following, with the risks escalating
1. Unmount SD card and transfer the Magisk uninstaller ZIP. After having unrooted the device, clean flash the ROM without any snags.
2. Embark on flashing with root access present. If something fools around reboot to recovery and start over.
3. Nothing special, attempt booting to system and see if the error message was a false alert (it could've been, considering Package Installer isn't an inherent part of the system).
Which one of these do you endorse? Maybe an alternative course of action?
PS: The filesystem doesn't seem to be corrupted. I haven't flashed anything so far, only created a backup of my files placed within Internal Storage. I haven't messed around with the PMIC but the battery percentage remains stagnant in OrangeFox when the screen turns off after having attained the timeout deadline; unsure if that's normal behaviour. I've installed Adreno Team Exclusive Thermals, anticipating to cut back on overheating (up to 39 °C) while charging.
It's crucial for me to act in a meticulous way, given that the phone might not boot up next time. I'm not at all conscious how bleak the situation is, though.
Randomly rebooted to recovery but still loading. I really hope it's not stuck there.
I'll see if fastboot commands work as soon as I get to use my computer wich has my phone authorised
Since no one has taken the trouble to guide me through the necessary steps, I attempted to do it on my own. Fortunately, my laptop recognized the device, allowing me to tackle with the boot loop. Before doing so, I sought to boot into system (it was the first time I've done this after being stuck in OrangeFox) and everything worked just fine. It was only a false alert.