Stock Android 6.0.1 Marshmallow for TextNow
Device Compatibility: Moto G (3rd Gen) 2015 (xt1548 ONLY)!
Android Version: 6.0.1
Build No. MCI24.107-70
System Version: 24.62.70.osprey_sprint.sprint.en.US.sprint
Kernel Version: 3.10.49
Baseband: M8916_2020632.44.321.54R
Carrier/Provider: TextNow (Sprint MVNO Subsidiary)
Android Security Patch Level: January 5, 2017
Build Version SDK: 23
PRL Version: 25060
ROM & FIRMWARE FILES:
DOWNLOAD LINK: https://drive.google.com/folderview?id=0B7-zQU1VihD3aHZ4N1VJelY0d2c
This link provides download access to the following files: bootloader.img, gpt.bin (Partition Updater), NON-HLOS.bin (Modem, AKA "Baseband"), fsg.bin (Radio Firmware), recovery.img (Stock 6.0.1 Recovery), boot.img (Stock 6.0.1 Kernel/Ramdisk), system.img_sparsechunk files (a series of /system image files which, when flashed, comprise the ROM itself) An executable flash-all.bat file is also included, which is basically a script instructing fastboot as to each and every partition to be flashed.
Because the TextNow Moto G3 was shipped with Android 5.1.1 firmware, and because no firmware update or OTA has since been released for the TextNow variant, many key firmware components are outdated (e.g., Baseband, Bootloader, Partition Index, Radio Firmware, WLAN Drivers, etc). I have compiled this stock MM ROM in fastboot flashable format to ensure that all relevant firmware partitions are updated during installation of the stock ROM. Future releases of this ROM, which will center on bug fixes and stability improvements, will be compiled in TWRP flashable zip format.
REQUIREMENTS & INSTRUCTIONS:
1. An Unlocked Bootloader;
2. A Windows PC or Mac;
3. The Android SDK Platform Tools, or, preferably, the latest version of Minimal ADB & Fastboot. Download the program from this link for Windows PC and install once download is complete. https://drive.google.com/file/d/0B7-zQU1VihD3TnhTNVVVZGZ4bVU/view?usp=drivesdk
4. On your PC or Mac, install the most recently released version of "Motorola Device Manager." This piece of software installs and periodically updates the correct USB Drivers for your Motorola smartphones or tablet. A current version can be downloaded here, on the Motorola/Lenovo website: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
5. Power on and allow your Moto G3 to boot into the OS. Go to SETINGS, then select ABOUT PHONE, find BUILD NO. and tap it approximately 7 or 8 times until you see a toast confirming that DEVELOPER OPTIONS is enabled. In DEVELOPER OPTIONS, enable OEM Unlocking and USB Debugging.
6. Once you have downloaded the stock ROM installation & firmware files from the above link, place these files on your PC Desktop, in the same directory/path as ADB/Fastboot. Connect your Moto G3 to your PC or Mac using an OEM or high quality equivalent micro USB to USB syncing/charging cable. In your ADB/Fastboot directory, open a command window by holding the SHIFT key and simultaneously right clicking with your cursor in the folder/directory of the path sought. In this instance, the ADB/Fastboot directory would be correct. In the command window type: "adb reboot bootloader" .....Your device should boot into AP Fastboot mode from the Android OS. If it doesn't, you may manually boot into fastboot mode by first powering off your Moto G3. Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select. Once in Fastboot Mode, open another command window in the ADB/Fastboot directory, then type,: "fastboot devices". The command window will return with a string of numbers under an entry titled "connected devices". The numbers are actually your device serial number. (If no numbers are returned following the command, or if a prompt appears saying "waiting.....", then your device is not properly communicating with ADB/Fastboot via your PC or Mac. Try switching USB Ports, switching syncing cables and/or uninstalling/reinstalling Motorola Device Manager.
7. Upon establishing a proper connection between your PC and Moto G3, click on and run the executable file titled "flash-all.bat" (located n the directory of files from the below link), sit back & wait a minute or two. Your Bootloader', Partition Index, Modem, Radio Firmware & Stock Recovery will be updated to Stock Android 6.0.1 Marshmallow. Your /system partition will also be flashed with a series of img_sparsechunk files, updating your Android OS to Stock 6.0.1.
** It should be noted here that once your partition index & bootloader have been updated, you will not have the option to downgrade either of these partitions at a later time. In fact, attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick. Your Modem (NON-HLOS.bin) and Radio Firmware (fsg.mbn) may be downgraded with no reported adverse effects.
8. Now, you will need to root your stock Marshmallow OS. (Many of the addon pre-installed applications on this stock ROM require superuser access.) To root the ROM, you will need to flash SuperSU v2.79 systemless root .zip via TWRP recovery. Links for both files are here:
@squid2's TWRP v3.0.2-r5: https://drive.google.com/file/d/0B7-zQU1VihD3ajYwR25xZ3dFT3c/view?usp=drivesdk
@Chainfire's SuperSU v2.79 Systemless Mode zip: https://drive.google.com/file/d/0B7-zQU1VihD3VFBidGk4SjFkQUE/view?usp=drivesdk
9. Upon initial boot, setup, etc., go ahead and update your PRL & Data Profile to ensure your versions are the most recent. Under SETTINGS, scroll down to SYSTEM UPDATES. Turn WiFi off and Cellular Data on. First choose the option to update your PRL. Once successfully updated, choose the update Profile option. A reboot will be necessary in order for these changes to take effect.
Add-ons Included (in /system/apps) & Credits:
TextNow v5.3.0 by TextNow, Inc.
SuperSU v2.79 by @Chainfire
BusyBox v49 by @denys Vlesenko
Fast Cleaner v3.2.8 by the @OPDA Team
Kernel Adiutor-Mod v1.0-07/18/2016 by @yoinx
CyanogenMod 13 File Manager v3.0.0 by The CyanogenMod Team
Google Nexus MM Boot Animation (Dark Theme)
Nova Launcher v 5.0.3 by @teslacoil Software
Candy Icons v2.3.3 @Vukasin Andelkovic
VIPER4ARISE FX v2.5.0.5 by VIPER ACOUSTICS & A.R.I.S.E SOUND SYSTEMS
Esira Music Player v1.0 by @A.R.I.S.E SOUND SYSTEMS
I also want to say a huge thanks to @dearmasfamily for his TextNow based stock Android compilations on the Moto E LTE 2015 (xt1526). His modifications to apns-config.xml and eri.xml on the Moto E LTE were a lifesaver during my network configurations for TextNow on the Moto G3. And thanks to @squid2 for his hard work on custom kernels for Osprey. His detailed explanations on boot image support have given me a much broader understanding of the systemless root methodology. Finally, @ResistanceIsFutile, your keen eye for detail, research, and general editing skills have been invaluable. Thank you.
Sent from my Lenovo TB3-850F using XDA-Developers Legacy app
Also for XT1543 please !
Heyner_Gomez said:
Also for XT1543 please !
Click to expand...
Click to collapse
I agree -- TextNow subscribers would benefit from a stock 6.0.1 MM ROM for the T-Mobile (or GSM unlocked) variant of Osprey. Unfortunately I do not own a xt1543. I would need a device at least tentatively in order to flash & dump firmware partitions for a stock MM build.
Looking Good
Easy to understand and presentation looks very much polished
- Good Job Sir :good:
Hark do I see special editing as well. . .
Build it and they will come
The OP download link for the ROM & Firmware files - if you use the "Download All" tab "top Right" corner there, will Zip all files together in an easy all at once download of them in two zipped parts.
Thank you @ResistanceIsFutile. Been messing around on XDA Forums Premium for Android to create my post. You taught me a great deal on thread composition & I am grateful for it. I'll be linking the ROM & firmware files within an hour or so. Also i will be including a patched boot.img for systemless root support. Simply flash SuperSU v2.79 via TWRP (files to be included in link) and root access should be without issue. My messaging settings are undoubtedly the culprit. Please send me a friend request. I'll fix the PM issue shortly.
@MotoJunkie01 Your certainly welcome, as I've learnt many things from you as well.
Friend request sent out. Don't know why I've waited so long really. I believe your the first.
I see your due a celebration on a couple counts, hope Saturday is the best for you.
RIF
{
"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"
}
I need testers to install and provide input on this.
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
tsakowich6217 said:
I'm currently running LineageOS 14.1. I read this bit of your post:
"attempting to downgrade bootloader.img or gpt.bin has been known to result in a hard brick."
I'm not sure I understand it fully. I apologize if this is a rather basic question, but if I install this from Lineage, will I have any problems? If I choose to install this, what should I avoid in the future to prevent a hard brick?
Thanks for your hard work!
Click to expand...
Click to collapse
No. You should have no problems at all. In a nutshell, stock firmware packages contain files to flash the bootloader (bootloader.img) and a partition table updater file (gpt.bin). Once these two partitions are updated, downgrading isn't an option. This doesn't mean you can't downgrade a stock ROM, say from 6.0.1 to 5.1.1. Downgrading is no issue at all as long as you avoid bootloader.img and ,gpt.bin.
Installing custom ROMs, like LineageOS, doesn't put you at any risk in this regard. You may upgrade or downgrade at your leisure. My warning in the thread merely cautioned against downgrading the bootloader and partition table in stock firmware packages.
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Then, hold Power and Volume Down simultaneously until the recovery menu appears. From recovery (if stock recovery) simply use Volume Down to navigate to Bootloader option then press Power to select.
Click to expand...
Click to collapse
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out solely to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us/en/products/CELL-PHONES/ANDROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Reset Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
Hope this helps and clears as with what the Moto site instructs.
ResistanceIsFutile said:
Hello @Gravemind2015
I'm limited as I no longer have a Moto G (3rd Gen) 2015 (xt1548).
I've just looked as to the manufactures steps (as these questions interests me).
These are for an External Reset and Clear Cache Partition though, but share common steps,
I couldn't find as steps called out to enter Recovery Mode specifically other than these sets of instructions .
External Reset.
https://mobilesupport.lenovo.com/us...ROID-SERIES/MOTO-G-3RD-GEN/documents/MS105537
Android 5.x (Lollipop)/Android 6.x (Marshmallow) External Rest Steps
1.With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
2.Press the Volume Down key to highlight Recovery mode.
3.Press the Power key to restart into Recovery mode.
4.The screen will display an Android robot with a red exclamation mark.
5.While holding down the Power key, press and release the Volume Up key, then release Power.
6.Use the volume keys to scroll to Wipe data/factory reset and press the Power key to select it.
7.Scroll down to Yes - erase all user data and press the Power key to select it.
Clear Cache Partition.
https://mobilesupport.lenovo.com/us/en/Solution/MS112729
Android Version 6.0 (Marshmallow) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Down button. While still holding Volume Down button, press and release the Power button.
3.Press and release the Volume Down button until you reach Recovery Mode.
4.Press and release the Power button to select Recovery Mode. The device will restart. An image of an Android robot with a red exclamation mark will appear.
5.Press and hold the Power button, press the Volume Up button once and then release the Power button.
6.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it. If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Once the cache wipe has completed, press the Power button to select Reboot System Now.
Android Version 5.0 (Lollipop) Clear Cache Partition Steps
1.Power off the device and unplug it.
2.Press and hold the Volume Up and Volume Down buttons and the Power button at the same time until the device turns on.
3.From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Volume Up button to select it. The device will restart. An image of an Android robot with a red exclamation mark will appear.
4.Press and hold the Power button, press the Volume Up button once and then release the Power button.
5.Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
6.If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
7.Press the Power button to select Reboot System Now.
@MotoJunkie01 states this-
Hope this helps and clears as with what the Moto site instructs.
Click to expand...
Click to collapse
Well, the lenovo support link you provided seems to have the accurate process. Bootloader unlocking page also has the same instructions. [Power off> power+volume down and it goes into bootloader(fastboot) mode rather than to recovery]
Anyways, this will be off-topic for this rom thread so I'd hope someone with access to this particular model with this carrier can test which method is correct Thanks for replying.
Broadcasted from Zeta Reticuli
Removed My own Content
ResistanceIsFutile said:
It could be the hard buttons keying sequences (power and volume) and then the use the Volume button to scroll and then which one (button) is needed to be used to select Recovery.
As I'm remembering getting into Recovery required to do it multiple of times when I had the phone - again using the proper keying of the hard buttons in the right orders.
At Least these buttons are side mounted on Moto's and not on the back as another phone I have.
Click to expand...
Click to collapse
Yes they are hard button combination.
The instructions I outlined (works with my XT1550 ) are the general instructions which are identical in rest of osprey thread except in this tutorial.
I had assumed that the firmware of these models were identical except for radio.
I was just wondering if this model really has a different mechanism or it's just a mistake in original post
Broadcasted from Zeta Reticuli
Gravemind2015 said:
@MotoJunkie01 : AFAIK holding down power+volume down button boots directly into the bootloader mode (not recovery) and fastboot is accessible.
In OP, point 6:
Normally it's the other way around. Probably a typo? Just curious.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Hi ©Gravemind2015....thank you for pointing out my clerical error. Instead of "recovery" I should have said "bootloader' or " fastboot" menu in that particular instance. I'll edit the instructions accordingly.
So i can just go and flash this via twrp?
MimzyDesigns said:
So i can just go and flash this via twrp?
Click to expand...
Click to collapse
This build is not a TWRP flashable zip. Needs to be flashed via fastboot. The next release will be TWRP flashable.
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
tsakowich6217 said:
I ran flash-all, but now I'm stuck at "fastboot flash -u system system.img_sparsechunk.1"
Had been sitting there for about 30 minutes before I gave up and unplugged to try again. Same result.
Any advice?
Edit:
Error message before it hangs up:
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.247s
Click to expand...
Click to collapse
Did the partitions up until that point successfully flash?
This does happen before that as well. But besides boot and sparsechunk.0 everything else works fine.
Edit:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash -u system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
target reported max download size of 268435456 bytes
sending 'system' (131082 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.244s
Related
I'm using some guys guide for mac users:
1. Take a deep breath. It is just software and you are going to master it!
2. Download and install the Mac OSX Android SDK. I am going to assume for the purposes of this list that you have put it in /Applications/android-sdk-mac_86/tools/ but it doesn't matter.
3. Get fastboot-mac from here. Rename it 'fastboot' and put it in /Applications/android-sdk-mac_86/tools/.
4. Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip AND gapps-passion-ERE36B-2-signed.zip
from here and put them in /Applications/android-sdk-mac_86/tools/.
5. Get recovery-RA-nexus-v1.6.2.img from here and put it in /Applications/android-sdk-mac_86/tools/
6. Put Get Radio_20100203_2_Signed_PASSION.img,
update-cm-5.0.4.1-N1-signed.zip and gapps-passion-ERE36B-2-signed.zip
on the root of the SD card. You can do this by mounting the phone via a USB cable (this works just like any USB stick except you have to click a button on the phone's UI).
7. In your phone settings > applications > development, set usb
debugging to enabled.
8. Turn off your phone and put the SD card with the 3 files on it
into your phone.
9. Hook up the USB connection to your phone and your mac.
10. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)
11. In Terminal on your mac, cd to /Applications/android-sdk_mac_86/tools
12. Type ‘./fastboot devices‘ to make sure your phone is recognized
(it should list a device number rather than simply returning to
command prompt with no feedback).
13. Type ‘./fastboot oem unlock‘ to unlock the bootloader (wohoo, your phone is now rooted!)
14. Use volume keys on the phone to navigate to yes and press the
power button to confirm.
15. When the phone finishes booting, in your phone settings >
applications > development, set usb debugging to enabled, then power
it down.
16. Reboot phone into fastboot: Hold down trackball, push the power
button and hold both until you see the fastboot screen. (The fastboot
screen is the one with the Androids on skateboards)
17. (you're still in terminal in /Applications/android-sdk_mac_86/tools)
Type ‘./fastboot flash recovery ./recovery-RA-nexus-v1.6.2.img‘. (Note
filename will change as recovery image is updated)
18. Type './fastboot flash radio ./Radio_20100203_2_Signed_PASSION.img'
to also update your radio at this point
19. Once the Recovery flash is complete (should be almost instant),
press the Power Button. The highlighted blue text should now say
HBOOT. Use the volume down button to highlight "Recovery" and hit the
power button to reboot into recovery.
20. if this step fails, power down the phone, and try this: hold down
the VOLUME DOWN button and then hold the POWER button until you get to
the skateboard screen; use volume down to highlight RECOVERY and hit
the POWER button
21. You should now be in the Recovery screen after a reboot -- this
screen has 9 green text options at the top and an android x in the
center of the screen
22. Once in Recovery Mode, use the trackball to scroll down to
"Backup/Restore" and press the trackball three times, and wait until
the backup is complete.
23. Once backup is complete, wipe, since you're coming from stock
(even fastboot oem unlock may not fully wipe, do it just in case) many
users report the phone not booting properly without a wipe at this
point.
24. Scroll down to "Flash zip from sdcard", and press the trackball.
25. Select the CyanogenMod update (update-cm-5.0.4.1-N1-signed.zip),
and press the trackball again to confirm. Wait until the flash is
complete. (Note: this will take a little while).
26. Once again, Scroll down to "Flash zip from sdcard", and press the trackball.
27. This time, select the Google Apps File
(gapps-passion-ERE36B-2-signed.zip), and press the trackball again to
confirm. Wait until the flash is complete.
28. Once you are back in the main menu, press the trackball select the
first option (Reboot system now) and reboot the phone.
29. If everything was done correctly, the phone should boot into CyanogenMod!
Click to expand...
Click to collapse
My few questions...
Do I really need SDK? I've been reading a lot, and some say use it, some don't mention it.
I've already found that some of his files are updated, so I'd be using the more recent ones.
Also, I'm thinking that I'm NOT going to mess with the radio. I don't have to, right?
ETA: And then I see that his post says nothing about superboot. Am I supposed to do both? Fastboot and then superboot?
And then another question... I plan on getting a 16gb class 6 sd card. Should I wait to do this until I get that? Will I have to do it all over again?
Thanks!!
I am by no means a pro at this, but to answer a a question or 2 of yours...
I never bothered using the SDK. I did download it, but like you, I followed other instructions that did not tell you to use the SDK.
The important part is to put all the downloaded files into your renamed "fastboot" folder, where fastboot will know where to look for it.
Concerning the radio, some ROMS may or may not require different radios, but for the simple process of rooting your phone, I'm pretty sure you're cool.
I used fastboot, but superboot (if I understand it correctly) is a total tool for your use. Someone correct me if I'm wrong, but I believe it takes the place of all the steps you listed above, and does it all in one command.
Good luck! Its easy, and it sounds like you have all the tools you need!
1) I didn't flash a new radio when I rooted mine (didn't for a couple of weeks until I was comfortable with flashing and abd and stuff). The radio is evidently the greatest risk of bricking the phone.
2) I've typically seen "superboot" to refer to a rom image that modaco hosts that includes the superuser perms and apk and not as a tool (as fastboot is referred to). ymmv.
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
First boot into recovery (757):
{
"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"
}
Mount System RW (102):
File Manager 1 (010):
File Manager 2 (019):
Install SuperSU (243):
Celebrate
third post reserved for whatever
fourth post reserved for whatever
fifth post reserved for whatever
is this working for phab2 pb2-650m?
I assume so. The original work was based on a 650M but I can only validate my additions on the 650Y since I don't have a 650M
Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
You should make a video of the procedure. So you are saying after flashing the recovery, have to press power and volume up+down together until phab2 posts. What is posts? Do you mean reboots? And what do you mean by roll the finger?
Synman said:
This is NOT a guide for n00bs. You will need a functional copy of ADB and FASTBOOT (as well as any required Lenovo ADB drivers if you are windows tragic) running on your PC with Debugging enabled prior to proceeding.
This is NOT my original work. All the real credit goes to some guys in Russia as best as I can tell. I merely google translated their work and cooked up my own method for rooting (which is a bit easier than what they recommend). You can find their source materials here: Russian Lenovo Website - Phab 2 Unlocking the bootloader thread.
Grab the latest version of SuperSU from Chainfire (https://download.chainfire.eu/696/supersu/)
Download the version of TWRP I found on the Lenovo Russia website here (it is attached to this post)
Copy SuperSU to your Phab 2's SD Card (it can go on either the internal or an external drive) (ADB push SuperSUxxx.img /sdcard/)
You need to unlock your bootloader if you have not already done so:
Code:
adb reboot bootloader
fastboot oem unlock
Allow your Phab 2 to fully reboot and verify debugging is still enabled and the OEM unlocking option is enabled in Developer options.
Now that we've got a good clean operational unlocked bootloader let's apply our new recovery:
Code:
adb reboot bootloader
fastboot flash recovery TWRP-PB2-650_3.0.2.img
Hold down the power button on your Phab 2 until it powers off.
Press the center of the volume rocker (both vol+ and vol- need to be depressed) and at the same time hold down the power button until your Phab 2 posts. You'll know you did the procedure right because an ASCII arrow symbol will be scrolling through the device's 3 boot options (Recovery / Fastboot / Normal).
Release the power button and roll your finger holding the volume rocker to the volume up side of the rocker. Release the volume button.
Press Vol+ until Recovery is selected (it is the first option)
Press Vol- and wait 20 or so seconds for TWRP to load.
You now have to decide if you want to make TWRP your permanent recovery. If so, mount SYSTEM as RW and using TWRP's Advanced File Explorer navigate to /system and either delete or rename recovery-from-boot.p (I renamed mine to recovery-from-boot.p.save).
Go back to TWRP's main menu and select INSTALL. Navigate to the SuperSU image you copied to storage at the very beginning of this guide and flash it.
When you're done, reboot.
Don't panic when your Phab 2 bootloops once. It'll boot fine on its second pass. In another 20-30 seconds you will be greeted by a fully rooted Phab 2.
Enjoy! Screenshots are attached to the second post.
Click to expand...
Click to collapse
Hey thank you for the method. My device is PB2-650m Philippine version. Twrp recovery installed without issue , but after flashing supersu, would not boot. Stuck on second boot. I flashed UPDATE-unSU.zip to unroot and factory reset device. Flashed SuperSu-v2.79 and rooted without issue.
Too bad you didn't make a video...
Synman said:
Too bad you didn't make a video...
Click to expand...
Click to collapse
I did not have time. My phone got stuck on 2nd boot and was trying to figure out way to fix it. I fixed it by deleting supersu and factory resetting. I found different SuperSU version and worked. Thanks to you for providing me and the other phab2 owners with custom recovery.
Anyone get voLTE to work on this phone (PB2-650Y)?
query
http://support.lenovo.com/in/en/products/Tablets/PHAB-Series/PHAB2/downloads/DS118503
Did anybody flash PB2-650M OTA update. If you did, is there a way to flash it on rooted device?
thanx
thanx 4 news, got updated just niw 1.4 gb approx. Lets see.
stock rom for pb2-650m
I bought this phone last month. I gonna root my device and install twrp recovery. before that i wanna know whether stock rom available for this? if yes, please share me the link.
l.a.s.
Was searching for it, Lenovo smart assistant etc.. but couldn't find one.
I tried "adb" command in Linux. But not working. Saying "????? No permission". If anyone having USB driver means please share it with me.
lenovo companion appi installed above app,
I nstalled above app, and in search found mobile assistant appfor lenovo, guess it automatically installed usb driver s
Adb command working. And also I unlocked my bootloader. Gonna flash twrp. Any custom ROM for this device?
Hi All,
I've run into an issue whilst trying to flash LOS 15.1 on a Moto x4 (XT1900-01). After flashing LOS 15.01, I get the message "No OS Installed! Are you sure you wish to reboot?" for every Reboot menu option available in TWRP (3.2.3-1) (reboot options from Reboot menu: System, Recovery, Bootloader, Slot A, Slot B). I'm not sure what happened. Here are the steps I took prior to hitting this:
1. Unlocked the bootloader
2. Flashed TWRP per the instruction on TWRP for Payton on TWRP site
2-1. fastboot boot twrp-3.2.1-1.img
2-2. adb push twrp-3.2.1.zip /sdcard
2-3. Installed the twrp-3.2.1.zip from TWRP (apparently to install to boot partition on both slots)
3. Installed LOS 15.01:
3-1. Formatted via TWRP by doing Wipe -> Format Data
3-2. Advanced Wipe via TWRP by doing Advanced Wipe -> Select System
3-3. copied LOS to sdcard: adb push Lineage15.zip /sdcard
3-4. TWRP Install by Install -> select the Lineage15.zip
4. Once complete, select reboot and this is where the message "No OS Installed! Are you sure you wish to reboot?" comes up.
I haven't opted to reboot for fear of not being able to get back to recovery. I'm not sure what to do at this point. I'd like to understand what happened, but I would also like to find a way to recover from this and either get back to square 1 with stock ROM or even better complete the LOS install. Thanks in advance!
Just reboot recovery
St.Noigel said:
Just reboot recovery
Click to expand...
Click to collapse
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
mikeybravo said:
I tried to reboot to recovery ignoring the error, I get nothing now. Phone won't turn on, can't key combo (vol up + power, vol down + power, any of them) and it just seems dead now. I've held each of the key combos for a couple minutes each, nada. Any thoughts from here?
Click to expand...
Click to collapse
Did you try to connect phone to the PC? Is phone charged?
St.Noigel said:
Did you try to connect phone to the PC? Is phone charged?
Click to expand...
Click to collapse
Yes, phone was at about 98 percent when doing reboot. Plugged into computer (Mac), adb devices returns nothing. Not sure how this could've gone as bad as it seems it did? Not sure of anything else I can try here...
have you access to Windows or Linux PC? I know nothing about Mac... (
St.Noigel said:
have you access to Windows or Linux PC? I know nothing about Mac... (
Click to expand...
Click to collapse
Yes, I plugged into both Mac and PC. MDM installed on PC as well adb tooling. Plugging into either computer does nothing, doesn't show up in device list. Tried the key combos while connected to each (vol up + power, vol down + power, power, power + vol up + vol down all for a couple/few minutes each). What I don't understand is what the heck happened. TWRP should've been flashed to boot on both slots based on TWRP docs for Payton. I read something about some issues with A/B slot switching (or not switching), but if TWRP was flashed to boot on both slots, I would've expected to at least be able to get back to recovery? I'm not really sure what to do from here since I can't even get the phone to turn on.
I have had seen that message on my phone too. I just reboot and it works just fine.
I ran into the same problem. I managed to fix my phone. From what I understand this happens if no OTA update was flashed before to initialize the partition structure in slot B. Check out [1] which suggests to install copy-partitions-payton.zip via sideloading it into TWRP before installing Linageos.
Concerning your brick: Your phone should still be recognized by your computer. Check the device manager or lsusb on Linux. For me I got something like "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)". Reading through the threads [2,3,4] it became clear to me that I needed a "blankflash" or the qboot utility to recover the phone. The utility talks to the phone via a serial interface over USB. Look through the threads to find the qboot utility. I needed many tries to find the correct qboot utility and to get it to successfully blankflash my phone. The --debug=2 command-line switch of qboot helped me to get confidence that something is happening at all. I needed to press vol+ and power before starting the qboot utility with "./qboot blank-flash --debug=2" on Linux. I think it was also necessary to then _not_ hold these buttons for too long. As I said the debug outputs help to figure this out. Good Luck!
[1] https://forum.xda-developers.com/moto-x4/development/rom-lineage-os-15-1-t3802265
[2] https://www.reddit.com/r/LineageOS/comments/9yahhc/i_hardbricked_my_new_phone_looking_for_advice/
[3] https://forum.xda-developers.com/moto-x4/help/moto-x4-hard-brick-t3777529
[4] https://forum.xda-developers.com/moto-x4/help/q-howto-x4-to-los-setup-bricked-t3883645
@macin42, thanks for the info on this. It makes sense, and I will give it a go. I'll follow up with the outcome as soon as I do; planning by the end of the weekend to give it a go.
@macin42, your instructions worked perfectly! Thanks so much for the help on this. As a recap on the issue: the problem for me was that I skipped the "Copy Partitions" step as it was a new phone and the phone hadn't received any "first" OTA updates. This step was necessary and wasn't mentioned in the official LineageOS install instructions on the LineageOS site. This step was mentioned however on the XDA LineageOS install instructions.
To recover from this, I followed the instructions that were given as help above by doing the following:
1. Downloaded the blankflash.zip from link provided above
2. Installed the Motorola Device Manager drivers (already had)
3. Installed adb and fastboot (already had)
4. Plugged in phone to PC via USB
5. Ran the following command while holding down the power up + volume buttons: qboot blank-flash --debug=2
NOTE: The qboot command didn't work for me the first time, but I re-tried a couple of times and it ended up working after the second or third try.
6. Once this completed the phone turned on and made it to the bootloader.
7. Once I made it here I was able to redo the steps that were given on the XDA thread to install LineageOS (post above), which were:
- Download the Copy Partitions zip from link above then:
- fastboot boot twrp.img
- adb sideload copy-partitions-payton.zip
- In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
- adb sideload lineageos-nightly.zip
- Navigate back to the Reboot menu in TWRP, select reboot, then select recovery, swipe to reboot. I did get the same "No OS installed" warning here but it wasn't an issue.
- This brought me to the LineageOS recovery.
- I chose to install Mind the GApps, so from the LineageOS recovery I selected Apply Update, Apply from ADB, then on computer adb sideload mind-gapps.zip
- Reboot
From here it was business as usual with the typical phone setup. Thanks again to those that helped on this!
Glad it worked out. In case your microphone and or sound does not work (silence in calls, recorder app does not work) please let me know - that's where i am currently stuck with my xt1900-7.
The TWRP 3.5.1 is developed by @hendramanu and support Galaxy A50s One UI 3.1 Android 11 DUB6 firmware, Android security patch level: 1 March 2021. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Flash TWRP and Rooting Instructions
Make sure the bootloader are unlocked
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing TWRP-3.5.1_9-0-A50s_A11_Magisk.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Appears.
Select Wipe -> Format data, type 'yes' and confirm
Select Install - multidisabler_samsung.zip, Swipe to confirm Flash
Select Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Install Magisk and Open it. Magisk will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Download
https://forum.xda-developers.com/t/...-9-0-for-samsung-galaxy-a50s-sm-a507.4251671/
Video Tutorial
Thanks for your contribution
help me, please !
Hello there. Hope this helps!
FIRST OF ALL, this WILL VOID your waranty. Read the steps BEFORE doing anything
ALSO PLEASE READ THE NOTES AT THE BELOW POST.
UNLOCK BOOTLOADER: It's not "easy" at all (You'll have to open your tab).
Go to device info on tab settings.
Press compilation number for several times until "you're a dev" message appears (It'll prolly ask your pattern/password to continue).
Go to dev options and enable OEM unlocking.
Shut down the tab.
Download PotatoNV sofware from here. (Credits to mashed-potatoes)
Download minimal adb and fastboot from here.
Prepare your environment:
Open your tablet
Grab a clip or a cable
Keep your cool
Follow the steps shown here. KEEP THE GENERATED CODE. This will avoid you from opening again the tablet in the case you have to do a downgrade. The way to unlock it again is writting
Code:
"fastboot oem unlock <code>"
at fastboot mode.
Here you have an image of where the testpoint is.
FLASH TWRP INTO THE TAB:
Follow CAREFULLY this steps:
Shut down the tab
Connect the tab to the PC and hold vol- & pwr button.
Now it'll appear a white screen with some text. If it appears "OEM unlock" in green, then everything's fine. IF NOT, follow unlock bootloader steps again. Then try rebooting into fastboot mode again (vol- & pwr).
Download Pretoriano80 .5 version TWRP from here.
Open Minimal ADB and Fastboot and write this:
"fastboot flash recovery_ramdisk path_of_twrp.img"
It should appear everything OK.
Type "fastboot reboot"
Fastly disconnect the tab from PC and hold vol+ & pwr button before Huawei logo appears (if it appears, just do a hard reboot (hold pwr button) and try again (just hold vol+ and pwr, no need to go back to fastboot).
You're now booting into TWRP!
RESOURCE DOWNLOAD
DOWNLOADING UNTESTED ROMS MAY LEAD TO MAJOR ERRORS
All HI6250 ROMs are "compatible" in some way, wouldn't recommend to install unless proven
A list with all tested and proven to work ROMs can be found here
Download any ROM you want from the above link. The list will be increasing with the time
Download the data decrypter from the MEGA folder (you can also find the link in the ROM list)
(OPTIONAL) you can download gapps. You can also download the version worked for me (little outdated) at the same MEGA link and update them later at the PlayStore.
(OPTIONAL) You can download Magisk from the "ZIPS" folder at the Mega link. GENERIC MAGISKS MAY (99%) NOT WORK ON THE GSIS.
PREPARATION STEPS
Boot into TWRP (vol- & pwr buttons while tab is off)
Don't make system Read Only (Just swipe the first window). This will lead you to a multiple choice menu
Head to INSTALL and select the decryter you will have in a SD card.
Swipe to confirm installation
Go again to main menu and head to WIPE and select "Format data option".
Type "yes" on the keyboard and press enter.
Then go to main menu and head to REBOOT>RECOVERY
If a message appears saying you to install TWRP app, just decline it.
Once in TWRP again, head to WIPE>ADVANCED WIPE and select dalvink/art cache, cache, data and system.
MARKING OTHER THAN THIS OPTIONS WILL LEAD TO AN IMPORTANT ERROR.
Return to main menu
THERE ARE 2 WAYS TO INSTALL A ROM:
1 -- VIA FASTBOOT:
Reboot your tab into fastboot mode (vol- & pwr buttons while connected to PC)
Open minimal adb and fastboot and type:
Code:
fastboot flash system <path_of_rom>.img
Now, wait... (Sparse header file error it's normal)
Once it has finished, type: "fastboot reboot" and disconnect from PC
2 -- VIA TWRP:
Once in TWRP head to INSTALL, press the "install image file" button.
Now head to the route where the .img file of the ROM is.
Select it, in the multiple choice menu select "SYSTEM IMAGE" and swipe to confirm installation.
Once finished, reboot to ROM or continue with the steps in order to get Google or Root working.