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.
Related
I have made this tutorial due to me not finding any other tutorials on fixing the problem presented in this guide. Dear admins if there is another guide on how to fix this problem please feel free to do what you must to this thread. Thank You
First of all is if you have the security error problem on your phone I can assure you that it is NOT bricked and can be fixed.
Also I am not and will not be accountable if this guide does not fix your phone. I also will not and should not be held accountable if this guide is to further damage anything of your phone.
PROCEED WITH CAUTION; Please Pre-Read this guide and understand it before proceeding.
Okay so I will guide you through on how to fix the security error problem most people have on their LG devices. I had encountered this problem on my friends LG MS769 (Optimus L9 – MetroPCS). This guide should work for mostly any LG phone.
This happened to me when I was flashing a custom recovery for the phone. I had successfully rooted the phone using a guide located at:
androidforums.com/optimus-l9-all-things-root/759935-how-root-metropcs-l9-lgms769.html
By following the above guide you will be able to successfully root and install SuperSU on you LG MS769. But keep in mind that even though it will root the phone is will NOT, I don’t know how to emphasis this as much, it will NOT: Unlock the BootLoader, Flash a custom recovery, or let you install a Custom Rom.
But let us come back the topic at hand. Okay so to fix this problem we will need the following.
LG Mobile Support Tool -- B2CAppSetup.exe -- Attached
A reliable Internet Connection
A computer with Windows XP/Vista/7/8 – (Untested on Windows 8)
TIME and PATIENCE --- We will be downloading a file about 500MB give or take some.
Okay let us begin in our endeavors of fixing our problems.
First use the below download link to download the LG Mobile Support Tool
After downloading that place it on your desktop and run it as administrator
After you run B2CAppSetup.exe it should automatically open the Mobile Support Tool, if not there should be a new .exe created on the desktop called LGMobile Support Tool just double click and open that.
Let the program update and install any necessary files that it requires. (It should automatically start to update and install, it should just prompt you with a UAC window)
Once you see the program open, click on the Install USB Driver button on the top left-hand side
Then a new window will come up asking for you for the phones carrier and the phones model number.
Once you are successfully done installing the drivers, we can proceed to the restoration process of the phone
Okay now we need to put the phone in S/W Upgrade Mode.
a.Remove phone battery, if it does not have a removable battery make sure phone is off
b.While holding down the VOLUME (DOWN or UP or BOTH) BUTTON(S) insert the microUsb in the phone while also having the USB side connected to the computer already. (To enter S/W mode it varies phone to phone which volume buttons must be pressed, try all three options)
Once the phone is in S/W Upgrade Mode the computer will start to install the drivers and the LG Mobile Support Tool will automatically detect it and start the restore process
a.Keep in mind that this process takes its time and should more than likely complete successfully giving you a working phone
b.NOTE: I have read some people calming that the process gets stuck at 4% and does not go on. If it does happen to get stuck at any percentage let it stay there for a while and see if it does go on, if not I would recommend retrying once on the same computer and if it still does not work I would give a second recommendation to try on another computer. Other than that I would suggest you contact you phone carrier or LG.
If all goes well you should have a fully functioning factory restored LG phone. Congratulations!!!!
Hope this guide was of help and I wish you best of luck in your further endeavors. :good:
punjabi4life said:
...
Click to expand...
Click to collapse
Thanks for the information but to enter S/W update mode I think after remove battery your should hold VOL+ then connect usb cable, not VOL-. Plesae update this, I'll link it in my signature:good:
Thanks I looked this up and fixed the instructions above :thumbup:
Sent from my Nexus 4 using xda app-developers app
LG Optimus F160L
Have you tried this method on LG Optimus F160L. I also stuck on this mobile.
Check my thread
http://forum.xda-developers.com/showthread.php?p=46564691#post46564691
No I have not. But more than likely my method to restore should fix it
Sent from my Nexus 4 using xda app-developers app
Security Error corrected!
Thanks for this info! I was able to update the SW from the LG Support Tool program but I had to switch to another computer to do it, and after several tries it finally took.
For this LG-P769 I had to hold the volume up button with the battery out and it went into the SW update mode on the phones screen. The update stopped after 33% update and I had to disconnect and install the battery, start the phone and let the Security Error extinguish, then plugged the USB cord back in and click the retry button of the tool, then it updates. Yes!
Note, wait until the phone reboots to the normal operating screen even though the tool says its done. This tool approx. 2 more minutes.
The phone is no longer rooted but it kept all the original apps except "Superus".
Not working for me, any help?
I have an LG-LS970, and I've made it to the point where the recovery software was downloaded and extracted, but something is causing an error and not letting the process finish. I assume this is the faulty ROM on the phone, since my phone is bricked from rooting and deleting Google Play apps (I was stupid and thought they weren't important to have). Any ideas?
If you had the recovery software installed you could of installed the gaps. Zip files through it.
Sent from my LGMS769 using XDA Premium 4 mobile app
Please help i've been at this for 2 days
I moved a boot.img file to my Metropcs LG optimus L9 lgms769 and now I am stuck at the security error. I rooted the phone but did not have the bootloader unlocked. I have tried the update tool and it stops at 4%, when I can get it to work. I haven't either understood the other methods mention or something, idk. Anyway, I would really like to get my phone working. Can someone please give me a good way to do this. I have the V10E_00.kdz file already. Thankyou
I already have the latest version but need to repair
Thanks for the instructions! I followed the steps and everything basically works but once the phone is in software upgrade mode, the LG tool just says "Your device has the latest software available from the LG Mobile Support Tool" and it doesn't install anything.
What happened is I rooted my phone and removed one too many system apps, now it won't boot up anymore. How can I get this tool to reinstall the same software I already have? Do I need to wipe it completely? Please help me out, I'm afraid I'll make it worse if I try anything else.
ivocado said:
Thanks for the instructions! I followed the steps and everything basically works but once the phone is in software upgrade mode, the LG tool just says "Your device has the latest software available from the LG Mobile Support Tool" and it doesn't install anything.
What happened is I rooted my phone and removed one too many system apps, now it won't boot up anymore. How can I get this tool to reinstall the same software I already have? Do I need to wipe it completely? Please help me out, I'm afraid I'll make it worse if I try anything else.
Click to expand...
Click to collapse
Hi ivocado, you could try this way:
http://forum.xda-developers.com/showthread.php?p=50729855
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Thank you!
BajoPrimate said:
Hi ivocado, you could try this way:
http://forum.xda-developers.com/showthread.php?p=50729855
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Click to expand...
Click to collapse
Thank you so much! I totally overlooked the recovery option in the tool. 30 minutes later and I have my phone back working perfectly. So happy! :good:
I took it to the T-Mobile store this morning and all they wanted to do was sell me a new one, saying the phone was dead. I owe you. Can I buy you a beer? Seriously, if you have PayPal I'll do it.
ivocado said:
Thank you so much! I totally overlooked the recovery option in the tool. 30 minutes later and I have my phone back working perfectly. So happy! :good:
I took it to the T-Mobile store this morning and all they wanted to do was sell me a new one, saying the phone was dead. I owe you. Can I buy you a beer? Seriously, if you have PayPal I'll do it.
Click to expand...
Click to collapse
Hi ivocado, you're welcome, I'm very, very happy with your success.
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
ivocado said:
Thank you so much! I totally overlooked the recovery option in the tool. 30 minutes later and I have my phone back working perfectly. So happy! :good:
I took it to the T-Mobile store this morning and all they wanted to do was sell me a new one, saying the phone was dead. I owe you. Can I buy you a beer? Seriously, if you have PayPal I'll do it.
Click to expand...
Click to collapse
Do you have any photos or screenshots on how your lg support tool looks like? Im having some difficulty since the software doesnt download.
ivocado said:
Thanks for the instructions! I followed the steps and everything basically works but once the phone is in software upgrade mode, the LG tool just says "Your device has the latest software available from the LG Mobile Support Tool" and it doesn't install anything.
What happened is I rooted my phone and removed one too many system apps, now it won't boot up anymore. How can I get this tool to reinstall the same software I already have? Do I need to wipe it completely? Please help me out, I'm afraid I'll make it worse if I try anything else.
Click to expand...
Click to collapse
Re install stock ROM!
perfect with lte2
punjabi4life said:
I have made this tutorial due to me not finding any other tutorials on fixing the problem presented in this guide. Dear admins if there is another guide on how to fix this problem please feel free to do what you must to this thread. Thank You
First of all is if you have the security error problem on your phone I can assure you that it is NOT bricked and can be fixed.
Also I am not and will not be accountable if this guide does not fix your phone. I also will not and should not be held accountable if this guide is to further damage anything of your phone.
PROCEED WITH CAUTION; Please Pre-Read this guide and understand it before proceeding.
Okay so I will guide you through on how to fix the security error problem most people have on their LG devices. I had encountered this problem on my friends LG MS769 (Optimus L9 – MetroPCS). This guide should work for mostly any LG phone.
This happened to me when I was flashing a custom recovery for the phone. I had successfully rooted the phone using a guide located at:
androidforums.com/optimus-l9-all-things-root/759935-how-root-metropcs-l9-lgms769.html
By following the above guide you will be able to successfully root and install SuperSU on you LG MS769. But keep in mind that even though it will root the phone is will NOT, I don’t know how to emphasis this as much, it will NOT: Unlock the BootLoader, Flash a custom recovery, or let you install a Custom Rom.
But let us come back the topic at hand. Okay so to fix this problem we will need the following.
LG Mobile Support Tool -- B2CAppSetup.exe -- Attached
A reliable Internet Connection
A computer with Windows XP/Vista/7/8 – (Untested on Windows 8)
TIME and PATIENCE --- We will be downloading a file about 500MB give or take some.
Okay let us begin in our endeavors of fixing our problems.
First use the below download link to download the LG Mobile Support Tool
After downloading that place it on your desktop and run it as administrator
After you run B2CAppSetup.exe it should automatically open the Mobile Support Tool, if not there should be a new .exe created on the desktop called LGMobile Support Tool just double click and open that.
Let the program update and install any necessary files that it requires. (It should automatically start to update and install, it should just prompt you with a UAC window)
Once you see the program open, click on the Install USB Driver button on the top left-hand side
Then a new window will come up asking for you for the phones carrier and the phones model number.
Once you are successfully done installing the drivers, we can proceed to the restoration process of the phone
Okay now we need to put the phone in S/W Upgrade Mode.
a.Remove phone battery, if it does not have a removable battery make sure phone is off
b.While holding down the VOLUME (DOWN or UP or BOTH) BUTTON(S) insert the microUsb in the phone while also having the USB side connected to the computer already. (To enter S/W mode it varies phone to phone which volume buttons must be pressed, try all three options)
Once the phone is in S/W Upgrade Mode the computer will start to install the drivers and the LG Mobile Support Tool will automatically detect it and start the restore process
a.Keep in mind that this process takes its time and should more than likely complete successfully giving you a working phone
b.NOTE: I have read some people calming that the process gets stuck at 4% and does not go on. If it does happen to get stuck at any percentage let it stay there for a while and see if it does go on, if not I would recommend retrying once on the same computer and if it still does not work I would give a second recommendation to try on another computer. Other than that I would suggest you contact you phone carrier or LG.
If all goes well you should have a fully functioning factory restored LG phone. Congratulations!!!!
Hope this guide was of help and I wish you best of luck in your further endeavors. :good:[/QUOTE
Ok its perfect but when install spinx.zip cstm rom it stucks n same lg security eror
Click to expand...
Click to collapse
izhar_ulhaq said:
Ok its perfect but when install spinx.zip cstm rom it stucks n same lg security eror
Click to expand...
Click to collapse
Hi izhar_ulhaq, if you don't unlock the bootloader, you can't flash a custom recovery nor install a custom rom.
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted
Help! The LG Mobile Support Tool is frozen at "Analyzing phone setting..." and I am at the S/W Upgrade screen.
I forgot to unlock the bootloader before installing custom recovery..
how to fix lg security error issue
yup i did just that now my phone works fine i have a metropcs lg ms770 the only thing peoploe should realize is that it takes time the computer tells you its updating and its done but when you check your phone it's really back to the same issue . you guys need to try it couple of times if it dosent work the computer needs to make that connection in order to run perfect if theres no connection theres no udate keep that in mind peace......
{
"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"
}
Is it working? My phone is in S/W Upgrade mode, but I don't see any upload bar anywhere
Background:
I originally had CWM and custom rom install on my phone. I decided to install a new rom, but the installation failled and Aroma installer kicked me out of recovery. I have no way re-entering recovery, so I used Smart Flasher and the correct ROM to flash the phone back. And now I'm stuck at Security Error.
Hello everyone,
I will share my experience with you, and I hope for a solution!
A few days ago I rooted my Lenovo tab 2 A10-30 successfully using Kingroot. Then, I tried to change Kinguser with SuperSU, which I also successfully did. However, I noticed that although the main root app was SuperSU, Kingroot was still on my phone, so I deleted it using a bloatware removal app and restarted the tablet. Now it won't turn on. It gets stuck at the Lenovo loading screen, and that's about it. When I press the power button + volume down button, it gets me to a Chinese menu that is not the recovery mode (there is no MMC, just options about voloume, colors, mic test etc). If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
I tried flashing the stock ROM using the Smart Phone Flash Tool, but the PC does not recognize fully the tablet (it just prompts me to install the Lenovo USB drivers, and I cannot access the tablet's internal storage). Moreover, the Lenovo windows applications do not recognize the tablet when I connect it to the PC.
I really do hope that there is a way I can fix it.. Thank you all in advance.
Hi,
I did almost exactly the same... Kingroot, tried to remove bloatware with another app, and ended up with a bricked tablet I can still access the bootloader, but flashing the tablet from there is to no avail.
I am still looking for the original ROM, which seems nowhere to be found. Did you, by any chance, make a backup first?
Another one here But I'am able to go into recovery and into adb sideload, from there I can view internal memory(/system). And it looks like system is trying to load supersu-daemon which was removed and it can't get past that. I tried to recover paths (to original ones), but it still wont go past loading screen. (it is just restarting the app_process32).
Now if we only could get the hold on original factory firmware... from there one we can sideload it via fastboot.
And for the drivers you need andorid usb drivers https://developer.android.com/studio/run/win-usb.html#top
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
So, I have spent about 5 hours attempting to find a way to dump the firmware without first rooting the device, so that I could share it with you guys (and have a backup for myself in case I attempt to root it myself.) Unfortunately it seems like it needs to be rooted before I can create a nandroid backup through adb. Unfortunately the tablet is not based on mtk, and I cannot find any qualcomm utils that can dump the firmware.
The one Qualcomm util I found (QFIL) seems like it is only for flashing, and for backing up some individual data for the tablet (I assume it may contain such as license keys for the commercial features in the recent phones such as Sony Xperia Z3). I also looked into fastboot, and that too can only flash a new firmware.
So, unless the tablet gets rooted I don't see any way to make a proper backup.
I am unable to post links in messages, so you need to do some manual editing.
dz0ny said:
TLDR; we are looking for TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip
Click to expand...
Click to collapse
This however seems like very valuable information, unfortunately the only places I can find that has this available for download is charging money for access to the file.
50$ at dlgsm,com www DOT dlgsm DOT com/register.php?file=TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip&dir=%2FFLASH-FILES%2FLENOVO%2FT_Series%2FTB2-X30F
or from 10$ at pars-hamrah,com: www DOT pars-hamrah DOT com/%D8%A7%D8%AE%D8%A8%D8%A7%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D8%A7%D8%AE%D8%AA%D8%B5%D8%A7%D8%B5%DB%8C-%D9%BE%D8%A7%D8%B1%D8%B3-%D9%87%D9%85%D8%B1%D8%A7%D9%87/38027-%D8%B1%D8%A7%D9%85-%D8%A7%D9%88%D8%B1%D8%AC%DB%8C%D9%86%D8%A7%D9%84-%D9%84%D9%86%D9%88%D9%88-lenovo-tb2-x30f-%D9%86%D8%B3%D8%AE%D9%87-s000015-%D8%A7%D9%86%D8%AF%D8%B1%D9%88%DB%8C%D8%AF-5-1-1-%D8%AF%D8%B1-%D9%85%D8%B1%DA%A9%D8%B2-%D8%AF%D8%A7%D9%86%D9%84%D9%88%D8%AF-%D9%82%D8%B1%D8%A7%D8%B1-%DA%AF%D8%B1%D9%81%D8%AA.html"]Here[/URL]
It might also be available www DOT fars-gsm DOT com/75531-tb2-x30f_usr_s000015_1601151950_q8009_row_qpst-zip.html, at least they list the changelog for the firmware.
Since I have no use for a firmware right now, I will not be buying access to one (unless I at some point manage to brick mine as well). But if anyone decides to do so, please share it so others can enjoy it as well. I also suspect that if the file was available, it would increase the probability of someone attempting to make a custom rom at some point as well, it is a very cheap tablet when on sale, so it should have good potential for a community.
PS: I also stumbled over something called vRoot, that might be an alternative to Kingroot, although I have no idea whether it is as good at rooting and not installing unwanted extra apps. I guess someone who has used it on a tablet/phone that has a backup available might be able to shed some light on that.
---------- Post added at 08:08 PM ---------- Previous post was at 08:02 PM ----------
omrtpsycho said:
If I press the volume up+ volume down + power button, it just brightens the screen and shows nothing.
Click to expand...
Click to collapse
This is the QFIL (Qualcomm Flash something system) mode, however I do now know whether that helps anything at all. Since it seems to me it probably wont accept the TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip file mentioned in the thread. It seems to expect some xml file, maybe the zip file contains that?
Hi guys i have been strugling with this unit The last 3 days. I have eksakt same problem. I found these files: lenovo-forums.ru/files/category/106-прошивки-lenovo-tab-2-a10-30/
I extracted Them but dont know how to flash Them ?? Hope u guys Can help (sorry for bad english)
To Download files from Lenovo-forums.ru i logged in with my Google account
[PUT ROM TEMPORARILY HERE: https://www.wetransfer.com/download...024ee2974a44f8aa50e3dcd120160615184237/a84735 ]
Wow, suddenly action! With the help of Dead2 and Andersbp I have made some progress. Here are my steps:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
The smaller one is simply an update, which you could install easily:
1) boot into Recovery Mode
2) select "Apply Update from ADB"
3) run: adb sideload TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip
Which works... UNLESS YOU ROOTED THE DEVICE. Then it fails, and does not want to update. Thanks Lenovo
So, the larger one is a different type of ROM. This one will not load with adb sideload (gives footprint and signature error). But it DOES contain all the files to flash with QFIL (Qualcomm Flash something system).
Here I'm stuck. I followed this guide:
http://guidebelajar.blogspot.nl/2016/03/guide-how-to-flash-firmware-lenovo-vibe-p1.html
and tried to install these packages:
1) You must download and install USB Driver for Lenovo on your windows computer or PC.
2) QPST-2.7.422-qfil-qcom-Upgrade-Tool-20140422
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Furthermore, the site suggests to install something on the device itself:
5) Create a folder with the name sdfuse in the root of the SD-card phone
6) Put the qsb-firmware (file with the extension .qsb) in the folder sdfuse.
Here I have 2 problems: First, my device does not boot, so I cannot create/copy files. Seconly: I cannot find qsb-firmware.qsb anywhere...
@ Dead2: How did you go through these steps?
Zwartoog said:
I purchased the ROM from the Iranian site, and downloaded the other from the Russian forum. So now I have 2 ROMs:
65M TB2-X30F_S000015_160115_ROW_TO_TB2-X30F_S000016_160602_ROW_WCA72E4AB5.zip (Russian)
1.1G TB2-X30F_USR_S000015_1601151950_Q8009_ROW_qpst.zip (Iranian)
Click to expand...
Click to collapse
Great, thanks for sharing the firmware, I hope you and everyone else with a softbricked tablet can get it fixed now
I am sure some of those would be willing to donate a couple of bucks to you if they get theirs working again.
Zwartoog said:
3) Download Qualcomm HSUSB USB COM Drivers
(Note that you need to register and log in to needrom.com FIRST. Then click the link, but it will give an access error. Remove all in the URL after needrom.com (so go back to the main site), then go back to the download link, and it will work - the file is there.)
1) and 2) install pretty fine, but 3) is just a zip with a lot of drivers, no installer. I have no clue on how to install the proper driver...
Click to expand...
Click to collapse
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
I got the driver package from here: www DOT teamandroiders DOT com/lenovo-usb-drivers-download/
Zwartoog said:
@ Dead2: How did you go through these steps?
Click to expand...
Click to collapse
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
I will assist in any way I can, but I will not attempt flashing my own tablet until I actually need to
Dead2 said:
After you get past installing the HSUSB driver, you are officially the one that has gotten furthest on this.
Click to expand...
Click to collapse
We'll get this working
Dead2 said:
Ok, I used a LenovoUsbDriver_v1.0.12.exe driver installer, and that includes the HSUSB drivers needed, and I can confirm that windows recognizes the tablet as being in HSUSB mode with those. Whether QFIL does I have not tested.
Click to expand...
Click to collapse
I tried that one too, but to no avail When I try to execute the executable, it ask for administrator permission, and after that vanishes...
I am running Windows 8, 64 bit. You?
Other question: when is your tablet recognised by Windows? Also in Recovery Mode?
Thanks!
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Andersbp said:
Great work so far guys ! I Will try tomorrow with The new information! Mine is rootet so dont look good for me :/
Zwartoog:
The russian site also have Big files (1gb)
You Saw Them ?
Click to expand...
Click to collapse
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Zwartoog said:
No, I have spent too many hours translating Farsi today, was quite happy to find this one easily accessible on the Russian site
Can you check one of the bigger files? Might come in handy if my version seems incompatible for some reason...
Click to expand...
Click to collapse
Sure Will try tomorrow
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
{
"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"
}
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
First i followed this guide:
https://2.bp.blogspot.com/-YxnBnMMx7Xg/VnaiVim76VI/AAAAAAAAURo/pz5IiaVdlcQ/s320/qfil.jpg
But insted of this:
9. Now, enter your Lenovo Vibe P1 into recovery mode. you can do it by :
Press the Volume Up button and keep holding it while connecting it to the computer/laptop using USB cable.
Lenovo Vibe P1 will vibrate one time, and you will see black screen.
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Now you can continue with the guide, and use QFIL.
I used this firmware: https://drive.google.com/open?id=0B9affStJ4JQ1U3JXUTZFTDJ6NU0
Extract the rar file. Inside you will find the files needed in QFIL.
Hope this helps you guys
Click to expand...
Click to collapse
Super! Will try this tonight. Just in case: which Windows version are you using?
Zwartoog said:
Super! Will try this tonight. Just in case: which Windows version are you using?
Click to expand...
Click to collapse
I use windows 10
Andersbp said:
Huge breakthrough
I now have a unrootet, unbricked and stable unit again!
Click to expand...
Click to collapse
Great work! I am glad I was able to help you guys get this fixed
Andersbp said:
You need to hold in VOLUME UP AND VOLUME DOWN AND POWER button at same time. Until you see
Click to expand...
Click to collapse
Yep, its at the bottom of my first post also, found that out by accident while trying to get into the normal recovery.
Now, hopefully someone will want to port TWRP and CM13 or Paranoid to this tablet
Doh i did not see that Dead2
Thanks everybody together we defeated the problem !
SUPER! Succes here as well! The trick was indeed to hold both vol UP and DOWN
Now: brand-new unrooted device
Thanks
Btw: I noticed that the rom from Andersbp is a TB2-X30L rather than the TB2-X30F. I used my F file (paid for it, dammit ), and that one also works well.
I am currently checking if I can modify the stock ROM to enable root / mult-user. Any hints?
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Andersbp said:
Nice zwartoog !
I Can root with kingroot.. Are there better alternatives ? Kingroot is Full of bloatware
Click to expand...
Click to collapse
Noo, no Kingroot. That's where all the disasters began. It is full of bloatware. Trying to uninstall Kingroot lead to bricking the device
Personally I am only interested in re-enabling the multi-user feature from lollipop. WHICH IS FOR SOME REASON DISABLED BY LENOVO Even when rooted and modifying the system/build.prop did not re-enable it.
I'm giving up now. At least I have a workable device. Restored pride. And more important: 3 happy kids
I think the TB2-X30L is the LTE version of the tablet, while the TB2-X30F is the wifi-only version. If correct, then there should be no problem
when using the LTE on a non-LTE model, but the other way around could potentially cause LTE to not work. The LTE firmware might have some
extra apps and settings enabled to cater to this ability, but it might also be completely identical. Btw, what does the model information say
after being flashed with the L firmware? In any case it is useful to know that they are cross-compatible, since sometimes there can be differences
in chipsets or screens that can cause minor or major problems.
As I mentioned earlier, another root alternative to kingroot seems to be vRoot, but I have not tried it myself. But now that it is possible to
recover a bricked tablet, it is also less risky to test such things.
BTW: Please remember to use the "Thanks!" button on posts you find helpful, I have tried to do so myself on the posts that I find helpful
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?
{
"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