Hi! I was using my N7 3G reading the news and suddenly it became unresponsive. It took about 2 seconds to recognize my touch. So i decided to turn it off and turn it back on. But after it turned back on the touch screen is completely dead. I can't even unlock it. Power and volume buttons still work. I'm on CM 10.1.3
I even forced reboot it many times by holding the power button for about 20s but that didn't help. Anyone ever had this issue too? It seems like a hardware problem. If that's the case i would have it repaired by ASUS but I'm afraid that I won't get warranty because I'm not on stock ROM+rooted+unlocked bootloader
Can you get into recovery? If so, try wiping the cache partition first to see if that helps.
If that doesn't help, do you have usb debugging enabled? If so,
should be able to use the Nexus 7 toolkit. Just boot your tablet, plug it in your machine, fire up the Nexus 7 toolkit and have it unroot and relock your BL.
You might also want to try and see if you can backup your data partition and your internal storage with the N7 toolkit. If you can do that, then you won't lose any of your data or application settings.
You should also be able to flash it back to stock as well via the toolkit and have it erase the user data.
If usb debugging is NOT enabled, then you might be hosed. You could at least do a factory reset in the main recovery.
Other than that, not much else can probably be done unless you want to open your tablet yourself and ensure all the connections are tight. There might be a lose connection for the digitizer and that's all you would need to do to fix it. Of course, that voids your warranty if you open it yourself. I don't know exactly where the hook up is. I'm sure a quick Google will tell you how to fix this if it's possible.
It definitely sounds like either your digitizer is bad or it's got a lose connection.
Good luck!
Sent from my Nexus 7 using Tapatalk 4
thanks for your help. I was going to plug it in my PC BUT IT'S WORKING AGAIN. I was like WTF lol :laugh: . So it must be a lose connection i guess .
By the way, I'm planning to go back to stock in case it happen again so that i can get my warranty at ASUS. And I don't know much about rooting/ flashing so I want to ask some questions .
1. Can I flash google's stock ROM just like flashing other ROMs like CM with bootloader unlocked?
2. Have you tried KitKat. If so have you experienced battery drain? The only reason I rooted and installed CM is that I hate the battery draining issue. I had it since I updated my N7 3G to 4.2.2 and it kept happenings in 4.3
Anyway thanks a lot :good:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
xateeq said:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
Click to expand...
Click to collapse
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Choriandus said:
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Click to expand...
Click to collapse
YES
my nexus 7 with jwr66y has struck on the screen boot failed
I tried to relock using nexus tool kit and then tried to flash stock rom and relock but unfortunately nexus root kit dint woed boot locker locked rk well and it displayed bootloader locked and failoed to flash stock rom and now all i got was a bootloader screen with locked state..help me
Hey, try to do the same procedure again.
Sent from my LG-D802 using Tapatalk
federer123 said:
but unfortunately nexus root kit dint woed boot locker locked rk well
Click to expand...
Click to collapse
Easy for you to say.
I don't know what the point of locking your bootloader would be - especially if you don't have a working ROM on the tablet (stock or otherwise).
If you are trying to go back to stock and never root again, well then: unlock your bootloader, get stock running on your tablet FIRST and only then lock the bootloader after everything else is working.
So, for the moment, unlock the bootloader and get a ROM installed. You can use a toolkit if you want, but using fastboot manually will avoid the "hiding" of any error messages. There are a TON of threads in here on how to do that.
And if you want any kind of decent help, don't use the phrase "it didn't work". That's totally ambiguous - it sort of implies that there is only one possible reason why something went wrong on your tablet, and we all know exactly what that one thing is. Not even close; there are hundreds of things that could have gone wrong.
A far better approach is to detail exactly what you were attempting, and then cut and paste any error messages you observed into your post here on XDA.
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT
Does anyone know if there is a way to root this phone without having to flash the rom? (Temporary or soft root)
I remember doing it on one of my older phones but all I can find for this is rooting by unlocking bootloader and flashing.
I would like to be able to retain my warranty if possible or at the least be able to unroot if I need to return this phone
Any help would be awesome!
Okey I'm on ls997 sprint, but using (perfectly fine) the old deodexd us996 rom (dirty santa'ed'). I do find hateful the corrupt message each time power up or reboot. I couldn't find ready decision of removing it for any other similar device to v20 that way I declare I will donate anyones work and time if he shows me the light. I do accept the possibility of bricking my phone. Would rather brick it trying and buy one than using it with this message. Also never gonna use stock out-of-the-box rom because all the bloatware etc so this solution is not fine for me. Highly appreciate any help.
That message will stay on if you want to be rooted unfortunately
no clue if possible: can you loose root in order to remove the message (somehow) while keeping the custom ls996 rom(on which the device already is) because I may not do any more changes and new roms. I don't make use of the root did it only in order to flash custom rom and loose all the bloatware and sim unlock (switched sprint).
It's there because dirty Santa had to flash a debug bootloader so We could even have root ...and the kdz for our phone hasn't been leaked... So just enjoy being able to use it there is no changing it right now...on one of the nexus they did it by changing a img file but don't know where or what phone.
Sent from my LG-LS997 using Tapatalk
The message is located in the bootloader and can't be removed. The only way to get rid of the message is to return to stock and lock the bootloader.
Thank you for answers.
I do understand this won't work for us https://forum.xda-developers.com/ne...-change-bootlogo-images-imgdata-tool-t3240052
I guess I will just get used to the message best solution :angel:
need someone to backwards engineering the Aboot and either replace the image with a all black image or remove it.
both are extremely risky as the aboot isn't a playful environment and can cause full hard brick.
LS997 doesn't have a KDZ to restore so i'm out for testing on this one sadly. Its been done for other devices in the past but its not a just open replace close deal.