Database Info

Tablet stuck in "Installing System Update to Error!" loop

My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.

Meth_Badger said:
My tablet froze on me and I powered it down to restart it and then it went into what folks on here call a bootloop. After holding down Power and volume down, it brought me to a screen that had three icons and I chose the one on the right by mistake and now it's looping again, but instead of the Asus screen with the refreshing icon, it's the android falling with an Error on his chest after quickly flashing Installing System Update.
The power volume combo works no more and the only way I can shut off my tablet completely is to use the power and volume up button. I can't get back to screen with the three icons no matter how many times I try.
I've already resolved myself to purchasing a new device, so my main concern is recovering the data, slim as that might be. Any recommendations?
Also, note that Ive never rooted or installed anything on my tablet. No roms or kernels or any other modifications. If I can get my data by any means necessary, I'd be satisfied, even If I Ihad to open it and retrieve the harddrive.
Hopefully Ive explained myself sufficently for you guys to help me. Cheers.
Click to expand...
Click to collapse
If I read your post correctly, you selected the right icon which is a Wipe data from your bootloader. When you executed that Wipe data, it will wipe everything on your internal SD including your /media folder or your personal files and data... The chance is very slim unless someone knows how to recover data from a wipe. Technically, your data is still there but it is only a dumb files which contain only 0's and 1's. Some recovery tools may be able to retrieve your data but I don't have that knowledge.. I hope that someone will be able to help you out and good luck...:fingers-crossed:

I'm afraid LMK is right: Your data is gone.
Do I suspect correctly that you interrupted the Wipe Data process after selecting it "accidentally"?
Choosign Wipe Data from the bootloader causes the BL to write a command to the misc partition to start the recovery and wipe the data partition. If you interrupted the process, there's no telling what and where that got corrupted - unless you just let it loop and pray that it finishes the wipe process which would erase the BL command. Connect it to power and let it loop for a few hours. What have you got to loose?
But your data is gone either way - sorry.

Morning, cheeky question(s)
Where are you located, and would you be interested in selling your bricked TF700? I have a broken screen among other things and would be interested in buying your tablet for spares if you are getting a new one?
PM me if you are interested.
Thank you
Freddie

I'm not all too sure what the Icon on the left wad, but I'm sure it said RKU or some sort. I would have given up all hope if I had hit the wipe data on the right.
Days recovery aside, is there anyway I can get my looped tablet to work? I plugged it into a comp and it didn't recognise it.

[Q] Phone Keeps Rebooting After It Dropped

My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.

Getting the power button fixed isn't too expensive. Hopefully that's all you need. ?

