Database Develop

Question for developers 2.0>G1?

So the blogger over at 'Android and me' has speculated that older devices will not receive the 2.0 update.
This guy has done this before, he also said 1.6 was too big for the G1 OS partition and of course we all know this was wrong.
I want to know what the dev's think, once all the bull**** is striped and the 2.0 source code is at stock for the G1. How large will it be? And how much room will be left over for downloading apps?
Thank you for your time.

And how much room will be left over for downloading apps?
Click to expand...
Click to collapse
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.

vixsandlee said:
Shouldnt be too much of an issue if you are running apsd.
They already have 2.0 running on G1's, i havent used it myself, but it is running, so I presume it fits.
Click to expand...
Click to collapse
I know, I know... I had 2.0 running for a time and it was great. I used apsd and linux-swap. What i want to know is conclusive evidence that the guy over at Android and me is full of ****.
He always speculates that the G1 will not get updates and is usually wrong. What i am wondering is how large the stock 2.0 for the G1 will be. The Dev's may have an idea.

the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.

Both htc and t-mobile have officially stated that the dream is still getting the 2.0 upgrade. As somebody else said, the point is moot for rooted users because we can always port the newer code to our aging phones, but there's a hitch: the moment htc stops supporting the device, we're on our own.
I've yet to see somebody build the android code for the dream without help from the pre-configurations found in the aosp for dream, and now that the sapphire is officially the adp2, i smell the demise of the dream near.
The biggest enabler of the custom firmware movement was the fact that the dream was also the adp1, so there was a lot of interest on making building the platform easy. We just piggybacked on that.
Take one look at has been accomplished with the hero so far. I still remember the whole "let's make htc give us our hero kernel code" because all thought it would open the door for custom hero firmware. they couldnt have been more wrong. without htc's support, all they got was a fancy linux kernel that they had no idea what to do with, and also discovered how little the kernel had to do with android.
There's now a grand total of two aosp roms for the hero, and they're both so broken that they're really just novelties.
What I'm going at is that once htc drops the dream, people are going to realize knowing linux will only take you so far and you'll have to know android if you plan to get at least a botched android build working on the device.
So eventually, even being rooted will not be enough to ensure continued ability to run the best and latest, unless, ofcourse, we get real devs (again, I'm not claiming to be one myself) in here.
Oh, and.... a bigger android install wont mean less app space... learn to android...
The android system belongs in the 70 mb system partition and, on a factory, official build, doesnt spill into the /data partition where you install your apps. And if you do have root and a2sd, what do you care how big the system is, you can always make your ext bigger, so it should't be a worry for a rooted user.
Really... learn 2 android...

s15274n said:
the guy at androidand me is EXACTLY CORRECT.
What you are failing to see is the guys over there are writing for non-rooted phones. They have said in previous posts that this was a moot point for rooted phones and admitted they were already running the upgraded OS.
Click to expand...
Click to collapse
You know that the guy at Android and Me has been wrong on this exact issue before right?
When 1.6 was still in the pipes he had a pie chart and everything explaining why it was physically impossible for 1.6 to fit on a G1 (non-rooted). Then 1.6 was pushed to everyone....
http://androidandme.com/2009/08/news/t-mobile-g1-owners-dont-expect-any-future-android-updates/
^^

He was using his best guess at the time after speaking with t-mo, htc and the lead developer from google. He also assumed we would get a VERSION of OS 1.6. Everything he stated then seemed logical... don't fault the guy for not predicting the future man.

What it all boils down to is this;
Whether a device will get an update or not has virtually NOTHING to do with the device specifications and/or storage space. There is LOTS of space available on the device, despite what some chicken little's speculate based on a moronic look at the "free space in /system" (which has VERY little meaning). What determines whether a device will get a particular update or not has everything to do with what the MANUFACTURER WANTS TO DO.
In other words, this is *all* in the hands of HTC. Even tmobile has hardly anything to do with this since tmobile themselves don't have the source for the proprietary binaries (which happens to be the stumbling block) -- although tmobile can say "not for ours" if they want, HTC can still build the binaries and/or system image for DREAM/ADP1. Fully in their hands and nobody else's.
Which leads to a couple of options for updates;
1) modify the current state of AOSP to remain compatible with existing HTC binaries,
2) reverse engineer HTC proprietary binaries so they're no longer needed.
I vote for #2. The replicant project seems to have this aim, but I don't know if they are still alive or if they died along with the open android alliance... http://trac.osuosl.org/trac/replicant/wiki

