So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.
I build for bliss. Wiping your system essentially formats it as does fastboot before Fashing a new system.img. custom ROMs include a highly compressed system image as seen I this screenshot of my out folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 6 using Tapatalk
---------- Post added at 19:46 ---------- Previous post was at 19:45 ----------
So its fine to wipe as long as your flashing a new system. Pay no attention to recovery, cache and userdata images. They're excluded from the final zip
Sent from my Nexus 6 using Tapatalk
DroidManIc said:
So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.
Click to expand...
Click to collapse
It is advised to wipe/format system when flashing. Once wiped it is ready for a rom to flash. There is always a way to recover from wiping the system but not having a rom to flash on the device.
Most roms wipe the system as they flash.
Good stuff, thank you both for the reply. I'm unlocked rooted and twrp installed and ready to flash!
DroidManIc said:
So I'm fairly new to the N6 (first nexus device) community... That being said, been flashing for about 5-6 years now and from what understand up till now you SHOULD NOT under any circumstances use the WIPE SYSTEM option when in TWRP because it will completely... Well, wipe your system. I've done this twice before and almost ended up w 2 paperweights (once as a noob and the second time on my m8 by accident) no boot, no rom and no way to transfer a rom to flash. Now, could someone help me understand why wiping the system won't screw w this this device? Thank you.
Click to expand...
Click to collapse
That is not even close to being true for basically any phone with TWRP/custom recovery.
The recovery loads well before the system, and is on a different partition. TWRP has supported sideloading for quite a few versions now, and any phone with an unlocked bootloader can likely use fastboot or an equivalent to rewrite the system from bootloader mode.
It's perfectly fine to not understand or not be informed... By why does every person who has little idea what they are doing have to over emphasise that they have been flashing for years? Its fine to have a gap in understanding or a lack of knowledge. Particularly with Android which is not as well documented as other systems... Even better to ask... But man everytime I read "I am not new at this, I have been flashing for years..." its followed by a fairly basic question.
So that I am not just *****ing, let me ramble about booting ... Read as much or as little as you like Anyone who wants to correct me please do, this will mostly be rough and loosely worded
Its important to understand that when turning on your phone, it doesn't just send electricity to Android, and spring to life.
If you think about it... If everything was fully shut down and lifeless with nothing active... How would your phone even know the power button was pressed? How would power button do one thing, but the bootloader key stroke combo (power and vol down at the same time) boot to a different mode? How does power button require being held down and time how long?
The hardware the power buttons attach to sit active and watch for button presses. When it sees the proper combination It will tell the "motherboard" its time to power up.
But still, It just can't be android... Android is stored on your internal SD card, which is partitioned... The data is split up into different chunks and the phone does not even know what chunk the system is in.
So motherboard starts to initialize very basic stuff. It will find its CPU, and will find storage, ect...
When it finds the storage, it will look for a special flagged partition that contains a simple program, the bootloader.
Bootloader is not android and almost has nothing to do with android, the system partition... whatever. Its running on VERY minimal hardware (hence when your in bootloader mode, you use the volume keys to scroll up and down... touch isn't loaded yet).
As long as bootloader is not broken/corrupt/erased and is not locked... Your pretty much safe. It has basic tools to receive data from a computer via fastboot, it can mount/write/wipe other partitions.
It also knows where your kernel is, and where your recovery is. Typically it will automatically just load the android kernel, which will continue to initialize the rest of your hardware, and and get all the software that gives you a user interface and control going.
It can also boot into recovery mode instead of booting into android. Recovery mode is yet another self contained program/operating system/partition that runs independent of android. It offers more interface and functionality then bootloader mode, but is still basic. I am sure you remember when recovery didn't used the touch screen either... This was because the factory touch screen drivers had not been loaded yet, the teams that write these recovery programs eventually included software to instruct the system how to read touch input though.
The point is the phone boots and initially only knows/needs/cares about the partition called "bootloader", which has a self contained program that has basic recovery options when paired with a computer and fastboot.
That bootloader looks for the partition "boot" which contains your kernel which will load the android OS off "system", and your personal data/preference off "userdata"
OR
The bootloader can load your custom recovery off the "recovery" partition, which can mount/read/write most other partitions.
The warnings about not wiping system were likely based off the idea that you needed to boot into android in order to download a rom to flash... but really you should always have a backup that you have made at a point when your system was working good stored on your "userdata" partition, or on an external SD card if you phone supports it.
However lacking those two options, at some point in the past you may have had trouble... But TWRP has supported MTP transfer for a while now, and failing that the sideload command, that flashes a rom from your computer via ADB has been supported for quite a few version, and even before that (starting in 2014 with TWRP 2.8.0.0) ADB was supported so the "adb push" command could be used to send data to a phone with no rom on it.
ANY of the above paragraph only really matters on a phone with a locked bootloader and custom recovery installed though, which is why people point the the nexus as being different (even though other phones have unlocked bootloaders). As long as you have a factory image of the phone, fastboot can be used to re-write the partitions to the phone without it even having a custom recovery (that how your custom recovery likely got on your phone in the first place... the same can be done for system or boot as well as the other partitions too).
Phones with a locked bootloader and/or no publicly released factory images are probably why you heard this warning in the first place.
Related
I've had my Note for some time, and now i think i super bricked it, here's the thing:
It was on the charger and i was using TeamViewer as a remote for my pc, it was heating quite alot, but it was holding up,
so i turned off the app, wifi, turned on power saving, and left it on charger through the night, when i woke up i tried to unlock the screen but nothing happened, so i tried to turn it on, it showed the Samsung Logo + the flash sign thing, and then the Paranoid Android boot anim, and then it just turned off.
I then thought it was something with the rom wrong so i got in the DL mode, or what's it called, it worked, but i dont know how to operate odin so i left that and went into the recovery and tried to reflash the rom from my sd card, but mid flashing it just froze, and after a few seconds it turned off, i tried booting into the os, nothing, then tried recovery, it was working, than tried to flash again, but same thing, freeze, turn off after few seconds, and after that, nothing, no samsung logo, no dl mode, no recovery, nothing, i see a small horizontal line when i try to turn it on but it just blinks for a fraction of a second, so i was thinking the cpu or gpu, or whatever, was cooked, then i plugged the charger in and the battery screen turned on, i responded to locking the screen and unlocking.
I got it from the repair shop a few hours ago and they say that they MAYBE can repair it, so i'm coming here seeking help,
I'm thinking that the NAND or eMMC or whatever memory that has the os and kernel on it is corrupted, so, is there a way to flash it with some third-party hardware, like you do on consoles for pirating purposes...
If that is possible please tell me what hardware do i need to directly flash a kernal/os/rom onto its main memory.
Thank you in advance!
In your case I would:
Find odin.
Find Samsung fastboot/recovery drivers
Find a stock samsung rom in Odin format.
Find philz kernel in recovery flash format.
With Odin, flash stock rom. Find tutorials for it, it's easy. Install the samsung drivers if need be.
If the device boots, let it boot, copy philz kernel to sdcard root.
reboot to recovery (power up + home + power combo)
flash philz kernel
reboot
let it boot
reboot to recovery
flash Custom rom
I would go with a charged battery first. For some reason I feel there is no juice left. You also could have corrupted the system and data partitions by flashing. So if you get to recovery after inserting a charged battery, then boot into recovery mode, format system, data and cache. Then install a new rom.
But for odin i need to go to DL mode first, right?
Becouse i cant access even that.
What happens when you try ?
Also, nokiamodeln91 is correct. Does the battery image show up when charging powered off?
Okay, i can get into odin.
Now what?
Flash a stock(ish) rom. Read about what you're doing.
So, i managed to get a stock rom on it, but i still cant boot into anything, except odin.
When i connect it to a pc i see the battery charging a few seconds then it boots into recovery on its own, i wiped data/factory reset, and wiped cache, but still cant get to os, what next?
Rochendil said:
So, i managed to get a stock rom on it, but i still cant boot into anything, except odin.
When i connect it to a pc i see the battery charging a few seconds then it boots into recovery on its own, i wiped data/factory reset, and wiped cache, but still cant get to os, what next?
Click to expand...
Click to collapse
Paste Odin logs and which rom did you flash?
Also, install ADB drivers. See if you have ADB debug enabled (shouldn't have)
There's a minimalistic adb packaged that could be usefull, try to run adb logcat
nokiamodeln91 said:
Paste Odin logs and which rom did you flash?
Click to expand...
Click to collapse
Its some indian GB rom, the only rom i could get, all the others are either on slow premium hosting sites or hot-file.
The flashing went well, i think, everything passed and was green, im not sure how to get the logs after i closed odin.
daedric said:
Also, install ADB drivers. See if you have ADB debug enabled (shouldn't have)
There's a minimalistic adb packaged that could be usefull, try to run adb logcat
Click to expand...
Click to collapse
I've installed adb drivers and the program, but where should the phone be when i try to adb to it, because when its in odin the adb device command does not detect it, and i cant get into the os to check usb debug?
Try ADB when it's failing to boot.
How? What to type, what keys on the phone to hold?
What to do?
leave it charging for a hour or so, then try to turn it on normaly.
So after i flashed a stock rom i got into some weird boot-loop, charging logo-->recovery logo-->charging-->recovery... and so on, until it somehow booted into recovery, sometimes, without any input whatsoever, and now it got out of that loop and is just on charging screen without blinking.
oh and i tried a brand new battery, which was empty (0.7V) vs my original samsung battery which i charged with external charger outside the phone when i thought it wouldn't charge it.
so to sum it up, first i thought that my battery was drained and charged it externally, but it didn't help, i believe the battery is fine, and charged, i tried it with some load it voltage dropped from 3.9V to 3.3V with ~50ohm resistor, i think that is fine, although i'm not sure.
The brand new battery that i bought was at 0.7V before charging, and when i inserted it into the phone and connected the charger no charging logo appeared, the phone was heating slightly and after 12-14 hours of charging, with the phone off of course (because there was no other state for it then), it still showed 0.7V.
oh and before, on the original battery that is currently running, the charging logo was blinking, i think it was trying to get into recovery, but there was no recovery.
PS: by the time i wrote this it got into the weird charge>recovery>charge>rec... boot loop again...
this post is a mess, as i'm writing a bunch of things that come up that may be important...
please ask if you don't understand what i just wrote up here.
EDIT: it got out of the loop again, dunno how long that will last...
Not a mess.
Ok, let's get facts. Is recovery a image with a "Android" laying down ?
When you flash something via Odin, on the first boot it MUST go into recovery and finish flashing something (CSC i believe)
That's what it must be trying.
So.. debug.
Does it do that loop thing UNPLUGGED?
when its unplugged nothing works, no odin, no recovery, nothing.
it booted into recovery, it showed something like CSC pass or something everything was good, the phone was completly working, just that it was recovery, and not the os that i want to get.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This logo, without the text below.
That's the recovery logo, probably the stock recovery (3e).
Can you force it to boot to recovery ? (and stay there ?)
i dont think so. maybe flashing the rom again and it getting there on its own, like i got there in the first place. so, what to do when i get into recovery?
Nothing... wait 4/5 seconds and it should reboot and this time boot properly.
Was at work using both my company phone (iPhone 5) and my personal phone (HTC One Mini 2) just fine. Put my personal phone away to get on with actual work and came home at around 5:30'ish. Played a bit ("a bit") until about 9/10pm (I think?) whereby I looked for my phone to just check things like WhatsApp and Snapchat and the phone wasn't turning on when I was holding the power button. I just thought to myself "huh, the battery must be dead" and put it to charge and the charging LED (as well as the charging screen with the "do not distribute outside htc blabla" dev screen) displayed so I just assume it's charging as per usual. Fast forward to about 1am, I have finished using my computer and decide to hop into bed. I go to turn on my phone by first powering down with power, vol up and vol down (as usual) and then try to boot the phone up. It boots as normal up until the O/S loading screen with a pac-man boot animation (I have PAC ROM installed) whereby it will freeze on the "game over" image of the boot animation and then proceed to go to a black screen. I thought to myself "hm, must be a mistake or something" and try it again to no avail. So I then go into recovery to do a fresh install and I try to wipe the phone and I do a factory reset in twrp, but upon trying to format data, the progress bar doesn't move (and so I left it overnight as I couldn't be bothered to wait). Upon leaving it overnight (1am to 7am) to format the data, I wake up to see that the progress bar hadn't moved at all from 0%. I then just thought "maybe the phone has actually formatted it but hasn't updated the image on screen so me being the dumbo I am, decided to force shut down the phone (with power, volup and voldown) and upon trying to boot the phone up again, it displays the HTC logo with the red writing, tries to boot into the O/S, fails, and then tries to boot into recovery and gets stuck in a boot loop (it will show the twrp logo and then a black screen, twrp logo and then black screen etc.). I have tried to flash twrp again (without first removing the twrp currently on it) but I was wondering what I could do in this situation. I am able to access the bootmenu (for hboot and fastboot) but nothing else.
TL;DR: I think I bricked my HTC One Mini 2. Came home, charged phone and phone got stuck at boot animation. Wiped phone in recovery, it got stuck on formatting data and now It can't boot into the O/S since it's wiped and it can't boot into Recovery for whatever reason.
DistincTHD said:
blah blah
Click to expand...
Click to collapse
This is not Facebook, go straight to the point.
Did you install a different kernel?
kativiti said:
This is not Facebook, go straight to the point.
Did you install a different kernel?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
DistincTHD said:
[IMG="HTC Dev Message"]
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Oops, Just realised you meant the whole post, not just the blah blah bit within the post. But yeah what I did, I explained above and in the original post. I basically just told a story to give a better idea of what generally happened before the phone just pooped out on me.
DistincTHD said:
Sorry for the confusion, I wasn't doing that because I couldn't/didn't want to explain, it's just a common message people get after dev unlocking their HTC phones. And no, It was working up until when I tried to use it last night randomly. I flashed PAC-ROM ages ago (like maybe 2-3 weeks ago or maybe even a month) with the HTC One M9 Camera Kernel and that's it. I then tried to use it last night and what I explained in the original post occurred.
Click to expand...
Click to collapse
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
kativiti said:
Something its corrupted so try to reinstall everything using the files from this post plus your choosen ROM.
When rebooting phone unplug USB cable.
Click to expand...
Click to collapse
I can't access twrp recovery but I do have fastboot enabled and working and I can access the boot menu so how would I go about wiping everything before re-flashing the recovery and then re-installing the o/s and everything else?
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
DistincTHD said:
Just tried to first erase everything before installing and it's locking me out of the phone? It's telling me that an administrator console is unable to erase the system or its data so I'm quite stumped at the moment
Click to expand...
Click to collapse
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
kativiti said:
you don't need to do all that.
try to flash twrp. (if OK use it to wipe everything)
If NOT ok flash stock recovery and unlock bootloader( yes again, this will wipe your phone and fix permissions)
Then you can do all you want.
Good luck.
let me know...
Click to expand...
Click to collapse
Right, so before I read that message, I flashed stock recovery and tried to reformat data and now It won't let be get into the boot menu and the HTC dev writing is gone (so I think it's locked again). On top of this, it just keeps booting into the reformatting data screen and just ends up hanging so I think I will let the battery drain or something (no idea how long it would take, probably days) and then try again from there. Pretty sure it is bricked now though lol welp. Is there any way to cancel a format?
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
I too would love and greatly appreciate any help! It's a great tab for the money
hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You flashed custom recovery ? the bootloader is not locked?
I tried a twrp custom recovery image. But I cant start the recovery mode. I do not know the status of the bootloader. How can i check that?
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
what do you guys think of my new shirt isn't it awesome
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bws78 said:
http://forum.xda-developers.com/android/development/recovery-official-twrp-gtaxlwifi-galaxy-t3437666
@jcadduono did it !
Let's try
Click to expand...
Click to collapse
Thank you very much, this works for me.
hell2003 said:
Thank you very much, this works for me.
Click to expand...
Click to collapse
don't thank me, thank @jcadduono in the official thread
Data partition encryption prevents root without a .zip rom
hell2003 said:
I try to root a Galaxy Tab 6A (SM-T580).
-I tried some CF-Autoroot images, but their is no image for the SM-T580.
-I tried also to install TWRP with no success. The device do not boot in Recovery Mode with the TWRP image.
The device runs on Marshmallow 6.0.1.
Can somebody help me please?
Click to expand...
Click to collapse
You can disable frp lock by removing your Google account. This will allow you to flash twrp with Odin.
Disable auto reboot in Odin before flashing twrp. After flashing twrp you can reboot into recovery by holding power and volume down to turn the device off. Then once it's off hold volume up home and power to reboot into twrp.
Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
If anyone could create a stock or custom ROM that is a flashable zip you'd be the MAN!
Until then I don't think we'll be able to root our device.
Still no roms available?
Now the only problem is you can't flash supersu.zip without formatting data first from the twrp wipe data main screen. This is because the data partition is unavailable due to encryption. Formatting data partition removes encryption and allows you to flash supersu, but now device won't boot after formatting data unless you flash a ROM from within twrp. Only problem is that there are no such Roms yet.
Click to expand...
Click to collapse
Does this mean that if you just root the device that the data partition is encrypted and cant use it as if it was not rooted?
Tried this last night but got the Fap lock. Didnt know about the google bit.
I want to download my current rom and backup is this possible?
I havent done this stuff since the HTC HD2 days
Thanks.
Rob.
I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it
hi
only for root..
Can i use cf-autoroot?
abarth83 said:
hi
only for root..
Can i use cf-autoroot?
Click to expand...
Click to collapse
Hanyone tried it?
Instructions
kleptobismol said:
I've successfully bypassed the Google FRP Lock on SM-T580 and posted the instructions in [URL="https://forum.xda-developers.com/galaxy-tab/help/bypass-frp-sm-t580-2016-t3446958]this forum[/URL]. If you cant figure it out send me a message and I'll walk you through it
Click to expand...
Click to collapse
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks
ohiostater86 said:
Hello, Can you repost instructions can't get page to load
This site can’t be reached
%22https’s server DNS address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN
Thanks
Click to expand...
Click to collapse
I was having the same problem, but i figured it out last night. Without OTG cable, Odin, SideSync, Realtek, or a PC. I'd been messing with it for 3 days, so Im not 100% sure of what everything said and i'm definitely not going to relock it to try an duplicate it, but if you've been all over youtube then you've seen methods that require a wifi connection, (I found it easiest to use my phone's wifi hotspot) you disconnect your hotspot or unplug your router immediately when it says checking for software update, which appears after clicking accept on the privacy policy. (Again it's easier to just turn off the hotspot than to unplug your router" When done correctly it souls say "couldn't sign in" and then the next screen will either ask you to set up time and date or it asks you to add a name to the tablet (can't remember which is first) then asks to set up a screen lock passcode or pattern (set up either one), after doing all this 100 times I noticed it asked me if i wanted to set up a IMAP/POP3 account to use within the Gmail app (which I'd been skipping) but for some reason it didn't give me this option every time. You have to be connected to the internet for the next part so if you haven't already go ahead and turn your hotspot back on or router and add any email address other than a Gmail (I used my yahoo account) then follow through with the setup into it takes you back to the very first screen you see when you turned on the tablet. Now just turn the tablet screen off and back on (just the screen, do not power down the tablet) put in your lockscreen password and now In the top right corner there should be a little yellow icon which lets you switch users (if you see this, you've got it beat) now create a new user signing into your Gmail and Samsung accounts (if you don't have one, create a new account) once you're done with that it will take you to the home screen, pull down the notification bar and go into settings (notice since you're on an added user you can't factory reset the device) find "Users", and then switch back to the owner profile, it then tells you that you still need to set up the tablet to continue. Once i clicked okay it now let me pull down the notification bar to access settings, but this time you're on the owners account so you can factory reset it, go to "Back up and Reset" and then go ahead and factory reset it again. If done correctly the FRP will no longer be on the tablet.
I rooted my T580 with this german howto:
https://www.android-hilfe.de/forum/...sm-t585-samsung-galaxy-tab-a-2016.788225.html
Root is ok now! But unlocking the LockScreen needs 5-10 seconds now. Has this sth to do with Knox 0x1 ?
Getting "Your device is corrupt" message and I want to start completely fresh.
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
LaTropa64 said:
I had setup a Nexus 6 a couple years back for someone who was mostly blind and I used tasker to let them do most things they needed by voice only.
It was working fine until a couple days ago when somehow the device upgraded from Lollipop to Android 7.0. The way I initially unlocked the phone and obtained root, I didn't think it would ever be able to upgrade unless I intervened but it finally happened seemingly on its own.
Anyway, it lost root and many of the tasker commands stopped working because of it so I tried to get it back by:
1) Using fastboot to flashe twrp-3.1.1-0-shamu.img to recovery
2) Booting into recovery and installing SuperSU with TWRP after I made a backup
After that, the phone booted back up normally but still didn't have root access so I restarted again but when I tried to get into recovery I got a "no command" message. I was finally able to get passed that by pressing volume down (I think) and it gave me the standard android factory reset, wipe cache, etc. options. I tried wiping the cache and then after reboot I got this message:
And then it just disappears after a few seconds and the phone will not boot up.
Now though I can still get back into the bootloader menu with Power and Volume Down and even get back to the TWRP recovery where I tried restoring the backup I made before installing SuperSU but the same problem occurs.
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
I'm not sure what to tell you, there's a lot of complication between these things but mostly seems like it'd include Re-flashing stock os 7.0 and obtaining root thru Android 7 without flashing any rom
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
And by complication I mean the whole concept of just starting over fresh
Sent from my Z988 using Tapatalk
---------- Post added at 08:09 AM ---------- Previous post was at 08:09 AM ----------
Good luck tho
Sent from my Z988 using Tapatalk
LaTropa64 said:
I don't know what I've done wrong but I just want to start over. What do I need to do to wipe the phone completely and start over like it was brand new out of the box?
Click to expand...
Click to collapse
Download a factory image from Google developer site. That site gives instructions to set-up your PC for fastboot (if you need it) and there is a flash all script in the download to handle the flash through fastboot. This thread will give you an overview. Using the flash all script will wipe the entire phone!
You can also fastboot flash each partition manually. If you use the -w flag, it will wipe all user data from the phone.
Be warned, the probability is you'll wipe the internal (user data) and if you want to try to back up first, you should be able to boot into TWRP and use ADB to do an a back up of user data to your PC using:
adb pull /path/to/files /home/[your username]/
E.G.
Windows:
adb pull /sdcard C:\Users\[your username]\Desktop
Linux:
adb pull /sdcard /home/[your username]/
You'll need administrator privileges on the PC to specify the output path.
---Edit---
You might look into the tasker beta to work with the newer nougat releases. I will say, all of my tasker profiles continued to work regardless of OS version with the exception of those relying on secure settings. Those I updated to use auto tools. There are other work around as well.
Follow what @ktmom says to get the device all straightened out firmware wise. As the device totally skipped Android 6 in doing its upgrade there could be undesired leftovers from the original install. Once you've installed the latest stock firmware from Google you can start over with your customizations, but be aware that installing TWRP, rooting the device, or both will cause the "device is corrupt" message you're seeing. That message will remain on every boot until a custom kernel which ignores dm-verity is installed.
In a few months, Galaxy S8 will get Bixby Voice so you could get one of them.
Sent from my Z988 using Tapatalk
Who in the hell would want to use Bixby?
Hello i bought a replacement screen for my phone about a month ago because everything was still working except the screen was broken from cracks. As i was about to replace the screen i noticed my phone is now not turning on at all even on charge. No red light, nothing. Is it possible the battery just needs to be replaced or is the phone completely dead?
Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.
ktmom said:
Try charging it for a few hours on a low power charger like a computer USB port.
When the battery gets very depleted, it can have trouble taking a charge from a faster charger.
Click to expand...
Click to collapse
Hi, i tried to charge it using the PC but it didn't change anything. Would it be worth it getting a new battery to test if it still works?
I guess that's a decision you have to make. Is the expenses of the battery worth the risk that something else is wrong. It's possible the power button assembly has a problem. It's possible the USB port is worn, damaged or dirty.
Paperweight now? Having a different issue but potentially fatal??
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
archos5005 said:
My nexus 6 has been my faithful companion for many years, and now, though it is not my main phone, is used as my bedside companion for many uses. I boot it up one day and it gives some sort of "file encryption error" and then would not boot. I downloaded a fresh rom and adp to try to wipe it and just get it back to any working state, but nothing seems to work. What am I doing wrong?? (see photos attached)
Click to expand...
Click to collapse
Let's start with some basics. It looks like the phone is stock (not bootloader unlocked).
What version was on the device before the problem?
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices page. The instructions there are solid.
If your not sure what was on the device, use the newest release.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
BTW; your images are not showing up because the use of the IMG tag is wrong. There should not be anything inside the brackets with the tag (e.g. ="error"). The link does go between the opening and closing tags as you have it.
In the future, it also is a good idea to start your own thread, instead of burying a question inside a unrelated thread.
ktmom said:
What version was on the device before the problem?
pretty sure it is the latest (for that model) Android 7.1.1
Can you boot to recovery? (With the phone powered off, press and hold Volume Down, then press and hold Power)
I can get to the screen that shows the green android man lying with his compartment open. Is that recovery? It seems that everytime I try an option, it does not "do" anything. E.g., factory reset just won't let me do it. It just doesn't work [is this a symptom of emmc memory just being damaged? I know on PC's, a total reformat can isolate bad sectors...]
Try sideloading an OTA the same as your current version. They are available on the Full OTA Images for Nexus and Pixel Devices[/URL] page. The instructions there are solid.
I think I've followed that, (see the second picture) but again those commands don't seem to "do" what the commands usually should do. Like I need a tougher solution--willing to totally wipe everything and reformat and start anew, like a low level format.
Based on your photo, the device is not unlocked. You won't be able to Fastboot flash anything if you can't unlock it which requires the OEM unlocking to be enabled in developers options. Since you can't boot, you are stuck there.
It's quite possible the eemc has failed and the device is damaged.
I think I tried unlocking it, but same thing it didn't "work" either that, or I'm just doing it totally wrong [is it not the command "fastboot flashing unlock"??].
Click to expand...
Click to collapse
Thanks in advance. I just don't want to accept that it was working great one day and then turning it on the next day the flash memory is just TOTALLY bad, you know?
When a you boot to recovery, then get the "no command screen" press and hold Power then press and release Volume Up. If you can get to recovery, do a factory reset.
Unlocking the bootloader won't work unless you have already enabled OEM unlock in the developer options when booted to system. I said this earlier.
ADB won't work unless the kernel is booted. ADB only works when booted to recovery or fully booted to system.
Unless the bootloader is unlocked, Fastboot doesn't get you anything.
If you get to recovery and a factory reset doesn't solve your problems, do an OTA sideload using the link I gave you before.
Please Do Not bury your comments within the wipe of someone else's post. It makes it impossible to follow the conversation. Just respond below the quoted post.