whyareallusernamestaken said:
My girlfriend dropped her phone yesterday and despite that it's encased in a bulky Ballistics case it appears that the power button is broken now. When I plug the phone into my laptop using her USB cable the phone automatically boots up the Google screen with the lock icon, vibrates and then shuts off and reboots again resulting in a boot loop. Unfortunately she's out of warranty. She opened the phone and the iron nub of the power button appears to be unmovable. She also tried going into recovery, but the phone continues to reboot.
Is there any way we can fix this? I read that some people can get theirs repaired at a repair shop, but I'm not sure how viable that is in Canada. Please advise.
Click to expand...
Click to collapse
I have had this issue for the past 4 days. After many attempts of trying to bang the phone a lil onto my hand (for where the power button is located at), sometimes the phone will boot fine, for as long as you do not click the power button again it won't act up.
(I am pretty sure I didn't drop my phone when I was napping in the car, it just started out of nowhere after I have been using lollipop 5.0 with franco kernel for like 2 months without any problem).
Same sypmtoms, bootloop (looked like the power button defective / boot IC on mobo defective), can't even stay on recovery/bootloader screen/system for longer than 5 sec.
Try these :
- spam click power button, until it is able to boot into system, you will have to keep clicking, for every click you either screen on/off you will realize Power Off options may pop up, it looks like the power button has been holded for few sec to trigger the power off, but all you do was spamming the click to keep the button active, you have to click until you feel that certain point the power off doesn't pop up, then stop clicking ( remember never to touch that power button again for NOW), if after a few sec of using the phone and it doesn't force shut down (result from power button defective where it sense its being clicked and hold for like 8-15 sec). Then you are good to carry on whatever I am to tell here.
- go to about phone, click the build number for 5-10 times until you get the unlocked developer mode
- back, click on developer options, enable usb debugging mode (this will pop another message asking you if you want the device to memorise your pc's mac address) that way it is synced with your pc.
- before you proceed with any other thing, go to playstore, download power button to volume button, enable volume power, check start volume power on bootup, check screen off. This will help you greatly for not touching the power button to unlock the screen when you are working on your pc.
- if you have all the correct nexus usb driver installed onto your pc, you need to get Minimal ADB and Fastboot installed onto pc. After installing, run Minimal adb and fastboot, a command prompt windows will pop out and is automatically redirected to the minimal adb folder. key in this command
"adb devices" to see if it detects your device or not. There should be at least a device listed if you have the usb driver installed correctly
- now you can make use of adb commands to reboot into bootloader/recovery to do any flashing of system, backup all your data that you needed to PC. Download official 5.0.1 nexus 5 image and extract it into the Minimal ADB folder.
- is your bootloader unlocked? if not do adb reboot-bootloader
- fastboot oem unlock (this will wipe all your data on the phone)
- fastboot reboot after the wipe is done
After that you can actually carry on with flashing back to stock images. Look at this link http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for flashing to stock factory image.
I am not sure which step has actually solved my problem, because on my first flashing of factory image, booting into system as a brand new device (no extra softwares, yet to recover any of my data). the problem persists as long as I clicked on power button once, it'll act up again random power off and bootloop.
I actually was on a follow-up cases with google play support team from Aus as my device was bought from Aus. After the last step of factory image setting, doesn't help, I intended to ship it back for RMA as my device is still under warranty and I suspected it was the hardware issues from power button too. They will send me another refurbished device. After ending the call, they sent me link to proceed with warranty claims where I need to fill in several forms and ship the device back to them.
I decided to give it one more try, due to my phone was previously unlocked, rooted, changed to franco kernel.
By restoring to stock images made my device unroot, I was afraid of google will accuse me for unlocking bootloader voided the warranty and not willing to replace another unit for me. I locked back the bootloader, then I remembered in bootloader, fastboot oem device-info shows that a record of a phone if it has been unlocked, it will show Tampered status as True, google probably can use that to track if a device has been unlocked before. So I unlocked my bootloader again (which causing another wipe for whatever data is in the device).
So I looked up on google again and found source for changing that tampered status to False in addition to locking the bootloader again, but to change that tampered status, I need to use TWRP to run the scripted zip file, so I used fastboot boot path (it is stated in the link I gave you above) to boot into TWRP images temporarily from my desktop and ran the zip file, I always practice wiping data, cache and everything before I boot the device back into a brand new factory image.
So I went to wipe dalvik cache. Rebooted the system - it was running the Optimizing x numbers of Applications.
Upon finished with that. I was surprised that, after a few clicks of power button, the random power off issues is no longer there. I even test clicking on the power button for entire day. The symptom isn't coming back. So I emailed google play support team to cancel my warranty ticket and close the case for now.
Should there be any problem again I will probably then claim the warranty for replacement.
Its been more than 24 hours now that I am using the device without any problem of random power off and on or stuck in bootloop due to power button defective.
I suspect it is either the 5.01/5.0 lollipop with ART that is causing something wrong with the boot IC / power button defective in a long run.
Or maybe it was some settings I have changed in franco kernel ? but it was running fine for 2 months which made me doubt that it is franco kernel
Or it could be some of the apps I used to tweak my phone settings - LLama and tactile player (which I have set something condition and actions for power button) but I doubt it is caused by these either.
I will observe and see if the problem comes back after some time of using the 5.0.1 stock image now.
Oh I am also back to using franco kernel, unlocked bootloader and rooted again. Haha...
Hopefully you are able to solve the problem by trying some factory reset method + wiping cache, partition and dalvik.
If not, you probably may have the hardware issues, I have seen some other forum/websites with n5 users upon replacing the mobo, no longer encounter such problem.
Regards,
Kean

Thanks for the replies. My girlfriend was able to get the power button repaired for $80 and replaced the external button for $7 + tax, she paid $98. At least it's cheaper than a new phone.

Broken GPU? Also How to RMA?

Hi guys, today my OnePlus broke, i think.
20 Minutes ago i was still using it normal.
Then, i turn the screen on and see this:
http://imgur.com/GP2563K
as you can see in the below video, the phone is completely operational, i can use whatsapp web from my pc and the colors of the stripes change according to what should be on the screen:
http://youtu.be/QlO-ttkmVms
i suspect that the gpu has a defect or maybe the connection to screen got loose, even though i did not drop the phone before this started.
the same thing is seen while booting and in the recovery, so it is not a problem with the os itself. what i need to know now, is:
-pictures of cwm so i can go to the backup menu and put a system backup on my pc and then wipe,
-how do i start an rma on the oneplus site? also i have rooted and unlocked the phone, how is one plus going to determine if that caused the error or not? (i know that is not the cause, but i want to be certain that i wont get denied my warranty)
-also if oneplus will send me a new phone, can i ask them to send one with the old backcover? i dont like the covers without the cyngn logo.

UPDATE: via https://code.google.com/p/androidscreencast/ i managed to start chromecast screenshare and now i can see the screen on tv. the image on tv and pc looks normal so maybe the screen is broken?

Hope you can get it fixed
Sent from my A0001 using XDA Free mobile app

~MaX~ said:
UPDATE: via https://code.google.com/p/androidscreencast/ i managed to start chromecast screenshare and now i can see the screen on tv. the image on tv and pc looks normal so maybe the screen is broken?
Click to expand...
Click to collapse
Try to going to fastboot (i know you see nothing but try it) and flash clean cm11s and then reboot the phone .....
Hope its not on HW ...

Strange...I heard about people who had problems with a green line which appeared random at the right / left side of the screen when they simply turned it on and that problem was something related to pixels and they solved it by playing a video (like this one https://www.youtube.com/watch?v=VN-KIlsxxOw ) for many hours. Try it and if this doesn't work then the only solution remaining before sending it to repair is a complete fastboot reflash of stock cm11s.
flash philz touch recovery which can be used with hardware buttons and to perform a backup do this:
1) press 3 times the back volume button (the button used to lower the volume when listening to music for example)
2) press home button (the soft-touch home button)
3) press again home button.
The recovery will start performig a backup...the phone will vibrate for 1-2 seconds when it will be done and it should last max 2 min (don't worry you will notice it). Anyway, since the philz touch recovery is cwm-based it could be that the buttons to press are the same for the original cwm recovery but it's a bit risky...
Now turn off the phone (keep the power button pressed for 10 seconds) then boot it again and plug it to to pc and you can find your backup files on the clockwormod folder.
Now you can perform the complete fastboot reflash. Good luck.

SM-G930F Maintenance Boot?

Hi all,
Just wondering if you Android pro's can tell me whether the G930F (Australian) can boot into maintenance mode?
My girlfriend bought one new on the way to the airport for her dream holiday in the USA mainly for the camera, then promptly forgot the swipe pass for the secure startup when she arrived home. USB debug is off, so I'm looking to get it back on. Got no problems with the FRP, she knows all the details for that, but it's just that the phone won't power on and connect to the network so we can do an account recovery. Or, at least get to a point where we can pull the photos off and then just do a hard reset.
If it's a no go on maintenance boot, would flashing the stock ROM back on get us past the swipe and at least to a point where we can actually recover the account from Google?
Just to be clear - the phone boots past the Samsung logo and then stays in "To start up your device, draw your pattern." and the option to go to an emergency call. We cant call the phone at this point, it just goes straight to voicemail.
Thanks heaps!

The 930F is the international model, Australia has no specific firmware or hardware differences so shouldn't have any reason not to be able to.
It sounds like you have the set to have the pattern required to start the device as opposed to just unlock it, and I'm not sure how early it kicks in preventing boot modes.
If I recall correct boot to recovery is vol up + home + power, boot to maintenance is vol up + power, and boot to download is vol down + home + power
Couldn't tell you if recovery or maintenance will let you pull data.
A factory reset within recovery might get past the pattern lock, but will wipe your photos.
A stock firmware flash in Odin should do it if recovery doesn't work, but also will wipe your photos.

Ah, I see. I appear to be able to get into Recovery and Download boots, but not maintenance. I'd seen that once you get into maintenance, you can turn on USB debugging from there, and I'd be all sorted. Hmmm.
That's a pity about the stock ROM flash, I thought that might be my best bet after maintenance boot.

Maintenance might be a snapdragon thing, googling it I can only see people doing it on the US model.

Oh right. Could I do anything like in this article -
Google "Physical Imaging Of A Samsung Galaxy S7 Smartphone Running Android 7.0" (sorry, I can't post outside links yet!)
- down to step 4? Is there an appropriate boot image available for the G930F?
Thanks heaps for the help so far!

Should be, every ROM zip I've seen has one in them. Not sure where you could get a stand alone stock one.

Ok, cool. Would the one found in this thread -
"ENGBOOT for S7 and S7 Edge (Qualcomm/Exynos) (Untested) (Still Seems Legit)"
- on these forums be ok? There's a file in the download labelled G930F_XXE1APBG_ENGROOT.tar (after extracting the .7z) that appears to be standalone. Is that what I'm after?
For reference, in Recovery boot, it tells me that the current PDA is G930FXXS1DQF6, and from that I can find that the CSC is G930FXSA1DQEF.

So she can't remember the pattern to unlock it? Or does it not boot properly despite entering the correct pattern? The S7 comes encrypted by default and the pattern is the key. No data is actually usable at the point it displays the pattern screen with the black background(because it can't actually access the wallpaper yet). If you can't get the pattern right all data currently on the device apart from the external SD(unless it's encrypted too) is lost It's a security feature, the only other way is a factory reset.