Ubuntu Home Edition

ButterflyCommunity​
Couple of friends and me came to an idea of making our own distribution.Our idea is to make Linux distribution suitable for not so geeky people(eg.older people like your mom or dad,or young people like children in elementray scholl).Thats how we started making Ubuntu Home Edition.Linux distribution based on Ubuntu that everyone can use.Theres no commom unnecesary problems that cause headache to your family.
We made our own update menager that allows them to update specific apps at time they choose.In addition to that UHE has enabled optition to clean it self every week,by "clean" i mean it cleans cache,history etc.
UHE comes preinstalled with all the software they could ever nedd browser,mail client,office client etc.
We think that UHE will be perfect solution for "familiy administrators",they will be able to setup UHE for their familiy,and just foget about it,no worry about av updates,product activations,maintaining computer.
I want to hear you opinion and recomondations as well as critics.
Official website
All the tips post here or send them to our tip email(find it under suppoet section on website),please dont PM for that reason.

Sounds like a good idea. I have family members, mostly older that only want internet and email. Ubuntu with Firefox/Chromium and Thunderbird would be all they need. How does this handle OS and software updates? If its something that can be kept up to date with little computer knowledge then this may be worth it.

Looks like it would be a pretty good idea.

I love the idea of it but your link is broken or it loads up a blank page with one icon on it so I can't really tell you much else about what I think. It's hard to get people to get started with linux but I think it's been getting easier than it used to be thanks to graphical installers. Just make sure to make the installer idiot proof and give it wide compatibility with some extra drivers for all those older people using crazy hardware and I think it'd be great! Keep it open source and offer the source everyone loves that. Uhm.... don't charge money? hehehe

All of my work is opensource,becaouse i belive that opensource is future.And yes there are extra drivers and extra languages build in.

Can I Install WP8 on a WP7 Phone?

is there any way to install wp8 on a wp7 phone?

Really ? Did you do any homework or read any of the blogs about Windows Phone 8 ? I guess not. A key word that you should know is "search" as you would of found your answer.
To answer your question, NO. Window Phone 7 users will get a upgrade to Windows Phone 7.8 and it will give you the new start menu of Windows Phone 8 but, nothing else.

Windows phone 7.8
There will be update to wp7/wp7.5 called wp7.8 and you have same interface than Windows phone 8

kilus said:
is there any way to install wp8 on a wp7 phone?
Click to expand...
Click to collapse
I'm pretty sure we'll be able to put some sort of custom ROM WP8 on a WP7 device.
Other than the secure boot, which should hopefully be easily turned off, I haven't seen anything which would prevent the OS from running on a WP7 device.

DavidinCT said:
Really ? Did you do any homework or read any of the blogs about Windows Phone 8 ? I guess not. A key word that you should know is "search" as you would of found your answer.
Click to expand...
Click to collapse
really? did you do any homework or read any blogs about how to get laid as a nerd? i guess not. a key word you should know is "balls," as you'd require a pair as a real man and help you stop masterbating at online porn, move out your mom's house, and finally get laid at 43 years of age.
hetwo said:
There will be update to wp7/wp7.5 called wp7.8 and you have same interface than Windows phone 8
Click to expand...
Click to collapse
thanks hetwo.
gedmurphy said:
I'm pretty sure we'll be able to put some sort of custom ROM WP8 on a WP7 device.
Other than the secure boot, which should hopefully be easily turned off, I haven't seen anything which would prevent the OS from running on a WP7 device.
Click to expand...
Click to collapse
thank you too.. its good knowing there are some decent intelligent people out there willing to answer questions without having to be a disrespectful troll.

Hey guys,
Firstly please don't get this wp8 forum off to a bad start and keep flaming each other? Respect each other and the rules please :cyclops:
Secondly, from my understanding current hardware specs of wp7 phones are not high enough, do not meet, wp8 requirements so the answer is probably no. The official line is a definate no, wp7 devices, even new ones like lumia 900 will not get wp8 update

