What to check after getting the new phone ? - Samsung Galaxy Nexus

My phone will be arrived tomorrow from Google.
And I want to know what code/ app I should use the check the phone before rooting or flashing rom.

Check the Screen
Use Dead Pixel Checker. Make sure you are in a completely dark room. Look for any banding on the screen, black dots on a completely black screen.

This post will help you more clearly decipher if there's anything wrong with your phone's screen.

Do we have a code to enter testing mode like other Samsung device ?
Or we can only install app to test

unlock your bootloader asap.
this way, if you want to root / flash custom ROMs.. you can back up your data on your phone without losing them.
also, get your phone to the latest OTA update

Related

[Q] Need help / Advice possible Brick :D

So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.
Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.
Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:

[Q] What should I do in case of semi-brick?

I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
After re rooting it it seemed to calm down and the frequency of restarting was down significantly.
Now after a week, it is starting to restart again. Should I of flashed the kernel? I see that throw around a lot here in these forums but I don't know if it pertains to my situation. Anything help would be appreciated.
TheZander said:
I rooted my HTC One X and unlocked the bootloader with HTCDev earlier this year. Recently I have had this problem with the phone where it bugs out. Sometimes in the middle of using the phone the screen will turn off and on showing the unlock screen while the Home buttons pulsate white.
So I did a factory reset and the phone seemed to work quite well not as buggy. After I had to revive it by leaving it on the charger for a couple hours.
I also have clockwork recovery still installed and I made a back up image that you guys talk about. The boot.img which I made after I rooted and facotry reset it. I don't think you can even get the boot img without it have that recovery program.
My question is should I try and mess with it some more? Should I re root it? I just want it function with out breaking now is my goal.
And is there any way to hide that whole "This is HTC software... do not distribute " message that comes up when I boot the phone? Because I know this voided my warranty but if I could get rid of that message my warranty is through a third party so I might be able to get a replacement if I can get that boot message off.
Click to expand...
Click to collapse
delete
matt95 said:
delete
Click to expand...
Click to collapse
delete what? am I posting wrong? is there some kind of forum rule or format for asking questions or something?

[Q] Screen Blacks Out - Should I send in to get fixed?

Just yesterday, my phone was working fine and then all of a sudden, my phone's screen turns completely black. I have the T-Mobile version of the Samsung Galaxy S4 with Stock Rom and the factory kernel. I did root my phone and tried to reset the phone by trying to boot up the recovery. It doesn't give me the screen. There is also no Samsung Logo when I boot the phone but a screen with green dots all over. Then, it is on and I can guess my password and such so the touch screen is functional. The LED lights up and the soft keys light up as well. The sound works perfectly fine. So I assume something happened to the LCD screen? There are no cracks or what not.
Since it is rooted, I cannot just send my phone in for repair as the warranty is voided and I cannot uninstall anything or unroot my phone because I cannot see where all my icons are and what not. Any suggestions on what I can do or try? I got it not too long ago too which is a bit disheartening.
Dame thing happened to my gs3, I did reset it back to stock through odin and sent it in. They told me after I sent it in that it had damage to it that was my dually like dropping it or something. No that wasnt the case, the screen just slowly fizzled out. Pain in the ass
Sent from my SGH-M919 using xda app-developers app
I actually don't know how to do a reset via odin. I flashed it and followed instructions/research but since I can't see what is on the screen nor boot it up to download mode or anything... I don't know exactly what to do. Well I think I can boot it up to download mode again. I don't think it will be a problem. I just can't do triangle away after that though after that.
In addition, I would still have root tools installed so wouldn't that give it away that it was rooted? Thus, gahhh this is annoying =( Sorry for ranting... Just very frustrated (like many phone users on here I'm sure).
Edit
I have it on stock rom though... I just need to unroot it... though I cannot see my screen to do anything about it =/
shadowchaud said:
I actually don't know how to do a reset via odin. I flashed it and followed instructions/research but since I can't see what is on the screen nor boot it up to download mode or anything... I don't know exactly what to do. Well I think I can boot it up to download mode again. I don't think it will be a problem. I just can't do triangle away after that though after that.
In addition, I would still have root tools installed so wouldn't that give it away that it was rooted? Thus, gahhh this is annoying =( Sorry for ranting... Just very frustrated (like many phone users on here I'm sure).
Edit
I have it on stock rom though... I just need to unroot it... though I cannot see my screen to do anything about it =/
Click to expand...
Click to collapse
If you have USB Debugging enabled you can used adb to remove root, I believe.
Odin back to stock should do it. Especially, with a busted screen.
Sent from my SGH-M919 using xda app-developers app
Android_Monsters said:
Odin back to stock should do it. Especially, with a busted screen.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
However, my issue isn't a broken screen. The screen itself appears to be fine and same with the digitizer. I don't see how flashing the stock rom will help. In addition, I don't think I can find my way around especially when the screen is all black. I may be able to because I have clockworkmod recovery on there. Just can't see any of the menus or anything.
flashing back to odin uses the phones download mode you dont need a custom recovery you just download the right files and put them in PDA in odin and flash them to your phone while its in download mode
haldi15 said:
flashing back to odin uses the phones download mode you dont need a custom recovery you just download the right files and put them in PDA in odin and flash them to your phone while its in download mode
Click to expand...
Click to collapse
Well the next issue is, it refuses to go into recovery mode or download mode. All I get when I try the button combination is a screen filled with tiny green dots.
do what he does in the video even though your phone doesnt show anything on the screen it probably still works so you can try this
http://youtu.be/DtE7KUc0KQc?t=37s

