Related
Is it possible to root the ASUS Nexus 7 without unlocking the bootloader? It so I keep my warranty and still use root only apps. I NEED root for MOGA Universal Driver for emulators. The reason I got the Nexus 7 is for a portable emulation station. Help?
Edit: Bootloader not Boatloader. SORRY CHANGED!
Pretty sure rooting will void the warranty anyways, you just don't get a warning about it
Sent from my Nexus 7(2013) running paranoid android FTW
tom_callahan said:
Pretty sure rooting will void the warranty anyways, you just don't get a warning about it
Sent from my Nexus 7(2013) running paranoid android FTW
Click to expand...
Click to collapse
No unlocking the bootloader does.
IMO even if there was an exploit for rooting without unlocked bootloader, I would go ahead and unlock the bootloader.
1) if you later decide you need to do something that requires unlocked bootloader, the process will force a wipe data/factory reset, causing you to need to backup/restore
2) if you mess something else, having an unlocked bootloader gives you more flexibility for restore options
3) you can always restore to stock and lock the bootloader later on. There is no forced wipe data/factory reset locking the bootloader (though if you lock it, I would highly suggest you be on stock everything)
sfhub said:
IMO even if there was an exploit for rooting without unlocked bootloader, I would go ahead and unlock the bootloader.
1) if you later decide you need to do something that requires unlocked bootloader, the process will force a wipe data/factory reset, causing you to need to backup/restore
2) if you mess something else, having an unlocked bootloader gives you more flexibility for restore options
3) you can always restore to stock and lock the bootloader later on. There is no forced wipe data/factory reset locking the bootloader (though if you lock it, I would highly suggest you be on stock everything)
Click to expand...
Click to collapse
I want to unlock my bootloader but I read that the Nexus 7 ASUS has a decent chance of defect. So I unlock my bootloader, root and 3 weeks later my wifi stop working. So that is what I worry about. I did already root and unlock my other Nexus 7 ASUS (I got the 16 GB thinking it had an SD card slot. But returning this for the 32 GB) so it's an easy task but it's the defect that's bringing the task down. I rooted ALLLLL my other devices with ZERO problems. The original Nexus 7 was rooted without bootloader unlock. So any chance of that with the ASUS? I MUST root to use my gamepad so I will unlock my bootloader if I have to.
Haxzor11 said:
No unlocking the bootloader does.
Click to expand...
Click to collapse
If you have to send the device in for any repairs, or anyone even takes a glance at the device, the fact that it is rooted will be most likely be evidence enough for denying any kind of warranty work. From a different site:
Q. Will this void my warranty? And can I brick my device?
A. Not necessarily. In the strictest sense, unlocking and rooting will make your warranty voidable at the discretion of Google / LG. Meaning they can choose to not honor your warranty if you try to claim damages caused by your hacking ways. In practice you will often be able to receive appropriate warranty service a defective device even if you have unlocked / rooted it, but I cannot guarantee it for you. A Nexus device is almost impossible to actually "brick". Sometimes you may do something foolish and cause a "softbrick" which is actually very easily fixable. Check out my Factory Image Restore Guide to learn how to fastboot the factory images to your device no matter what you did to it and return it to brand new, out of the box condition. The same procedure can be used if you need to claim warranty service for an actual defective device and want to return it to stock before sending it in for repair/replacement.
Click to expand...
Click to collapse
tom_callahan said:
If you have to send the device in for any repairs, or anyone even takes a glance at the device, the fact that it is rooted will be most likely be evidence enough for denying any kind of warranty work. From a different site:
Click to expand...
Click to collapse
Thanks man! Rep +1! Locking the thread!
Can't find out to lock this thread. Can a mod do that for me?
tom_callahan said:
If you have to send the device in for any repairs, or anyone even takes a glance at the device, the fact that it is rooted will be most likely be evidence enough for denying any kind of warranty work. From a different site:
Click to expand...
Click to collapse
See Magnusson-Moss Act Chapter 50 of United States Code Section 2304 "Waiver of standards"
They can't void your warranty just by you installing aftermarket software modifications. They actually need to prove your changes caused the warranty issue you are asking to be repaired.
I'm sure there are cases where you can install software that ends up damaging the hardware, but installing root is very very unlikely to (by itself) have caused any hardware damage.
This act (ie law) was originally put in place so car manufacturers couldn't void your warranty for using aftermarket parts (like windshield wipers, oil, etcc) They can, however, refuse your warranty if they show your aftermarket parts caused the issue in question.
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
Haxzor11 said:
Can't find out to lock this thread. Can a mod do that for me?
Click to expand...
Click to collapse
fastboot thread lock
sfhub said:
See Magnusson-Moss Act Chapter 50 of United States Code Section 2304 "Waiver of standards"
They can't void your warranty just by you installing aftermarket software modifications. They actually need to prove your changes caused the warranty issue you are asking to be repaired.
I'm sure there are cases where you can install software that ends up damaging the hardware, but installing root is very very unlikely to (by itself) have caused any hardware damage.
This act (ie law) was originally put in place so car manufacturers couldn't void your warranty for using aftermarket parts (like windshield wipers, oil, etcc) They can, however, refuse your warranty if they show your aftermarket parts caused the issue in question.
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
fastboot thread lock
Click to expand...
Click to collapse
Wow, learnt something new. Dude! You should be an attureny (F*kc spealling). Thanks! I will use this to my advantage!
sfhub said:
See Magnusson-Moss Act Chapter 50 of United States Code Section 2304 "Waiver of standards"
They can't void your warranty just by you installing aftermarket software modifications. They actually need to prove your changes caused the warranty issue you are asking to be repaired.
I'm sure there are cases where you can install software that ends up damaging the hardware, but installing root is very very unlikely to (by itself) have caused any hardware damage.
This act (ie law) was originally put in place so car manufacturers couldn't void your warranty for using aftermarket parts (like windshield wipers, oil, etcc) They can, however, refuse your warranty if they show your aftermarket parts caused the issue in question.
Click to expand...
Click to collapse
That's good for parts, not so much for service repairs, re-flashes, etc. See below from Wikipedia, I'm not going to spend too much time digging through to quote the exact sections from Magnusson-Moss Act.
"Although the Act covers warranties on repair or replacement parts in consumer products, warranties on services for repairs are not covered."
I've been curious about how the Bootloader is locked down and why it's so difficult/impossible to unlock. How does the mfg get the initial load onto the device when it's manufactured?
I read that this bootloader has some 2048 encryption and that it's impossible to crack. However, I feel like there should be a way to alter the systems firmware from a PC or some kind of connection to the device.
Buchez said:
I've been curious about how the Bootloader is locked down and why it's so difficult/impossible to unlock. How does the mfg get the initial load onto the device when it's manufactured?
I read that this bootloader has some 2048 encryption and that it's impossible to crack. However, I feel like there should be a way to alter the systems firmware from a PC or some kind of connection to the device.
Click to expand...
Click to collapse
The way I read it somewhere is this,
There are efuses built into the processor/motherboard/memory/whatever that the new bootloader "blows" when it is installed. These efuses are necessary pathways for the older bootloaders, hence why they won't install. I don't believe the new bootloader is "locked" per say, it just prevents earlier versions from being installed. There is also a guide somewhere on these forums to recover your device from a brick if you tried to downgrade the bootloader. The new bootloader also doesn't prevent you from installing earlier roms, as long as they are flashable from recovery. Just do not try to use Odin to revert to an earlier rom. That's what causes the bricks, and although there is a procedure to recover, it doesn't sound easy and you end up back on MJB when you're done anyway. Hope that helped.
To whoever wrote the original post I referred to above, my apologies for not giving credit.
Thanks for the reply.
I'm pretty solid with flashing ROM's and such. I have been wondering if it would be possible to use a regular PC and some cool software to reset or reformat the firmware on the system.
Here is a link to the article I was reading:
http://rootzwiki.com/news/att-locks-down-its-galaxy-s-iv-bootloader/
Say I have brand new S3 hardware right off the factory floor. How does that system get injected with the software? When the factories get damaged or "Bricked" units back and refurb them, how do they do that. I know that you can use the SD card trick to jump your phone back to life, but there has to be some master way to do this
Buchez said:
Thanks for the reply.
I'm pretty solid with flashing ROM's and such. I have been wondering if it would be possible to use a regular PC and some cool software to reset or reformat the firmware on the system.
Here is a link to the article I was reading:
http://rootzwiki.com/news/att-locks-down-its-galaxy-s-iv-bootloader/
Say I have brand new S3 hardware right off the factory floor. How does that system get injected with the software? When the factories get damaged or "Bricked" units back and refurb them, how do they do that. I know that you can use the SD card trick to jump your phone back to life, but there has to be some master way to do this
Click to expand...
Click to collapse
I don't have an S3, I'm on the S3 section because my mom broke her phone, so this is speculation based on when I owned an Optimus G:
There are qualcomm tools that can fix a lot more than Odin and Fastboot can, apparently, and manufacturers have access to those. When I had an Atrix 4G someone told me they replace the entire board when eFuses are burned incorrectly, but that sounds really expensive. Anyway, just my 2 cents, i'm out~
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
I agree though, as people are responsible for their actions and so must know the consequences of modding their devices, they should just give another level of access to remove s-off. The warranty is void once you unlock the bootloader anyway.
More info around s-off/NAND/partitions etc:
http://forum.xda-developers.com/showthread.php?t=2619392
gsmyth said:
S-off opens up access to pretty much everything and so allows more control. With that are the risks of totally bricking your device. Staying S-on still gives you some protection from mucking things up and the freedom to flash roms/recoveries/kernels.
Click to expand...
Click to collapse
Now I simply voided my phone's warranty without any use.
Damn it HTC.
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
How did you unlock it? Do you have s-off?
MJ999 said:
Now I simply voided my phone's warranty without any use.
Damn it HTC.
Click to expand...
Click to collapse
Use sunshine to get s-off.
MJ999 said:
The question is pretty much straight
Why does HTC S-On the devices when they allow us to unlock bootloader?
HTC says that the main idea of unlocking bootloader is that you can unleash our own phone.
Why can't they just S-OFF the devices when unlocking the bootloader ?
Can anyone fill me in
Thanks
Click to expand...
Click to collapse
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
This
When you are S-on/BL locked, your carrier (or HTC/Google) is your system administrator. The carriers take this a bit further, and even manage some of your apps. In a lot of ways, you are a guest on the system, even though you "own" it. However, assuming you just want to use it to make phone calls and post to facebook, for most people this is fine. (my wife's phone isn't even rooted)
When you are BL unlocked, you take over some parts of that sysadmin job, and can now replace parts of the operating system and manage your own apps. You can also disable external control of your device by rooting and turning off certain services. However, the truly critical stuff, the stuff that could keep your phone from booting, are outside of your control. You are now no longer a guest, but you aren't exactly an owner either.
When you S-off, you are taking on the job of being the system administrator entirely. You are 100% responsible for what happens to your phone. Your '44, your Magnum rounds, your foot. Be careful.
gsmyth said:
How did you unlock it? Do you have s-off?
Click to expand...
Click to collapse
I unlocked my bootloader.
No, I don't have S-OFF
KJ said:
Use sunshine to get s-off.
Click to expand...
Click to collapse
BerndM14 said:
You can still unleash some of your phone by just unlocking, which is probably why they gave the option. You can still flash a custom recovery, you can still root, you can still flash custom ROMs.
S-OFF you can flash different firmwares, you can resize partitions, you can convert to other models. Why would the majority want these? And by the looks of some of these threads, why would even some of the majority of "flashers" need it? Root + Custom Recovery + Custom ROM should be enough to satisfy most.
S-ON then just protects the phone from more serious changes that might lead to more serious damage if *you* don't know what *you're* doing.
Click to expand...
Click to collapse
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
MJ999 said:
I unlocked my bootloader.
No, I don't have S-OFF
I know about it, but I just want the H/K Mod, I don't think I need to spend 25 bucks for just the mod.
If anything better comes up, I will try sunshine
and during the meantime some devs might also find another way to S-Off hopefully.
But @BerndM14 don't you think HTC should have asked to you choose S-On or S-OFF when unlocking the bootloader or so ?
Click to expand...
Click to collapse
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
BerndM14 said:
You wont' hear any arguments from me about that, I've made a post about that ages ago in which I stated that manufacturers should give you the option to have your phone rooted, unlocked and in HTC's case S-OFF, if it's a warranty issue then why not just a bit more for warranty purposes, but we still need the choice. Will they ever do something like that? I doubt they'll do anything like that any time soon but it would be nice and I've said so a long time ago already.
Especially as far as development on the devices are concerned. I don't see why they would share the Kernel source to allow developers to develop for the phone while at the same time expecting the developer to just hack away at the device in order to get the necessary permissions to develop for the device!
Click to expand...
Click to collapse
Thank the GPL for that last one. Android is essentially a very custom distro of Linux, and the Linux community has already shown that they will go after violators. It's how the Linksys WRT54G became the WIFI router to own. IOW, they release it because they have to, but they don't have to make it easy, or usable.
We have seen with the Samsung and LG devices that it is possible to lock down a device fully such that it won't boot anything that isn't cryptographically signed. They will do as little as necessary to comply with the license, without giving us the ability to actually use that knowledge. After all, what good is kernel source if you don't have a signing key the CPU will accept?
That is the primary reason I chose the M8. It was one of the few flagship phones that is still able to be fully owned.
Do google know that we've unlocked the bootloader? (as Sony do as they ask for email adresses etc and confirm the ulock)
Wondering about warranty.
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
dkryder said:
there is a notice about unlocking of bootloader may violate warranty . thing is it is stated in a somewhat vague manner, it is not like CAUTION YOU ARE ABOUT TO VIOLATE WARRANTY but rather worded like you may be in violation of warranty. anyway, i think it does violate and yes there is most likely a software switch that sets a value in hardware register which can be recovered to determine that the bootloader was unlocked. if you have the least bit of concern do not unlock.
Click to expand...
Click to collapse
Ok thanks.
One last google noob question; does rooting usually need an unlocked bootloader?
On xperia root is more difficult to achieve with a locked bootloader, but can be done, thanks to the devs.
I guess I will read the 6P thread to get a feel for the situation.
Cheers again.
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
dkryder said:
i do not know if it is possible, in practice as far as i know it is necessary to unlock if any modification is wanted. recently it is popular to gain root without mod of /system partition. hopefully that is what is achieved with the pixel c.
edit: never done this but, fastboot boot recovery recovery.img then flash a superuser from temp recovery. however it seems you would still be restricted from mod of /system
in future.
Click to expand...
Click to collapse
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
mskip said:
If you use fastboot boot then you do not need to specify a partition (only if using fasboot flash *partition* image.img).
The device is still very new but im sure a custom recovery will be released soon so an easy root can be achieved.
MArk.
Click to expand...
Click to collapse
I sure hope so. That's one of the only things keeping me from buying it already. It's kind of worrisome that the development forums are almost completely dead (save for the one thread trying to get root without a custom recovery, of course). I guess I'm just spoiled by using only Nexus devices, so having very active development is usually the norm.
well, the thing was only a rumor about sales start up until a report in a german site on 12/5 or so that sales would start 12/8 and then on 12/8 a confirm that at 1pm eastern u.s.a. sales would begin. talk about giving people a decent notice about a device this pixel c was a new low for google. it's almost they decided to sell them as android tablet at last moment instead of tossing in trash as a complete failure as chrome os tablet so, yeah, it will take a while for anyone that has skill to develop this device to ante up the funds and take delivery. if bootloader remains locked and boot temp recovery to flash supersu does that restrict the root in any way? i am just curious about this as my bootloader is unlocked.
Why we still don't have Custom ROMs and kernels for this device after almost six months of his realise?
Is it problem in MTK or..?
MTK hard bricks the device way too much, and to unlock need some special Xiaomi account with some access that only few people has.
I have bricked my RN8 pro once and unbricked it without any special account ... I dont believe thats the reason for lack of custom software...
zOOk1981 said:
I have bricked my RN8 pro once and unbricked it without any special account ... I dont believe thats the reason for lack of custom software...
Click to expand...
Click to collapse
Because you didn't hard bricked your phone, you should read Xiaomi EU statements concerning this phone, way too many people have hard bricked their devices for no apparent reason and only way to unbrick is with authorized account.
alejandromujica.rsm said:
Because you didn't hard bricked your phone, you should read Xiaomi EU statements concerning this phone, way too many people have hard bricked their devices for no apparent reason and only way to unbrick is with authorized account.
Click to expand...
Click to collapse
I believe it's only an issue if you mess up the boot partition image. I've flashed 5 GSI ROMs and then back to stock with no issues. I just avoided touching the boot partition (aside from using magisk). My model is the EU one, but I'm curious if any of the bricked users flashed their boot partition before bricking?
wang1chung said:
I believe it's only an issue if you mess up the boot partition image. I've flashed 5 GSI ROMs and then back to stock with no issues. I just avoided touching the boot partition (aside from using magisk). My model is the EU one, but I'm curious if any of the bricked users flashed their boot partition before bricking?
Click to expand...
Click to collapse
I to believe the same thing. I have flashed from GSI back to stock, and vise versa atleast 3 times. I don't get what the issue is either
wang1chung said:
I believe it's only an issue if you mess up the boot partition image. I've flashed 5 GSI ROMs and then back to stock with no issues. I just avoided touching the boot partition (aside from using magisk). My model is the EU one, but I'm curious if any of the bricked users flashed their boot partition before bricking?
Click to expand...
Click to collapse
bpawnz said:
I to believe the same thing. I have flashed from GSI back to stock, and vise versa atleast 3 times. I don't get what the issue is either
Click to expand...
Click to collapse
Also keep in mind you obviously know what you are doing. I'd say we cannot be hold responsible for people not following precise guides posted by those who knows better, but, between people starting to flash stuff before waiting for their bootloader to be unlocked (yeah waiting 7 days can be frustrating... it is...), those not flashing the right thing at the right place, those forgetting a step or more (or thinking they can shortcut a whole process), there also is something we have to consider.
It seems from the many post I have read in many places, most of the phones which ended bricked were the Chinese model (and when I say bricked I mean bricked. Of half of the people who claim their phone is bricked I am pretty sure they are not even if they think it is).
You probably know like me, people with no skills at all in that particular area or with computer sciences at all, talking to you about, i am going to flash this, remove that, root and put this in system... and they dont know what a bootloader is when you ask them if they unlocked it...
And if anything goes wrong they completely panic (my phone is bricked help me help me!), overreact without any cool, often making things even worse trying to fix something they hasty diagnosed wrongly, ending up in really bricking their phone if it was not already.
As we all know here, people in China are not allowed to do some stuff or using some other stuff (apps etc), they do not live in a democracy out there (do we?), and it would not surprise me State has phones to be made a certain way for local market so people cannot just simply go and flash what they want to do what they want with their phones.
Obviously there kind of always is a way around, but, maybe not as easy and Plug n Play solution.
Some made the choice to order their phones from AliExpress or any Chinese website like they are used to do with their other toys making quite same savings doing so (aren't all of our toys made in China after all?), and end up with more difficult device to work around.
It seems that Eu/Gobal flavors of the phones are somehow more permissive (or people having them know how to read/follow tutorials better, or just more used to flashing with decades of trainings idk). For this Eu/Global market they have to follow some rules and regulations if they want to be approved for that said market (for all I know maybe they also had to put some specific backdoors so our own state services can snoop in?) example the call recording option considered as a privacy issue for people being recorded in EU/USA.
Now about touching the boot partition, from what I have read, it would be more when messing with recovery most phones ended bricked when people try to flash it/make it stick in recovery on some phones flavors (Chinese imo).
If the flavor that was shipped to dev was a Chinese one, no wonder why they got so many problems.
I am not even sure the Global/Eu one was ready to ship at that time.
Anyway just speculating here, because me too I am wondering what's the problem with this phone.
And not really being 'root' of the device you purchase with your own money straight out of the box also is a concept I am having hard time to live with. I cannot understand why we customers tolerate buying a phone for which we do not have an easy recovery option (rescue DVD or whatever, plug in, restore, done) if case anything goes wrong, or just if we want to restart fresh.
It used to be like this before with all phones and computers.
Nowadays it is not anymore most of the time.
Regards.
how bootloader relock in redmi note 8 Pro. i alredy relock bootloader in many redmi devices with this command 'fastboot oem lock " is this will work on redmi note 8 pro.
Big news from telegram
@saucyPotatoNews
Search on telegram for more info
ivo_cajkovac said:
@saucyPotatoNews
Search on telegram for more info
Click to expand...
Click to collapse
this is hoax...this Potato Open Source Program is still develop for Redmi Note 8/8T
check this link
https://miui.blog/redmi-note-8/posp-redmi-note-8-ginkgo
https://forum.xda-developers.com/redmi-note-8/development/rom-potato-sauce-project-t4005789
https://github.com/PotatoProject
This ROM is for Qualcomm Snapdragon chip
Redhexa said:
this is hoax...this Potato Open Source Program is still develop for Redmi Note 8/8T
check this link
https://miui.blog/redmi-note-8/posp-redmi-note-8-ginkgo
https://forum.xda-developers.com/redmi-note-8/development/rom-potato-sauce-project-t4005789
https://github.com/PotatoProject
This ROM is for Qualcomm Snapdragon chip
Click to expand...
Click to collapse
It is not. I recommend you joining the official telegram group to get all the updates first hand.
Apparently the person posting this is the lead dev of POSP, so I think it is quite a legit claim.
That he is working on begonia is also visible on his github:
https://github.com/AgentFabulous?tab=repositories
Talked to the developer personally ... Stable version should be released in week or two...
Redhexa said:
this is hoax...this Potato Open Source Program is still develop for Redmi Note 8/8T
check this link
https://miui.blog/redmi-note-8/posp-redmi-note-8-ginkgo
https://forum.xda-developers.com/redmi-note-8/development/rom-potato-sauce-project-t4005789
https://github.com/PotatoProject
This ROM is for Qualcomm Snapdragon chip
Click to expand...
Click to collapse
Not a hoax.
EDIT: Add some screenshots
Agent_fabulous said:
Not a hoax.
EDIT: Add some screenshots
Click to expand...
Click to collapse
If so - is there any who has made update in pixel experience? Must be alike on both rom
I'm grateful for the one first custom ROM that we have been waiting for half year ...