Hopefully soon wp8 on WP7 by Custom Rom

timmymarsh said:
Secondly, from my understanding current hardware specs of wp7 phones are not high enough, do not meet, wp8 requirements so the answer is probably no. The official line is a definate no, wp7 devices, even new ones like lumia 900 will not get wp8 update
Click to expand...
Click to collapse
Definitely not via an update, that's clearly been addressed by Microsoft. However existing WP7 hardware is surely powerful enough to run WP8. The single core processor is definitely not a problem, and low end WP8 devices are looking to be lower in specs than current WP7 devices.
I'm no expert in usermode on WP, but I know the NT kernel extremely well, and it's more than capable of running on our hardware.

Some body will hack it
Sent from my Lumia 900 using XDA Windows Phone 7 App

Only problem maybe drivers. It is Microsoft way to release oem from out of warranty obligation to keep an outdated product updated.
Who wants to sell one shirt and that person never buys another because it last too long. I understand wanted to save money. But how can they keep making money if the people that work for them is trying to make something2 years old work off of the mere 500$ the phone is worth. Hey has to make money or they will disappear like farmer jack and circuit city
Sent from my HD7 T9292 using XDA Windows Phone 7 App

kilus said:
really? did you do any homework or read any blogs about how to get laid as a nerd? i guess not. a key word you should know is "balls," as you'd require a pair as a real man and help you stop masterbating at online porn, move out your mom's house, and finally get laid at 43 years of age.
.
Click to expand...
Click to collapse
Hahaha. If you read ANY PLACE on this site, it says to SEARCH before posting.
You must not know how to read. This has been a major topic of discussion over every Windows Phone 7 related site.
It does not take a geek or loser like yourself just to spend 2 min reading before posting a subject that has been posted everywhere.
The new upgrade goes to the NT kernal over the WinCE one. That does take more horsepower than current devices can do. It will have native support for C++ and a lot of other modern tech (NFC and others). The current chipset in current devices will not be able to handle it with reasonable performance. As I understand it.
IF some hacker was to create a rom for a current device, it would not support more than 1/2 of the OS and the performace would not be anything worth using unless they stripped everything out.
It's really questionable if a hacker will be able to get it working on current devices and what type of performance. If you really want to know the changes, it's a little long but, it really shows what it can and will do...
http://channel9.msdn.com/Events/Windows-Phone/Summit
It's the full streaming event, and it's almost 2 hours but, it's impressive and I can see why they went this route.

DavidinCT said:
The new upgrade goes to the NT kernal over the WinCE one. That does take more horsepower than current devices can do.
Click to expand...
Click to collapse
Absolutely not true. The NT kernel will run on seriously low specs without any issues. It'll happily run on an old pentium 233 and 32MB RAM without any notable issues in performance. In fact,WP7 hardware is sufficient to run full blown Windows 7, not just the NT6 kernel (assuming the processor was x86 and not ARMv7)
I don't se drivers being a huge blocker as the number of drivers for NT6 is huge, and even in the worst case scenario any drivers we may be missing can be written.
It'll be interesting to see how quickly someone gets WP8 running on a WP7 device.

gedmurphy said:
Absolutely not true. The NT kernel will run on seriously low specs without any issues. It'll happily run on an old pentium 233 and 32MB RAM without any notable issues in performance. In fact,WP7 hardware is sufficient to run full blown Windows 7, not just the NT6 kernel (assuming the processor was x86 and not ARMv7)
I don't se drivers being a huge blocker as the number of drivers for NT6 is huge, and even in the worst case scenario any drivers we may be missing can be written.
It'll be interesting to see how quickly someone gets WP8 running on a WP7 device.
Click to expand...
Click to collapse
It's a good question. As I got that from a Tweet by someone at MS. As I understand Windows 8 has a updated kernel that they are using on WP8. Not sure on it, as I thought it was the same as you (I'm a 20 year Windows Systems admin, I know the NT kernel COULD run on 286 machines if needed, not sure on the updated one, just going on what I heard).
It might of been the option of forcing users to have not hard reset their phones (like going from 32bit to 64-bit, no upgrade path) and that would cause a big impact on customer reports. As I have understood from watching the whole MS thing on it, it came down to performance problems that ended it before it started. Some chipsets to support the new OS are not on WP7 devices, so it limits the options current users can take advantage of.
It's not just about the devices and the end users , its' about the PR nightmare. Any press is good but, bad press is a whole different story. In a year or 2 no one will even talk about this. Android does this all the time and even Apple did it to their first gen device.
Who knows. Maybe one of the great hackers here or DFT will make it run on a current device. It makes me question it though.
As long as WP7 devices have been out, Not one WM 6.5 devices (not incuding the HD2 as it was used as a test device for MS on WP7 and drivers were leaked) got a WP7 upgrade OR No Android device got WP7 or the other way around. There are plenty of Android devices or even a handful of 6.5 devices that could of run WP7 fine.
The hackers can do only so much but, time will tell, I just wonder IF POSSABLE (with out MS), just how long it would take.
It will be interesting to see tho...
I do know I am about 95% sure I will be buying one on release, just depending on the models on release.