Screen OFF after attempting to change bootanimation

THIS IS FIXED. NO NEED TO RESPOND. JUST REFLASHED THE ROM.
Hey there.....
I was just goofing around and tried to load a different bootanimation.zip.
The preview in BAM-android looked good so I went ahead.
On reboot, I see the Samsung / Cyanogenmod logo.
..but no boot animation. but the lack of boot animation isn't a really a big deal.
the real problem is that the screen is off when the phone is fully loaded.
I can click on icons and hear that the phone is active, but the screen is off.
Any ideas on how I can fix this?
Thank you very much!
I thought I could re-flash the ROM but it seems as though the screen is blacked out in recovery mode as well.
The screen does show the samsung logo and then goes dark. I am a little helpless without being able to use the screen to troubleshoot anything.
I have some specific questions that are more general for someone who is more knowledgeable with Android than I am:
1- Is there any way to view the screen of my android device on my PC?
2- Can a custom ROM be flashed without using the phone itself to do so (since the screen is not working, even in recovery)?
(something along the lines of using Odin for the stock ROM)
3- What would be a good way to backup the configuration of my phone using my computer without being able to use the screen on the phone?
Any help is appreciated. Even a suggestion that is totally outside of my current line of thinking. Thanks!
just as a side note, I am probably going to flash the Stock ROM using ODIN then flash a custom ROM. I wanted to check with you all to see if I was overlooking a simpler solution or if I should just go ahead with that plan.

[Q] Nexus 7 (2013) 4.4 KRT16S Touch Screen Dead

Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Help
frarredo said:
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
red_ferrari007 said:
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
Click to expand...
Click to collapse
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
frarredo said:
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
red_ferrari007 said:
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
Click to expand...
Click to collapse
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Flashing Help
frarredo said:
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
red_ferrari007 said:
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
Click to expand...
Click to collapse
I can't say for sure that unlocking the bootloader will solve your issue but it will for sure wipe your device. I would recommend creating a back up, but since you can't enable USB debugging to create a backup using adb, you are most likely going to need to be okay with losing all your data first.
As far as I know, I Dont know of any way to enable USB debugging without going into settings first. =\
Check the forums?
I'm at work right now, and I'm also not familiar with the process on a PC. I know how to do it on a mac, since that's what I use and am familiar with. I know that for windows its a very similar process but there are some device specific drivers that you must download and install on your machine before hand.
Without a computer in front of me right now ( I'm at work ) I can't tell you exactly what to do for a PC
Look online there are tons of guides also check you tube.
I should be free later around 2 or 3pm ( pacific ) and if you can't figure it out and would still like to my help. Id be happy to help you then.
Sent from my Nexus 5 using Tapatalk
red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
i am ready !!!
sfhub said:
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
Click to expand...
Click to collapse
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
red_ferrari007 said:
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
Click to expand...
Click to collapse
First step, do you have the USB drivers from google installed? If not download/install from here:
http://developer.android.com/sdk/win-usb.html
Then boot into bootloader (Press/Hold Power+VolDown until bootloader menu comes up)
Then download and unzip this file on your PC
http://forum.xda-developers.com/attachment.php?attachmentid=2405103&d=1384987176
Connect your tablet to the PC via USB cable.
Open up command prompt
Go into the razors-krt16s directory from the unzipping of above file.
type in command line
fastboot oem unlock
follow the directions on the screen. You need to use volup to select yes, and Power to accept.
it will proceed to wipe your user data.
post back when you are done.
i am ready !!!
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
red_ferrari007 said:
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
Click to expand...
Click to collapse
Have you unlocked the bootloader?
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
If you have unlocked the bootloader, follow the directions in this post to flash JSS15J
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
I am suggesting JSS15J instead of JSS15R because it is the closest factory image to JWR66N that you can get.
DONE !!!
i think its done
the LOCK STATE: UNLOCKED is shown
which u recommend ?
Should I proceed with JSS15J ???
red_ferrari007 said:
Should I proceed with JSS15J ???
Click to expand...
Click to collapse
yes.
Instructions in above post.
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
red_ferrari007 said:
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
Click to expand...
Click to collapse
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Last doubt
sfhub said:
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Click to expand...
Click to collapse
Just one doubt before proceeding
From ur link i downloaded JSS15J stock image
ur guide also mentions to download an addon zip file correct ? but its name is JSS1Q addon,zip
So is it correct ???
I need to extract that addon file to that extracted ? STOCK image file rite ?

Categories

Resources