Hello all, I haven't been here for about 2 years, got busy with some things. I'm currently running a home compiled JSS15Q that has a touchscreen hack to load in the firmware that works best with my tablet. I'd like to build 5.1.1 LMY48I from source and give it a try. Do I need to upgrade any bootloaders or other stuff before attempting to push the new OS on there?
It's been 2 years since I did any of this stuff so I'm a bit foggy about it all. I had a good handle on it back then, but I've slept a lot since then. I might go with sfhub's locked in firmware this time since I was accomplishing pretty much the same thing just a different way. That's, of course, assuming that the old firmware is compatible with the newer releases of Android OS.
I built the older release in a VirtualBox VM running Ubuntu 12.04. I think I need to upgrade some things to be sure that the compile of 5.1.1 works as it should. I was about out of space on the 12.04 VM and I was going to grow the partition, but I'm thinking it might be smarter to just follow the build-from-source instructions from scratch in a new VM install. It takes a huge amount of space to do a build. AOSP took 20GB and JSS15Q took about 40GB of drive space. I "only" set up a 100GB VM which means I likely don't have enough room to download the newer release source.
If anyone that's done this has any advice, I'd sure appreciate hearing it. Thanks for reading.
Sounds like you already have it figured out.
There is a new bootloader so don't forget that. Sfhubs firmwares work fine.
I forget how big it was when I synced 5.1.1 but if you delete the jellybean code you should be fine.
LOL You're giving me wayyyy too much credit. I'm pretty much stumbling around in the dark here. I went with the new VM using Ubuntu 14.04. I struggled through all the apt-get commands especially the one with libgl1-mesa-glx:i386. It just didn't want to install because of some dependency quirk of some sort with something called cheese. I finally found a solution by doing this:
sudo apt-get install libglew-dev libcheese7 libcheese-gtk23 libclutter-gst-2.0-0 libcogl15 libclutter-gtk-1.0-0 libclutter-1.0-0 xserver-xorg-input-all
God only knows why I had to do all that to get the libgl-mesa-glx installed, but it finally let me do the get for libgl-mesa-glx:i386. Then I could finally create the symlink for the mesa library. After that, I successfully repo synced the source tree; it took up 35GB of disk space. I did the lunch command, picked flo user (11) and started my make command to build. That's running right now.
I was concerned about the proprietary binaries for the broadcomm stuff, but I found a directory under ./device/asus/flo called self-extractors. I'm guessing that stuff takes care of itself now and you don't have to do the steps of finding, downloading and extracting it into the tree. That's my guess anyway. I'm following this "howto":
http://source.android.com/source/requirements.html
I had been looking at an older one on blogspot, but it was for a different device and I figured it would be better to follow the one I'm using instead since it seems more current. I hope this build works okay and doesn't drag badly from bloat. I like my tablet's responsiveness on jellybean. I'm wondering now if I shouldn't have just gone to kitkat instead of all the way to lollipop. Oh well, live and learn. Thanks again for you input and for reading this. Let me know if I'm messing up.
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
afremont said:
I got it compiled. It took about 2.5 hours. I tried to find the program that I modified before, but I can't find it anywhere in the source tree. They've apparently moved everything around real good. If anyone knows where the touchscreen firmware update takes place, I'd appreciate knowing. It used to be in a program named ektf3k.c That program no longer exists in the build. I can use sfhub's utility to lock in the firmware I need, but I'd still like to know how where they moved the firmware update stuff.
Click to expand...
Click to collapse
I built the whole thing without the proprietary binaries installed. I'm guessing that my build is basically useless. I'm kinda disappointed that they don't bring up the binaries until after they walk you through the lengthy compile process. I guess I have to do a make clobber, unpack the binaries and then do the whole build over again. The build went fine as far as I can tell.
Can anyone verify if I have to do it all over with the binaries unpacked? I'm afraid to try flashing the stuff I built just to see what happens. Would there be any harm in that?
Related
I got a file and some apps & drivers.
You can find a PDF file in the attachement.
Please read it to see whether it can help.
Apps & Drivers:
http-//rapidshare.com/files/455584224/KinTwoSetupApp.rar
( - should be replaced with : )
Hi guys, here is another USB driver for KIN TWO which is a little bit different to the one uploaded above.
http-//rapidshare.com/files/456921463/KUSBDrivers.rar
( - should be replaced with : )
Thanks to every one here.
Let's work together/
This looks to be exactly what we are looking for. This will definitely open up the possibilities of modifying the current kin os, or porting a new os to the device. However, this guide is useless without the tools and files mentioned in the document. You said you had some files as well, do you have these files?
SPST Vn.n.n.msi.
PB10ZUnPB20ZU (Lab) Vn.n.n.msi.
SPSTUSBDriverInstall.msi.
InstallPMXMTP.msi
With these files we be able to finally successfully hack this phone.
This is great. We have the resources, now we must figure out how to get a modified os on the phone using the tools.
Awesome find KinPhoneLover; not sure how and where you got this SPST, but it could be the very thing that is needed. For people who bricked their kin phones, they should try the "refurbish feature" to see if that will successfully reset their phones back to "factory mode". As for getting a new OS on the phone, in the pdf at the "Upgrade section", when you browse for the firmware file, it is a .ecn file. Not sure how flashing is done for Cyanogen and those other Android custom firmwares, or their file type extensions. If SPST only supports/allows .ecn files, that could be a problem trying to use those Android custom firmwares.
wow, this is exactly what we needed....did this get leeked or something? it says its from the sharp corp., so im guessing they got it somehow by chatting with them? why isnt there a lot of buzz about this??? i can read my phone number and everything off of this...so close to getting android, or just putting java apps on it..
Too bad its only 32 bit But yes. This is one step closer. Please, people with brick kin, test it out. See if we can get the ball rolling again.
Radar2004 said:
Too bad its only 32 bit But yes. This is one step closer. Please, people with brick kin, test it out. See if we can get the ball rolling again.
Click to expand...
Click to collapse
yes, i have to use my slow home computer, instead of using my quad core 64bit laptop
Just got everything up in running. Is anyone else having a problem with the SPST constantly dropping the connection with the phone and reconnecting? I'm not sure if this is due to running XP in a virtual box or if its something I can readily fix.
Short Answer: doesnt work.
Long Story: This needs your phone to be ON even for refurbish option and then, able to connect to a COM port. Unfortunately, that doesnt happen in SBL / APX mode and phone doesnt boot (autoreboots) so no COM mode available.
Just another software installed (for me).
No news in the front, guys. I guess i just need to get rid of verizon software (the one trying to get an OTA), not something from "normal" kin states.
Okay so now that we have a tool to upgrade the software all we need are custom firmware files to flash to it. However I don't see any option to read/dump the firmware using this software.
dezgrz seems to be correct, there don't seem to be a way to read/dump the current OS to make a backup of it. The PRL and ERI options don't seem to be what we want. The Provision option is the only option where we can read stuff from the phone. Could someone run that option, check all those settings (NAM1, security, feature, data, etc) and write it to a file and upload it? Maybe there will be something useful in there.
I gotta order a new battery, then I'll see if I can get anywhere with this... need to load up a 32bit OS first, apparently.
Either way, this is a huge step. Maybe not complete, but still a huge step. Thanks OP.
Hm..??
This seems interesting. I been watching this site until someone "Exploited" the phone. I have a mac, and does this work for kin? What does it do?
zero2duo said:
Could someone run that option, check all those settings (NAM1, security, feature, data, etc) and write it to a file and upload it? Maybe there will be something useful in there.
Click to expand...
Click to collapse
That features seem to be available already with "QPST" software... which didnt make anything advance (yet).
As i said, i renamed my NAM succesfully, and changed some security options (which i guess that doesnt matter, cause i *was* able to work anyway).
not much you can do that you cant do already, besides looking at your phones info. I was able to change voicemail numbers, was *86, i changed it to to just 8, and it says voicemail, but doesnt connect. Still playing around.
Why don't you just take it back to Verizon and get a replacement. How would they ever know you messed it up trying to hack it?
MicroNateDram said:
Why don't you just take it back to Verizon and get a replacement. How would they ever know you messed it up trying to hack it?
Click to expand...
Click to collapse
You should read the whole threads and/or other threads to understand why.
This phone needs to get hacked. I love my phone but i dont like the OS that the phone has. If this phone isnt hacked by the time summer comes, ill be glad to participate. I've hacked many phones but this may be a challenge. I would like to see apps on this phone.
PS I know the phone has java so where can i go to play games or apps for java?
Kinuser1 said:
PS I know the phone has java so where can i go to play games or apps for java?
Click to expand...
Click to collapse
Javascript
johnkussack said:
Javascript
Click to expand...
Click to collapse
Out of all the things I know, why wouldn't I know that its Javascript? Jeeezus. I would happily spend time on this phone but my grades are more important. Now what site could I go to on my phone to play apps/games.
P.S your post didn't really help me.
Hey guys, Since the 4.0.3 CDMA/LTE binaries are not available on google's site, I had to find and pull them manually from 4.0.2, using the Maguro GSM sh install log as a reference for the files I needed. So I thought I would save the trouble for anyone else to have to do this and post the files here.
Here are the files:
https://rapidshare.com/files/731354314/toro_403_LTE_bins.zip
the zip includes the files needed, as well as the modified make files needed to tell the compiler to include the libraries in the build.
simply extract to /vendor/samsung/ in your Android Source directory, then build!
Thanks for this!
Doesn't the extract-files.sh script in AOSP do this for you?
I love you. I was about to go home and figure out how to do this, but you posted the binaries for me.
Thanks!
Dude thanks a ton! I was trying to figure out why my roms weren't booting...then I realized that only the graphics binaries were posted by google. Just to make sure, these files are pasted under /device/samsung/toro/files-go-here correct?
binaries usually get put into /vendor, not /device.
I was able to compile a bootable version using only the Google supplied binaries, though it wasn't fully functional (it did boot).
If you have a GN, the better way is to just go into device/samsung/toro, and run the extract files script with your phone connected (it uses ADB to pull them from your phone)
For some reason if I use the extract files script, I can't get the damn thing to boot. I forgot to run it once and built without it...it booted, but the radio wasn't working. So should the binaries that google posted go in /vendor as well?
The script puts the files in the appopriate location (vendor/samsung/toro/proprietary if memory serves)
Coincidentally, the build I compiled from Google provided binaries had the same problem of not having radio connectivity.
To be honest, I have yet to get a functional compile using the extract script as well, though I've heard others have. I didn't do much troubleshooting, instead just kanged AOKP's vendor and device tree from github.
Good to hear I'm not the only one. I just built it again and now I'm stuck at the google logo. I might just go ahead and grab those off git as well.
SoCmodder said:
For some reason if I use the extract files script, I can't get the damn thing to boot. I forgot to run it once and built without it...it booted, but the radio wasn't working. So should the binaries that google posted go in /vendor as well?
Click to expand...
Click to collapse
Yes. They may even be the same exact GPU binaries the script pulls from the phone (I've never checked).
would it be smart to run clobber before trying to build again?
SoCmodder said:
would it be smart to run clobber before trying to build again?
Click to expand...
Click to collapse
Based solely on having seen a warning that says you should after running the extract script, I'd say yes =)
For those of you who can't boot off your builds, are you building 4.0.3_r1? By default that build is configured to require a newer radio and bootloader than what's out officially, so you'll have to modify the board config to get those to boot on production Galaxy Nexuses.
Herp derp, yeah that's what I was trying to do. I just kanged the AOKP one's for now. I suppose I should look into them and learn how to straighten it out myself though.
A little off topic I suppose, but do any of you know if the current SU.zip will work with the new bootloader/radios?
SoCmodder said:
Herp derp, yeah that's what I was trying to do. I just kanged the AOKP one's for now. I suppose I should look into them and learn how to straighten it out myself though.
A little off topic I suppose, but do any of you know if the current SU.zip will work with the new bootloader/radios?
Click to expand...
Click to collapse
All the production bootloader/radio versions should be compatible with each other. Just change device/samsung/toro/board-info.txt to require whichever version is currently on your device and your build should boot.
After digging into it last night and this morning, I found:
- No bootloader issues. The board-info.txt issue was fixed upstream, and is in branch ics-mr1.
- Turns out even though it looked like it was hung at the Google logo, my device was actually up and contactable via adb. Logcat showed a problem initiating the graphics subsystem.
- The extraction script doesn't appear to grab some of the graphics drivers. Notable is that there is no vendor/imgtec, like there is when you use the binaries from Google.
Ultimately, I was able to get what seems to be a fully functional build (4G, sound, wifi, calls confirmed) by NOT using the extraction script, extracting the google binaries, and then extracting the binaries provided by the OP of this thread.
I have built and slightly tweeked CM 10.1 but to be honest, it does drain that battery quite a bit and sometimes it freezes in landscape mode.
So I sync'ed up the source for the AOSP and then I realized that I needed binaries and I don't have the stock ROM to extract them from.
Are these "Galaxy Nexus (Sprint) binaries for Android master (20130603)" the right binaries for SPH-l710 ?
Under the Toroplus section at the very bottom of this page https://developers.google.com/android/nexus/drivers
Basically I just want try moding from stock because of the battery thing, I need to add Arduino support and maybe tweek USB or write an app, so that my phone can hook up over usb to an Arduino board and chit chat. I want the Arduino to control motors while Android gathers sensor data and decides where to go, Arduido will just follow orders. Anyways, battery consumption is huge in this project.
EDIT-1: Also, what version of Android are the 20130603 binaries for?
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
CNexus said:
These are the binaries
https://github.com/themuppets/proprietary_vendor_samsung
d2spr folder.
That's not all you need to build for our device though.
I suggest just building an existing rom rather than syncing AOSP....you're gonna need to make a TON of edits to even get it to build, much less boot. I know because I'm very much involved with a new AOSP rom called omnirom and bring ups for that rom. It's not easy. We're still making edits to the source to even get it to build for non-nexus devices
Click to expand...
Click to collapse
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Edge-Case said:
hmm
I thought it would be a lot easier than it has been to build a stock rom, but I guess not, I am not trying to build kit-kat though, I want to build for 4.1.2 as I think thats where their updates left off but maybe I am way outta the loop.
What about the factory images? Are those flashable with the "flash-all.sh" over fastboot? Idk either way I haven't been able to get fastboot working, I don't think I have even been able to boot into fastboot, when I "adb reboot bootloader" I go to what looks like Odin's download mode, and when I do the volume up+down+power I just boot into "safe mode" and get to the launcher like normal but its in safe mode. I rooted it on Windows about a half a year ago or so using Odin and some dude's tuts on YouTube "High on Android" or something. I haven't really studied rooting so I guess thats my bad not knowing really what I was doing, but I haven't looked back and wouldn't be here now if it wasn't for it.
I'll take your word for it but I am going to keep trying to figure it out, Figureing out all this proprietary stuff is tuff, maybe I should get a device or board targeted to developers lol, didn't know Id ever say that, I thought I was going to major in Chemistry.
Click to expand...
Click to collapse
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
CNexus said:
All of the downloads on the Google site are for and will only work with nexus devices
Those proprietary files are the bare minimum to "inject" our device's characteristics into a rom. That's how I ported Sense actually
Click to expand...
Click to collapse
Makes Sense.
So if I am learning anything... I would need binaries ("blobs"), I am sure Sprint, Google, and Samsung proprietary apps, and the nessiccary make (Android.mk) files, maybe some kernel patches and/or kernel object files, and hopeful to all hell I don't have to do too much XML modification I need to go find a trust-worth factory zip for the sph-l710 and rip everything I need out of that, and the bootloader I need to get it all back to stock eventually in case kit-kat does get updated by the Samsung (I am guessing thats whose hands it is in, I think they have a counter), who knows maybe the open source community will get there first.
Thanks for your help, saved me a ton of hassle.
I was wondering if someone could help me. I've been playing around with flashing roms and basic stuff for a long time, but I figured I'd like to play around with kernel building, and just generally trying to learn about android/linux/java more. So far the only kernels I've successfully built were for the 6P just because I tried it following google's source website. I've been trying to just see if I could build a stock kernel for the 10, so I could see if I could actually flash it. My builds always fail at the same places, so I tried cloning the repositories of flar2 and tbalden just to see if I could make their kernels and my build fails on the same. Looking at source codes from other devices such as the OnePlus3 I see that it's basically the same, and so I tried building that and it fails exactly for me at the same areas as well.
I'm using an older 2012? Core-i5 laptop that I had laying around, installed Ubuntu 16.04 LTS. I got the newest android NDK, put the path into .bashrc so I could just use CROSS_COMPILE=aarch64-linux-android- without having to type out the full path every time. I'm wondering if there's just something wrong with my build environment and I need to start over? I see all these tutorials, but they're all old and usually covering older 32-bit kernels. They mention all the variations of using sudo apt-get install, followed by a bunch of various packages. So I'm wondering if these are older packages conflicting with something? Does anyone happen to have any guidance on this. I just want to get setup and be able to build a single HTC 10 kernel and then go from there.
duowing said:
I was wondering if someone could help me. I've been playing around with flashing roms and basic stuff for a long time, but I figured I'd like to play around with kernel building, and just generally trying to learn about android/linux/java more. So far the only kernels I've successfully built were for the 6P just because I tried it following google's source website. I've been trying to just see if I could build a stock kernel for the 10, so I could see if I could actually flash it. My builds always fail at the same places, so I tried cloning the repositories of flar2 and tbalden just to see if I could make their kernels and my build fails on the same. Looking at source codes from other devices such as the OnePlus3 I see that it's basically the same, and so I tried building that and it fails exactly for me at the same areas as well.
I'm using an older 2012? Core-i5 laptop that I had laying around, installed Ubuntu 16.04 LTS. I got the newest android NDK, put the path into .bashrc so I could just use CROSS_COMPILE=aarch64-linux-android- without having to type out the full path every time. I'm wondering if there's just something wrong with my build environment and I need to start over? I see all these tutorials, but they're all old and usually covering older 32-bit kernels. They mention all the variations of using sudo apt-get install, followed by a bunch of various packages. So I'm wondering if these are older packages conflicting with something? Does anyone happen to have any guidance on this. I just want to get setup and be able to build a single HTC 10 kernel and then go from there.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1748297
Here you go
It's kinda sad to see the forum for the Duo not really progressing even with a device with an unlocked bootloader.
This device is amazing , it sucks to see it not getting much love from the dev community
I was thinking the same. I'm sure making the dual screens function as they should might be offsetting.
josh_zombie said:
I was thinking the same. I'm sure making the dual screens function as they should might be offsetting.
Click to expand...
Click to collapse
Android 11 supports multi screens out the gate from what ive heard.
Im also hoping someone just makes an optimized deodex stock rom. the ram management isnt great :\
you can try GSI in the meantime
GSI?
also i noticed this was a dead forum. ppl are on the reddit. but im wondering if ppl just waiting on the Android 11 release then hustling on that. ALSO a lot of BS bad press from APPLE funded mainstream reviewers....so i mean..... i really get annoyed with my device SOMETIMES but MOST of the time....im loving it....and its a HUGE head turner and convo starter....its a great device
Same and same. Was really looking forward to that speaker mod.
After having to use an iPhone as a work issued device for the last 10 years, and being an Android person since the first Droid arrived way back when, 2 weeks ago I bought this device. I LOVE IT!!! I am now loving reading my ebooks, could never find a device I liked to read them on. I have literally 10 years of books to catch up on. The form and function of this device is far more advanced than the iPhone XR I was using. Yeah the camera leaves something to be desired, but it makes up for it in form and function. I don't need a great camera, what I need is a flexible device that allows me to integrate my work and home life balance. The 2 screens and being able to do more things at once is awesome. I am really hoping development takes off for this device.
darkherman said:
you can try GSI in the meantime
Click to expand...
Click to collapse
Have you tried any of the gsi roms yet? I've been thinking if it too.
This device was released first in the USA. I believe now that other countries are starting to get this device. I believe we will see a lot of development for this device. Remember android 11 and 12 were designed for dual and non dual screens. More to come guys. Im actually interested in learning linux. I heard it just commands.
none24 said:
It's kinda sad to see the forum for the Duo not really progressing even with a device with an unlocked bootloader.
This device is amazing , it sucks to see it not getting much love from the dev community
Click to expand...
Click to collapse
They are baking the multi-screen features into Android 11. Any custom development now requires incorporating all that stuff into a ROM (which means ripping it from an existing ROM, figuring out how it all works and then porting it to AOSP, maybe a piece of cake, maybe a nightmare) whereas in theory the AOSP 11 source will allow us to just build as-is and get at least minimal dual-screen support without having to do a bunch of extra work.
Microsoft has some decent documentation up for the Duo already but it's Microsoft's first Android device, there is a lot of work to be done.
renegadeone8 said:
They are baking the multi-screen features into Android 11. Any custom development now requires incorporating all that stuff into a ROM (which means ripping it from an existing ROM, figuring out how it all works and then porting it to AOSP, maybe a piece of cake, maybe a nightmare) whereas in theory the AOSP 11 source will allow us to just build as-is and get at least minimal dual-screen support without having to do a bunch of extra work.
Microsoft has some decent documentation up for the Duo already but it's Microsoft's first Android device, there is a lot of work to be done.
Click to expand...
Click to collapse
Yeah, I agree. It's a lot of work and you have to find the software changes that they made inside the system image. I managed to get the system images separate from the OTA files, but I'm stuck on extracting the data from the system image. Microsoft used a different file type than other developers, but once we can access the data from system images, we'll be one step closer to ROM development!
JengaMasterG said:
Yeah, I agree. It's a lot of work and you have to find the software changes that they made inside the system image. I managed to get the system images separate from the OTA files, but I'm stuck on extracting the data from the system image. Microsoft used a different file type than other developers, but once we can access the data from system images, we'll be one step closer to ROM development!
Click to expand...
Click to collapse
I'm looking forward to it!
This is one device with tons of potential screaming for development. I would buy it just for the things a rooted Duo could do!
We already have gCam.
What I need as a rich DeX like desktop mode where I can plug in my dock and connect to multiple monitors and work like I do with my regular Surface.
Then minute that happens I'm grabbing one ASAP.
System and Vendor Files Extracted for Build 2021.817.35 (and for future builds):
[Resource] System and Vendor Files for Surface Duo & How-To Guide
Extracted System and Vendor Files Please use these files for your correct system version only! I am not liable for any system crashes or errors. This is only a resource for development purposes. Access Extracted Files (GitHub): Access System...
forum.xda-developers.com
This is awesome!
Also Microsoft recently announced Android 12L support next year.
Google's Android 12L update coming soon to support Surface Duo 2 and other large screen devices - OnMSFT.com
Google is planning a feature for its latest Android 12 operating system large enough to warrant a name change dubbed Android 12L that will give tablets,
www.onmsft.com
Hopefully it'll be both Duos getting the update to 12L
Would someone be willing to test my TWRP boot image? My Duo is bricked and I can't flash any files to the system anymore :/
This is the software you need to be on: 2021.913.25. If you can, you can dm me or reply here!
I'm on 2021.913.27 unfortunately, and I have another duo thats been off for a few months if that will help at all.
Im already 2400 in the hole and moved on to the iPhone 13mini so I'm happy to help test if it can get this device a few steps closer to functional.
kmccall said:
I'm on 2021.913.27 unfortunately, and I have another duo thats been off for a few months if that will help at all.
Im already 2400 in the hole and moved on to the iPhone 13mini so I'm happy to help test if it can get this device a few steps closer to functional.
Click to expand...
Click to collapse
The phone doesn't power on anymore? If you can send me the 2021.913.27 zip file that's used to restore your phone, I can make a TWRP image you can test.
JengaMasterG said:
The phone doesn't power on anymore? If you can send me the 2021.913.27 zip file that's used to restore your phone, I can make a TWRP image you can test.
Click to expand...
Click to collapse
you misunderstand so heres the full story you can skip if you want
I purchased 2 Duos with my partner. He stopped using his after a short while and some mild water damage and I stopped using mine after cracking it. The insurance process with Asurion was such a pain in the ass that I never got either repaired but both still boot and operate completely fine. I just hate them.
I would like to hate the phones I spent so much money on a lot less and am willing to even accidently brick them in the process but haven't done more than rooting and TWRPing samsung and OnePlus phones. but I work in robotics so it can't be too outside my depth to assist with.
Click to expand...
Click to collapse
TLDR: I have two beatup Duo phones that boot and run perfectly. I am happy to help flash and mess around with them.
[[ If you can send me the 2021.913.27 zip file that's used to restore your phone ]]
Where would I find this file? Or is there a way to get non rooted phones to spit out their updater files?
kmccall said:
you misunderstand so heres the full story you can skip if you want
TLDR: I have two beatup Duo phones that boot and run perfectly. I am happy to help flash and mess around with them.
[[ If you can send me the 2021.913.27 zip file that's used to restore your phone ]]
Where would I find this file? Or is there a way to get non rooted phones to spit out their updater files?
Click to expand...
Click to collapse
Oh gotcha. You can find how to get it here:
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
You can send me the zip file. I'll get the resources from it and send you a boot image to boot from fastboot. If the phone successfully boots, we have TWRP. If not, it's back to the drawing board.
JengaMasterG said:
Oh gotcha. You can find how to get it here:
Surface Recovery Image Download - Microsoft Support
support.microsoft.com
You can send me the zip file. I'll get the resources from it and send you a boot image to boot from fastboot. If the phone successfully boots, we have TWRP. If not, it's back to the drawing board.
Click to expand...
Click to collapse
And if it bricks, I'll somehow still be satisfied. I'll get back to you this evening.
Just started my shift