The reason for almost none of the 6.5 devices running WP7 could be that most of the old devices running 6.5 didn´t have the needed display (capacitive and the WP7 resolution) or processor. Take the Toshiba TG01: resistive display and higher resolution.

btw....moved to Q&A:good:

this will be possible atleast for hd7 and focus 1st gen:good:

hackarchive said:
this will be possible atleast for hd7 and focus 1st gen:good:
Click to expand...
Click to collapse
for hd7? i see...

hackarchive said:
this will be possible atleast for hd7 and focus 1st gen:good:
Click to expand...
Click to collapse
Just wondering... Where did you get your info on that ? Your HD7 and focus besides the display and case is almost like every other Windows Phone 7 device (standard hardware across all models).
Even though it has been clearly said by Microsoft that NO 1st or 2nd gen devices will get the update you seem to think the HD7 will.
Maybe it's me but, I'm smelling a little BS here....
Unless Microsoft says that they will be updating or DFT decides to dig in, your not getting a upgrade on any first or 2nd gen device and that includes the HD7 and Focus.

The problem with the kernel is not that it by itself would need that much power to run but rather that they would have to develop loads of drivers for it to work, as they would not be able to use those that already exist for Windows CE.
A bigger problem might be the Bootloader process. The NT Kernel at least on ARM requires an UEFI firmware which is likely to be pretty different from the bootloaders we currently have on our phones.
So the steps would be:
- Develop an UEFI firmware for current WP7 hardware (HSPL needed because it would replace the old bootloader) - including UEFI hardware drivers
- Develop drivers for the chipsets from scratch
- Find out on how many hardware characteristics Microsoft chose to rely that are simply not there on old devices
I'm not saying that it is impossible to do or that it won't ever be done but I guess until it's done almost no one will still be using such an old phone.

RE:
DavidinCT said:
Hahaha. If you read ANY PLACE on this site, it says to SEARCH before posting.
You must not know how to read. This has been a major topic of discussion over every Windows Phone 7 related site.
It does not take a geek or loser like yourself just to spend 2 min reading before posting a subject that has been posted everywhere.
The new upgrade goes to the NT kernal over the WinCE one. That does take more horsepower than current devices can do. It will have native support for C++ and a lot of other modern tech (NFC and others). The current chipset in current devices will not be able to handle it with reasonable performance. As I understand it.
IF some hacker was to create a rom for a current device, it would not support more than 1/2 of the OS and the performace would not be anything worth using unless they stripped everything out.
It's really questionable if a hacker will be able to get it working on current devices and what type of performance. If you really want to know the changes, it's a little long but, it really shows what it can and will do...
http://channel9.msdn.com/Events/Windows-Phone/Summit
It's the full streaming event, and it's almost 2 hours but, it's impressive and I can see why they went this route.
Click to expand...
Click to collapse
Helooo???
Low end WP8 devices will have lower HW specs than some current WP7 devices.
WP8 could run very well on a focus s or HD7 or any other.
There will be custom roms for many current devices, there are many smart guys here that I'm sure will try to do this. Let's hope they will manage to do it.

Wp8 on android device?

