{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google Project Tango Tablet
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Unofficial Lineage OS 16.0 thread for the Google Project Tango Tablet, codename yellowstone.
How to Install:
Please follow the instructions on our Unofficial ODS Wiki page here.
If you don't follow these instructions, please don't expect support here. You NEED to flash the PSCI firmware via the process described in the wiki above, or you run a significant chance of bricking your device.
We also don't support 3rd party add-ons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Issues:
Camera's and flashlight don't and likely won't ever work due to incompatibilities in proprietary binaries.
Due to the fact the cameras are broken, the ATAP/Tango apps will crash upon opening.
USB Tethering is broken for some people.
SELinux is permissive (if you're a developer, you can help on this one!)
Downloads:
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps/Pixel goodies.
Add-ons (WeatherProviders/AddonSU packages
How to build yourself:
Follow the ODS Wiki Guide here here, except just after running
Code:
. build/envsetup.sh
run
Code:
repopick -f 279494
then proceed as described.
Returning to Stock:
Follow the ODS Wiki Guide here here starting at step two, except instead of downloading/using `yellowstone_pie_psci.zip`, use yellowstone_kitkat_stock.zip
XDA:DevDB Information
[UNOFFICIAL] LineageOS 16.0 for the Project Tango Tablet (ATAP), ROM for the Nvidia Shield Tablet
Contributors
npjohnson, ryanbg, steel01
Source Code: https://github.com/LineageOS/android_device_google_yellowstone
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Stock KitKat
Version Information
Status: Stable
Created 2020-10-16
Last Updated 2020-10-16
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
I wanted to ask, what exactly needed changing to the bootloader stuff that allows newer custom ROMs to boot? I'm legitimately curious and I would like to know if those modifications basically open it up so that it all lands on the OS side for getting stuff like cameras working in the future if that's even possible.
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
xaxxelous said:
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
Click to expand...
Click to collapse
The link provided is working for me but I don't see why you couldn't use those extras. Just make sure to grab the ones for LineageOS 16.0. But @npjohnson please correct me if I'm wrong.
EDIT: The main link works to the list of extras downloads but none of the extra downloads on the page work.
there is an issue with the script.
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
there appears to be a typo. The last part of the command seems to be --go Got it working here
---------- Post added 17th October 2020 at 12:15 AM ---------- Previous post was 16th October 2020 at 11:48 PM ----------
Unless I'm wrong there's also a typo on the wiki page you made.
Lines like:
With the device powered off, hold Volume Down + <kbd+ Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Should probably be like:
With the device powered off, hold Volume Down + Volume Up + Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Well I did some testing and for the most part the tablet works better than it's ever had. Before I had an issue with it powering off with a "dead battery" but flashing a full charged battery icon after powering off. That issue has gone away now.
Thank you and anyone who has helped bring this ROM to life, it's really amazing to see newer software working so well on these old tablets. I honestly didn't think it would ever happen.
xaxxelous said:
Thanks!
Could be me, but it looks like the links to the add-ons are 404. These should work, right?
https://download.lineageos.org/extras
Click to expand...
Click to collapse
Fixed.
ShapeShifter499 said:
I wanted to ask, what exactly needed changing to the bootloader stuff that allows newer custom ROMs to boot? I'm legitimately curious and I would like to know if those modifications basically open it up so that it all lands on the OS side for getting stuff like cameras working in the future if that's even possible.
---------- Post added at 10:04 PM ---------- Previous post was at 10:02 PM ----------
The link provided is working for me but I don't see why you couldn't use those extras. Just make sure to grab the ones for LineageOS 16.0. But @npjohnson please correct me if I'm wrong.
EDIT: The main link works to the list of extras downloads but none of the extra downloads on the page work.
Click to expand...
Click to collapse
Fixed.
And to answer the question - It's a hybrid of tn8's (Shield Tablet) nvboot and a heavily disassembled/reassembled applications bootloader to support the newer TLK/Secure World and PSCI kernel from tn8, allowing us to use kernel 3.10 from nv-tegra as opposed to 3.4 from Google. Much cleaner, must snappier, plus it lets us use Shield Tablet proprietary files for graphics, etc. which has an official Nougat release, which is way easier to work with than KitKat blobs from stock. We split out and use as many tn8 blobs as we can, and yellowstone stock where we need to.
It was designed almost entirely by @ryanbg -he's a legend, and one of the big reasons this device got anything more than cm-14.1 - I did most of the Android-side bringup (which was rough), but his work on kernel and firmware enabled it
ShapeShifter499 said:
there is an issue with the script.
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
there appears to be a typo. The last part of the command seems to be --go Got it working here
---------- Post added 17th October 2020 at 12:15 AM ---------- Previous post was 16th October 2020 at 11:48 PM ----------
Fixed - don't know how I missed that, sorry.
Unless I'm wrong there's also a typo on the wiki page you made.
Lines like:
With the device powered off, hold Volume Down + <kbd+ Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Should probably be like:
With the device powered off, hold Volume Down + Volume Up + Power until a menu is displayed. Use Volume Down to highlight “Recovery mode”, then press Power to select
Click to expand...
Click to collapse
Fixed.
ShapeShifter499 said:
Well I did some testing and for the most part the tablet works better than it's ever had. Before I had an issue with it powering off with a "dead battery" but flashing a full charged battery icon after powering off. That issue has gone away now.
Thank you and anyone who has helped bring this ROM to life, it's really amazing to see newer software working so well on these old tablets. I honestly didn't think it would ever happen.
Click to expand...
Click to collapse
Yeah, that was an old bootloader bug. Plus we swapped to newer battery graphics to match Lineage branding
Also, not responding to anyone in specific, just noting, I also added instructions to build at home to the OP!
npjohnson said:
And to answer the question - It's a hybrid of tn8's (Shield Tablet) nvboot and a heavily disassembled/reassembled applications bootloader to support the newer TLK/Secure World and PSCI kernel from tn8, allowing us to use kernel 3.10 from nv-tegra as opposed to 3.4 from Google. Much cleaner, must snappier, plus it lets us use Shield Tablet proprietary files for graphics, etc. which has an official Nougat release, which is way easier to work with than KitKat blobs from stock. We split out and use as many tn8 blobs as we can, and yellowstone stock where we need to.
It was designed almost entirely by @ryanbg -he's a legend, and one of the big reasons this device got anything more than cm-14.1 - I did most of the Android-side bringup (which was rough), but his work on kernel and firmware enabled it
Click to expand...
Click to collapse
I was looking into it seeing if maybe I could help. I had been looking at the tos.img alone thinking that was it. But wow man I probably would have never gotten to the bootloader like that. Thank you and @ryanbg for putting all the work in.
So I have a new issue. My IMEI is blank and my sim card doesn't work. I had this sim working before on stock firmware, service through t-mobile
---------- Post added at 02:46 AM ---------- Previous post was at 02:25 AM ----------
I redownload the zip and the script inside still has an issue for Linux
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
ShapeShifter499 said:
So I have a new issue. My IMEI is blank and my sim card doesn't work. I had this sim working before on stock firmware, service through t-mobile
---------- Post added at 02:46 AM ---------- Previous post was at 02:25 AM ----------
I redownload the zip and the script inside still has an issue for Linux
[[email protected] yellowstone_pie_psci]$ ./flash.sh
Nvflash 4.13.0000 started
unknown command: --g
[[email protected] yellowstone_pie_psci]$
Click to expand...
Click to collapse
This is weird... I use t-mobile on yellowstone - and it works fine. Can you get me logs?
npjohnson said:
This is weird... I use t-mobile on yellowstone - and it works fine. Can you get me logs?
Click to expand...
Click to collapse
I was able to use the package you uploaded to revert to kitkat stock and confirmed the t-mobile sim works with this tablet. It just doesn't work on the latest build you have.
This is from a fresh reinstall. Installed are the LineageOS Recovery (lineage-16.0-20201009-recovery-yellowstone.img), the LineageOS 16.0 main build (lineage-16.0-20201009-UNOFFICIAL-yellowstone.zip), and the LineageOS SuperSU add on (addonsu-16.0-arm-signed.zip). I grabbed a logcat from first boot, I tried to use the option to use the cellular network which failed and I skipped all google sign in so I could try toggling cellular network in the settings.
Logcat: https://gist.github.com/ShapeShifter499/51f14342a14416a44ed1fdec27c071cc
Here is one more logcat, taken after first boot. I toggled the "Airplane mode" in settings to no avail, SIM was still not detected and no network connection was made over cellular.
Logcat: https://gist.github.com/ShapeShifter499/856e638f29e33f1aac156ca19dc2c790
ShapeShifter499 said:
I was able to use the package you uploaded to revert to kitkat stock and confirmed the t-mobile sim works with this tablet. It just doesn't work on the latest build you have.
This is from a fresh reinstall. Installed are the LineageOS Recovery (lineage-16.0-20201009-recovery-yellowstone.img), the LineageOS 16.0 main build (lineage-16.0-20201009-UNOFFICIAL-yellowstone.zip), and the LineageOS SuperSU add on (addonsu-16.0-arm-signed.zip). I grabbed a logcat from first boot, I tried to use the option to use the cellular network which failed and I skipped all google sign in so I could try toggling cellular network in the settings.
Logcat: https://gist.github.com/ShapeShifter499/51f14342a14416a44ed1fdec27c071cc
Here is one more logcat, taken after first boot. I toggled the "Airplane mode" in settings to no avail, SIM was still not detected and no network connection was made over cellular.
Logcat: https://gist.github.com/ShapeShifter499/856e638f29e33f1aac156ca19dc2c790
Click to expand...
Click to collapse
Dmesg as well pls
npjohnson said:
Dmesg as well pls
Click to expand...
Click to collapse
Here is a dmesg
https://gist.github.com/ShapeShifter499/1912a442e3887df9458fa7d6a73828ee
I tried to install the recovery listed in the downloads page. It failed and said-- FAILED (remote: (InvalidSize)) I copy and pasted the name of the file, so that should have been ok. Not sure what I did wrong, and ideas would be helpful.
thew-tab said:
I tried to install the recovery listed in the downloads page. It failed and said-- FAILED (remote: (InvalidSize)) I copy and pasted the name of the file, so that should have been ok. Not sure what I did wrong, and ideas would be helpful.
Click to expand...
Click to collapse
Sounds like you didn't repartition yet...
I didn't seek anything in the wiki about how to partition, unless I completely missed, thanks for the quick response.
npjohnson said:
Sounds like you didn't repartition yet...
Click to expand...
Click to collapse
thew-tab said:
I didn't seek anything in the wiki about how to partition, unless I completely missed, thanks for the quick response.
Click to expand...
Click to collapse
It's literally the first several pages of the wiki.
The PSCI firmware package.
@npjohnson If I wanted to fork some of the repos to do my own edits, tests, and maybe port a different ROM to get working. Which of the repos contain the latest accepted edits? The LineageOS github ones or the ones on your own github? I figure at least I would get the proprietary blobs from your github or the last ROM.
Also got any ideas about the SIM card issue? I suspect this error I see in the dmesg is it but I don't know for sure "init: Could not find service hosting interface [email protected]::IRadio/slot1" which led me to this https://stackoverflow.com/questions...nterface-android-hardware-radio-config1-0irad
ShapeShifter499 said:
@npjohnson If I wanted to fork some of the repos to do my own edits, tests, and maybe port a different ROM to get working. Which of the repos contain the latest accepted edits? The LineageOS github ones or the ones on your own github? I figure at least I would get the proprietary blobs from your github or the last ROM.
Also got any ideas about the SIM card issue? I suspect this error I see in the dmesg is it but I don't know for sure "init: Could not find service hosting interface [email protected]::IRadio/slot1" which led me to this https://stackoverflow.com/questions...nterface-android-hardware-radio-config1-0irad
Click to expand...
Click to collapse
SIM is now fixed. And that error by proxy. Yes, just use lineage.dependencies to trace dependencies, all on lineageos org, and vendor is on themuppets as always.
17.1 doesn't boot at all, but that's a tegra t124 wide chipset issue - graphics crashes and panics the device. 16.0 is near to perfect.
ShapeShifter499 said:
Here is a dmesg
https://gist.github.com/ShapeShifter499/1912a442e3887df9458fa7d6a73828ee
Click to expand...
Click to collapse
Okay, this was an issue on my end - I fixed it, newest build via OTA fixes it.
npjohnson said:
Okay, this was an issue on my end - I fixed it, newest build via OTA fixes it.
Click to expand...
Click to collapse
Perfect, I can now connect to LTE, though I only seem to ever get slow H or H+ connections over T-Mobile. Same as on Stock. Probably the old cellular chipset to blame.
I do see two other issues but I don't know how fixable they are.
1) Charging over USB micro-B barely works when booted in. It doesn't like to draw much current. As example, one of my power banks shuts off when this tablet is plugged in to it. Another being that it seems to discharge when plugged into a USB wall wart rated at 5V 2A. I know with some devices it was possible to change the kernel to force a higher charge rate or temporarily toggle it. Does anyone happen to know if that's possible here?
2) 1080p videos work amazing when they are under 60FPS, 60FPS videos will studer but not slow down the system. Videos 1080p 30FPS play perfectly. 60FPS videos also play perfectly if they are under 1080p of quality.
I don't expect it to play anything higher than 1080p in quality but I wonder why the 60FPS is the limit for 1080p when 30FPS seems smooth.
ShapeShifter499 said:
Perfect, I can now connect to LTE, though I only seem to ever get slow H or H+ connections over T-Mobile. Same as on Stock. Probably the old cellular chipset to blame.
I do see two other issues but I don't know how fixable they are.
1) Charging over USB micro-B barely works when booted in. It doesn't like to draw much current. As example, one of my power banks shuts off when this tablet is plugged in to it. Another being that it seems to discharge when plugged into a USB wall wart rated at 5V 2A. I know with some devices it was possible to change the kernel to force a higher charge rate or temporarily toggle it. Does anyone happen to know if that's possible here?
2) 1080p videos work amazing when they are under 60FPS, 60FPS videos will studer but not slow down the system. Videos 1080p 30FPS play perfectly. 60FPS videos also play perfectly if they are under 1080p of quality.
I don't expect it to play anything higher than 1080p in quality but I wonder why the 60FPS is the limit for 1080p when 30FPS seems smooth.
Click to expand...
Click to collapse
It's not older chipset -- it's missing bands :/ - unfixable
1. Charging can't be fixed. The regulators are MESSED UP, and it is charging the best it possibly can. The dock quick-charges it safely. - Working as intended
2. Totally expected, older hardware, and the app may be using software rendering instead of hardware - the top result for "1080p 60fps" on youtube plays fine.
Related
NOTICE: This will not work on the latest firmware updates. Flashing will cause bootlooping and you will have to reload software.
If CASUAL brought you here, your version is outdated.
Well, this has been quite the saga thus far...
Us: Suck It Verizon (exploit)
them: Suck it XDA-Developers (OTA patch)
Us: Back Atcha Verizon (exploit)
them: Stop it XDA (OTA Patch)
Us: No You! (exploit)
Introduction
CASUAL will guide you through the process. Put your device into “Developer Mode>USB Debugging”. Click the do it button. If you experience a problem, PLEASE USE THE PASTEBIN button to post a log. CTRL+L>Pastebin> come back here and press ctrl+V. We need a log or it didn't happen. 70% of the time when someone posts a general description, we need more information.
Overview
You are expected to be STOCK.... Stock anything, but stock. If you are not stock and have a custom recovery, this will cause you to only be able to flash back to stock using Odin or Heimdall. Be stock. You will need to download and execute the CASUAL application below. Then click the Do It! button. You need Java. Do you have Java?.
note: if it fails, try turning everything off and back on, then run it again before posting for help.
Windows 32/64 Users: CASUAL will put your device into Download Mode. It will automatically flash everything. If drivers are required, jrloper's CADI (CASUAL Automated Driver installer) will handle it. Make sure you're connected to the internet.
Windows 8 is supported but you must install drivers for Download Mode first. See this post
Windows XP IS NOT supported! If you can make Windows XP work, share the knowledge. XP is 12 years old now, Microsoft and I both discontinued support for Windows XP.
Linux 32/64/raspberry pi Users There may be a permission escalation in order to install heimdall, either way sit back and relax. CASUAL automates the entire process.
Please run the following in a terminal first:
Code:
sudo apt-get install openjdk-7-jdk gksu dpkg
NOTE: Linux 32/64 bit Heimdall may require an update. I will be taking care of it this weekend. If it works, please let me know so I can remove this message.
Mac Users: Mac works easier than any other system at the time of this systems. Please report problems.
Download
CASUAL(R515b) No You Verizon! CASUAL is used to automate the process. The exploit was developed by Elite Recognized Developer Ralekdev and packaged by AdamOutler. To run CASUAL you need Java. Do you have Java?
For nightly builds click here: http://goo.im/devs/AdamOutler/VZWGalaxyNote2
Help and Troubleshooting
Are you having a problem? First check this post out for remedial troubleshooting. . If that doesn't fix it, then press CTRL+L, press the Pastebin button, come back here and press CTRL+V to paste your log. Don't hit the donate button, that doesn't fix it. Donate only if you feel it's worth donating to. Use CTRL+L and then hit Pastebin and paste the log here if you need help.
Jailbreak video for Windows users only!
This video desmonstrates CASUAL used with Odin to flash the Galaxy Note 2 firmware. Thanks to DroidModderX. While the video uses an old version the procedure is mostly the same.
Jailbreak video for LINUX only!
This video demonstrates the one-click CASUAL Linux Unlock method... at 2AM.. so don't expect me to be cheerful. While the video uses an old version, the procedure is mostly the same.
image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About CASUAL
CASUAL stands for Cross-platform ADB Scripting, Univeral Android Loader. CASUAL jar files are a wrapper for the CASUAL scripting language. CASUAL allows rapid and accurate deployment of hacks and exploits. At any time, if a serious problem is detected with any script, the kill-switch will be flipped and you will be brought to a support page (most likely here) so you can download the latest version. Otherwise for minor corrections, new CASUAL scripts can be deployed remotely.
Updates
CASUAL provides updates WAAAAY quicker than Verizon. As soon as I push an update to the Subversion repo it appears automatically in EVERY casual. See below for the change log.
8May13: After last the issues with this release, I spent 5.5 hours updating to VRAMC3 and .1 testing this package. . It works well, I assure you.. I assume the previous release had a bad MD5. I apologize for any inconvience.
9May13: Initial Release
10May13: Fixed windows driver issue. Added clearer instruction messages to wait (fixed "hanging"). Added better error handling. CASUAL R492 -- killed old versions
F.A.Q.
//TODO
General
//TODO
Windows :
//TODO
Linux :
//TODO
Mac OS X :
Heimdall keeps failing with "ERROR: Claiming interface failed!"
You need to disable the default USB drivers with the following commands:
Code:
sudo kextunload -b com.apple.driver.AppleUSBCDC;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMControl;
sudo kextunload -b com.apple.driver.AppleUSBCDCACMData;
I just got my Note 2, I've tried your tool several times and I keep getting this when my phone reboots into download mode:
<took out the garbage>
USB connection seems a bit shaky.
You have a different cable to try?
Dont post logs here. They're ugly. Use pastebin. Please remove all of that. I specifically said not to post that.
Try it again with a better cable. I see it is disconnecting and reconnecting repeatedly. That's a bad cable if I've ever seen one... Odin mode does not have error correction like ADB. Its really picky about having good cables and a good USB port.
When this works, please post that it worked.
jrloper said:
USB connection seems a bit shaky.
You have a different cable to try?
Click to expand...
Click to collapse
not right now, but I tried other USB plugs and its not connecting on those.
---------- Post added 10th May 2013 at 12:00 AM ---------- Previous post was 9th May 2013 at 11:57 PM ----------
AdamOutler said:
Dont post logs here. They're ugly. Use pastebin. Please remove all of that. Holy cow man! I specifically said not to post that.
Try it again with a better cable. I see it is disconnecting and reconnecting repeatedly. Thats a bad cable if I've ever seen one...
When this works, please post that it worked.
Click to expand...
Click to collapse
Sorry, I'm a novice with having to post that stuff. I don't have to post logs much.
I don't understand how the cord could be bad since its the one that came out of the box yesterday. But I don't have access to one right this second
ShotgunSam said:
not right now, but I tried other USB plugs and its not connecting on those.
Click to expand...
Click to collapse
We've seen this a lot. Its your cable. I have several cheap cables that don't work with Heimdall or Odin. Also some usb ports dont work either.
Good job Adam once again. Wonder when they'll eventually just give up and stop pestering Samsung.
Sent from my SCH-I605 using Tapatalk 2
No you!
I do believe that this is my very 1st post on this site. Adam thank you for all of your hard work.
On EDIT: Went into the temp file and individually clicked on each of the .exe files. Rebooted phone and restarted CASUAL. Everything worked fine after that.
Thanks again! Donation sent yesterday.
Tried 2
different cables on 2 different ports. No luck so far. http://pastebin.com/741wqT3T
Any ideas?
This is a brand new Note 2 on the latest OTA which installed at the store when I got it.
Thanks!
Thank You Adam!!! You sir, are a life saver!
Original thread you posted 2 days ago worked for my Note 2 I purchased used on Sunday. Same cable I have connected to my computer for years now, process was butter smooth. Phone updated to 4.1.2 before I had a chance to get home and root.
Only had to battery pull after it hung initially. Thanks! Will send donation as soon as I get PP funds.
Worked on my Note 2 unlocked it to where i can use my Tmobile sim, but it keeps giving me a warning "sorry this sim card is not supported" but i can make calls, i cant add APN settings though.
Jgun33 said:
On EDIT: Went into the temp file and individually clicked on each of the .exe files. Rebooted phone and restarted CASUAL. Everything worked fine after that.
Thanks again! Donation sent yesterday.
Tried 2
different cables on 2 different ports. No luck so far. http://pastebin.com/741wqT3T
Any ideas?
This is a brand new Note 2 on the latest OTA which installed at the store when I got it.
Thanks!
Click to expand...
Click to collapse
Looks like it failed while attempting to install CADI. Do you have administrative permissions?
We may need to make a change to the execution of CADI.
I got an error as well.
http://pastebin.com/ddD8b749
Taking a deep breath...here we go
---------- Post added at 06:05 PM ---------- Previous post was at 05:32 PM ----------
Worked like a charm. Booted right into TWRP. Lost root - but TWRP fixed it
Im getting the same error with numerous usb cables and using different usb ports.
http://pastebin.com/sWSn891k
mmoorman12 said:
I got an error as well.
http://pastebin.com/ddD8b749
Click to expand...
Click to collapse
Looks like your virus scanner trashed CASUAL before you even ran it. Disable your virus scanner.
Osmannm123123123 said:
Im getting the same error with numerous usb cables and using different usb ports.
http://pastebin.com/sWSn891k
Click to expand...
Click to collapse
No you didn't. You're the first to get this error. You have UAC disabled or you have no administrative permissions. Notice the loop while attempting to install drivers. also, it returned "null" as in it returned less a blank line.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download
Remix OS Build
Installation
You must have twrp 2.8.2.0 installed not the newer 2.8.7.0
Place zip on internal or external storage you can do this via adb in recovery
Wipe Cache, Data, and Dalvik
Install zip
Reboot and wait for it to boot.
Not Working
XDA:DevDB Information
Remix OS 2.0 Mad Catz M.O.J.O, ROM for the Mad Catz M.O.J.O.
Contributors
Unjustified Dev
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2016-01-26
Last Updated 2016-01-25
Reserved
Looks amazing, will be getting my MOJO in a few days and installing this. Thank you for your work on this device @Unjustified Dev!
Is everything working?
wow.. very cool!
downloading it now, will install this week.
Drakey83 said:
Is everything working?
Click to expand...
Click to collapse
Sure is
https://www.youtube.com/watch?v=xbVs0xzrYK8
User feedback was posted in preview thread
http://forum.xda-developers.com/showpost.php?p=64987062&postcount=12
Unjustified Dev said:
Reserved
Click to expand...
Click to collapse
Hey man! Great work. You thought at all about trying this on Molly?
I gave it a shot, but must've missed something in the porting process.
npjohnson said:
Hey man! Great work. You thought at all about trying this on Molly?
I gave it a shot, but must've missed something in the porting process.
Click to expand...
Click to collapse
Use my port as a base. I took adt-1 blobs a long time ago . Framework should be identical adt-1 is based on my tree. You'll have to edit storage list to get USB mounted correctly. Just unpack my boot and replace ramdisk and kernel. For audio , bt , WiFi. Sync aosp 5.1 r5 and build wpa_supplicant. Replace wpa supplicant , libwpa client and libhardware legacy. For Bluetooth I built bluetooth.default to fix bt name and pushed my own libbt-vendor . For audio mine is legacy so you will have to rebuild libaudiopolicyservice that isn't legacy which should also give you a policy manager that should get audio going once you add your hal. You may also want to add in those extra Molly drm blobs they weren't needed for me. Should also be able to throw in stock power hal without any issues.
Installed this yesterday and everything works great. Still figuring out the OS but nothing causing problems yet .
The only thing that bothers me ,and I have to figure out if there is a way to disable it, is the sleep time. The options are 0-30 min and not option to disable from what I can see. If the MOJO goes in sleep mode I can't get it to come back on. I am using an air mouse, maybe this air mouse is not able to wake up MOJO. If you have a way around this please let me know.
Either way, things are working great and really love the new OS.
-=UnR34L=- said:
Installed this yesterday and everything works great. Still figuring out the OS but nothing causing problems yet .
The only thing that bothers me ,and I have to figure out if there is a way to disable it, is the sleep time. The options are 0-30 min and not option to disable from what I can see. If the MOJO goes in sleep mode I can't get it to come back on. I am using an air mouse, maybe this air mouse is not able to wake up MOJO. If you have a way around this please let me know.
Either way, things are working great and really love the new OS.
Click to expand...
Click to collapse
It has to be the airmouse I can wake it with kb. This bug was fixed in the kernel a long time ago. About adding never sleep mode I'm not sure that's possible the code for it has been removed you can only configure times. I can add a day option if that makes it better?
Unjustified Dev said:
It has to be the airmouse I can wake it with kb. This bug was fixed in the kernel a long time ago. About adding never sleep mode I'm not sure that's possible the code for it has been removed you can only configure times. I can add a day option if that makes it better?
Click to expand...
Click to collapse
It is an air mouse and keyboard. I tried all the buttons on the air mouse and did not wake it up. I am sure I tried the keyboard as well to wake it up but no luck either. I'll try again and let you know. Maybe try switching to the other USB port and see if that makes a difference. I believe now the air mouse dongle is in USB 3.0. So maybe if I use 2.0 it would get it to work.
One other question, when I flashed the firmware I chose to install SU and noticed that Remix detects the device as rooted and does not allow updates. Would OS Updates work without the SU installed?
-=UnR34L=- said:
It is an air mouse and keyboard. I tried all the buttons on the air mouse and did not wake it up. I am sure I tried the keyboard as well to wake it up but no luck either. I'll try again and let you know. Maybe try switching to the other USB port and see if that makes a difference. I believe now the air mouse dongle is in USB 3.0. So maybe if I use 2.0 it would get it to work.
One other question, when I flashed the firmware I chose to install SU and noticed that Remix detects the device as rooted and does not allow updates. Would OS Updates work without the SU installed?
Click to expand...
Click to collapse
I think there's certain buttons on the kb not sure it wakes for me I'll test later. About ota updates the device isn't official this was a by hand port from the remix ultratablet.
Unjustified Dev said:
Use my port as a base. I took adt-1 blobs a long time ago . Framework should be identical adt-1 is based on my tree. You'll have to edit storage list to get USB mounted correctly. Just unpack my boot and replace ramdisk and kernel. For audio , bt , WiFi. Sync aosp 5.1 r5 and build wpa_supplicant. Replace wpa supplicant , libwpa client and libhardware legacy. For Bluetooth I built bluetooth.default to fix bt name and pushed my own libbt-vendor . For audio mine is legacy so you will have to rebuild libaudiopolicyservice that isn't legacy which should also give you a policy manager that should get audio going once you add your hal. You may also want to add in those extra Molly drm blobs they weren't needed for me. Should also be able to throw in stock power hal without any issues.
Click to expand...
Click to collapse
Alright. Thanks! Anything MOJO specific I should be in the lookout for to remove?
npjohnson said:
Alright. Thanks! Anything MOJO specific I should be in the lookout for to remove?
Click to expand...
Click to collapse
Honestly only thing mojo specific is the audio and power hal which your going to replace. The rest of the executables won't hurt because your init won't use them. Maybe etc/bluetooth/bt-vendor.conf I don't think the Marvell libbt hal checks for this file though.
Great rom! Everything works so far. But how do I get back into recovery after rebooting without flashing root?
Sent from my LG-V400 using XDA Premium HD app
Unjustified Dev said:
I think there's certain buttons on the kb not sure it wakes for me I'll test later. About ota updates the device isn't official this was a by hand port from the remix ultratablet.
Click to expand...
Click to collapse
I tested again and cannot get the device out of sleep with the air mouse/keyboard. You said you can add longer sleep times? If that is the case would you be able to add maybe a day and something longer, maybe a week?
Appreciate the help.
Hi,
I have just flashed my mojo with this SW and I must say I'm pretty amazed.
So far I only came across one issue. Maybe I'm too stupid but how do I remove Icons from the desktop? I can only move them around and I would like some programs to be only in 'start menu'
As for the wakeup feat I tested with Motorola Bluetooth Mouse and it wakes up no problem. All I have to do is to move a mouse. I even tried to turn off the mouse, let it go to standby, turn on the mouse, it connected and when I moved the mouse it woke up.
Also so far all programs work without problem. I wonder if it will be more stable than factory mojo rom that froze on me every 2-3 days.
Edit: MX Player does not want to work. I start a movie and it plays for 2 seconds then the playback freezes. Does anyone have the same issue? Any solution?
I flashed it and everything runs great, pretty amazed to, appreciate to Unjustified Dev....great work.
I have the same fly control problem (whit a MELE f10 pro control) solve by going to Developer Options>Stay awake and Disable USB audio routing (for avoid audio problems whit that particular control model). Tried Mx Player pro any problem here. I try rooting whit towel root unsuccessfully, any suggestions?
dudex1 said:
Great rom! Everything works so far. But how do I get back into recovery after rebooting without flashing root?
Sent from my LG-V400 using XDA Premium HD app
Click to expand...
Click to collapse
Wondering the same thing. I lost root access when I installed RemixOS and can't use any 3rd party app to boot into recovery.
Vudu doesn't work, Flixster crashes at playback.
primo_4c4 said:
I flashed it and everything runs great, pretty amazed to, appreciate to Unjustified Dev....great work.
I have the same fly control problem (whit a MELE f10 pro control) solve by going to Developer Options>Stay awake and Disable USB audio routing (for avoid audio problems whit that particular control model). Tried Mx Player pro any problem here. I try rooting whit towel root unsuccessfully, any suggestions?
Click to expand...
Click to collapse
Kernel has patches to block towelroot. You have to manually go back and fastboot boot recovery and flash chainfire's SuperSU zip if you want root.
DISCLAIMER: Neither I nor XDA or the members of this site can be held responsible for any data loss or hardware damage caused by the use the tools, firmware and applications mentioned or linked to in this thread.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The nabi SE is an Android-based tablet computer produced by Mattel under the Fuhu Nabi line. Released in 2016, the SE runs on Android 6.0 "Marshmallow" utilising a MediaTek MT8127 system-on-chip. Like some of the tablets from their line-up, a number of variants themed after popular children's franchises by Mattel were also produced, differing only in bundled content, branding and certain exclusive apps e.g. streaming video players with variant-specific content; ROMs used for all nabi SE variants are largely the same and appear to be mutually compatible.
Tech specs:
1.3 Ghz MediaTek MT8127 quad-core processor
ARM Mali 450MP GPU
1GB RAM
7" capacitive touch screen with 1024x600 resolution
16GB ROM (8GB user-accessible, expandable to 32GB with a microSD card)
Android 6.0 Marshmallow with Blue Morpho UI
0.3 MP front camera
2 MP rear camera (720p video)
2500mAh rechargeable lithium-ion battery
Sensors: Accelerometer
GPS: no
FM radio: no
Depending on the variant, the tablet may also come bundled with content based on characters from their respective franchises. The American Girl edition for example has videos and games featuring characters from the line, namely Isabelle Dance Studio, Grace Sweet Shop, Maryellen Rocket Rally and Scene Sounds. As with most children's tablets, it has parental controls built in and Google Play services.
Magisk Root
So far Beta 16.3 is known to work (albeit with some issues) as previous versions churn out a corrupt image. I am not sure why flashing Magisk through TWRP won't work, but I might look into it some time.
Bootloader unlock
That in my opinion is what I like about the Nabi compared to the LeapFrog Epic I previously covered in another thread. Dunno if it does matter to unlock, but since there is at least some boot-level enforcement going on I'd say you should perform a bootloader unlock to be sure. Make sure to install ADB/Fastboot drivers, then in developer options, tick OEM Unlocking to allow the bootloader to be tampered with. Turn off the device, then reboot to fastboot mode by holding power and volume up for a few seconds until a DOS-ish prompt appears. Select fastboot mode, then press volume down. Now plug in the device to your PC, and in a command prompt, key in "fastboot oem unlock" sans quotes. A warning will then appear, which you should say yes to. If done properly, you should now have an unlocked Nabi SE.
Issues
Tablet is stuck in fastboot mode
I've heard from a number of parents over at the Nabi Facebook page that their children's tablets somehow get stuck at this prompt...
Code:
=> FASTBOOT mode...
or this...
Code:
Select Boot Mode:
[Recovery Mode]
[Fastboot Mode] <<=
[Normal Mode]
...likely due to kids unwittingly fiddling around with the volume and power buttons. I've made a small batch-based utility for getting them out of limbo, but as I only own a regular Nabi SE and an American Girl variant, I'd like to ask those who own the other editions to PM me for details. Once that's done I'll release it ASAP.
Forced encryption
Encryption is permanently enabled by default in this device. Which is a good thing as far as security goes, but it's crapshoot when you're trying to make backups. I think this could be fixed with Magisk but I haven't thoroughly tested it yet. You can however format /data and mount it through TWRP though, if that's any consolation.
Stock ROMs:
NOTE: The following ROMs can only be flashed through SP Flash Tool v5.1532. Make sure to have a full backup of your device ready before attempting any flashing procedures!
Code:
NBTY07SMKG-US (vanilla Nabi SE):
https://androidfilehost.com/?fid=15664248565197191210
NBTY07SMKG-US-AG (American Girl edition - ABD7AG20160823A00):
https://mega.nz/#!b5RgFTgK!da1QDYFo3EMZI5SqNtY2lHPUqz2g6eUJJTI_rF1t4wI
https://www.androidfilehost.com/?fid=11410963190603899020
NBTY07SMKG-US-BB (Barbie edition):
https://www.4shared.com/s/fvn6nAvZ_gm
https://androidfilehost.com/?fid=11410963190603905324
NBTY07SMKG-US-HW (Hot Wheels edition):
https://www.4shared.com/s/fa3Ez7lgOfi
https://androidfilehost.com/?fid=11410963190603905325
Nabi SE demo-to-retail conversion package (will post instructions later):
https://mega.nz/#!HxQGWA5Z!7A4N1FDWeSDGBFG3ASmLydWqjeIUP8z253HXZJ7Cxpk
Custom recovery images:
TWRP 3.0.2.0
NOTE: Same note as the full scatter packages above. Can be flashed either through fastboot or using SP Flash Tool. If you are unable to boot to fastboot mode in order to do a bootloader unlock and thus flash the following recoveries, try flashing this LK binary attached in this post.
Code:
https://github.com/huckleberrypie/device_Mattel_NabiSE
https://github.com/TeamWin/device_Mattel_NabiSE
More screenshots can be found here:
https://imgur.com/a/JT1HC
TWRP 3.0.2.0 for American Girl edition
NOTE: Same note as the full scatter packages above. Can be flashed either through fastboot or using SP Flash Tool.
Code:
https://github.com/huckleberrypie/device_Mattel_NabiSE/releases/tag/1.0-AG
More screenshots can be found here:
https://imgur.com/a/oyPO2I0
Carliv Touch Recovery
Mad props to AMR Development for this one.
Code:
https://mega.nz/#!z0ZHwC4a!2AlpIQJTxJnpVYa29ZFKqXQzQThO-vBvS4xnBQndhCg
Source tree: https://mega.nz/#!v0YlCDJI!5NXZcsJrJf-JdxHCcC_CiSXtXZwCENfr5rkdMBfQyh8
More screenshots can be found here:
https://imgur.com/a/mZR3f
Custom ROMs:
TBD; debloated stock ROM being planned
Known variants
NBTY07SMKG-US / Nabi SE
3.0.9 - ABD7TY20160831A00
NBTY07SMKG-US-AG / Nabi SE (American Girl)
3.0.10 - ABD7AG20160823A00
NBTY07SMKG-US-BB / Nabi SE (Barbie)
???
NBTY07SMKG-US-HW / Nabi SE (Hot Wheels)
???
NBTY07SMKG-US-DM / Nabi SE (Store Demo Unit)
3.0
NBTY07SMKG-US-TF / Nabi SE (Thomas and Friends; cancelled)
???
I'm getting bootloops after following directions directly on a nabi se, not asking for responsibility but maybe people shouldn't follow this guide...
Gigabuster said:
I'm getting bootloops after following directions directly on a nabi se, not asking for responsibility but maybe people shouldn't follow this guide...
Click to expand...
Click to collapse
Did you flash this on a stock vanilla Nabi SE using SP Flash Tool? I never had any problems getting it to run on my SE; I don't get how this has been causing bootloops on your unit. :/
instructions
blakegriplingph said:
Did you flash this on a stock vanilla Nabi SE using SP Flash Tool? I never had any problems getting it to run on my SE; I don't get how this has been causing bootloops on your unit. :/
Click to expand...
Click to collapse
c
Can you help me i been trying to get a demo to retail. but i been unable im not a computer tech i been able to get into de fastboot mode , but i dont know what to do next.
monas3 said:
c
Can you help me i been trying to get a demo to retail. but i been unable im not a computer tech i been able to get into de fastboot mode , but i dont know what to do next.
Click to expand...
Click to collapse
In this case you don't have to use fastboot. Turn off the device (there doesn't seem to be any other method of turning it off other than draining the battery on purpose :/), then perform a readback using SP Flash Tool. I don't have the scatter file from the demo unit atm (addresses/offsets specific to demo are in that text file), but I'll PM you the full details ASAP.
There, just built another TWRP variant for the American Girl edition. Dunno if anyone would care but I decided to do so should anyone somehow get their hands on such a unit. Links are on my original post.
blakegriplingph said:
There, just built another TWRP variant for the American Girl edition. Dunno if anyone would care but I decided to do so should anyone somehow get their hands on such a unit. Links are on my original post.
Click to expand...
Click to collapse
Thank you!
cjlopez213 said:
Thank you!
Click to expand...
Click to collapse
I presume you happen to have an American Girl tablet as well, right? Just let me know if you run into anything and make sure you made a backup of your tablet's firmware first, OK?
blakegriplingph said:
I presume you happen to have an American Girl tablet as well, right? Just let me know if you run into anything and make sure you made a backup of your tablet's firmware first, OK?
Click to expand...
Click to collapse
Yeah I got a Barbie for my youngest and an American Girl for my older daughter. I think the Barbie tablet is fine without root. I'll be sure to keep you posted in case I get some errors.
cjlopez213 said:
Yeah I got a Barbie for my youngest and an American Girl for my older daughter. I think the Barbie tablet is fine without root. I'll be sure to keep you posted in case I get some errors.
Click to expand...
Click to collapse
Cool! I've actually been looking for someone who owns a Barbie and Hot Wheels edition for quite some time lol. Needed the firmware from those for my collection, and of course for the greater good, if you know what I mean.
Anyone up to coaxing Nabi into spilling at least some kernel sources for the SE? The GPL sources page has sources for the MT8127 variant of the Junior, but the one for the SE is MIA for whatever reason. A friend of mine has tried contacting their Twitter to no avail. :/
Excuse the double-post, but for the sake of science I decided to tear down one of my SEs to see what's inside besides that FCC approval listing. By the looks of it, the SE uses a subframe presumably for a bit more rigidity. The way the SE is constructed is a bit of a double-edged sword, i.e. you can make it less susceptible to kids screwing the lid off, but servicing or replacing the battery can be quite a chore to pull off. At least the logic board has some test points labeled
https://imgur.com/a/IvLrErv
There, just uploaded the Barbie and Hot Wheels ROMs. A friend of mine just got his hands on the Barbie and Hot Wheels tablets so it had to be done.
Nabi Elev-8
Hi, I was just wondering if anyone has been able to root the Nabi Elev-8? If anyone could point me in the direction to try to root this, I would very much appreciate it.
DaddyShortLeggs said:
Hi, I was just wondering if anyone has been able to root the Nabi Elev-8? If anyone could point me in the direction to try to root this, I would very much appreciate it.
Click to expand...
Click to collapse
Not sure about that tbh as I don't have an Elev-8 with me.
blakegriplingph said:
Not sure about that tbh as I don't have an Elev-8 with me.
Click to expand...
Click to collapse
Well I downloaded King root and tried to root it twice and it didn't work. I woke this morning and tried it again but this time it successfully rooted. Does anyone know if I can install twrp and any roms out there for it?
DaddyShortLeggs said:
Well I downloaded King root and tried to root it twice and it didn't work. I woke this morning and tried it again but this time it successfully rooted. Does anyone know if I can install twrp and any roms out there for it?
Click to expand...
Click to collapse
Not from what I can tell. All I know is only the original Nabi, the Nabi 2, the DreamTab and the SE have support but not the Elev-8.
blakegriplingph said:
Not from what I can tell. All I know is only the original Nabi, the Nabi 2, the DreamTab and the SE have support but not the Elev-8.
Click to expand...
Click to collapse
Damn that sucks. Well I at least got it working better than what it has been before I rooted it. Now I just have to figure out how to use SuperSU-Me Pro to get rid of King root and purify.
DaddyShortLeggs said:
Damn that sucks. Well I at least got it working better than what it has been before I rooted it. Now I just have to figure out how to use SuperSU-Me Pro to get rid of King root and purify.
Click to expand...
Click to collapse
I have a question but let me say that I uninstalled kingroot and purify and I successfully unlocked my bootloader. Is there a way that I could get twrp for my Nabi Elev-8?
It is a fairly new device so I haven't seen anything on it but I'm hoping someone could point my in the right direction. Any info would be helpful. Thanks!
Same here, looking for root!
Coolpad root
Good luck on this to you I am working as well and will post what I find
Picked up one of these today, we just started working on it a few minutes ago, I'll post the method once done. This could be hours, days, months, who knows, We do have fastboot and the Coolpad Kit from elsewhere on the forums so it shouldn't be hard. But we are working on it.
Same here I really want root, oddly for fastboot oem unlock it doesn't unlock , I have oem unlock enabled in developer options but when I run the command fastboot flashing unlock or fastboot oem unlock or pretty much any command besides fastboot getvar all it comes back with something like FAILED remote unknown command and I have no idea why I have the cool pad legacy/lithium cp3705a if anyone can lend me some knowledge on why the fastboot commands don't work that would be nice I was going to flash a gsi and try to patch a stock boot image via magisk but I can do anything without unlocking the bootloader first, I'm hoping it's not a kernel related issue
sawclan22 said:
Same here I really want root, oddly for fastboot oem unlock it doesn't unlock , I have oem unlock enabled in developer options but when I run the command fastboot flashing unlock or fastboot oem unlock or pretty much any command besides fastboot getvar all it comes back with something like FAILED remote unknown command and I have no idea why I have the cool pad legacy/lithium cp3705a if anyone can lend me some knowledge on why the fastboot commands don't work that would be nice I was going to flash a gsi and try to patch a stock boot image via magisk but I can do anything without unlocking the bootloader first, I'm hoping it's not a kernel related issue
Click to expand...
Click to collapse
Yeah still working on it, waiting for some pie PoCs to come out. But fastboot is borked. I've requested the source code from them we'll see how that goes, doubt it will go anywhere. Can't even find the proper drivers for it. MTKTool is outdated so it can't even get a read on the FS to make a scatter file. All one click apps I tried didn't work so I wouldn't recommend those. OneClickRoot said it could root it but I'm not about to pay them to find out.
I did find a binary(locksettings) in system that allows you to set and remove passwords via command line which seems a bit insecure, but possibly exploitable, and an empty "cdrom_install.iso" in /system/etc But It just says:
"This directory contains the raw data that OEMs want to expose
to end-users.
Due to the limitation of mass storage. The cdrom ISO file should
be larger than 600KBytes.
If you put less files into this directory. Then it will create
a dummy file to fill the gap."
With a nice 616KB pad file.
That's all I've been able to get so far.
Thanks for the update that sums up what I've got as well although i didn't see that system img
---------- Post added at 03:51 AM ---------- Previous post was at 03:47 AM ----------
Oddly my device seems to be having some sort of bug. The touchscreen will just randomly lock up , I've reset the device , I realized it doesn't so it in safe mode , so I tried deleted apps from adb shell that did nothing , but since it works in safe mode and the device has project treble support I feel as though flashing a gsi would fix the problem , but I can't so that with a locked bootloader
sawclan22 said:
Thanks for the update that sums up what I've got as well although i didn't see that system img
---------- Post added at 03:51 AM ---------- Previous post was at 03:47 AM ----------
Oddly my device seems to be having some sort of bug. The touchscreen will just randomly lock up , I've reset the device , I realized it doesn't so it in safe mode , so I tried deleted apps from adb shell that did nothing , but since it works in safe mode and the device has project treble support I feel as though flashing a gsi would fix the problem , but I can't so that with a locked bootloader
Click to expand...
Click to collapse
You might want to go through your apps and disable a bunch of the bloat. They had like 3 facebook managers, installers and stuff in there. That could be doing it. I haven't had any such issues but i've only had the phone a few hours and have been in a shell exploring it most of that time.
Update: EDL Mode is accessible. We haven't been able to successfully do anything with it yet due to lack of a firehose, but 9008 mode does work with EDL Cable. If anyone has a SDM450 firehose around that would be ideal.
I already noticed edl mode was there was planning on finding out what to do today , I have a firehouse for the board which is prog_emmc_firehose_8953_ddr.mbn , but I wasn't sure how that worked I'm not to familiar with edl mode or what it can do , also I'm not a dev just an experienced Android / Linux user
---------- Post added at 01:32 PM ---------- Previous post was at 01:30 PM ----------
What would u even use to flash in edl mode? Say a gsi , because there's no stock firmware we can extract , but we can always get a rooted gsi if I'm not mistaken because the device does have project treble support
Sapphiress said:
You might want to go through your apps and disable a bunch of the bloat. They had like 3 facebook managers, installers and stuff in there. That could be doing it. I haven't had any such issues but i've only had the phone a few hours and have been in a shell exploring it most of that time.
Update: EDL Mode is accessible. We haven't been able to successfully do anything with it yet due to lack of a firehose, but 9008 mode does work with EDL Cable. If anyone has a SDM450 firehose around that would be ideal.
Click to expand...
Click to collapse
The firehouse for the oppo a71 has same specs board RAM and soc would that work
sawclan22 said:
The firehouse for the oppo a71 has same specs board RAM and soc would that work
Click to expand...
Click to collapse
I'll see if I can find one. They have the board incorrectly listed as both an MTK board and as an msm8953 even though from what I've been able to find msm8953 is strictly the snapdragon625. And Snapdragon 450 doesn't have an msm designation. This thing is a mess inside.
It's been awhile since I've done this mind you. Android has changed a bunch since the 2.X and 4.X days. I've been on a Nexus 6P for years which is open by default.
Wish it was as easy as installing gingerbreak and tapping root like the old days. Lol
---------- Post added at 03:14 PM ---------- Previous post was at 03:03 PM ----------
sawclan22 said:
What would u even use to flash in edl mode? Say a gsi , because there's no stock firmware we can extract , but we can always get a rooted gsi if I'm not mistaken because the device does have project treble support
Click to expand...
Click to collapse
I would get temp root via a RCE or EoP pull the boot image, modify it and flash it in EDL therefore enabling fastboot and making the phone ready for TWRP. After that it's just a matter of writing a program that does this for you and the phone would be ready for development.
Well I've done all I know how to do I'll just leave it to you guys and keep an eye on this forum
Hey Sapphires,
Have you generated the root process for the Coolpad Legacy yet?
[email protected]
manoftech said:
Hey Sapphires,
Have you generated the root process for the Coolpad Legacy yet?
[email protected]
Click to expand...
Click to collapse
Waiting for a poc or a firehouse to surface. Android 9 doesn't have many exploits available yet.
Device Unlocking Process Status?
Have we got anywhere with the device unlocking and rooting procedure with this device.
djdruin said:
It is a fairly new device so I haven't seen anything on it but I'm hoping someone could point my in the right direction. Any info would be helpful. Thanks!
Click to expand...
Click to collapse
dravenz7 said:
Have we got anywhere with the device unlocking and rooting procedure with this device.
Click to expand...
Click to collapse
Nope. we are also NOT vulnerable to CVE-2019-2215 at least on my device with the June Patch. Just waiting for a valid exploit.
This is as far as it gets.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You guys suck
diag port
I don't know if you guys figured this part out yet or not but I was able to open the engineering menu and turn on the diagnostics port and modem. I'm not very familiar with using it to my advantage but I used quick shortcut maker to open it. It was under yulong labtest I believe. One of the menus are all in chinese so I'm not real sure what else it would let you access.
TreyVega said:
You guys suck
Click to expand...
Click to collapse
Well let's see you do something there buddy, obviously you're the expert on the subject.
Cracking enterprise level security isn't just clicking a button. and you ain't paying me. I have a stack of phones and other devices to work on and other more pressing things to do with my life. So, kindly, take your opinion and shove it, root will be released when it's released.
m3nty said:
I don't know if you guys figured this part out yet or not but I was able to open the engineering menu and turn on the diagnostics port and modem. I'm not very familiar with using it to my advantage but I used quick shortcut maker to open it. It was under yulong labtest I believe. One of the menus are all in chinese so I'm not real sure what else it would let you access.
Click to expand...
Click to collapse
EDL mode won't help without the proper mbn, none of which that are publicly available work. Or if you're talking about the hidden flasher activity we found that awhile ago but I haven't really looked too far into it as i don't have a USB-C OTG drive.
I searched the web and the forum I couldn't find any info about SM-A115U ( Boost Mobile USA)
I have Samsung 6 edge plus & I was able to root it back in 2017 using CF AutoRoot with SM-G928C (zenlte-zenltejv).
SM-A115U seems like it's one of the challenging phone to have the bootloader unlocked, I checked the 'changing time method prior to 7 days' and going to 'updating firmware' then I enabled Dev. Mode but it didn't work (the OEM unlock option is not showing)
Therefore does anyone have any Idea?
How can I unlock the bootloader myself ?
I patched with Magisk but when flashing with ODIN 13.4.1 It didn't work due to the bootloader being locked,again the OEM unlock option is not showing.
I wish I knew. I'm trying to do the same thing. There are directions for OTHER models - apparently we need to change the firmware from the U to the M (Latin America / Peru etc) --- that will give us the oem unlock option...
unfortunately for me I've tried a few firmware's and it seems there is -something - not compatible which is causing an error in ODIN to fail. -- Likely the fact that we have the 115U and I'm trying to put software from the 115 (something else - that has oem unlock option)
I am under the impression at this point that 100% of every US samsung snapdragon processor on every model number phone is impossible to root.
-add to that something called Qualcomm secure boot that is also apparently a problem now; my knowledge id vague on this point... but I believe we will need to buy an Exynos version from overseas to get the bootloader unlocked.
I would love for someone to show us otherwise how to do it.
I know from researching the s20 us version that some one is offering a paid service to use proprietary samsung tools that CAN unlock the snapdragon bootloader; for a fee.
I dont know:
who it is
how to contact them
how much it costs
or if it can be done for the a115u.
edit - this link leads to more info - much more complete
Galaxy A11 SM-A115 Need TWRP
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are...
forum.xda-developers.com
the a115u doesnt offer 'oem unlock' in developer mode.
The a115u1 DOES. The following is a link that worked for me; slow download speeds so expect a 3 hour wait... unless you pay.
i am still working on it; will post more if I have success.
A115u1 firmware: A115U1UEU2ATG2 / OYM2ATG2 v10
PDA/AP Version A115U1UEU2ATG2
CSC Version A115U1OYM2ATG2
MODEM/CP Version A115U1UEU2ATG2
Region USC — United States
Build Date 2020-07-03
Changelist 18814262
OS Q
OS Version 10
https://www.full-repair-firmware.co...DL0ExMTVVMVVFVTJBVEcyL0ExMTVVMU9ZTTJBVEcyLw==
New Baseband is
A115U1UEU2ATG2
SO what does the UEU mean?
Update; I was having difficulty getting into download mode.. still cant seem to manually achieve it.
I can access a couple recovery menus but not the download mode one (without the app)
To get into Recovery you:
Turn off the device.
Press and hold the Volume Up key, then press and hold the Power key.
When you see Samsung Galaxy A11, release the Power key but continue holding the Volume Up key.
When you see the Android Recovery screen, release the Volume Up key.
To get the (blue) screen for unlocking bootloader:
Access the Blue custom OS menu:
Press and hold the Volume Up & DOWN keys, then press and hold the Power key.
When you see Samsung Galaxy A11, release the Power key but continue holding the Volume Up & DOWN keys.
When you see the Android Recovery screen, release the Volume Up & Down keys.
Phone will go black - reboot- SAMSUNG logo will appear and you'll need to wait while it reinstalls the OS...
Then you need to re open Developer options and usb debugging etc ...
Now you can work on TWRP and Root/ Magisk (I dont know how yet but will get there)
The A05U is in the same boat as the A115U. https://forum.xda-developers.com/t/need-default-prop-file-for-sm-a205.4125991/
There you will find my working theory that may help solve this puzzle. Anyone with a little experience can get a hex editor and i will pm you the offset addr. in which the firmware keys reside within the AP image...(only for the 205...for now)...Also, another attack vector is to decompile the system image and go in and change default.prop OEM_UNLOCK_SUPPORTED=0 TO 1, recompile and package it as a standalone .tar or .zip and flash in Odin (assume patched version 3.14.1 cuz i had some success FRP'ing with it). The reason i recommend standalone is due to the fact that fota.zip is also signed with the same 8 digit key as the binaries, however the zip file itself is encrypted and will not allow for manipulation to the contents.
Fastboot, ADB, and so far Combo Files (of which i do have for the A115, [205 combos were worthless] and am reluctantly about to tes, as this is my Daily Driver). So if anyone is interested in A115 Engineer binary, I have acquired one [link on pm].
Back to vector 1...I am about to begin the tedious process of aqcuiring the firmware keys for the A115, once I have them it will hopefully be a matter of time before this is done. All we need is for one character to change: OEM_UNLOCK_SUPPORTED = 0. It needs to be 1. But, finding digital signatures enables us the ability to rebrand, mix n' match and circumvent firmware device specific subjectivity.
Blombardo said:
edit - this link leads to more info - much more complete
Galaxy A11 SM-A115 Need TWRP
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are...
forum.xda-developers.com
the a115u doesnt offer 'oem unlock' in developer mode.
The a115u1 DOES. The following is a link that worked for me; slow download speeds so expect a 3 hour wait... unless you pay.
i am still working on it; will post more if I have success.
A115u1 firmware: A115U1UEU2ATG2 / OYM2ATG2 v10
PDA/AP Version A115U1UEU2ATG2
CSC Version A115U1OYM2ATG2
MODEM/CP Version A115U1UEU2ATG2
Region USC — United States
Build Date 2020-07-03
Changelist 18814262
OS Q
OS Version 10
https://www.full-repair-firmware.co...DL0ExMTVVMVVFVTJBVEcyL0ExMTVVMU9ZTTJBVEcyLw==
New Baseband is
A115U1UEU2ATG2
SO what does the UEU mean?
Update; I was having difficulty getting into download mode.. still cant seem to manually achieve it.
I can access a couple recovery menus but not the download mode one (without the app)
To get into Recovery you:
Turn off the device.
Press and hold the Volume Up key, then press and hold the Power key.
When you see Samsung Galaxy A11, release the Power key but continue holding the Volume Up key.
When you see the Android Recovery screen, release the Volume Up key.
To get the (blue) screen for unlocking bootloader:
Access the Blue custom OS menu:
Press and hold the Volume Up & DOWN keys, then press and hold the Power key.
When you see Samsung Galaxy A11, release the Power key but continue holding the Volume Up & DOWN keys.
When you see the Android Recovery screen, release the Volume Up & Down keys.
Phone will go black - reboot- SAMSUNG logo will appear and you'll need to wait while it reinstalls the OS...
Then you need to re open Developer options and usb debugging etc ...
Now you can work on TWRP and Root/ Magisk (I dont know how yet but will get there)
Click to expand...
Click to collapse
I call bullcrap. I've been trying all afternoon to root a SM-A115U. I was finally able to flash A115U1U (took 2 hours). However, I have had absolutely NO LUCK obtaining root with Magisk. Please explain your process using Magisk, what version Odin, what version Magisk, what process. Because all I have had is soft bricks.
Show us a picture of root checker saying its rooted...because I bet it isnt.
Sorry this phone is a piece of garbage... I wont use it and am not interested in wasting my time messing with it...
I assure you it is rooted - took me about 12 hours to get it there and when I saw no TWRP - and No NFC on the hardware side.. I was done with this thing.
If I dig it out of the shelf where its collecting dust - and turn it on - and get a screenshot - and I remember to log back in here.. I'll give it to you...
But it is 100% properly rooted with magisk - took me ages to figure it out and I soft bricked it once in the middle. there is no way I could possibly walk you through it and I probably couldnt do it again myself unless I spent another 5 hours messing around with it.
I simply followed tutorials - then downloaded multiple versions of Odin - found a shady looking one from some unsupported place with developer names I couldnt even tell you... it was a custom version of odin for sure.
On the magisk side i just used the official one and followed their directions on how to make the file on the phone / move to pc/ modify / move back to phone and install...
on the TWRP side I found a developer who walked me through how to request the source code from samsung; I did.. they provided it.. and I gave up at that point... the dev was willing to help but I dont care anymore and am looking for a better phone...
Blombardo said:
Sorry this phone is a piece of garbage... I wont use it and am not interested in wasting my time messing with it...
I assure you it is rooted - took me about 12 hours to get it there and when I saw no TWRP - and No NFC on the hardware side.. I was done with this thing.
If I dig it out of the shelf where its collecting dust - and turn it on - and get a screenshot - and I remember to log back in here.. I'll give it to you...
But it is 100% properly rooted with magisk - took me ages to figure it out and I soft bricked it once in the middle. there is no way I could possibly walk you through it and I probably couldnt do it again myself unless I spent another 5 hours messing around with it.
I simply followed tutorials - then downloaded multiple versions of Odin - found a shady looking one from some unsupported place with developer names I couldnt even tell you... it was a custom version of odin for sure.
On the magisk side i just used the official one and followed their directions on how to make the file on the phone / move to pc/ modify / move back to phone and install...
on the TWRP side I found a developer who walked me through how to request the source code from samsung; I did.. they provided it.. and I gave up at that point... the dev was willing to help but I dont care anymore and am looking for a better phone.
Click to expand...
Click to collapse
Since it's just sitting on a shelf collecting dust I would gladly take it off your hands to see what I can figure out, see we can make rooting and custom recovery a bit less complicated for other users. I can't risk bricking mine at the moment as its my daily driver and my hubby would likely have a melt down if I did something to it if interested pm me
it took me almost 10 minutes to get that crappy a11 to boot up; catch up with a million notifications and open the root checker for you...
I'm not lying nor an idiot; I am also not interested in dealing with jerks who are rude. At this point ZagNutty you will need to be more polite to me and others if you expect help... Generally I'm not in a position to offer assistance with Android development as I'm a novice myself.
Here is your image...proving my root; or that I have good photoshop skills...
a11 Root Checker Basic.jpg
drive.google.com
@giddingsgrl I would be happy to sell this phone so long as I wasnt loosing too much money on the deal; I'm not giving it away... I will just add it to the pile of random devices on my shelf for when we have game night and I need spares for my drunk buddies...
send me a PM if you want to buy. I'm not looking to sell but would for just below retail.
I will add the patched version of odin I used to my temp folder on google drive; set to delete june 2021.
Temp delete on June 2021 - Google Drive
drive.google.com
I had a heck of a time getting the bootloader to activate on this model; I had to use a third party tool to reboot into bootloader a few times = tool is called Force Load bootloader Samsung+300K+Tool
and is in that to be deleted folder I shared.== also found online randomly
-And LAST here is my 21 page document on the a11; which I had no intention of sharing with teh world... but I redacted my imei and now its safe to share... not all is valid; much is my own personal notes... so dont look at this like some tutorial that will be perfect... it includes steps I took that nearly Bricked this thing - along with causing a bootloop I had to fix -- then a wrong storage size problem; along with my ways of correcting the issues to make it work... SO TREAD LIGHTLY or you will bootloop or break it...
Android Samsung a115u
0Basic tutorial: https://forum.xda-developers.com/t/guide-the-correct-way-to-flash-custom-roms.3885962/ General Steps to take on PC I. Device Drivers 2. Android SDK 3. Random tools for your device if needed 4. New Firmware (if needed) plus GAPPS if not included 5. Custom Recovery - TWRP 6. Get...
docs.google.com
I achieved Magisk root on my A115U by first crossflashing it to the U1 unlocked firmware using the patched Odin found here: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/
Then I enabled the OEM unlock option in the dev settings, went to download mode, and unlocked the bootloader. After that, I followed the instructions here to get Magisk up and running. It is a fairly simple process.
I even only flashed the U1 bootloader over the original locked down U bootloader for ****s and giggles at first and the phone to my surprise booted up normally, it still reported itself as being a SM-A115U, but the OEM unlock option actually appeared in the dev settings. Great method if you don't want to factory reset the phone.
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see that the phone's original CSC is TMK, which means that it was Metro by T-Mobile branded when it left the factory. I have since sold the phone though, so I cannot help further.
Before:
After:
You have to properly extract the boot image from the A11's Odin firmware files and patch it using the Magisk app to get root, otherwise you will softbrick like I did when I tried the first time. My screenshot shows Magisk as being installed, which means that the phone has root. Also here's my screenshot of the Viper4Android Magisk module installed and working perfectly, that's more then enough proof that I got the A11 rooted.
I showed you my ss of the root checker showing that I had root... another person has confirmed its working.. thats two people who have root on this paper weight.
How about you pony up 100 bucks and I'll ship you mine... its rooted and working fine... lol
What is the best TWRP to use with the SM-A115U/SM-A115U1?
MOD ACTION:
Thread cleaned.
Guys, please post your messages in a polite manner and be civil to each other. Remember what Rule 2 says:
2. Member conduct.
2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It is unacceptable to post nude or pornographic imagery, which includes the exposure of male or female genitalia and / or female breasts.
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.
2.5 All members are expected to read and adhere to the XDA rules.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
raykai said:
What is the best TWRP to use with the SM-A115U/SM-A115U1?
Click to expand...
Click to collapse
Hey, saw your PM, but just going to post here so anyone can see this. Put the wrong link, sorry. This is the link: https://blog.d204n6.com/2020/08/rooting-samsung-devices-2020-with.html
And I used Frija to download the latest U1 firmware. Search for it in the forum search bar and download it. As for TWRP, another XDA member made an unofficial build for the A11 here.
@TNSMANI Is it possible if you or another admin can create a device forum for the Galaxy A11?
Wish39 said:
@TNSMANI Is it possible if you or another admin can create a device forum for the Galaxy A11?
Click to expand...
Click to collapse
It will have to be done by the Admins not by a Moderator. Please post your request HERE with justification.
Zagnutty said:
I call bullcrap. I've been trying all afternoon to root a SM-A115U. I was finally able to flash A115U1U (took 2 hours). However, I have had absolutely NO LUCK obtaining root with Magisk. Please explain your process using Magisk, what version Odin, what version Magisk, what process. Because all I have had is soft bricks.
Show us a picture of root checker saying its rooted...because I bet it isnt.
Click to expand...
Click to collapse
Can you tell me what you used to flash the a115u1? I'm trying to do the same with a a115u and failing everywhere
Bringtheice said:
Can you tell me what you used to flash the a115u1? I'm trying to do the same with a a115u and failing everywhere
Click to expand...
Click to collapse
I also already have a115u1 rooted with magisk and twrp installed and xposed framework. It was passing safety net before I installed the xposed
Wish39 said:
You have to properly extract the boot image from the A11's Odin firmware files and patch it using the Magisk app to get root, otherwise you will softbrick like I did when I tried the first time. My screenshot shows Magisk as being installed, which means that the phone has root. Also here's my screenshot of the Viper4Android Magisk module installed and working perfectly, that's more then enough proof that I got the A11 rooted.View attachment 5265759
Click to expand...
Click to collapse
How did you get viper working properly?
Wish39 said:
Hey, saw your PM, but just going to post here so anyone can see this. Put the wrong link, sorry. This is the link: https://blog.d204n6.com/2020/08/rooting-samsung-devices-2020-with.html
And I used Frija to download the latest U1 firmware. Search for it in the forum search bar and download it. As for TWRP, another XDA member made an unofficial build for the A11 here.
@TNSMANI Is it possible if you or another admin can create a device forum for the Galaxy A11?
Click to expand...
Click to collapse
Hi there, I want to know how do you choose which U1 firmware to download? one with the same CSC such as ATT for ATT (for example) or XAA for ATT would be fine as well?