Not sure quite what's happened, I'm assuming a hardware flash issue, but if anyone has any ideas how to fix this, do chip in.
Using nexus 7 (unlocked, but stock and unrooted) when it crashed. Since crash, it looks decidedly read only. It'll boot and you can do a limited number of things, but then it's liable to crash again. Nothing you do is stored, so if you uninstall an app, or change a setting, it'll be back to how it was before after reboot.
Used fastboot to wipe the partitions, but nothing has any effect. Doing a factory reset doesn't wipe user data. Wiping user data from fastboot does nothing. Flashing another recovery does not work, and the stock recovery remains. I can boot twrp using fastboot.
Is this just a hardware fault and I'm stuffed?
Thanks for any and all help,
Related
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
mcwildcard said:
I've got a bit of a problem with my Nexus 10, I want to do a factory reset to remove encryption, but the factory reset fails every time. I've tried the stock one via the menus, and the clockwork one via recovery, but neither works. I thought I'd have a go at re-rooting it to see if I could force the issue, but the recovery isn't able to mount the SD, so I can't get to the file to flash. The unit is spoofing a Galaxy Nexus for SkyGo purposes, which seems to be causing the adb drivers to not work on my PC, as it's obviously not seeing it as a Nexus 10 when I connect. I can't remove the spoofing, as it needs to be rooted, which brings me full circle.
It's a right pickle!
Any ideas what I might be able to do to get the unit rooted again?
Click to expand...
Click to collapse
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Rirere said:
Custom recoveries don't deal with encryption, if I'm remembering things correctly. If your stock recovery's not working either, then that's a serious cause for concern (and is likely why factory reset isn't working for you). To be honest, you may be kind of hosed on this install around. I'd recommend that you boot up, back up your data using Titanium Backup, offload it (connect it to a PC/cloud service while device is on), then plonk into fastboot and just reinstall (or RUU).
Click to expand...
Click to collapse
Therein lies the problem though, for whatever reason my PC won't recognise the nexus 10, despite the drivers being installed from the ADK etc.
Because of that, I can't use fastboot or anything PC based. I suspect it's because the device is spoofed as a Galaxy Nexus.
The device is currently unrooted too, so that also limits my options.
My data isn't really a problem, I'm happy to wipe everything, it's all backed up on my NAS anyway.
Isn't there any sort of physical reset button anywhere that will force a factory reset?
Managed to get the drivers working on my gf's laptop, not sure why my PC wasn't playing ball, but this is all fixed now.
Ta!
Ok i know the fourm is somewhat littered with these posts, and i've tried to do as much myself as i can.
Last night my phone offered the KitKat OTA update.
Its a Nexus 4, with unlocked bootloader, TWRP recovery and root, but no system modifications.
I accepted the update, thinking that it would simply update to kitkat and lose my root. On rebooting to install, the phone launched TWRP by itself, and TWRP ran the update, it went thru various stages of patching things before getting to a step saying something about permissions, where it stopped with an error.
I rebooted the phone and ended up stuck at the new 4.4 boot animation.
I went back into TWRP and tried clearing the caches, and also using the "fix permissions" option but still it hung at the boot animation.
So needing to get the phone working, with minimal data loss, i downloaded the 4.3 stock image, and flashed the boot and system files on in fastboot mode. Hoping to get the phone rolled back to 4.3 where it was before.
Partial Success, in so far as the phone booted, but things are somewhat "weird".
Some data has vanished, such as my call log, and my SMS inbox. Other data seems fine, such as my email client, my wifi settings, google login info, backgrounds etc. But on top of that there are weird quirks, for instance if i swipe down the notification bar, the settings button doesnt work, and i think notifications arent actually showing up either. Similarly, the home button is broken and does nothing. And even more strangely the keyboard appears to be missing!
I'm thinking we're probably at the stage of having to flash a complete factory image, and at least the phones booted so i can pull off my images and things. I'm somewhat pissed about my SMS as i didnt even think of backing them up because it was an OTA update and i assumed it would Just Work.
Any thoughts on what has happened here?
Regards
Kevin
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Same case, mi phone only works with 4.3. Download the 4.3 image, and only flash boot and system, dont flash userdata.
Try flashing the images and making it wipe your device so you don't have any data left. (AKA Clean flash, you did a dirty flash)
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Aragorn84 said:
ok, so i decided to reflash 4.4, and things are still weird.
Same faults as before, no keyboard, no notifications etc etc.
I did fastboot update image image-occam-krt16s.zip, but that doesnt seem to have erased by Apps etc.
I presume i'm going to have to do a full wipe with -w switch and start from scratch?
Click to expand...
Click to collapse
Yes you do. A clean flash is a full wipe.
Yeh that sorted it, Sorry about the double post above, i tried to edit it but it wouldnt let me.
I copied my images off and did a full wipe and now its working again.
It seems like the forum is littered with these messages, but no-one seems to know the actual cause? I presume its somehow related to the modified recovery not applying the update properly?
Would appreciate any advice, please.
My daughter's Nexus 7 Wifi (grouper/nakasi) is bootlooping.
[Yesterday, an app wouldn't install from Play Store (error code -24); went to go to Settings, to clear Play Store cache, but Settings wouldn't open. Rebooted, now it's bootlooping]
The device is still locked, so I'm obviously very limited in what I can do. Is there any way at all I can recover things, without having to do a wipe?
Failing that, I'd like to at least save her app data, and SD contents, before a wipe.
I've tried clearing /cache from (stock) Recovery, no change.
I can connect with adb, but only when in Recovery sideload. I can't connect with adb when it's bootlooping.
I can't flash a factory image, with wipe disabled, since it's still locked.
I tried to sideload an update, but the update fails, since they're all from->to, and it is already on the latest 4.4.2.
I tried mtpfs, but it won't mount.
Anything else I can try, please, before resorting to wiping, and losing all her app data and any pics she may have taken?
Since your N7's bootloader is locked and is on stock recovery, your hands are pretty much tied. I can't think of any solution then a unlocking and fastboot flashing a stock image.
But maybe someone with more knowledge comes by and can help you.
So, I did a wipe/reset from Recovery, which re-formatted /data & /cache.
And it still won't boot... I wonder what is wrong?
What is the recommended procedure now? Would that be to oem unlock then flash a factory image, and oem lock?
Just to follow-up - it was just less than 1 year old, so I rang Google, who did an RMA over the phone, and are sending me a replacement.
They no longer have stock of wifi-only, so are sending a 3G model. Not that I need that. I have heard that this model uses more battery even when there's no SIM in it. Hope not.
Can't fault the service.
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
SwoodGrommet said:
I recently flashed my GT-i9506 and installed CyanogenMod. After finishing, the back and menu buttons (more often the menu button) kept getting pressed with the backlight on and vibrations too without me touching them. The weird thing is that while I was trying to fix it by going to various recovery modes after constantly switching the problem happened there too. The screen was recently replaced but I don't recall this happening at all on the stock ROM after the repairment.
Here's what happened:
I used Heimdall to flash TeamWin recovery but kept getting a common problem with PIT files while in download mode (can't post links because I'm a new user)
I compiled SaburoJiro's Heimdall fork as suggested and that seemed to fix the issue. TeamWin recovery was flashed succesfully.
I flashed the official CyanogenMod rom for gt-i9506 following the instructions on their wiki page. Everything seemed to work fine up until the point where the OS started up.
What I tried:
Tried various recovery images including TeamWin and ClockworkMod Recovery. The problem happens on both.
Used both Odin and Heimdall to flash.
Factory resets and cache clearing
A temporary solution is to enable the on screen navbar, which disabled the hardware keys which were causing the problem. The keys still keep lighting up while the screen is on but they don't do anything.
Is there any way to restore the phone beyond recovery mode (which this seems to happen in too)? I'm pretty sure this isn't a hardware issue.
Click to expand...
Click to collapse
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Lennyz1988 said:
It's 100% a hardware issue. No software would cause this and even then it also happens in recovery. It's impossible to have the same behavior in recovery and in normal android without it being a hardware issue.
Click to expand...
Click to collapse
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
PePeMoke said:
I think Lennyz knows best but did you erased the internal storage too while doing a factory reset?
I've got some strage issues after I flashed a ROM and I could resolve it when I erased the internal storage too on factory reset.
Click to expand...
Click to collapse
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
For CWM I do not know..
I use TWRP and there you can select what should be wiped under "advanced wipe".
You can select system, boot, data, cache and internal storage.
If you got TWRP use this!
Note that everything on your phone will be deleted including custom recovery.
You'll have to flash it again via Odin afterwards.
Then flash the ROM and Gapps via custom recovery.
I do not know whether this will solve the problem because it really could be a hardware issue as Lennyz said..
Maybe you should wait with that after the company repaired it again.
SwoodGrommet said:
Okay, I guess something went wrong when the screen was repaired. I'll call the company that fixed it later. Is there no possible way that any software can enable these buttons?
I factory reset a couple of times using both ClockworkMod and TeamWin. It still kept all the images from the camera though. How would you erase all internal storage using ClockworkMod? Format /system? Or perharps just /data and /storage/sdcard1? Asking since I don't want to brick my phone by doing something I shouldn't be doing.
Click to expand...
Click to collapse
It's possible but not in your case. There is no software booted when you are in the recovery except the recovery itself.
@SwoodGrommet
Could you figure it out?
My Nexus 6p just rebooted randomly, and it's stuck in a bootloop. I am on 6.0.1 (ignore the thread name, it's a typo), I did not upgrade to 7. I am rooted and bootloader unlocked. I can access recovery (TWRP). Can anyone help?
I just attempted to update to the latest build of 6.0.1 (since I had been putting it off) via fastboot, and that still didn't fix it. Still bootloops. Hoping to avoid a factory reset if possible.
Factory reset didn't help... Tried to format the data, didn't work.
Sadly it sounds like your 6P bit the dust. You can see if any of the posted possible solutions in this thread help, but...
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Yeah, I don't know... I thought if I could boot to recovery, it would be easy to fix. But no matter how many times I wipe, factory reset, format, use adb to reinstall, it keeps bootlooping.
Yeah sounds like the boot loop of death. If you formatted data and fastbooted the factory image and still no go, that's pretty much that.
Great. I'm just over a month outside the warranty period and they want me to pay $160+ to get a replacement. And the replacement will have just a 90 day warranty, and if this issue occurs again, which is likely, I'll have to pay $160 again. Never getting Huawei again.