Is it possible to run an actual Windows Rom in an android device? I remember hearing about this probably a few years ago with wp7, I could've sworn people had figured it out. I've got an AT&T note and miss Windows, but not enough to permanently switch to a Windows device. Any ideas?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app

Never

nitin88g said:
Never
Click to expand...
Click to collapse
Ignore the genius who says never. It comes down to hardware support. If you had two phones on the market with identical hardware, one running Windows Phone, one running Android, then you might be able to switch the bootloaders and operating systems. WP8 has a new secure boot which I know less about. WP7 didn't, but some of the bootloaders were still locked.
So yes, it's possible, but I don't know of a compatible Android device. The first I'd look at would be the ATIV S and the Galaxy S III, but I expect they're very different. There are a few slightly more complicated options but they're not really worth mentioning because.. developers just aren't interested.
I'm sure you could do it if you were willing to give up the rest of your life for a while. Shame isn't it? You'd think MS would release Windows Phone as a download for existing popular handsets in the same way Canonical is doing for their fledgling OS.

[N960U/U1/W][DISCUSSION][Close to rooting]

Hello Fellow XDA Users!
Some of you might remember me from over the years or maybe just from SamPWND root on the S8/S8+. I have had a number of devices since SamPWND with a few being Sammy's. I have been real busy with life and work but of course every spare time I get has been breaking Samsung devices!
I've found some exploits I never released publicly due to the devices being "unpopular" but figured since I am close now as well as what I have found so far most likely works on most Samsung devices (I've only tested on Tab S4 and N9 from Big Red) that I wouldn't keep this one away from everyone.
With that being said, I do not have FULL root yet but am very close. I wanted to create this thread as I don't have let's of free time these days to hopefully bounce ideas around to achieve our end goal a lot faster.
I am going to spare all the specific details to the masses but will let you know what I got so far. I prefer to collaborate over other applications that are more "real time" if there are any developers that read this then PM me and we can share contact info. If you just want to toss ideas in here then that is ok. I just don't want to have someone potentially take my hard work and claim it as their own before I can achieve root. I have been almost non stop since the N9 was released so you can understand hopefully why I want to be the one to bring root to you all!
With that being said, I will begin telling my story and what I have so far.
Some time last year I was working on another Sammy device after SamPWND as I wanted root of course. I spent weeks and weeks trying to find exploits until I finally did! For this time I wanted to see what Sammy would offer for it as it was a tablet, the XDA forum was deserted etc. They did pay out a 2500$ reward so it was ok.
The reason I bring this up is because the exploit plays a factor here as well. The exploit was a mix of SamPWND and SamFAIL as I used the same rooting script as SamPWND but with a custom partition that wasn't checked for integrity when flashing in ODIN.
On this partition there were some init rc scripts. I noticed these scripts could be executed on combo firmware as root user. This means I could mount the partition in Linux, modify the scripts to my liking, sparse it back up and flash in ODIN. Then I could execute them. Believe it or not, they were executed by entering a simple setprop command in ADB. So from start to finish I simply extracted this partition, modified the scripts to install root as well as packaged the root package in with the image, flash it and then execute an adb command and viola! I felt like a loser it took me so long to find yet was so simple to exploit.
This ties in to where I am at now. I spent months looking through various attack vectors with no luck due to enhanced security not just with Sammy but Android also. So one day last week I decided to take a look at combo firmware again. In no time I found something interesting and then I slapped myself for spending months again when I should have looked at init scripts first.
I found it on my Tab s4 initially but wanted to see if the same file was on my N9 on combo and it was!
The first script runs as system user. For some reason the entire folder it is in is world readable/writable which means there is a script I can modify. This one is not an init script but is a script none the less that runs as system user that I can modify and execute with a simple adb command. Of course we want root, not system so I keep looking.
So I started writing all sorts of scripts/commands and executing it as system user since it's better than running as shell user right? One day I decide I am going to try and change permissions on the entire device. To my surprise it actually changed permissions to ALOT of partitions/files including EFS. I start messing with efs but don't want to break my phone so I settled with backing it up, enabling hidden menu, changing my sales code, enabling factory test mode etc. Etc.
One day I decided to see if I could access the same scripts I used previously. The partition was not readable (perms denied) so initially I thought it was a dead end. Then for some reason I tried to go into the sub-directory where I knew the scripts were and guess what!? The parent directory perms were not changed but its sub directories were! Now I am somewhere I have been before and now I have some scripts that I know are executed by init and as root and how to trigger them.
I spent over a week and all my spare time trying to gain full root but progress is slow moving due to new security. I can make a script that backs up every partition on the device, mounts "most" partitions as rw, dd magisk boot images (of course secure check fail due to locked bl but I had to try lol), create folders and push files to roots etc. Etc. Its basically like having full root but you have to run it in a script for everything you do.
Since we have locked bootloaders, we cannot boot modified boot.img. There's also more security causing me to have issues with system root. One of those issues is the fact that system, vendor and odm partitions cause the kernel to panic instantly as soon as they are mounted.
I managed to force some stuff quickly before the crash but they also have something called "secure write protect" which basically backs out anything you might have written before it reboots. I have tried installing chains systemless root and even tried to install magisk without modifying the boot but I am just getting frustrated and tired.
One thing I am currently trying is a safestrap recovery. The end goal is to try and get a GSI on that is pre rooted. Yes, I also tried to dd a gsi and tried with a file manager... it appears to write but it doesn't. I think there is some security going on as it along with odm and vendor are "protected" partitions.
I can modify rootfs and just about every other partition on the device with ease but haven't successfully gained root via su or magisk etc. Some stuff will cause device to boot with good old custom unlock splash screen and even say custom and custom binary in ODIN. That plus it being project treble certified indicates we shouldn't have any issues using GSI's and more soon as we can get ot nailed down!
So in a nutshell, I now have the ability to do almost anything as root user using init scripts on our locked bootloader devices but we only have a little bit left to go in figuring out how to get su binaries onto the device thanks to sammy and googs enhanced security updates.
Hopefully this gets the convo going and I wanted everyone to know that it's not "impossible" and now seems like a guarantee! Let's get some ideas going in here on this last hurdle! If you are a developer please also PM me as I tend to forget to check xda sometimes plus I like a more real time conversation when it comes to this stuff.
We are almost there!
Donation Link: https://forum.xda-developers.com/donatetome.php?u=3812611

