Question
Looking at Google developer page original images for 2013 Nexus 7 WiFi are labeled with the model =razor
Cyanogen calls the same model above flo
Which one is right?
Sent from my SAMSUNG-SGH-I337 using xda premium
I think razor is the ROM designation and FLO is the designation for the hardware.
TaintedByte said:
Q: What is the name of this Nexus 7? I keep hearing all these different names! Thanks to zaclimon.
A: Our device is named after a previous one with the same name, thus confusion will arise. The official name for it is Nexus 7 (2013), this is what Google calls it. Amazon brought a new name: Nexus 7 FHD presumably after "full high definition". Furthermore, there are two other names that refer to our device, Flo (this thread's title) refers to the board of the device (hardware). While Razor is the device's codename.
Click to expand...
Click to collapse
In other words, you see Flo in CyanogenMod because that build was built for the Nexus 7 Hardware. You see Razor because that's Google's official device ROM.
Related
https://developers.google.com/android/nexus/drivers#razor
what is codename for our new nexus 7 ?
Razor or Flo ?
sambistt said:
https://developers.google.com/android/nexus/drivers#razor
what is codename for our new nexus 7 ?
Razor or Flo ?
Click to expand...
Click to collapse
Droid-Life gave a great run-down of this:
"If you are confused by the name “razor” since you have also seen us refer to the new Nexus 7 as “flo,” I’ll try to explain. Each Nexus device is essentially given two names: a device name and a product name. Take for example the Galaxy Nexus LTE. You’ll see it often referred to as “toro” which is the device name, but in the software updates for it, it is referred to as “mysid” aka the product name. So for the new Nexus 7, we have a product name of “razor” and a device name of “flo.” Product names are typically listed with factory images since they are tied to the software of the device."
thanks!
we have factory images for nexus 7 fhd - this is great
Flo is short for Flounder I guess since all are based off types of fish.
I think everyone settled on Nexus 7 HD.
Lots of sites call it FHD, which is inaccurate seeing how that describes a specific resolution that is not what the new Nexus 7 uses.
I typically call it the N7HD. I have a huge thread on this over in General.
Sent from my Nexus 7 using xda premium
sambistt said:
https://developers.google.com/android/nexus/drivers#razor
what is codename for our new nexus 7 ?
Razor or Flo ?
Click to expand...
Click to collapse
Already posted, it will be good to searched before to post
If you need more info read this post from @TheManii (Wiki Admin / Recognized Contributor)
I didnt bother reading the middle pages, but:
Wifi Model:
Marketing name: Nexus 7
Play market url: Nexus 7 (2013)
Name in help pages: Nexus 7 (2013)
Rom branch name: Razor
Device name: Flo
Board name: Flo
Motherboard model number: ME371K
Device model number: K008
LTE Model differences:
Marketing name: Nexus 7
Play market url: unknown
name in help pages: Nexus 7 (2013) LTE
Rom branch name: Unknown
Device name: Deb
Board Name: unknown
Motherboard model number: ME371KL
Device model number: unknown
These will be revealed when the 2013 N7 LTE is actually released
--------------------------------------------------------------------------------------------------
Goog refers to it as the Nexus 7 (2013) and Nexus 7 (2013) LTE in their help pages.
For the purposes of the xda wiki pages, I refer to them in the same manner.
Calling it Nexus razor is definitely "wrong" as noone refers to the N4 as the nexus occam.
For the GN, the rom branch name is only brought up when it's relevent: usually when otas are involved.
Calling it flo would be "correct" in the context of roms though, as roms usually have the device name in their filenames to refer to what device it's for.
Like how grouper/tilapia roms shouldn't be assumed to be compatible unless the author states so, deb and flo roms shouldn't either.
You can call it whatever the hell you want as noone's going to stop you, as long as it's unambiguous.
It doesnt necessarily mean that you're using the "correct" name though.
--------------------------------------------------------------------------------------------------
Some background info:
Some devices have multiple rom branches for a device:
Galaxy Nexus GSM:
rom branch name:
Takju: models bought via play in the us
Yakju: models bought everywhere else
YakjuXX: models supported by samsung directly and not google
All GN's have the same board name, but different device names:
Board name: tuna
device name:
GSM GN: maguro
vzw GN: toro
spr GN: toroplus
Some devices have similar roms, but not identical ones:
Nexus 7 wifi:
device name: grouper
rom branch name: nakasi
nexus 7 3g
device name: tilapia
rom branch name: nakasig
Click to expand...
Click to collapse
I think that is clearly explicit
Flo is the device specific codename name (N7 2013 WiFi). Razor is the codename for the board.
Sent from my Nexus 7 (2013).
MikeyCriggz said:
Flo is the device specific codename name (N7 2013 WiFi). Razor is the codename for the board.
Sent from my Nexus 7 (2013).
Click to expand...
Click to collapse
Actually it's quite the inverse but philos resumed it all. XD
Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
deleted
HELP I'm not sure if I'm in the right place to get the right answer
My Google Nexus Tablet has robot laying down with triangle shape and red exclamation mark over his open chest. Words below robot say " no command" I tried to do the data reset several times.. upset I can't get my tablet to work. Any suggestions are welcome.
ima1 said:
My Google Nexus Tablet has robot laying down with triangle shape and red exclamation mark over his open chest. Words below robot say " no command" I tried to do the data reset several times.. upset I can't get my tablet to work. Any suggestions are welcome.
Click to expand...
Click to collapse
Wrong thread but if you see
Code:
EXT4-fs (mmcblk0p30): VFS: Can't find ext4 filesystem
in view recovery logs then post again in this thread.
I don't suppose anybody on here will know if there's likely to ever be a port of Sailfish OS for the flo?
I've read that Jolla has made a port for the nexus 4 and that they're working on ports for the nexus 5 and nexus 7 but I'm not sure if that's the 2012 or 2013 model.
Anybody know anything?
killakilna said:
I don't suppose anybody on here will know if there's likely to ever be a port of Sailfish OS for the flo?
I've read that Jolla has made a port for the nexus 4 and that they're working on ports for the nexus 5 and nexus 7 but I'm not sure if that's the 2012 or 2013 model.
Anybody know anything?
Click to expand...
Click to collapse
Well, the HADK is out now, so we can start working on that ourselves. I wonder if we'll be able to use it with MultiROM...
UPDATE: Tried building but realized there isn't a cm_10.1 branch for flo because it was released with 4.3 (10.2). I'm not sure if it's okay to fallback to 10.2 or if I might run into more errors later on but I'll see what happens.
Do you believe that the thread of oppo find 7 should separated in two: oppo find 7 and oppo find 7a? Do you believe that there will be need for this when the roms start to come out?
purplexed9 said:
Do you believe that the thread of oppo find 7 should separated in two: oppo find 7 and oppo find 7a? Do you believe that there will be need for this when the roms start to come out?
Click to expand...
Click to collapse
Makes sense to me.
I don't think there will be a need. It is sounding like the same rom will work for both and they come with the same software. Outside of screen calibration and impressions there is nothing much to make into a separate section as what applies to one applies to all. Unless of course future QHD owners aren't wanting to soil themselves by associating with the unfortunate vanilla 7A owners, that certainly calls for a new section. lol
No way will the same ROM work with all 4 versions of the F7. Just between the 7/7A there's 2 different processors. Maybe that could be settled with just a different kernel but I doubt it.
People are already using the same rom on two variants of the 7A and their tech guru is claiming the same rom with an auto detect could work for both the 7 and 7A. Tech guru is far from a word that would be used to describe me however. I'm sure entropy or one of the other guys will come along and set us (me) straight. Were it to be the case that different roms were required it would probably be a good idea to split the development section into two although that doesn't seem to be proof against people installing the wrong rom version as I've seen on many other phones.
About 90% of Oppo's deltas between 7 and 7A are handled at runtime by the kernel using a PCB version register.
Oppo's naming conventions are a bit confusing:
Find 7A = find7 (kernel defconfig)
Find 7 = find7wx (kernel defconfig) = Find 7S (kernel comments)
Find 7 OnePlus Edition = find7op (kernel source) = OnePlus One (what OnePlus calls it)
There are a few small things in the kernel that are handled by defconfigs instead of runtime - none of us have looked to see if these can be all switched to runtime because we don't have FHD 7 units yet.
Ideally there will be a common build. Worst case there will be a defconfig delta and 99% of the code will be common and (probably) the end result will be a common thread for omni (I hope...) Kind of like if I bothered to create a thread for galaxys2-family devices for Omni, I'd probably just create a unified one for I9100/I777/N7000 at this point. (maybe not N7000 but def. I777/I9100)
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Hellscythe said:
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Click to expand...
Click to collapse
Still, create a different f7 variant under the main f7 thread. As I have written, separate the devices of the thread, not create a completely new thread.
Sent from my P6-U06 using xda app-developers app
Hellscythe said:
No. For the same reason why all the different Galaxy S4 variants are kept under the Galaxy S4 thread.
Click to expand...
Click to collapse
Um what? Every single carrier variant of the GS4 was given its own entire forum (not just an Exynos/Qcom split). (in retrospect probably a bad idea, but not surprising given Samsung's prior track record)
Also, "thread" is probably not the appropriate term for what the OP was asking.
Entropy512 said:
Find 7A = find7 (kernel defconfig)
Find 7 = find7wx (kernel defconfig) = Find 7S (kernel comments)
Find 7 OnePlus Edition = find7op (kernel source) = OnePlus One (what OnePlus calls it)
777/I9100)
Click to expand...
Click to collapse
Is the hardware in the OnePlus One and the Find 7 really that similar? Or was this said partly tongue-in-cheek?
bobbarker2 said:
Is the hardware in the OnePlus One and the Find 7 really that similar? Or was this said partly tongue-in-cheek?
Click to expand...
Click to collapse
It is.
Between OnePlus' relation with Oppo, the documented specifications, etc. - Pretty much every difference in the defconfigs/source for the two devices corresponds to the few documented differences in specs between the two devices.
The OnePlus One is a Find 7a with the following tweaks:
1) Nonremovable battery (kernel change: battery authentication disabled)
2) A PN65T instead of PN544 (kernel change: PN65 support in the NFC driver. The PN65 is pointless now that Google has sunsetted hardware SE support)
3) RGB LED instead of the blue-only Skyline (kernel change: different LED driver)
4) Left/right "mirror" reversal. (power button on right of OnePlus, left for F7a, etc.) Kernel change: none
5) MSM8974AC instead of MSM8974AB (kernel change: none, handled automatically at runtime)
farfromovin said:
No way will the same ROM work with all 4 versions of the F7. Just between the 7/7A there's 2 different processors. Maybe that could be settled with just a different kernel but I doubt it.
Click to expand...
Click to collapse
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
krabman said:
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
Click to expand...
Click to collapse
I saw that and stand corrected. You gotta cut me a little slack, coming from a Samsung background where every single variant, along with basebands, cause huge issues. Glad to see it done simple from Oppo.
krabman said:
Addel (product manager for oppo) just confirmed that the same 2.0 beta download can be installed on both 7 and 7a phones. It would seem that roms that don't include the baseband can be installed across the platform.
Click to expand...
Click to collapse
could also be the software baseband compatible with both versions of the hardware modem
(nexus 5 US and int'l phones use the same software modem, though supporting different LTE bands)
http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095
Entropy512 said:
It is.
Between OnePlus' relation with Oppo, the documented specifications, etc. - Pretty much every difference in the defconfigs/source for the two devices corresponds to the few documented differences in specs between the two devices.
The OnePlus One is a Find 7a with the following tweaks:
1) Nonremovable battery (kernel change: battery authentication disabled)
2) A PN65T instead of PN544 (kernel change: PN65 support in the NFC driver. The PN65 is pointless now that Google has sunsetted hardware SE support)
3) RGB LED instead of the blue-only Skyline (kernel change: different LED driver)
4) Left/right "mirror" reversal. (power button on right of OnePlus, left for F7a, etc.) Kernel change: none
5) MSM8974AC instead of MSM8974AB (kernel change: none, handled automatically at runtime)
Click to expand...
Click to collapse
So after things get rolling: Find7, Find7a, and OPO owners should be able to flash roms for all devices, followed up by the correct kernel?
Yes. That's pretty much the expected outcome.
Sent from my X9006 using Tapatalk
farfromovin said:
So after things get rolling: Find7, Find7a, and OPO owners should be able to flash roms for all devices, followed up by the correct kernel?
Click to expand...
Click to collapse
If we can't do a unified kernel, we'll be doing separate complete builds for both. But you could expect in that case we'll have something similar to the Samsung Galaxy S2 family, where the I9100, I777, and N7000 all inherit a "common" device tree that contains 95%+ of the stuff for each device.
Hey guys, I just need your help.
I got this link to unlock and root my Nexus 7 2013,http://forum.xda-developers.com/show....php?t=2381698. so basically my doubts are is this for both wifi and LTE versions?is this limited to OS or I can even do it for 4.4..4?Please help me out.
The quick answer is: easy to find.
So, the link you meant to post in your OP was: http://forum.xda-developers.com/showthread.php?t=2381698
In that thread it tells you where to download the toolkit (from the awesome WugFresh): http://www.wugfresh.com/nrt/
On that very page, it has a device compatibility list.
Supported Nexus devices:
· Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
· Galaxy Nexus: CDMA/LTE Verizon Models
· Galaxy Nexus: CDMA/LTE Sprint Models
· Nexus S: Worldwide, i9020t and i9023 Models
· Nexus S: 850MHz, i9020a Models
· Nexus S: Korea, m200 Models
· Nexus S 4G: d720 Models
· Nexus 7: Asus Tablet
· Nexus 7 3G: Asus Tablet
· Nexus 7 v2 (2013): Asus Tablet
· Nexus 7 v2 (2013) LTE: Asus Tablet
· Nexus 10: Samsung Tablet
· Nexus 4: LG Phone
· Nexus 5: LG Phone
However, if your reading comprehension and attention span is as low as it seems from not finding that information in the link you (tried) to post, and your level of skill with computers has you posting invalid links, and every thread you've ever made has been an easily answered with a search question - maybe rooting devices isn't for you anyway?
---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------
Or is that a bit rude?
gwon said:
The quick answer is: easy to find.
So, the link you meant to post in your OP was: http://forum.xda-developers.com/showthread.php?t=2381698
In that thread it tells you where to download the toolkit (from the awesome WugFresh): http://www.wugfresh.com/nrt/
On that very page, it has a device compatibility list.
Supported Nexus devices:
· Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
· Galaxy Nexus: CDMA/LTE Verizon Models
· Galaxy Nexus: CDMA/LTE Sprint Models
· Nexus S: Worldwide, i9020t and i9023 Models
· Nexus S: 850MHz, i9020a Models
· Nexus S: Korea, m200 Models
· Nexus S 4G: d720 Models
· Nexus 7: Asus Tablet
· Nexus 7 3G: Asus Tablet
· Nexus 7 v2 (2013): Asus Tablet
· Nexus 7 v2 (2013) LTE: Asus Tablet
· Nexus 10: Samsung Tablet
· Nexus 4: LG Phone
· Nexus 5: LG Phone
However, if your reading comprehension and attention span is as low as it seems from not finding that information in the link you (tried) to post, and your level of skill with computers has you posting invalid links, and every thread you've ever made has been an easily answered with a search question - maybe rooting devices isn't for you anyway?
---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------
Or is that a bit rude?
Click to expand...
Click to collapse
Well yeah thats a bit rude and I m hurt by that.Yeah I did read his list of compatible devices but there is no mention of 4.4.4 support being added for Nexus 7 LTE.Basically While using wugfresh method I could not root nor flash TWRP since while clicking on Root it said the link to download TWRP does not exist.I have rooted a couple of devices before but I m having a tough time finding the right link this time.
I do have other links but there is no mention whether its for wifi or LTE so this is causing quite a lot of confusion.
I have bootloader flashed with Wugfresh method but I wanna root and flash TWRP now, please help me out if you are good at this?
gwon said:
The quick answer is: easy to find.
So, the link you meant to post in your OP was: http://forum.xda-developers.com/showthread.php?t=2381698
In that thread it tells you where to download the toolkit (from the awesome WugFresh): http://www.wugfresh.com/nrt/
On that very page, it has a device compatibility list.
Supported Nexus devices:
· Galaxy Nexus: GSM Models (both yakju and non-yakju builds)
· Galaxy Nexus: CDMA/LTE Verizon Models
· Galaxy Nexus: CDMA/LTE Sprint Models
· Nexus S: Worldwide, i9020t and i9023 Models
· Nexus S: 850MHz, i9020a Models
· Nexus S: Korea, m200 Models
· Nexus S 4G: d720 Models
· Nexus 7: Asus Tablet
· Nexus 7 3G: Asus Tablet
· Nexus 7 v2 (2013): Asus Tablet
· Nexus 7 v2 (2013) LTE: Asus Tablet
· Nexus 10: Samsung Tablet
· Nexus 4: LG Phone
· Nexus 5: LG Phone
However, if your reading comprehension and attention span is as low as it seems from not finding that information in the link you (tried) to post, and your level of skill with computers has you posting invalid links, and every thread you've ever made has been an easily answered with a search question - maybe rooting devices isn't for you anyway?
---------- Post added at 08:20 AM ---------- Previous post was at 08:19 AM ----------
Or is that a bit rude?
Click to expand...
Click to collapse
here is another link but he says its for 4.3, can it still be put on 4.4.3 or 4? https://www.youtube.com/watch?v=H0Yo7rEoLpE
Thank you friend!
Why can't you just use some app like Rashr or Rom manager?
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Do they use without rooting in the first place?
Sent from my iPhone using Tapatalk
nsnarayan10 said:
Do they use without rooting in the first place?
Click to expand...
Click to collapse
If you can't figure out how to root using a toolkit, you should hold off on rooting until you have a much better understanding of how your device works.
I suggest doing A LOT of reading in the general and q&a forums before you attempt doing anything. Good luck.
Why not use towelroot?
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
I haven't heard of towel root but I wil surely check it out and get back to you.thanks
Sent from my iPhone using Tapatalk
A Nexus is a Nexus is a Nexus. It's the same process to unlock the bootloader and root on all of them.
The only difference between the WiFi and LTE versions of our tablet is a baseband chip and the software to support it. If you don't have data on your LTE Nexus, you can flash a WiFi-only ROM and it would work just like the WiFi version.
nhizzat said:
A Nexus is a Nexus is a Nexus. It's the same process to unlock the bootloader and root on all of them.
The only difference between the WiFi and LTE versions of our tablet is a baseband chip and the software to support it. If you don't have data on your LTE Nexus, you can flash a WiFi-only ROM and it would work just like the WiFi version.
Click to expand...
Click to collapse
oh you mean to say we can use the same root files for both wifi and LTE versions and it wont brick the device?but we should not use files that are made for 4.3 for 4.4 right?
Please get back to me on this and my doubt would almost be cleared!
The root file itself (SuperSU.zip) is universal. I've used it to root my Xoom WiFi, SGS3, Note 2, Nexus 7 LTE, and Moto X. The bootloader unlock process is the same regardless of the Nexus device, what's specific is the recovery and rom. However, like I said before, a Nexus 7 LTE will work just fine with a Nexus 7 WiFi rom as long as you're not expecting to have LTE capability.
Just to reconfirm u r saying with the same root file we can root any damn smartphone in the world and it's the recovery file like CWM and TWRP alongside custom rom that are compatibility based right?
Coming to last sentence what do you mean 'a Nexus 7 LTE will work just fine with a Nexus 7 WiFi rom as long as you're not expecting to have LTE capability'.
Thank you so much and I must say your help is serving very well.
Sent from my iPhone using Tapatalk
nsnarayan10 said:
Just to reconfirm u r saying with the same root file we can root any damn smartphone in the world and it's the recovery file like CWM and TWRP alongside custom rom that are compatibility based right?
Coming to last sentence what do you mean 'a Nexus 7 LTE will work just fine with a Nexus 7 WiFi rom as long as you're not expecting to have LTE capability'.
Thank you so much and I must say your help is serving very well.
Click to expand...
Click to collapse
Rooting methods vary from Android device to Android device, but SuperSU will work on most any Android version. Think of it this way: your N7 needs its own ROM, right? The ROM has particular things for display drivers, audio, and so on. But an app will work on your N7 like it could on a Samsung or HTC.
Regarding LTE, he simply means that if you flash a custom ROM that does not support LTE, it will have all features except LTE.
Nexus 7 (2013, Wi-Fi) shows up as 2012 model with 720p resolution after Android 6.0.1 update. Tried a factory reset and clean flash to AOSP 6.0.1 (MOB30X).
Why is it showing up as a 2012 model and limited to 720p?
For the factory images, it seems Android 4.3 (JSS15R) has the best performance with this Nexus 7 (2013) Wi-Fi, followed by: 4.4.3 (KTU84L) and if you need features: 4.4.4 (KTU84P)
encore2097 said:
Nexus 7 (2013, Wi-Fi) shows up as 2012 model with 720p resolution after Android 6.0.1 update...
Click to expand...
Click to collapse
Same device as yours, same OS version, which I've always kept completely current. My Nexus shows as 1920x1080, with fingerprint google/razor/flo:6.0.1/MOB30X/...
never seen a status like yours. I'd ask you if you accidentally installed the 2012 firmware by mistake, but I know they never made 6.0 or higher for the nakasi.
good luck ????
Sent from my Nexus 7 using XDA Labs
This is enraging! I have literally spent the entire day, from 3am this morning, restoring to stock and using the OTA update just to get me to this fouled update that demotes the Nexus to last year's model!!! :crying: