Database Info

[Q] A new US TF700 but a few questions.....

Just bought a TF700 from Amazon (much cheaper in the States than where i live) but got a few questions:
(a) Its still on ICS and I suspect that i will end up installing custom roms etc as I have done with my GS2. I read that i should before i root or unlock bootloder i should backup using NVflash (i think mine is pre 30) but does that prevent me from going to JB or does it not matter?
(b) I use wifi channel 13 at home, but i know my tablet as i bought in US probably has wifi channels 1 to 11. How can i change the wifi to include up to channel 13?
(c) Are there any other diff between a US version of TF700 and a WW version? I note that on the Asus website they have different firmwares.
Thanks!

blion said:
Just bought a TF700 from Amazon (much cheaper in the States than where i live) but got a few questions.
Are there any other diff between a US version of TF700 and a WW version? I note that on the Asus website they have different firmwares.
Thanks!
Click to expand...
Click to collapse
It is possible to convert your tab to the World Wide or other appropriate firmware by a reflash.
Do you know how this is accomplished?
If not post back and we can guide you.
Also I'm not sure about the wifi channel change, yet there there is most likely a way to change that.

The way to change the WiFi is via a build.prop text edit hack. It's as simple as changing the country code from US to GB
You must be at least rooted to do it. Of course if you take an nvflash blob copy then unlock the world is your oyster! :victory:

Thats OK said:
It is possible to convert your tab to the World Wide or other appropriate firmware by a reflash.
Do you know how this is accomplished?
If not post back and we can guide you.
Also I'm not sure about the wifi channel change, yet there there is most likely a way to change that.
Click to expand...
Click to collapse
Sorry but I dont know how to convert it to a WW. Would appreciate it if you could let me know!
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Also do you know the answer to my question (a)? I want to update to JB but worried i wont be able to after using NVflash.....

sbdags said:
The way to change the WiFi is via a build.prop text edit hack. It's as simple as changing the country code from US to GB
You must be at least rooted to do it. Of course if you take an nvflash blob copy then unlock the world is your oyster! :victory:
Click to expand...
Click to collapse
Thanks but could you provide more info on how to edit build.prop??
I will try and root tonight. Can you explain what is an nvflash blob copy??? I come from using GS2 where there was not a need to unlock the bootloader but i read that unlocking the bootloader (and therefore losing warranty) is required in order to install a custom rom.

blion said:
Thanks but could you provide more info on how to edit build.prop??
I will try and root tonight. Can you explain what is an nvflash blob copy??? I come from using GS2 where there was not a need to unlock the bootloader but i read that unlocking the bootloader (and therefore losing warranty) is required in order to install a custom rom.
Click to expand...
Click to collapse
Doing the nvflash thing will in no way stop you updating to jellybean however updating to jellybean will stop you doing the nvflash thing. Nvfash is security nothing more. You can recover from any bricks after you do it.
As for gaining root and editing build.prop I would suggest you read the stickies in the general forum. Think about unlocking and flashing a custom rom if you are not comfortable doing the edits yourself as it's all too easy to get into a bootloop (recoverable) if you don't know what you are doing.

Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Hi, I have a tf700 that I bought from the US and I live in the UK, I have always used US firmware and have never had a problem with wifi.

maxal said:
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Hi, I have a tf700 that I bought from the US and I live in the UK, I have always used US firmware and have never had a problem with wifi.
Click to expand...
Click to collapse
You won't but if you set your UK wifi router to use channel 13 you will Your US infinity won' see it. To fix you flash a WW rom or do the build prop edit and it will work again.
As for other differences I'm yet to find any yet. Other than wifi they both behave the same way.

maxal said:
Do you know what are the difference between a US and WW firmware other than the Wifi channel??
Click to expand...
Click to collapse
AFAIK, the list of included system apps is slightly different, and also the other apps are at least recompiled for each country version.