Yeah, black background is where we're at, and yeah, can't remember the pattern. So there's no way to get past that at all? Not even flashing the boot image?
Hmmm. Is there any way to reset the amount of attempts? We can at least keep trying different patterns that way.

JamesMudd said:
Yeah, black background is where we're at, and yeah, can't remember the pattern. So there's no way to get past that at all? Not even flashing the boot image?
Hmmm. Is there any way to reset the amount of attempts? We can at least keep trying different patterns that way.
Click to expand...
Click to collapse
NOTE: This is based on what I know. If anybody else has any ideas please don't hesitate to share!
Does it let you enter a backup password? She might have some ideas there?
Your best bet would maybe be a firmware reflash, but that's a very slim chance. So try that first(Remember to use HOME_CSC!). You can try flashing the boot image but beware, if the phone is full stock then the encryption system has some self-defence mechanisms that can permanently lock the data if unauthorized firmware is detected(or anything else suspicious like resetting the attempts). It technically *shouldn't* disable secure startup though; Remember, the whole point of encryption is to make it physically impossible to access data without the key, so it wouldn't be doing its job if you could just disable it at will. Samsung is also pretty anal about security these days.
Edit: Does she have a Samsung account? It might have backed the photos up already.

Factory Wipe Pixel 2 with totally unusable screen

My brother recently moved out and he left me with his old phone, a Pixel 2. I would like to factory wipe it in order to sell it, but the screen is completely broken. It still boots up and works fine, but the screen shows no output and tapping doesn't register. Is there a way to wipe the phone via fastboot? The bootloader is locked, phone is unrooted, etc.

I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps

ice711 said:
I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps
Click to expand...
Click to collapse
The only issue with that is that I have no clue if it actually worked. I can check if the device is in fastboot to get the ball rolling, but after that there is no haptic feedback or anything to let me know it is wiped. Thanks for your input though. I tried doing it but I'm not sure if it actually did anything

ice711 said:
I would suggest going into recovery and doing a factory reset. You only need the volume and power keys. You said there's no output on the screen, so you would have to watch a YouTube video and count the number of times to press the corresponding keys. Hope that helps
Click to expand...
Click to collapse
I'm pretty sure I was able to wipe it using this method - the phone now shows up as an empty storage device and adb devices no longer shows any devices. The fingerprint sensor (its how i've been trying to find what state the phone is in) also has no feedback when touched now. Thanks for the solution my friend!