Forgot as a reminder that I can confirm the scripts there on tab s4 and n9 combos.. it's very likely they are present on S9/S9+ also and potentially other devices but they will need to be confirmed once we get to that point.

Was just barely reading up on Samsung defex security.. hope that's not the problem since only fix I can find requires hex patching the boot.img

so i noticed you gave quite a lot of info without going too much into details. i understand that you don't want anyone to steal your ideas and take credit.
would be a shame to get root.
and not get the credit where it is due..
now, that being said, isn't making these statements public open up the door for samsung to notice these possible exploits and patch them up for good? thus rendering all your efforts in vain? As even if the details were kept at a minimum from kangers to use them, the samsung devs can probably read through the lines quite easily.
anyways, hope your effort will bare fruit for as long as it is possible.( samfail lasted what 3 or 4 months? before patches made it too difficult to keep up)
Regards

bober10113 said:
so i noticed you gave quite a lot of info without going too much into details. i understand that you don't want anyone to steal your ideas and take credit.
would be a shame to get root.
and not get the credit where it is due..
now, that being said, isn't making these statements public open up the door for samsung to notice these possible exploits and patch them up for good? thus rendering all your efforts in vain? As even if the details were kept at a minimum from kangers to use them, the samsung devs can probably read through the lines quite easily.
anyways, hope your effort will bare fruit for as long as it is possible.( samfail lasted what 3 or 4 months? before patches made it too difficult to keep up)
Regards
Click to expand...
Click to collapse
I can see where youre coming from but I dont think they can glean exactly what I have as theres are probably hundreds of scripts throughout the system.
Also, this approach is far from new. People have been using init scripts for rooting purposes for many years.
I also tried it with newer firmware and it actually didnt work. So it already requires an older frmware and I expect Sammy will increment bootloaders soon making it unavailable to those who have updated at that poimt in time. I figured best to put out the word on progress now and those can choose to wait or not.
Exploits never last very long. The only way to ensure longevity is to remain on old firmware. There was SamPWND before there was SamFAIL. This could be the perfect time. Unless I am the only one working on this device there will be other exploits to be found.
With that being said, only you have posted all day and no devs have reached out to join in the fun so at this rate by the time full root is achieved it most likely will already be patched.
Thats just my thoughts though.

elliwigy said:
I can see where youre coming from but I dont think they can glean exactly what I have as theres are probably hundreds of scripts throughout the system.
Also, this approach is far from new. People have been using init scripts for rooting purposes for many years.
I also tried it with newer firmware and it actually didnt work. So it already requires an older frmware and I expect Sammy will increment bootloaders soon making it unavailable to those who have updated at that poimt in time. I figured best to put out the word on progress now and those can choose to wait or not.
Exploits never last very long. The only way to ensure longevity is to remain on old firmware. There was SamPWND before there was SamFAIL. This could be the perfect time. Unless I am the only one working on this device there will be other exploits to be found.
With that being said, only you have posted all day and no devs have reached out to join in the fun so at this rate by the time full root is achieved it most likely will already be patched.
Thats just my thoughts though.
Click to expand...
Click to collapse
the note 9 kinda missed the party bus.
ive had almost all Sammy's devices and i have to unfortuanly say this is by far the most bleek state of development ive ever experienced.
but back in the day, there was far less android competition.
edit:
and i think that if not the competition, the fact that alot of people feel content with what stock samsung is offering. when the device came out, the forums were littered with Shakespearean: 'to root or not to' type of threads.

This is great news. Hopefully some devs contact you. Loved your work with the S8.

Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?

Wow, this is very interesting, and I loved reading your detailed post. I am super exited, and can't thank you enough for all your work elliwigy! :good:

Full on beast!
Sent from my SM-N960U using Tapatalk

PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here.
Click to expand...
Click to collapse
I wanna say s8/+ and the note 8.. both of which root solutions I used.
Word brotha ?? thank you for your diligence. I love that your hobby can help out so many who don't have the time, will, or discipline to learn it.

PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?
Click to expand...
Click to collapse
you should be fine as long as you remain on rev1 firmware..

PsiPhiDan said:
Yeeeeeeeesssssss!
Very exciting! If we're updated to Pie, are we out of luck then though, regarding the firmware?
I remember you doing some great stuff but I don't recall the phone... Galaxy S3? Note5? Note7? Note8? HTC M8? EVO 4G LTE? OG EVO? Anyway, I am excited to see you here. ?
Click to expand...
Click to collapse
lol ive had a lot of devices thats for sure but most my work is on samsung

teknowiz23 said:
I wanna say s8/+ and the note 8.. both of which root solutions I used.
Word brotha ?? thank you for your diligence. I love that your hobby can help out so many who don't have the time, will, or discipline to learn it.
Click to expand...
Click to collapse
Yeeeeeeeesssssss!
You are always the loveliest "Rev1 firmware baby"

elliwigy said:
you should be fine as long as you remain on rev1 firmware..
Click to expand...
Click to collapse
So.. I had to get a replacement via Asurion, and before setting it up I installed the earliest unlocked firmware. Sm-n960u on Verizon plan. I understand that this should work as long as I don't update, correct?

teknowiz23 said:
So.. I had to get a replacement via Asurion, and before setting it up I installed the earliest unlocked firmware. Sm-n960u on Verizon plan. I understand that this should work as long as I don't update, correct?
Click to expand...
Click to collapse
Yes, just make sure you stay away from anything that says N960UxxU2 or S2

Jammol said:
Yes, just make sure you stay away from anything that says N960UxxU2 or S2
Click to expand...
Click to collapse
Mine says Rev 1.1. Does that mean game over for me?

PsiPhiDan said:
Mine says Rev 1.1. Does that mean game over for me?
Click to expand...
Click to collapse
No that's for hardware revision. Is normally for when a device has had a hardware fix that changed something from the original design. So if they realized the fingerprint readers on rev1 were crappy and changed it out for future ones, they would show rev1.1 or whatever numbers they want to classify it as.
I'm not sure what they may have changed on the Note 9 though. Could have been camera or even something internal such as memory or radio chip.

What you want to stay away from is any changes to the attached image. Don't update to anything that says U2 or S2 at that section of the firmware.

Thank you for your hard work on this .