Good news......confirmed my new tab is 9.4.5.26 version which i think will enable me to use NVflash!!
I want to try Cleanrom and want to make sure i get this absolutely correct (i dun wanna brick my new tf700!!!).
(a) Follow the guide to backup using NVflash (http://androidroot.mobi/t3_nvflash/)
(b) Install the official asus 4.1.1 bootloader (current version seems to be V10.4.4.23)
(c) Install TWRP 2.3.1.0 (follow this guide http://forum.xda-developers.com/showthread.php?t=1938129)
(d) Do i still need to install SuperSU or can I go to install Cleanrom directly??
Is there anything i should be mindful of before flashing??
Thanks in advance!!!!

blion said:
Good news......confirmed my new tab is 9.4.5.26 version which i think will enable me to use NVflash!!
I want to try Cleanrom and want to make sure i get this absolutely correct (i dun wanna brick my new tf700!!!).
(a) Follow the guide to backup using NVflash (http://androidroot.mobi/t3_nvflash/)
(b) Install the official asus 4.1.1 bootloader (current version seems to be V10.4.4.23)
(c) Install TWRP 2.3.1.0 (follow this guide http://forum.xda-developers.com/showthread.php?t=1938129)
(d) Do i still need to install SuperSU or can I go to install Cleanrom directly??
Is there anything i should be mindful of before flashing??
Thanks in advance!!!!
Click to expand...
Click to collapse
You'll need to unlock it at some point too
SuperSu is included in CleanROM so not needed.
It's all very straight forward and remember because you are coming from Stock you won't need to do a full wipe.

sbdags said:
You'll need to unlock it at some point too
SuperSu is included in CleanROM so not needed.
It's all very straight forward and remember because you are coming from Stock you won't need to do a full wipe.
Click to expand...
Click to collapse
Thanks! Ops forgot about unlock. Will unlock, backup NVflash, install asus bootloader, TWRP and then insall cleanrom???
Lastly, should i install odex or deodex version of cleanrom??? The verdict seems to be split.....not sure what practical difference there is between the two..............

blion said:
Thanks! Ops forgot about unlock. Will unlock, backup NVflash, install asus bootloader, TWRP and then insall cleanrom???
Lastly, should i install odex or deodex version of cleanrom??? The verdict seems to be split.....not sure what practical difference there is between the two..............
Click to expand...
Click to collapse
I'd start with the deodex version but they are so close to each other and easy to switch between. Try them both. You don't lose any apps or data by switching between the two as same base.

Just purchased can i root JOP40D.WW.epad-10.6.1.27.1-20130711 ?

Hi, I just purchased a TF300 from ebay (arrived this morning).. My first task was to try and root it and I've been at it all day without success. I've trawled many forums, used search bars galore and don't know what to do. I've tried Motochopper (which I now know doesn't work) along with other various apps to no avail. I've even unlocked the machine thinking that would help but no.
Obviously this wont have been rooted before so where does it leave me? What are my options? I'm rather new to android (only got my Galaxy S4 a month ago) but i'm learning quick.. just a bit frustrated as to where to go now..
any help greatly appreciated
Thanks
barry

Solved...
I downgraded to a previous firmware version and then rooted..

holidayaddict1 said:
I downgraded to a previous firmware version and then rooted..
Click to expand...
Click to collapse
you could unlock your bootloader and flash a custom rom that will really improve the tablets performance but you do void your warrenty (although you might not have one as you bought off ebay)

holidayaddict1 said:
I downgraded to a previous firmware version and then rooted..
Click to expand...
Click to collapse
Yeah and then use root keeper to keep root before updating to the new firmware

nooktablet said:
Yeah and then use root keeper to keep root before updating to the new firmware
Click to expand...
Click to collapse
I'm not really into these custom roms that look all fancy i prefer the stock look - are there any like this and do they install the same way that i installed the older firmware (I used the volume down power combo then selected RCK or something similar).

holidayaddict1 said:
I'm not really into these custom roms that look all fancy i prefer the stock look - are there any like this and do they install the same way that i installed the older firmware (I used the volume down power combo then selected RCK or something similar).
Click to expand...
Click to collapse
well first you unlock your bootloader with the app from the asus site, the use fast to install a custom recovery (twrp 2.5.0.0) the use twrp to flash the custom rom, and if you flash cromi-x it looks completely stock the only difference is if you go into settings and look at the about tablet tab then it says cromi-x in the build tab, there is a step by step guide to getting twrp installed and ill talk you through installing cromi-x if you want but it isreally easy
Sent from my ASUS Transformer Pad TF300T using Tapatalk 4

[Q] Rooted and unlocked bootloader

Hi Everyone,
I am new in XDA with Nexus 5 mobile, i am wondering can i update my rooted and unlocked bootloader Nexus 5 through OTA with stock rom and stock kernal? Thanks Everyone

Duckone said:
Hi Everyone,
I am new in XDA with Nexus 5 mobile, i am wondering can i update my rooted and unlocked bootloader Nexus 5 through OTA with stock rom and stock kernal? Thanks Everyone
Click to expand...
Click to collapse
Yes, you will receive and be able to install the OTA (if you also have the stock recovery) but you will loose root though.

Thanks alot for your kind reply.

This is all covered in the "ota helpdesk" thread stuck at the top of this general forum.
Always read stickies before asking questions... including the one that says not to ask questions in the general forum
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit

rootSU said:
This is all covered in the "ota helpdesk" thread stuck at the top of this general forum.
Click to expand...
Click to collapse
The Helpdesk thread must have been un-stickied in the last few days, because I saw you give this answer several times but had to go digging to find it myself.
There's conflicting information out there -- I've spent hours reading posts here but have had some places tell me that I *can't* get an OTA update when rooted, while some tell me that I *can*. I think the nuance is the problem. It sounds like OTA will work, but only if you haven't changed any system files, and also will wipe out your root and custom recovery. Still, I'd rather have to re-root than to manually update.
The best solution is the one that gets me from "rooted, stock version X" to "rooted, stock version X+1" in the least amount of time!

Ghengis042 said:
...I'd rather have to re-root than to manually update...
Click to expand...
Click to collapse
Actually, flashing the stock image yourself is quite easy and can be less problematic.

PhilipTD said:
Actually, flashing the stock image yourself is quite easy and can be less problematic.
Click to expand...
Click to collapse
Good to know. So, I'm getting an N5 in the next week or two (shipped today, but has to be forwarded overseas by a relative ) and want it rooted, stock. Best bet is to OTA update (if it doesn't ship with 4.4.2) -> unlock bootloader -> install CWM -> install SuperSU? Then, next time Google issues an update, download the OTA ZIP and install it from CWM?
Won't that remove CWM and root, like I was saying? Or is there some version of the "stock image" I can download that doesn't overwrite recovery and/or the su binary/APK?

What you've said is correct, and then after an OTA just reflash CWM* and then re-root it - takes all of 30 seconds if you have the image on your computer
*CWM might give you the option of removing the stock recovery reflash script before rebooting, so say yes to it if it mentions it

Ghengis042 said:
... Or is there some version of the "stock image" I can download that doesn't overwrite recovery and/or the su binary/APK?
Click to expand...
Click to collapse
Take a look here.

PhilipTD said:
Actually, flashing the stock image yourself is quite easy and can be less problematic.
Click to expand...
Click to collapse
I am new to Android, so i would like to ask more before root, that would be less problem
BTW thanks for everyone's reply

[Q]DNA unlocking & rooting method

Hi. I am a noob at rooting. Which of your unlocking and rooting method should I use for a Verizon HTC DNA that is updated to its current version of Kit-Kat? Firewater? I just did a factory reset for a fresh start. I have not installed any "user apps." Basically it is cleaned. This is my first at rooting a phone, but I have rooted Kindle Fire once. I do know about the warranty. I would also like to know a method to unroot as well incase I want to go back for any reason. Need help as soon as possible.

crazyleopard77 said:
Hi. I am a noob at rooting. Which of your unlocking and rooting method should I use for a Verizon HTC DNA that is updated to its current version of Kit-Kat? Firewater? I just did a factory reset for a fresh start. I have not installed any "user apps." Basically it is cleaned. This is my first at rooting a phone, but I have rooted Kindle Fire once. I do know about the warranty. I would also like to know a method to unroot as well incase I want to go back for any reason. Need help as soon as possible.
Click to expand...
Click to collapse
Did you unlock the bootloader via HTCdev.com already?

LS.xD said:
Did you unlock the bootloader via HTCdev.com already?
Click to expand...
Click to collapse
No, I have not started on anything because not sure what the first step is. Sorry for my question. I have been looking online, including youtube for the answer. I most likely find how-tos that are outdated and wasn't sure if they would still work.

crazyleopard77 said:
No, I have not started on anything because not sure what the first step is. Sorry for my question. I have been looking online, including youtube for the answer. I most likely find how-tos that are outdated and wasn't sure if they would still work.
Click to expand...
Click to collapse
GO HERE
press "unlock bootloader" and follow the instruction

press "unlock bootloader" and follow the instruction [/QUOTE]
Ok thank you. I am assuming that is my first step. Do I need to set up or install anything on laptop before i press unlock bootloader? Do I need to come back to get more of your directions or is that it?

crazyleopard77 said:
press "unlock bootloader" and follow the instruction
Click to expand...
Click to collapse
Unlocking the bootloader is fully guided on HTCdev.com. You will need more steps like installing a custom recovery and a superuser app using the custom recovery. If your not sure about what to do, you can use Teamviewer and i will perform unlocking / rooting for you
This toolkit may also help you WinDroid HTC Toolkit

LS.xD said:
Unlocking the bootloader is fully guided on HTCdev.com. You will need more steps like installing a custom recovery and a superuser app using the custom recovery. If your not sure about what to do, you can use Teamviewer and i will perform unlocking / rooting for you
This toolkit may also help you WinDroid HTC Toolkit
Click to expand...
Click to collapse
ok. i had just installed teamview both on phone and pc.

crazyleopard77 said:
ok. i had just installed teamview both on phone and pc. my id there is xxxxpassword isxxx name is Stephanie.
Click to expand...
Click to collapse
DONT POST ID+PASS PUBLIC!!!!!!!!!!!!!!!!!!! Set new password and send it via PM !!!!!!!!!!!!!!!!!!!!!!
Are you crazy????

Don't Re-Lock Your Bootloader

As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.

Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs

avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP

avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.

Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs

Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"

That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse

Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.

ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.

tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:

ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.

I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.

Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery

I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse

Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.

WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.

WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.

Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.

WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.

tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .