{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Supported Models:
Galaxy Tab Active Pro 10.1 SM-T547U, SM-T547U1 and SM-T547W.
US/Canada bootloader unlock thread:
here
Download & Guide:
1. Unlock your bootloader.
2. Download TWRP for Tab Active Pro 10.1: gtactivexl and extract to recovery.img
3. Download and install magisk stable
4. Press the Install button in the Magisk card
5. Make sure “Recovery Mode” is checked in options. In most cases it should already be automatically checked.
6. Choose “Select and Patch a File” in method, and select the recovery.img.
7. Reboot to download mode and flash vbmeta_disabled.tar in AP slot and reboot. Device will reboot to stock recovery mode prompting you to wipe data so wipe data and reboot to download mode again.
8. Use 7zip to compress the patched recovery.img to tar (rename it to recovery.img after patch).
9. Put the the patched TWRP tar for your device with Odin in the AP slot and click start.
10. Reboot to recovery via recovery key combo.
11. Disable encryption:
- Go to Advanced > Terminal, type: multidisabler.If vendor complain about free space left on device, will attempt to resize vendor. and it ask to - Run multidisabler again!.- Type: multidisabler again. will see - Finished. when done.12. Go back to Wipe > Format Data > type yes.
13. Reboot to system, Enjoy.
Magisk in Recovery:
If your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.
Since Magisk now hijacks the recovery, there is a special mechanism for you to actually boot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.
As a summary, after installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Long press volume up) → (Recovery Mode)
(Note: You CANNOT use custom recoveries to install or upgrade Magisk in this case!!)
Click to expand...
Click to collapse
Note:
To disable encryption manually:
You need to replace fileencryption=ice with encryptable=ice only in userdata line (maybe rest lines) in vendor/etc/fstab.qcom
To avoid stock recovery restoration manually:
Rename system/recovery-from-boot.p to recovery-from-boot.p.bak
Click to expand...
Click to collapse
Support:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Telegram group
Bugs:
- Encryption not fully working.
Thanks:
TWRP team
@jesec for unlock guide
@ianmacd for multidisabler
Sources:
Kernel tree
Device tree
Changelog:
30.11.2021 - Update to TWRP 3.6.0
- Update multidisabler
28.05.2021 - Initial Release.
T547U – A Perfect Device for Android Auto Head Unit
Afaneh, thanks for your great work. SM-T547U is a very special device, manufactured in 2019, and ignored since then. What I mostly like about TWRP is its excellent and clean Backup & Restore of the entire Android Operating System, everything done outside of Android environment. I have tested this TWRP brought forward by Afaneh on my “Galaxy Tab Active Pro” and it works without flaws.
I have bought this special device to install it in my car as a head unit. Checkout the web and see for yourselves what guys are doing with their tablets to bypass the expensive head units manufactured by the OEM like Kenwood, Alpine, but these OEM head units lack full compatibility with Android devices. The current Android Auto is still in development stage, it takes so long to connect with Android devices and whenever it does so, only about five apps in your android device are synced; not worth it. Whenever these manufacturers create new things, they downgrade their innovations at the same time to save money. The new 10 inches screen sold by these manufacturers no longer come with DVD function, the offline GPS removed and Google map added so that you pay to navigate the streets, their WIFI-certified does not necessarily mean that you can use it to navigate the internet and update softwares, but just to connect your external devices,…the list is long. Below is a link to an example of what I want to do with my tablet…
According to the above video which was recorded in 2017, Root + Xposed are needed to carry out the project, and since Xposed was not yet available by then he recommended choosing SM-T825, most especially for those living in USA and for compatibility with AT&T.
Well, as for me, I am choosing T547U because its technical features are far better than that of T825. Also remember that T547U is a North American model and it is compatible with all registered telecommunication companies in the USA and Canada. When I bought T547U, it came with Canadian Android version, and after unlocking the bootloader, I installed the USA Android version. See the attached image called "CSC_Code", showing all the available companies in the USA that you can switch to, for their extra services if you want. Xposed is available for Android 10_Q and 11_R; I have it installed on my T547U (see the attached images below). For Root and Xposed contact Afaneh, the Admin. What I like about his project is the electrical connection and the software programming of the tablet to get information from the automobile. If you know of better programming softwares than the one he has used in the video, let me know. To install my T547U, I will use the Ram-mount specially made for my device as can be seen in the following link. It has POGO pins, which means I will be inserting my device to use in the car and removing it to use at home (theft-proof).
https://www.rammount.com/part/RAM-HOL-SAM52PD2U
The reasons why I have chosen T547U is as follows:
1. This is the only tablet that I can find in the market with 7600 mAh battery and it is removable like the old phones! I hope we all know the advantages of a removable battery.
2. It has a USB-C v3.1 with DEX function, compatible with HDMI. The HDMI which means Audio + Video + Data through the same port makes it easy for connection in the car and eliminating the use of so many adapters.
3. As a Samsung device, it has a very wide support groups that know how the firmware works.
4. It has 3.5mm jack. Many modern devices no longer have this.
5. It has LTE and a SIM-card slot. Its use for cars is explained in the link to the video.
6. Its ruggedness is fit for use in extreme conditions. P68 dust/water resistant (up to 1.5m for 30 mins). This means if you like you can permanently install it in your car and park it outside under -30 degree centigrade. This ruggedness is my warranty that is already built into the device. So I’m not worried about losing the Samsung warranty for unlocking the bootloader and rooting T547U. All my old devices that I no longer use are still working; this means if I take good care of this rugged tablet, it will outlive the Samsung 2-year warranty with so many conditions that hardly gives you a new device in exchange when something goes wrong.
7. I don't care about Wi-Fi calling that discourages so many people from unlocking and rooting their devices because it is not always a free service. Additional charges may apply – in case your Wi-Fi connection is lost for some reason, the call may switch to your data and cause you to pay extra. The best Wi-Fi calling are Skype, WhatsApp, etc.
Thanks for your attention. See all the attached images, and I will keep you informed as I progress.
https://www.samsung.com/ca/tablets/...ro-10-1-inch-black-64gb-wi-fi-sm-t547uzkaxac/
sunnyy15 said:
T547U – A Perfect Device for Android Auto Head Unit
Afaneh, thanks for your great work. SM-T547U is a very special device, manufactured in 2019, and ignored since then. What I mostly like about TWRP is its excellent and clean Backup & Restore of the entire Android Operating System, everything done outside of Android environment. I have tested this TWRP brought forward by Afaneh on my “Galaxy Tab Active Pro” and it works without flaws.
I have bought this special device to install it in my car as a head unit. Checkout the web and see for yourselves what guys are doing with their tablets to bypass the expensive head units manufactured by the OEM like Kenwood, Alpine, but these OEM head units lack full compatibility with Android devices. The current Android Auto is still in development stage, it takes so long to connect with Android devices and whenever it does so, only about five apps in your android device are synced; not worth it. Whenever these manufacturers create new things, they downgrade their innovations at the same time to save money. The new 10 inches screen sold by these manufacturers no longer come with DVD function, the offline GPS removed and Google map added so that you pay to navigate the streets, their WIFI-certified does not necessarily mean that you can use it to navigate the internet and update softwares, but just to connect your external devices,…the list is long. Below is a link to an example of what I want to do with my tablet…
Click to expand...
Click to collapse
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
mrlawrence said:
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
Click to expand...
Click to collapse
If device shipped with android 10 you cant go back to 9.
And its better to post your device model so I can check.
afaneh92 said:
If device shipped with android 10 you cant go back to 9.
And its better to post your device model so I can check.
Click to expand...
Click to collapse
It's model number SM-T547U (tab active pro unlocked) - but this device is supposed to support Android 9-11, no?
mrlawrence said:
It's model number SM-T547U (tab active pro unlocked) - but this device is supposed to support Android 9-11, no?
Click to expand...
Click to collapse
You can downgrade to android 9 if you are on v2 bootloader only.
afaneh92 said:
You can downgrade to android 9 if you are on v2 bootloader only.
Click to expand...
Click to collapse
My baseband version is T547UUEU4BUC1_B2BF
Does that mean I have bootloader version 4?
Do any devices even have a version that low in 2021? Or is it device dependent?
Anyway, I'd still like to root my tablet either way, but (assuming I don't have bootloader v2) that's really disappointing to hear about downgrading...
mrlawrence said:
My baseband version is T547UUEU4BUC1_B2BF
Does that mean I have bootloader version 4?
Do any devices even have a version that low in 2021? Or is it device dependent?
Anyway, I'd still like to root my tablet either way, but (assuming I don't have bootloader v2) that's really disappointing to hear about downgrading...
Click to expand...
Click to collapse
Yes its 4.
You cant go back to 2020 firmware too, and dont update to v5 if you want to root.
contact me for bootloader unlock
mrlawrence said:
My active pro came with Android 10, but I'm set on using 9 because of certain apps I want to use that interact with the clipboard, among other reasons. I just turned it on for the first time, and when I activated developer options the OEM unlock option wasn't there, so I reset the tablet to factory settings. Will I have to wait 7 days before I can install TWRP?
Also, can I just follow this tutorial to downgrade to android 9 after unlocking the bootloader (but before installing TWRP...?)?
This is my first time trying to root something (which I'm planning on doing after I've downgraded), but since it seems like there are pretty much no threads about the active pro (wtf!), except maybe this one about the tab active 2, any tips you have would be appreciated! I'm particularly worried about where to safely download Odin and the firmware (I'm just using the links in that video for now), but atm I'm stuck at the unlocking the bootloader phase...I'm a total noob tbh. Installing TWRP will make installing Magisk easier, right?
If I'm being honest, I'm not 100% sure about what steps to even follow...like to unlock the bootloader, can I follow the steps in this video? (I already have platform tools/fastboot/adb downloaded to my computer) Or does it depend on the device?
Since there are so many different guides for different devices (except the tab active pro 10.1 unlocked...), I'm just not confident I'm following the right steps for anything, you know?
Click to expand...
Click to collapse
Welcome to Galaxy Tab Active Pro. The process to get all what you want with this device is long, but don't be scared; step by step makes a long journey and most of what you want are possible. Answering your questions by adding to what Afaneh had already told you...
Only devices with Exynos chipset have the “OEM unlock” toggle button. Our Tab Active Pro has Qualcomm' Snapdragon chipset and even if you have bootloader unlocked and device rooted, you will never see "OEM unlock" in the Developer option.
No need to wait 7 days before installing TWRP. The only requirement is to get your bootloader unlocked. Afaneh will help you to do that. When it is advertised "Samsung Galaxy unlocked...", that only means "Network unlocked" so that you can use the LTE with any phone operator, but the bootloader is still very locked Before you unlock the bootloader make sure are on the bootloader version you like and available.
You told Afaneh that your baseband is T547UUEU4BUC1 ("_B2BF" for USA). When I bought mine it has the Canadian version T547UVLS4BUB1 on Android 10. Have a look at page 3 of the file attached...
T547UUEU2BTH6_B2BF (August 2020 update) Android 10
T547UUES2ATD1_B2BF (April 2020 update) Android 09
This is where a downgrade of OS is possible because Android 9 and 10 have the same bootloader version 2. So what Afaneh is telling you is that if you unlock your bootloader and later on downgrade with the same bootloader, you should have no problem. But if you downgrade or upgrade to a different bootloader, your bootloader will automatically lock up again and back to square zero, hahaha... So you decide.
I have the SM-540 (the wifi-only version) of the Galaxy Tab Active Pro 10.1, exact model is SM-540NZKAXAR. Is this device supported? I looked it up and it also has the Snapdragon chipset.
studentoflife said:
I have the SM-540 (the wifi-only version) of the Galaxy Tab Active Pro 10.1, exact model is SM-540NZKAXAR. Is this device supported? I looked it up and it also has the Snapdragon chipset.
Click to expand...
Click to collapse
Need to be exact chipset to work.
sunnyy15 said:
Welcome to Galaxy Tab Active Pro. The process to get all what you want with this device is long, but don't be scared; step by step makes a long journey and most of what you want are possible. Answering your questions by adding to what Afaneh had already told you...
Click to expand...
Click to collapse
Thanks for all the help. I actually stopped at the disable encryption step because I wasn't sure if it was necessary/safe.
I've been reading a little online about it and it sounds like maybe it's no longer necessary, but might speed up my device? Can you or @afaneh92 offer some more insight on that for this specific tablet? Like, is there any downside to keeping it enabled? Can I disable it later? What kinds of risks come with disabling it?
I hate to say it, but this one concern has been holding me back this whole time (I was able to get the bootloader unlocked with Afaneh's help), so if you could help me out with this I'd appreciate it. I honestly was just too embarrassed to ask before.
mrlawrence said:
Thanks for all the help. I actually stopped at the disable encryption step because I wasn't sure if it was necessary/safe.
I've been reading a little online about it and it sounds like maybe it's no longer necessary, but might speed up my device? Can you or @afaneh92 offer some more insight on that for this specific tablet? Like, is there any downside to keeping it enabled? Can I disable it later? What kinds of risks come with disabling it?
I hate to say it, but this one concern has been holding me back this whole time (I was able to get the bootloader unlocked with Afaneh's help), so if you could help me out with this I'd appreciate it. I honestly was just too embarrassed to ask before.
Click to expand...
Click to collapse
The disabler is just to make twrp stick after reboot and to diasable data encryption so you can read it in twrp and make internal storage readable.
@afaneh92 Could this process resolve an ex corporate Active Pro still locked down by MDM?
When I attempt to use Odin to apply the latest samsumg firmware I get the following error on the Download bootloader screen: MDM Mode. Can't download (PIT)
My model is a SM-T545
I'm not in the US/Canada region either.
I can perform factory resets, and if I let it go through the MDM/Knox Cloud setup I can enable developer features. If I enable flight mode at the correct stage I can enable OEM Unlock and USB debugging but to date that hasn't helped with the ability to apply the firmware via ODIN. I did also try nand erase and re-partition but it always fails before any changes are made to the device.
Jaffau said:
@afaneh92 Could this process resolve an ex corporate Active Pro still locked down by MDM?
When I attempt to use Odin to apply the latest samsumg firmware I get the following error on the Download bootloader screen: MDM Mode. Can't download (PIT)
My model is a SM-T545
I'm not in the US/Canada region either.
I can perform factory resets, and if I let it go through the MDM/Knox Cloud setup I can enable developer features. If I enable flight mode at the correct stage I can enable OEM Unlock and USB debugging but to date that hasn't helped with the ability to apply the firmware via ODIN. I did also try nand erase and re-partition but it always fails before any changes are made to the device.
Click to expand...
Click to collapse
No
is it possible to root Active pro SM-545 (gtactivexleaa), SMD 670, areno 615, android 10?
Thank you
edokk69 said:
is it possible to root Active pro SM-545 (gtactivexleaa), SMD 670, areno 615, android 10?
Thank you
Click to expand...
Click to collapse
No different device.
Thank's
Picked one of these up recently and looking to get root going. This is the USA Wifi+LTE version, T547U.
The unit came with Android 11 out of the box, and my baseband versoin is T547UUEU5CUI2_B2BF.
Am I completely out of luck? Would I be better off with the Wifi-only version?
Thank you
Related
[Edit] 2/05/2011: Use this new guide instead: http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
[Edit] 1/13/2011: If you are on stock 2.2.1 FRG83D, click here to for SuperOneClick Root !
{
"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"
}
*
So I recently decided to take my 100% stock Nexus One to Sense UI and I've documented every single step of the way. I've written this guide for two reasons. First, this entire process is scattered around in dozens of threads, written by equally as many people. Not only that, but most people in these threads assume that you know by heart exactly what adb, fastboot, recovery, and others are all about. Second, to put it bluntly, most people are pretty terrible at writing documentation. Writing down what you did so other people can follow seems extremely difficult for many people. Luckily, this is a skill I am good at. So here is a full consolidation of all the information, re-writtern for clarity as I went along step-by-step, from my many hours of attempting to bring my Nexus One from 100% stock to Desire's Sense UI. (Edit: Some people have said they'd run through this guide in 20 minutes!! It might look like a lot, but a lot of steps take a few seconds.)
Disclaimer:
You agree that by doing this process, I'm not responsible for any bricked devices.
Unlocking the bootloader will void your warranty.
This process will erase all of your phone's data.
Please don't copy/paste this elsewhere (to prevent having outdated info); just link back.
If you need immediate help, these guys might be able to help -> http://webchat.freenode.net -> Channel "modaco".
And this guide is written as if you are using Windows XP.
*(Yes, the above image of Google's campus is totally unrelated, but totally cool!)
Note: the notifications tray is personally modified
-------------------------
Backup [Optional]
On PC: www.gmail.com -> Contacts -> Export, choose Google CSV
On N1: Market -> AppMonster (or any other Backup application you prefer) -> Backup all apps
(If you want/need to backup sms etc, I don't know what non-root app does this)
Remove any authenticators etc
Downloads
Download nexus-addon-0.1-signed.zip, (From thread: CyanogenMod-5)
Download Desire Sense UI OR CyanogenMod:
Sense UI:
Download the latest version here: MoDaCo Custom ROM Desire Port (Choose with MoDaCo Additions, without A2SD)
Alternate download location (mirror) for r21: alpha-r21-update-modacocustomrom-nexusone-desire-withadditions-sig.zip
Cyanogen Mod:
CyanogenMod
Download the "Google Addon" as well
Don't download any "radio" updates unless you know what you're doing! (I would highly advise against it!)
Place both zip files (3 for Cyanogen) on N1's sdcard (don't unzip)
Setup SDK
Download android-sdk_r06-windows.zip
Unzip to C:\ drive so it looks like C:\android-sdk-windows\
Run SDK Setup.exe
Double click everything so it has a red X except for green check mark next to "USB Driver Package"
(Click for larger image)
Install
On N1: Settings -> Application -> Development -> enable USB debugging
Connect phone to PC, do not mount
New Hardware Found -> Point the install location to C:\android-sdk-windows\usb_driver\
(Click for larger image)
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Press Enter
Type: adb devices
Press Enter
(Click for larger image)
- It should say something similar to "HT123P123456 device" (this is your phone's serial number).
- If it says "cannot find" or "invalid path" etc, make sure you're typing *exactly* what the green text above says.
- If it says something else, try to reinstall the USB Driver package and restart your PC.
- If it still doesn't work, reply to this thread and say "adb devices does not work. When I type 'adb devices', it says _______________. My PC is running _______________." [Choose one: Windows XP | Windows Vista | Windows 7 | Mac | Linux]
If it works, your PC is correctly recognzing the phone. Continue on to the next step!
Unlock Bootloader
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up:
(Click for larger image)
FASTBOOT should be highlighted. Press the Power Button to go into Fastboot.
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Type: fastboot devices
- Note: Mac users need "fastboot-mac", available here: http://developer.htc.com/adp.html
(Click for larger image)
- It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong. Make sure you pressed the Power Button to go into FASTBOOT.
- If you are typing fastboot devices and it just returns a blank line or ???????? (ie Windows 7 64-bit users), try using USB drivers in the PdaNet install: http://www.junefabrics.com/android/download.php
- If that doesn't work, try not pressing the Power button to enter Fastboot. A few people have had it work that way. (Or may have been holding the Power button for too long.)
- If you can't get this step to work, reply to this thread and say "When my phone is in the bootloader and I type 'fastboot devices', it says __________ instead."
Type: fastboot oem unlock
Read what the screen says. (Decision time!) (All data will be wiped here)
(Click for larger image)
Your phone should reboot with a picture of an open padlock under the Google logo. If so, everything is good so far!
(Click for larger image)
Flash Recovery - (Update 09/01/2010: this may not work on SLCD Nexus Ones. Need an SLCD-supported recovery and then a ROM with SLCD support)
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up
FASTBOOT should be highlighted. Press the Power Button to go into Fastboot.
PC: Download latest .img file - Amon_RA's Recovery Image
Place img file into C:\android-sdk-windows\tools\
PC: Start -> Run -> cmd -> press Enter. A black window should appear.
Type: cd C:\android-sdk-windows\tools
Type: fastboot devices
It should say something similar to "HT123P123456 fastboot" (this is your phone's serial number). If it doesn't say this, something is wrong. Make sure you pressed the Power Button to go into FASTBOOT. If you can't get this step to work, reply to this thread and say "I'm trying to flash the recovery image. I unlocked my bootloader but fastboot devices doesn't work anymore. When I type 'fastboot devices', it says __________ instead."
Type: fastboot flash recovery recovery-RA-nexus-v1.7.0.img (Note: the underlined part may be different depending on what you downloaded.) (Tip: On Windows XP, you can press tab to auto-complete the filename.)
It should say: sending 'recovery' (3962 KB)... OKAY . . . . . writing 'recovery'... OKAY This should take a few seconds.
(Click for larger image)
If it doesn't work, try using Superboot (ignore this unless you're having issues flashing the Recovery):
Modaco's Superboot -> "Before download, check your device 'about' screen to determine whether you need a superboot for 'ERD79' (the original shipping ROM, 'ERE27' (the official update) or ERE36B (the new leaked update)."
Turn phone off -> Hold Trackball, then hold Power until white bootloader screen shows up
Don't touch anything
Open superboot file on PC
Try to Flash Amon_RA's Recovery again
If it still doesn't work, reply to this thread and say "When I tried to flash the recovery file, it said ________________ instead."
If flashing the recovery was successful, use the menu options to boot directly into recovery, or turn the phone off and continue on with next step!
Root
Turn phone off -> Hold Volume Down, hold Power button
Press Volume Down to highlight Recovery -> press Power to select Recovery. Your screen should look like this:
(Click for larger image)
Do this step only if you didn't use Superboot: Use trackball -> "Flash zip from from sdcard" -> nexus-addon-0.1-signed.zip
- If you get a Triangle with a ! in the middle alongside an Android for 5+ minutes, you MAY have to remove battery and re-flash recovery (I had to do this once.) (Make absolutely sure that nothing is happening on your phone, as removing the battery when it's doing something can cause a brick.)
- Alternatively, try the optional Superboot method, and then re-flash Amon_RA's recovery image.
Select Reboot.
Install ROM (Sense UI, Cyanogen, etc)
Turn phone off -> Hold Volume Down, hold Power button
Press Volume Down to highlight Recovery -> press Power to select Recovery
Backup/Restore -> Nand backup
Wipe -> Wipe data/factory reset
Wipe -> Dalvik Cache
Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
- If you get an error such as "E:\Can't open /sdcard/[blah].zip (bad)", the file is probably corrupt. (Modaco has had some issues with this recently; I don't know why.)
- If you want to make sure, use http://portableapps.com/node/19346 and drag the zip file onto it to verify the MD5 sum. For r21 with MoDaCo Additions, the MD5 should be: e5eb15ea971b220ffdfcac8f56037013
If you're using Cyanogen, flash the Google Addon.
Reboot
- If a picture of an Android falling out of a box shows up, something went wrong. Just wait for it to reboot into recovery. (Good you made a backup! Just in case.)
- Go back into recovery, Wipe all data again, Wipe Dalvik/cache again, and reflash the Sense ROM.
- If it still doesn't work, reply to this thread and say "I keep getting the Android falling out of the box when flashing the Sense ROM, even after repeated wiping."
If successful, a white HTC splash screen appears. It should take about 2-3 minutes to load into Sense.
If it gets past that, congratulations! You made it!
Post in this thread that it worked! And if you're feeling generous, feel free to send me a beer!
And finally, enjoy and have fun!
-->
--------------------------------------------------
Install a Different ROM
If you want to install a new version of a ROM, switch to a different ROM like Cyanogen, etc, only repeat the "Install ROM" section. The only difference is you'll be downloading / flashing a different zip file of course.
Make sure you backup (and wipe!) first before flashing any new roms!
To go back to the original Android ROM, either Restore your backup, or download the zip file from the following thread and repeat the Install ROM section: http://forum.xda-developers.com/showthread.php?t=614850
Known Issues:
Bluetooth is known to be buggy / will most likely not work. (Can't be fixed until HTC releases the Desire source code.)
USB mount notification does not appear - use 'USB Mount' application from menu.
To set live wallpapers, go into Settings -> Personalize.
--------------------------------------------------
What's the status on Bluetooth?
http://android.modaco.com/content/g...8-mar-desire-port-to-nexus-one-status-update/
A status update!
I now have the release candidate of the Desire ROM!
The new ROM, which is MUCH newer than the build I have been using to date is faster and smoother, the Camera app is better synchronised with the flash, the Live Wallpapers selector is in the right place, the base is ERE27 rather than ERD79 and there are numerous little fixes all over the place! Of course, it will take a bit of time for me to do a full quality port over for the next MCR, but i've done a quick hack to flash it on and see what works.
That's the good news - the bad news is BlueTooth, Camera, USB connect popup and FM Radio still don't work correctly out of the box. BUT - I have discovered why.
Basically, it all comes down to the kernel.
I have confirmed that all of the above (i'm not 100% sure on BT, i'm still investigating that one) use specific features in the Desire kernel that aren't available in the generic kernel. HTC enhancements if you will. The Desire ships with a .29 kernel which, based on what i've seen in the apps and the setup of the config file, is pretty heavily customised. Unfortunately the Desire kernel doesn't boot on the Nexus One, so we're in a bit of a sticky situation until the Desire kernel source gets released, and it's unclear when that will be (HTC's track record in that regard isn't fantastic)!
All is not lost however, as I have started looking at a new approach to fixing the problems, as seen in the camera fix for Alpha 16. I'm basically hunting down the kernel specific hooks and - where possible - i'm rerouting those to an alternate location that I can control. Taking the camera app as an example, the libcamera.so file was checking kernel specific points before deciding whether the flash should fire or not. It was doing things like checking for a phone call, checking for a wimax connection (!), and when these checks didn't work properly, it was preventing the flash firing. By editing this library and rerouting those locations, I was able to make the flash fire - much better than just dropping in the 'wrong' library which was the previous solution. Similarly, the camera application itself was dropping back to 3 Megapixels by default because it was looking for a 'sensor resolution' file produced by the kernel, which didn't exist. By determining this as the cause and reverse engineering the Camera application, I was able to make 5 Megapixels the fallback resolution instead. Problem solved.
Hopefully a similar approach can be used for the other problems (FM radio, USB connection and Bluetooth) and we'll get everything 100% - believe me i'm working on it.
If we CAN get this working fully, the work i'm doing here - if I can get it 100% - will also enable Desire users to have newer kernels and custom kernels with all the goodness that brings, without being dependent on a HTC Kernel source release.
There's lots to do - starting with the RC port to use as a base - but it's been a fun ride and it's gonna get funner. Thanks for all your support!
P
Click to expand...
Click to collapse
Update:
http://twitter.com/buxit/status/13119161481
http://twitter.com/PaulOBrien/statuses/13119278256
Reserved...
Quick question..will CyanogenMod ever support the new Sense UI built in? I realize its in Alpha stages but when its actually stable enough/all features working.
Because from what I understand only the Modaco rom comes with it?
What do you mean by "rooting"
As I understand, after you unlock bootloader and have Amon_Ra recovery you should be able to install any custom rom including both Modaco and CM
btw, if you are newbie, u should try out CM, Modaco or Enom stable first. Modaco Sense is in alpha state and still has many problems
Good guide btw
Great guide! Just explain to me the recovery image though, I don't understand what that one does, since I haven't actually done anything yet. >.>
Amon_Ra recovery is extremely helpful. It replaces the existing recovery and adds many features, including nandroid backup to back up and restore your phone in case you got screwed. It also applied zip custom roms from SD card(1 click) so you don't have to use command prompt -> more newbie friendly I guess.
btw, I don't think you need to flash Google apps in step E, correct me if I'm wrong though.
and take extra caution when flashing Radio, don't pull out the battery or do anything stupid because your phone might brick
Cheerio, very helpful guide. I'll bookmark it to link to people in the future.
"Quick question..will CyanogenMod ever support the new Sense UI built in?"
I doubt it. I don't think he did any Sense roms for the G1. But that's ok: Cyanogen if you prefer stock Android, Modaco if you prefer Sense UI. It's good to have options. And isn't that the greatness of Android?
---------------
"What do you mean by "rooting"?"
Rooting gives you superuser access. This is similar to using the Administrator account on Windows, but more so.
From http://www.linfo.org/root.html - "root is the user name or account that by default has access to all commands and files on a Linux or other Unix-like operating system. It is also referred to as the root account, root user and the superuser."
From http://wiki.cyanogenmod.com/index.php/Main_Page - "In addition to locking the phone, carriers may impose software limitations to prevent using the handset in a manner that might undercut their voice plans - Skype, Google Voice, etc - or putting strain on the data network - tethering, streaming video, etc - The way round this is to acquire 'root' (administrator) access on your phone so you can install/modify/fix/break anything you want."
Click to expand...
Click to collapse
Many applications require root like Wifi Tethering, N1 Torch, and of course, installing some custom roms
---------------
"Great guide! Just explain to me the recovery image though, I don't understand what that one does, since I haven't actually done anything yet. >.>"
duylong186 had a good explanation. So I'll just post a picture
Having a Nand Backup/Restore is downright AMAZING by the way. It's the ULTIMATE undo button!
This is also good info, just to stress this point again:
and take extra caution when flashing Radio, don't pull out the battery or do anything stupid because your phone might brick
Click to expand...
Click to collapse
Be careful everyone!
nice guide. i did everything except flash the radio. i would get the android out of the box error. everything is working fine here so far. anyways, i have all the google apps as well.
sticky please! great work
Thx for the great guide! Got Sense working on my N1 now!
about flashing the radio...
flashed the radio twice..once from stock to the OTA version, then to leaked (current) version.
both times, i applied the update, rebooted, android out of box appears, phone does its thing, get to a point where it says its updating index or something and hangs...reboot at that point...new radio with no issues both times.
point of my post - don't panic if you see the android out of the box...
nmeofdst8 said:
about flashing the radio...
flashed the radio twice..once from stock to the OTA version, then to leaked (current) version.
both times, i applied the update, rebooted, android out of box appears, phone does its thing, get to a point where it says its updating index or something and hangs...reboot at that point...new radio with no issues both times.
point of my post - don't panic if you see the android out of the box...
Click to expand...
Click to collapse
To be honest, I'm not exactly sure what the android-out-of-the-box means.
Are you saying that it will always show that after flashing any radio, and it is normal?
I cant even install the SDK
"Failed to fetch URL //dl-ssl.google.com/android/repository/repository.xmll reason: HTTPS SSL error. You might want to force download through HTTP in the settings."
The program loads but i dont get a usb driver folder....
marmankites said:
I cant even install the SDK
"Failed to fetch URL //dl-ssl.google.com/android/repository/repository.xmll reason: HTTPS SSL error. You might want to force download through HTTP in the settings."
The program loads but i dont get a usb driver folder....
Click to expand...
Click to collapse
Try changing the settings to force http?
Awesome, got a bit further... next issue is down to stupid windows os...
When trying to do the recovery carebear img... as i hit enter windows launches "windows disc image burner" and It doesnt do anything to my phone, I hit cancel and go round in a loop.
marmankites said:
Awesome, got a bit further... next issue is down to stupid windows os...
When trying to do the recovery carebear img... as i hit enter windows launches "windows disc image burner" and It doesnt do anything to my phone, I hit cancel and go round in a loop.
Click to expand...
Click to collapse
Which letter / step #, and what are you typing?
Got past this stage. was windows being stupid, on a different pc now
Finally got to E6.
If you get a Triangle with a ! in the middle alongside an Android, remove battery and re-flash recovery (I had to do this once)
Had this 3 times now! This is not enough of an idiots guide for me
Should I try the non carebear one?
marmankites said:
D6...Type: fastboot flash recovery recovery-RA-nexus-v1.6.0-carebear.img (Tip: you can press tab to auto-complete the filename -- on WinXP)
Thanks for any help! anyone have Gmail chat or anything who has any ideas?
I cant type links but... i306.photobucket.com/albums/nn248/marmankites/helpnexus.jpg
Click to expand...
Click to collapse
Ah I see.
In the picture, you are typing "recovery-RA-nexus-v1.6.0-carebear.img", which is the file name only.
You should be typing:
fastboot flash recovery recovery-RA-nexus-v1.6.0-carebear.img
Read carefully
Should I try the non carebear one?
Click to expand...
Click to collapse
The carebear one doesn't do anything except just change the background picture to a carebear
Thanks to USFBjornTutorials for the video at https://www.youtube.com/watch?v=I4kI8ZdwcZ4
ALL INSTRUCTIONS ARE SOLELY THE STEPS CREATED BY USFBJORNTUTORIALS I MERELY JUST MADE THE STEPS UNDERSTANDABLE AND EASIER TO FOLLOW . I NOR XDA ARE RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
PRE-REQUISITES
Un-rooted Sony XPERIA Z3V
All Files Below
Fully Charged Phone
Phone in USB Debug mode active
Phone with Unknown Sources for App install active
TESTED
January 17, 2016
There was some IMPORTANT missing steps that I was able to figure out and lay out a proper step by step guide.
Step 1: Make sure you disable Driver Signature if you're running on Windows 8-10: HERE
Step 2: Download and install correct Flashtool Version and install HERE
>>>>CORRECT FILE SHOULD BE flashtool-0.9.18.6-windows.exe 119MB
>>>>Install 3 drivers, from C:\Flashtool\drivers (Fastboot Mode, Flashmode, Xperia Z3 Device Driver) - If all install successfully, you successfully disabled Driver Signature.
>>>>Driver pack verstion v1.8(20141101)
Step 3: If you do not have build # 23.0.E.0.376, download this firmware and place it in C:\Users\(YourUser)\.flashTool\firmwares
>>>>NOTE This was a little confusing since the 0.9.18.8 FLASHTOOL is the one that creates the Firmware folder in .flashtool
>>>>DOWNLOAD FROM HERE (Otherwise Skip This Step)
>>>>FILE NAME D6708_23.0.E.0.376_VER.ftf 1.54GB
Step 4: Download this file , and place it in your SD card or Internal Phone Memory. You will need this in a later process (Do not Unzip) :
>>>>DOWNLOAD FROM HERE
>>>>FILE NAME flashable-prerooted.zip 1.54GB
>>>>Copy file to SD
>>>>Placing file in Internal Storage causes problems during flash.
Step 5: Download this, it will be used to root when you have Build # 23.0.E.0.376:
>>>>DOWNLOAD FROM link bad at Youtube page.
>>>>I BELIEVE THIS IS THE FILE HERE
>>>>FILE NAME D6616_ROOTFULL.ZIP
>>>>Unzip to same Download folder. Creates folder called D6616_root
>>>>The video uses a file called D6616_ROOTFULL.zip so I was able to find the file.
Step 6: Download this to install DualRecovery Click XZ Dual Recovery, then XZDualRecovery 2.8.21, and download the second one on the list, which is an installer.
>>>>DOWNLOAD FROM HERE
>>>>FILE NAME T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip 24.9MB
Step 7: Flashing Steps
Launch FLASHTOOL
At this point your Phone should say its Android 4.4.4 Build 23.0.E.1.44
WAIT
If Phone asks to Allow USB Debug, click YES
Select D66XX Sony Xperia Z3 and double click
Click YES to continue
WAIT
Copy flashable-prerooted.zip to Phone SD Card. >Copying to Internal causes problems during flash<
Click Lightning Bolt
Select FLASHMODE
Click OK
If Firmware does not show up, click the '...' box and find your file
Click 'Flash'
WAIT
Wait until is says to Turn Phone OFF
Now Hold Vol- button then insert USB
Phone now in FLASH Mode
Allow FLASHTOOL to continue
WAIT
Disconnect Phone when done and Turn ON
At this point you should have Android 4.4.4Build 23.0.E.376 on your phone
Go through phone setup steps
Reconnect Phone in USB Debug with Unknown Sources checked >>>IMPORTANT<<<
Now go the D6616_root folder
Install javainst.exe. (If not already done)
This installs Java 8, Java x64 8, JDK 8 and JDK x64 8
Allow Java installer to finish
Close Java Installer
Run exploit.bat
Go to Developer Options, Scroll down to 'Select Debug App' and select com.dosomder.testapp2
Check 'Wait for Debugger' right below the Select Debug App option
Then hit any key to continue the Exploit in the CMD box
Wait for commands to finish
If everything went OK you will see a message that says exploit.bat was successful
Hit any key to continue again and wait for all the commands to finish
Phone with auto Restart
Phone is now ROOTED!!!
SuperSU is now installed on phone
Check ROOT access by opening SuperSU. If file opens properly you have access. If not you will have to retry.
Now go back to your main folder and un-Zip T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip creating a folder lockeddualrecovery
Go to folder and run install.bat
Select #4 to install ADB drivers to windows. (If not already done)
Click any Key to continue and go back to main menu
Select #1 to install on ROM with SuperSU
Grant USB debug on phone
Grant ROOT access on SuperSU
Wait for installer to so its thing
Unplug USB
Phone Restarts to Recovery
You now have TWRP v2.8.7.0 Recovery!
Click Install
Find the flashable-prerooted.zip file you copied earlier
Swipe to Confirm Flash
Allow Phone to install Firmware
Click REBOOT SYSTEM
Wait for Phone to boot, takes a while. About 10 minutes
You now have a Sony Z3V Rooted with Lollipop Android 5.0.2 Build 23.1.D.0.509 on your phone!!!!!!
You can access TWRP by clicking Power + Vol- during boot or use the Quick Boot app
IF PHONE GETS STUCK AT SONY BOOT LOGO, TRY AGAIN AND DOWNLOAD FLASHABLE-PREROOTED.ZIP FILE AGAIN. Since both files are so big you can expect errors in the download.
Thanks to @zxz0O0, for achieving root for our Z3v, @USFBjornTutorials for initial video, @Androxyde for FLASHTOOL, @[NUT] for TWRP Flash Tool, @hqdvista for Java exploit tool, @GigaSPX for the Flashable Pre-Rooted 5.0.2 Firmware and countless others for their individual work.
{
"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"
}
Here it is. Android 5.0.2 Build 23.1.D.0.509 on the Sony Z3v D6708.
Runs great and smooth
Good writeup, very detailed.
MOD EDIT There is never a need to quote the whole OP, especially for a 4 line reply.
It is nice that it's very detailed, but I've updated my guide to skip all these frustrating steps from the beginning. Now this can be done in merely a few steps.
Oh and, you've never credited the prerooted Lollipop zip in my name since I have added a mod to it and it's the exact same link that I distribute.
GigaSPX said:
It is nice that it's very detailed, but I've updated my guide to skip all these frustrating steps from the beginning. Now this can be done in merely a few steps.
Oh and, you've never credited the prerooted Lollipop zip in my name since I have added a mod to it and it's the exact same link that I distribute.
Click to expand...
Click to collapse
Done. I've been looking for various methods and one that I tried last year Bricked phone. The video helped fill in the gaps. No disrespect meant by any of this. I do procedures for a living so I wanted to make something that was easier to follow.
bullriders said:
Done. I've been looking for various methods and one that I tried last year Bricked phone. The video helped fill in the gaps. No disrespect meant by any of this. I do procedures for a living so I wanted to make something that was easier to follow.
Click to expand...
Click to collapse
How was your phone bricked?
I remember when the bootloader was first unlocked and I tried method. Worked for 2 days then phone would not do anything. Not charge, reset or even go into download mode.
Took it to store acted like I didn't know what happened and they ended up replacing it since they could not reset either
bullriders said:
I remember when the bootloader was first unlocked and I tried method. Worked for 2 days then phone would not do anything. Not charge, reset or even go into download mode.
Took it to store acted like I didn't know what happened and they ended up replacing it since they could not reset either
Click to expand...
Click to collapse
Could you perhaps go into deeper details how you achieved it? It might be related to the other developer whose phone hard bricked on him too.
I'm sorry...
Did you just seriously release a 57 step procedure to install rooted Lollipop to the z3v without doing the research here to see that it can be done in 7 steps?
AddictedToGlass said:
I'm sorry...
Did you just seriously release a 57 step procedure to install rooted Lollipop to the z3v without doing the research here to see that it can be done in 7 steps?
Click to expand...
Click to collapse
Don't be too hard on him. This would have gotten my guide beaten if he released his before or at the same time mine came out. But it's good to rather simplify things in a matter of 7 steps to get where you need to be. xP
I could have done it in 7, but the other guide I was using seemed to have steps missing and a bunch of information missing.
I am only trying to help, But I guess providing detailed instructions for people that aren't experienced isn't necessary.
And I did check every once, the ones I tried last year bricked my phone and I didn't want to chance it again.
GigaSPX said:
Don't be too hard on him. This would have gotten my guide beaten if he released his before or at the same time mine came out. But it's good to rather simplify things in a matter of 7 steps to get where you need to be. xP
Click to expand...
Click to collapse
bullriders said:
I could have done it in 7, but the other guide I was using seemed to have steps missing and a bunch of information missing.
I am only trying to help, But I guess providing detailed instructions for people that aren't experienced isn't necessary.
And I did check every once, the ones I tried last year bricked my phone and I didn't want to chance it again.
Click to expand...
Click to collapse
I've always felt everyone needs to root at least one phone step by step to gain a grasp of what is actually going on during the process. GigaSPX's "automated" method is far easier and greatly appreciated but if someone who has never done this before has a problem then unbricking the phone is a lot more difficult and intimidating. Having contact with the actual rooting/installing a ROM process is a learning experience.
It's like putting a kid new to driving behind the wheel of my manual shift truck or sitting them in front of a DOS computer. I grew up with DOS and tinker around with Linux a little so the command line is sort of an old friend. My stepkids look at it as if it is a mutated monster.
What about updating without root and not wanting to root phone? Just flash ftf works?
Sent from my Sony Z3v on Tapatalk
I don't think that will or can work because to flash 5.0 you have to unlock the bootloader and install TWRP
MGSBigBoss said:
What about updating without root and not wanting to root phone? Just flash ftf works?
Sent from my Sony Z3v on Tapatalk
Click to expand...
Click to collapse
bullriders said:
I don't think that will or can work because to flash 5.0 you have to unlock the bootloader and install TWRP
Click to expand...
Click to collapse
You can flash unrooted stock Lollipop. You just download the FTF file through Xperifirm, put the Z3v in flash mode, then just flash it there. Although I think you would have much better benefits being rooted.
GigaSPX said:
You can flash unrooted stock Lollipop. You just download the FTF file through Xperifirm, put the Z3v in flash mode, then just flash it there. Although I think you would have much better benefits being rooted.
Click to expand...
Click to collapse
I'm going to wait before the flashing til Feb and see if verizon drops a update. If not I'll flash but a rep told me expect it in summer or spring break. Have you spoken with verizon again for any validity?
Sent from my Sony Z3v on Tapatalk
I wouldnt count on update. Verizon is in the business of getting you to spend money on phones, not give life to older devices.
Sony has had the Lollipop update available to carriers for a year now but many in the US deny the updates to users.
I'm aging if the computer industry behaved how wireless providers do, people would flipping riot.
from a business standpoint I don't see how either Sony or Verizon would gain from releasing an update this late in the game. This phone was released in October 2013? The people that upgraded to this phone when it was released will be coming out of their contracts in a few months so Verizon has no incentive to upgrade it. They want people rolling in to a new two year payment plan on a new devices rather than going month to month with an old device. I can't see why Sony has any stake at all in this at all. They aren't selling any new phones to Verizon customers and likely won't be anytime in the near future so they have zero reason to assist/push verizon with the update. I could be wrong but I think this phone is dead and forgotten. Which is too bad because it was better version of the Z3, imho, with wireless charging and better reception than the other versions.
BladeRunner said:
from a business standpoint I don't see how either Sony or Verizon would gain from releasing an update this late in the game. This phone was released in October 2013? The people that upgraded to this phone when it was released will be coming out of their contracts in a few months so Verizon has no incentive to upgrade it. They want people rolling in to a new two year payment plan on a new devices rather than going month to month with an old device. I can't see why Sony has any stake at all in this at all. They aren't selling any new phones to Verizon customers and likely won't be anytime in the near future so they have zero reason to assist/push verizon with the update. I could be wrong but I think this phone is dead and forgotten. Which is too bad because it was better version of the Z3, imho, with wireless charging and better reception than the other versions.
Click to expand...
Click to collapse
The only difference is that the regular Z3 has the better, all aluminum around look, better ISO camera for nightshots, and it has a screen RAM for improving battery life to be as good for two days.
Pretty much, we got jipped.
In my personal experience with both an unlocked Z3 and a T-Mobile Z3 I was not impressed, the Z2 and the z3v were far better devices. Whatever improvements may have been made in the camera were more than offset by the poor reception (it is a phone, after all) The Z2 had the best battery life of any pjhone I've owned. I was getting 60+ hours off the charger with 5+ hours of SOT. I'm decidedly not a power user but that is still a significant time not being plugged in. In my normal use I couldn't really see much of a difference between the z3v and the Z3 battery life.
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?
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?
TL;DR: Removing com.coloros.weather.service through ADB and upgrading to Realme UI 2.0 will cause a flicker-brick on the lock screen.
Possible solutions:
Run adb shell cmd pm enable com.coloros.weather.service; will only work if you keep the USB debugging enabled and tick 'Always allow connection from this PC' during previous ADB sessions.
Wait for Realme to release an OTA to fix this problem. No one knows how long it will take to develop and propagate, no one even knows whether they see this issue yet, and once they saw it, no one knows whether they'll consider fixing it.
Quick wins:
How to allow running adb-command during this flicker-brick state? USB debugging is enabled; however, since I did not tick 'always allow', the device shows as 'unauthorized' on adb devices.
How to raise this issue to Realme? How to let their relevant (technical) team know about this problem? Usually, a case from customer service has to be escalated multiple times to reach the technical team.
Spoiler: Plea
As listed on recovery options below, one of the quick solutions for this problem is to simply wipe the device or flash an ozip over it. However, I just lost my wife last month to COVID. We sent each other a lot of voice messages during her final days. I tried reinstalling WhatsApp using the same number. The latest backup WhatsApp found on Google Drive is dated early July. There are also many camera roll pictures not showing on Google Photos. Hence my worst-case solution is worded "wipe the phone, move on, and make amends". However, I am not ready to accept this solution yet.
======================= Full issue description and analysis =======================
Hi! I need some help regarding the "lock screen flicker" issue upon upgrading Realme 7 RMX2151 to Realme UI 2.0 (based on Android 11). The problem is widely known, and the suspected root cause is already found. However, I'm here to seek suggestions and ideas.
The issue is not specific to Realme 7; it generally applies to all Realme UI 2.0 upgrades. But since my device is Realme 7 RMX2151, I decided to post it here. The title might be a bit misleading since the flicker is unlike a CRT flicker, but simply the screen turns on and off frequently. To watch the issue:
Spoiler
It's not my video, but the problem is the exact same.
What still works:
Alarm works, also snoozing and dismissing them
Receiving and rejecting calls works, but the contact name won't appear since the phonebook is still encrypted
Pressing and holding the power button will trigger a grey rectangle that persists during the flicker
Pressing and holding power + volume up will reboot the device
Pressing and holding power + volume up + volume down will reboot the device into Recovery
The Recovery works perfectly, including OTA updates
The root cause is the removal of com.coloros.weather.service package. A user may choose to remove this package to 'debloat' their phone and remove the unused app. Little did they expect that this seemingly unimportant package will cause the lock screen flicker issue upon upgrade. This has been acknowledged by Mywk on his thread "[GUIDE][EU/IN ROM] REALME UI Debloat List"
Mywk said:
Weather Service
[WARNING] Uninstalling this and updating your phone to Android 11 WILL BRICK your device.
Code:
adb shell pm uninstall -k --user 0 com.coloros.weather.service
Click to expand...
Click to collapse
Suggested solutions so far:
Enabling com.coloros.weather.service through adb
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
- some kind of luck that the device will allow debugging even though it had not been unlocked after the first boot
From r/Realme Discord Server
{
"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"
}
Click to expand...
Click to collapse
[CONFIRMED DATA LOSS] Get into recovery mode and wipe the device. However, some users reported that the issue persists after the device wipe unless the device is downgraded to Realme UI 1.0. For Realme 7 RMX2151 (non-EU), the official downgrade package can be downloaded here. Copy the ozip into the root of the SD Card and install it through Recovery. It is appropriately signed, so it can be used on stock recovery.
Wait for Realme to release an OTA update to fix this issue and make it available. It could take months for it to propagate, though. I'm not sure whether they are aware of this issue or think it is worth fixing (debloat = user's fault?)
[SUSPECTED DATA LOSS] Flash an ozip of the same or more recent firmware. The ozip flash feature of stock recovery does not clearly state 'Keep Data', unlike check OTA that says so directly under the command. But shouldn't an update ozip (to a more recent version, not a rollback) works like regular OTA?
[CONFIRMED PARTIAL DATA LOSS] Pulling the internal storade through recovery mode. App data will be lost.
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
Boot into recovery mode. Choose to install ozip from the device. Recovery will then ask for the device password to decrypt the internal storage. Do not choose any file. Connect the phone to the computer and do an adb pull.
Use a Boot ROM (BROM) exploit by Dinolek and k4y0z to inject the package com.coloros.weather.service. Or, in my specific case (USB Debugging enabled but RSA Public Key not saved on device), write the public key on /data/misc/adb/adb_keys.
However, I need more guidance on how to do this, as most tutorials I saw was to overwrite the phone with a custom ROM, while my current objective is to return my phone to normal function through reinstalling com.coloros.weather.service or at least decrypt the internal storage and pull the files out (app data will be lost). I cannot understand and adapt the tutorial to my objective or even know whether this BROM exploit will help me.
Possible outcomes:
Best scenario: You could magically issue an ADB command to reinstall com.coloros.weather.service in the flicker-bricked state. I did keep USB debugging enabled, but I did not save my computer's RSA key on the device; hence the device shows up as 'unauthorized' on adb devices. Any suggestions?
Not-so-bad: somehow, an ADB command could be issued in recovery mode or normal boot to pull the data. The same problem occurs: I did not save my computer's RSA key on the device; hence the device shows up as 'unauthorized' on adb devices. Any suggestions?
Another scenario: Realme realizes this issue and works on a fix. The fix is made available as an OTA and can be downloaded through recovery mode. Any ideas where to ask to increase the chance of this happening?
Worst case: wipe the phone, move on, and make amends with whatever App Backup, Google Photos, WhatsApp Cloud Backup, etc., successfully keep.
any updates? usb debug not working i removed long time ago weather service didnt know that issue with new realme ui 2.0 now my phone is broken... realme 6
droi1 said:
any updates? usb debug not working i removed long time ago weather service didnt know that issue with new realme ui 2.0 now my phone is broken... realme 6
Click to expand...
Click to collapse
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
said1219 said:
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
Click to expand...
Click to collapse
is there maybe a way to enable usb debugging via recover mode? Or at least backup my data from it? Or go back to Realme UI 1.0 im realy lost....
droi1 said:
is there maybe a way to enable usb debugging via recover mode?
Click to expand...
Click to collapse
No. If there is, then it would be a HUGE security bug.
droi1 said:
Or at least backup my data from it?
Click to expand...
Click to collapse
Enter recovery mode.
Decrypt your storage. Choose "Install Updates" -> "From storage". Enter your device Password/Pattern/PIN. Do not choose any file. We're doing this only to get the recovery to decrypt storage.
Run adb root (this requires you to tap 'always allow' the first time you set up adb, see this screen. If you don't tick that box, then you're out of luck. No way to recover data.)
Run adb pull /data/media/0/path/to/file. e.g. adb pull /data/media/0/DCIM/Camera/IMG_20211002_211234.heic. If you want to pull 10.000 files, run this command 10.000 times. Please note that this command cannot pull your application's data. The named file will be copied to the directory that adb resides.
After doing that for like, 2 weeks straight, I succesfully get all my data except the chat history of WhatsApp, Signal, and Threema.
droi1 said:
Or go back to Realme UI 1.0 im realy lost....
Click to expand...
Click to collapse
No. Please refer to my post on another thread.
said1219 said:
No. If there is, then it would be a HUGE security bug.
Run adb root (this requires you to tap 'always allow' the first time you set up adb, see this screen. If you don't tick that box, then you're out of luck. No way to recover data.)
Click to expand...
Click to collapse
my phone is not rootet i get this error in minimal adb:
unable to connect for root: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
droi1 said:
my phone is not rootet i get this error in minimal adb:
unable to connect for root: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Click to expand...
Click to collapse
The command is to gain root access, not to root your phone. The command to root your phone is adb oem unlock to unlock the bootloader, flashing a custom bootloader (e.g. TWRP), and then flashing a root zip file (e.g. Magisk).
The error message indicated that you did not tick 'always allow' the first time you set up adb (see this screen). Sorry, you're out of luck. No way to recover data.
said1219 said:
The command is to gain root access, not to root your phone. The command to root your phone is adb oem unlock to unlock the bootloader, flashing a custom bootloader (e.g. TWRP), and then flashing a root zip file (e.g. Magisk).
The error message indicated that you did not tick 'always allow' the first time you set up adb (see this screen). Sorry, you're out of luck. No way to recover data.
Click to expand...
Click to collapse
i only want backup Photos from Whatsapp and DCIM not even this is possible? I will never ever debloat my Phone again with ADB...
droi1 said:
i only want backup Photos from Whatsapp and DCIM not even this is possible? I will never ever debloat my Phone again with ADB...
Click to expand...
Click to collapse
No. Your PC is not authorized to access the data in your phone.
thanks for your help
i did wipe data in recovery (retain contacts, mesages & photos) but same issue the weather service is not back so i have to format the phone
ended up in same situation on my xt
droi1 said:
thanks for your help
i did wipe data in recovery (retain contacts, mesages & photos) but same issue the weather service is not back so i have to format the phone
Click to expand...
Click to collapse
they trapped us real good. sneaky bastards. lets make sure to let them know that they are only digging their own grave.
Any solution yet? I'm stuck, too.
The problem's been discussed in this thread, too (however, no solution either - yet) :
Flicking Lock Screen after update to latest Android 11 OTA update
I just saw an update notification that Android 11 had been released. Since my phone was running Android 10, I proceeded the update without hesitation (and without backup). The phone is running stock rom without root (I guess I did unlock the...
forum.xda-developers.com
said1219 said:
No updates so far.
Realme stated that they won't fix this issue. Debloating through adb is considered an unsupported modification of base OS. If the OTA breaks the OS, their direction is to wipe the device (data will be lost).
I consider this is lousy engineering and hazardous to user data, though.
Click to expand...
Click to collapse
Is this an official Realme statement? Where did you find this?
Thx.
said1219 said:
[CONFIRMED PARTIAL DATA LOSS] Pulling the internal storade through recovery mode. App data will be lost.
This solution only works if:
- you enabled USB debugging (a prerequisite for debloating through ADB) and did not disable it afterwards
- you ticked 'always allow connection' (forgot the exact wording) when using adb to save the keys on the device
Boot into recovery mode. Choose to install ozip from the device. Recovery will then ask for the device password to decrypt the internal storage. Do not choose any file. Connect the phone to the computer and do an adb pull.
Click to expand...
Click to collapse
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Edit: idk how to delte comment I apologise for this
said1219 said:
...
Click to expand...
Click to collapse
said1219 said:
...
Click to expand...
Click to collapse
Quasar.Illumia said:
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Edit: idk how to delte comment I apologise for this
Click to expand...
Click to collapse
You can't delete the post your self, but you can request using the report form to do that, anyway, you can replace all the words from the duplicated posts, by, for example, three points ... or by some word.
What are you trying to do onto your device?
If you are trying to see your device while in stock recovery then it's not possible, while in other stock recoveries you can at least, perform ADB sideload, in Realme stock recoveries (as in Xiaomi), this is disabled (by normal means), you can update only either browsing to internal or an SD card.
jime1 said:
they trapped us real good. sneaky bastards. lets make sure to let them know that they are only digging their own grave.
Click to expand...
Click to collapse
I immediately switched to Samsung after that incident, although I keep my bricked Realme charged regularly, hoping that RUI 3.0 flashed on top of the flicker-bricked phones will fix the phone.
I considered getting a cheaper Samsung (priced like Realme), but after considering the performance penalty and remembering that I upgrade my phone biannually, I got the S20 FE which are priced twice as expensive but I plan to keep using this for 4 years.
lowbu said:
Is this an official Realme statement? Where did you find this?
Thx.
Click to expand...
Click to collapse
Half a year ago I came to largest Realme Service Center in Jakarta, considered their Level 3 support desk nationally, and had a screaming match over this issue.
Quasar.Illumia said:
So uh my phone is 6 pro and enabled always allow button just before this incident but whenever I I connect my phone to my laptop it doesn't read, does it probably have to do with that prompt that asks the phone to "allow files" &"charging only" thing?? If so how can my lappy read my device again?
Click to expand...
Click to collapse
ADB should be run in the lockscreen, the screen that "flickers" upon boot finish. Not in the recovery mode as per your photo.
Have you reinstalled Windows on your PC? Since reinstalling Windows erases the ADB keys if not backed up properly from user folder.
How long since you last connected your phone to your PC? If I remember correctly, unused ADB keys are automatically deleted after a period of time from your phone.
And I think you need to either pick MTP or PTP to allow ADB. "Allow charging only" disables data exchange entirely. This is to prevent an attack like this: a public USB charging port is provided at a public location, e.g. airport. Unbeknownst to the user, the charging port is connected to a laptop which then automatically tries to pull the entire content of any device connected to it. "Allow charging only" will cause the laptop to see nothing, exactly like your photo that said "no device attached", although in your case I suspect it's due to the device not being in normal booted state.
said1219 said:
Have you reinstalled Windows on your PC? Since reinstalling Windows erases the ADB keys if not backed up properly from user folder.
How long since you last connected your phone to your PC? If I remember correctly, unused ADB keys are automatically deleted after a period of time from your phone.
Click to expand...
Click to collapse
Just few days ago like literally a day before the incident, and yeah I think the adb keys resets but idk about that since its just 3 days as of now
said1219 said:
And I think you need to either pick MTP or PTP to allow ADB. "Allow charging only" disables data exchange entirely. This is to prevent an attack like this: a public USB charging port is provided at a public location, e.g. airport. Unbeknownst to the user, the charging port is connected to a laptop which then automatically tries to pull the entire content of any device connected to it. "Allow charging only" will cause the laptop to see nothing, exactly like your photo that said "no device attached", although in your case I suspect it's due to the device not being in normal booted state.
Click to expand...
Click to collapse
And this one is my only problem, the mtp thing should asks the user of the phone to allow a device do a "file transfer" right? I can't do that due to the screen doing the flicker thingy. Idk about your de ice but my lappy can't read my phone without it
Edit: also question, does the adb key resets depending on laptop used?
And also my phone again is realme 6 pro, does reformating my phone guaranteed to fix this?I think Im out of options since I saw posts about the OTA thingy not fixing this too and my online classes are near too