Hi
I recently completed installing official LineageOS 17 on my 6T using TWRP, not the recovery on Lineage wiki page. Restarted the phone a few times and playing with it for a couple of days. Things seem to be working well. I do have a few doubts though:-
(1) About the A/B partition thing. I did a simple wipe prior to installation and I am not sure I have installed it on the correct partition. How can I check to make sure ? Can I copy partitions now and if so, how ?
(2) I do not plan to use payment apps on the phone but I do plan to use the protonmail apk which I have already installed. How safe is it to leave the bootloader unlocked especially when the "Automatic System Updates" is on ?
Thanks
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
2. You can't lock the boot loader unless you make your own build and sign it. So it must remain unlocked. There is a guide for doing this if you want in the guide section.
OhioYJ said:
1. There is no wrong partition. Every update / installs will alternate between A/B partition. If it boots don't worry about it.
Click to expand...
Click to collapse
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
anuk221 said:
Thanks so much for allaying my fears. I read somewhere that in case of issue with Lineage partition, the mobile will try to boot up the other partition which might have older version of Android OS, causing a brick.
I was thinking of configuring my gmail account on the stock email app and was apprehensive that an unlocked bootloader might cause a safety block from Google.
Click to expand...
Click to collapse
On a clean / first install of Lineage you would typically install it twice to get it on both A/B partitions. The other option is to use the copy partitions zip. The zip is mentioned in the Lineage wiki I believe
It's not a safety block, you just will come up as not certified, which likely is already the case. This will not cause you any problems other than certain apps won't appear in the play store. (Such as Netflix, things like that).
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
The other partition would only try and boot if Lineage failed to boot. If you didnt install it twice, it would be an easy fix now to just install it again, or use the copy partitions zip. Usually I just update or install without worry, but I would backup just to be safe in this case since your steps are a little out of order. Always better to be safe than sorry.
OhioYJ said:
I have a installing Lineage guide here. See the section on Magisk about getting the device to be certified again. There is a cliff notes version in the second post as well, you can see my Install method and update method.
Click to expand...
Click to collapse
Thanks for the link. I had checked your guide amongst others prior to installation.
I was getting the following startup screen on boot and it didnt lead into TWRP recovery or bootloader even when I used the "volume up+power" combination at startup :-
{
"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"
}
Which is what led me to think that I hadnt done a clean/proper install. I had used "Tool ALL IN One" to unlock the bootloader and I had deviated from wiki and gone the TWRP route for recovery since I was not sure if selecting "Apply Update" in recovery and then "Apply from ADB" would work.
Anyways, I redid the whole thing again last night using Lineage OS recovery. I still get the above screen at startup but now when I select the power button, it takes me into LineageOS recovery.
Again everything seems to be working well prima facie, except that this time when I insert a Sandisk USB C Dual Drive, I get a message "Issue with Sandisk USB Drive. Tap to fix". The drive works fine on my 8T !
anuk221 said:
Thanks for the link. I had checked your guide amongst others prior to installation.
Click to expand...
Click to collapse
Different devices have different kernels with different things enabled / disabled, giving them different capabilities. Honestly I've never tried thumb drives on my phones, I guess I could try one on my 6T and 8T and see what I get later. I'll see if I can find an adapter cable, as I don't have a USB C drive.
You do have to let go of the power button for a moment to get into fastboot. It will pause when it gets to that bootloader unlocked screen. At least that's always been my experience.
Every time you install LOS on the 6T it replaces TWRP with LOS recovery. TWRP must be re-flashed everytime if that's what you prefer to use. That's why that step is in my guide.
OhioYJ said:
Different devices have different kernels with different things enabled / disabled, giving them different capabilities.
Click to expand...
Click to collapse
That is correct. The drive in question is a 64GB drive formatted in exFAT. I tried another drive, 32GB formatted in NTFS and it was being detected by both the 6T and the 8T ! Probably an issue with the exFAT kernels as you pointed out.
I am surprised though that some very basic features which I had assumed would be available seem to be missing - No option of ungrouping/declubbing sms conversations, no option of exporting to SIM, no option of getting timestamp in call log. In that sense LOS appears to be more of a de-googled version of android than a standalone OS.
Related
Okay, so I was on the Stock 2.3.4 GB rooted rom, I tried to flash Android Revolution but somehow I downloaded the Sensation one and tried to flash and it gave error Status 7 (4EXT).. So, I went back to stock 2.2.1 and perm-rooted and my S if still off, so I flashed recovery and tried to flash Runny Mede, it dosen't dare to pass the MyTouch 4G logo, and just starts a boot loop right there. Please help, I want to enjoy other roms just like you guys too! Also, everytime I mount my phone as a Disk Drive, windows asks me to Scan for errors, I do it (with both options checked) and it just immediately closes and goes into the root of my SD.. Please help me.
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click it and choose your device to safely remove it from your computer.
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
crawler9 said:
Make sure when flashing a new rom to wipe data/cache. I'd recommend wiping system too, just to make sure you don't run into other issues.
This comes from memory only, (Anyone- don't hesitate to correct me if I'm wrong) and I couldn't find any info about it to confirm, but I believe Status 7 simply means the installation of the zip file you attempted to flash was aborted, i.e. nothing was flashed. Many ROMs have checks in them to confirm you're flashing to the correct device, and if not, will refuse to proceed, and this may be what you encountered.
As for Windows asking you to scan for errors, this happens any time you disconnect your phone or unmount it without safely ejecting via Windows. It's unlikely you would actually have any disk problems or corruption unless you disconnected or unmounted while files were still being transferred or edited. Safely unmounting would be considered the best practice. When you're ready to disconnect your phone from your computer, or to unmount the SD card from Windows, look for an icon like this.
Click it and choose your device to safely remove it from your computer.
Click to expand...
Click to collapse
estallings15 said:
Going back to froyo and "re-rootong" was a complete waste of time.
Status 7 would indeed mean nothing was flashed (nice post by the way, to the guy above me).
All you needed to do was wipe system, data and cache a flash the correct ROM. Alternatively, you could have restored the backup that you should have made before you tried flashing ARHD.
Try holding Vol down at boot to get to bootloader. Once there select Recovery. That will get you on the right path. Remove PD15IMG from the root of your SD before you do this.
Edit: I just remembered that your recovery is stock if you flashed PD15IMG. You will need to flash a recovery.img with adb. The steps are in the clockworkmod thread that is stickied in the dev section. There used to be a PD15IMG of an older 4EXT recovery floating around. You might try locating that.
Click to expand...
Click to collapse
Thanks to both of you, I tried flashing TRAD v1 and it worked, made a nandroid, just flashed virtuous Affinity maybe 2 minutes ago and its booting. I guess I just panicked a bit. c:
It's easy to do if you aren't used to flashing. Those minor heart attacks aren't fun, either.
Tell me about it. : )
{
"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"
}
Following the "Root Question" thread (https://forum.xda-developers.com/moto-e4/help/root-question-t3626349), rooting and customizing the E4 becomes pretty simple.
Here's what I did, following that thread:
Booted to the Bootloader
Flashed my phone back to stock (to start fresh) using the Moto E4 Factory Image
Used "adb boot" to boot into the cedric TWRP image
Downloaded and transferred Open GAPPS (7.1, ARM, Stock), su, and dm-verity (from the root thread) to an SD card
Flashed GAPPs, su, and dm-verity, then cleared the cache, and restarted to system
Walked through phone setup, logging into Google account
*Manually had to install Google Camera via the Play Store website, as it didn't show up automatically for some reason (?)
Post-setup, install a SU management app (SuperUser from JRummy), Flashify, and Magisk
Use SuperUser to get Root access, use Flashify to flash the original boot.img, then use Magisk to root, and restart w/ Magisk root, then remove SuperUser
!Magisk root is working, but is not currently passing SafetyNet
Adding Open GAPPs whilst in the recovery replaces and adds all of the stock Android (Pixel) software items, including the Pixel launcher. The only exception was the Google Camera, which did not get installed correctly/completely/at all, for some reason. I had to manually visit the Play Store site, locate the camera, and install--which worked fine.
Save for the colored pixel navigation icons and live/dynamic wallpapers, this transforms the E4 into a mega-affordable Pixel.
I'd like to try this.
Well, I did but the dialer was wonky.
I dirty flashed Gapps. On encrypted phone with Magisk. Seems encrypted was the only way to get Magisk instead of SuperU, which didn't seem worth the trouble since I couldn't actually do anything with Magisk or any modules besides administer root. I digress...
I tried to clear cache from Fireflash. Since ADB with TWRP is a pain. I jacked up my PIN code and restored to a TWRP backup I had with the other S.U....
So, I have tried to start over but I don't know how to flash stock image. TWRP says invalid zip or something.
I reverted to stock and the not Magisk. I've had OnePlus 1 and Oneplus 3 and Nexus 5 before. I realize they had a little bit broader dev support when new, but this Moto is just different enough to stump me.
TIA
bakerbarber said:
I'd like to try this.
Well, I did but the dialer was wonky.
I dirty flashed Gapps. On encrypted phone with Magisk. Seems encrypted was the only way to get Magisk instead of SuperU, which didn't seem worth the trouble since I couldn't actually do anything with Magisk or any modules besides administer root. I digress...
I tried to clear cache from Fireflash. Since ADB with TWRP is a pain. I jacked up my PIN code and restored to a TWRP backup I had with the other S.U....
So, I have tried to start over but I don't know how to flash stock image. TWRP says invalid zip or something.
I reverted to stock and the not Magisk. I've had OnePlus 1 and Oneplus 3 and Nexus 5 before. I realize they had a little bit broader dev support when new, but this Moto is just different enough to stump me.
TIA
Click to expand...
Click to collapse
You are trying to figure out how to flash stock? Use rsdlite
I gathered that looking into it earlier. Thanks for replying. I was hoping it was something a little more straight forward that I already knew how to do. My last Motorola was a Pebl. Hahaha.
I installed rsdlite last night after a little reading. I'll be doing it tonight maybe after some more reading.
I appreciate it. Great idea in the first place flashing Gapps. Might have to try the aroma installer though. I don't want or need everything stock with such little space on this phone.
bakerbarber said:
I gathered that looking into it earlier. Thanks for replying. I was hoping it was something a little more straight forward that I already knew how to do. My last Motorola was a Pebl. Hahaha.
I installed rsdlite last night after a little reading. I'll be doing it tonight maybe after some more reading.
I appreciate it. Great idea in the first place flashing Gapps. Might have to try the aroma installer though. I don't want or need everything stock with such little space on this phone.
Click to expand...
Click to collapse
It's super easy to use, you just open rsdlite, select where you downloaded the stock images, plug your phone in, and press install. That's it. It takes a while (like half an hour) to finish.
bakerbarber said:
I gathered that looking into it earlier. Thanks for replying. I was hoping it was something a little more straight forward that I already knew how to do. My last Motorola was a Pebl. Hahaha.
I installed rsdlite last night after a little reading. I'll be doing it tonight maybe after some more reading.
I appreciate it. Great idea in the first place flashing Gapps. Might have to try the aroma installer though. I don't want or need everything stock with such little space on this phone.
Click to expand...
Click to collapse
Yep, it's up to you. I used the Stock package, and after updating all apps via the Play Store, I had 8 GB of free storage space available.
The E4 processor is slower, and even more noticeable, the low light camera performance of the E4 is not good. You will not get a Pixel from an E4.
Cool project though.
How to install google camera from playstore ?
Can you provide an apk ?
For anyone who's interested come check out the Moto e4 community on G+ https://plus.google.com/communities/106649090634219918238
*** Important: Your Warranty Is now Void. Always take a Nandroid backup. I am not responsible if you damage your phone or lose any data***
Hello everyone. I created this guide for the Canadian D852 since I didn’t find anything that was straight forward. Credit goes to all the developers who made it possible for us to keep using our beloved LG G3.
This is my first attempt to create and share a guide. I hope it will be useful to other users. If you find any error or have suggestions, please send me a message.
Download all the files before you begin. Do not forget to copy your ROM and GAPPS to your SDCARD before you install TWRP.
Go back to Lollipop using LGUP **Always use USB 2 port. It won't work with USB3**:
Download your kdz (d85220… not d85230). I downloaded mine from:
https://lg-firmwares.com/lg-d852-firmwares/
Follow these instructions (works with D852 don’t worry):
https://forum.xda-developers.com/showpost.php?p=64624353&postcount=3
Choose the kdz from your provider. For example, I have an unlocked Fido phone but I want to use it with Bell. So I used the Bell 20k KDZ.
When selecting a file to flash, type *.* and press Enter in the filename for your .kdz to show up. If you do not, it will only show .tot.
{
"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"
}
Root your phone using this method:
Enable ADB debugging.
Unplug usb cable.
Go to Settings > About Phone > Software Information and tap build number until you are presented with "You are now a developer".
Back to Settings screen.
In Developer Options, enable USB Debugging.
Connect usb cable.
Click OK when asked to allow USB debugging in android.
I use the root.bat method. If it doesn’t work go back to step 1 and try again.
https://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Install TWRP using Autorec:
Copy the rom and GAPPS to your SDCARD before you install TWRP.
Download the file from here:
https://mega.nz/#F!rtI1naZT!LJIKUVpv8fYjrvhpykA4_A!2o433RBZ
Transfer the file to you internal or external SD card.
Head in to Settings -> General -> Security, then scroll down until you see Unknown sources. Tick the checkbox, then hit OK on the next prompt.
Install APK via the file manager.
Open App.
Grant root access.
Wait a few seconds while it does some backup.
Wait for prompt to say that it is ready to flash.
Click the button to Flash TWRP.
Wait for it to be done.
Phone will reboot into TWRP
Update TWRP to the latest version if you want.
Download and install Nougat rom. Tested with CrDroid v3.6 and open_gapps-arm-7.1-nano.
https://forum.xda-developers.com/lg-g3/development/rom-crdroid-t2955012
http://opengapps.org/
**I’m not sure if it’s necessary but I did it anyway** Flash Dene Hybrid Baseband via TWRP (don’t forget to wipe cache and dalvik after) if necessary (mobile data is unstable etc…).
https://mega.nz/#F!rtI1naZT!LJIKUVpv8fYjrvhpykA4_A!2tJFBLLK
Source: https://forum.xda-developers.com/lg-g3/development/canadian-d852-stock-bumped-rooted-rom-t3056843
That’s it! Enjoy Android Nougat!
N.B. That is the only way I was able to get a stable mobile data connection. Only flashing baseband did not work for me.
Thanks, barguin, for a very informative thread.
How is the battery life on this Nougat ROM? I will be switching from Fulmics MM, and my provider is Fido.
Battery is very good. I can do a full day easyly.
Regards!
@barguin: thanks for the quick response. Did you try Exposed for Nougat? I know that Exposed is frowned upon in the CrDroid thread, but there are a couple of modules I would like to try. Thanks.
I do not use exposed...sorry.
Thx
You saved my pitiful unrooted D852! Thxsm
Officeryanki said:
You saved my pitiful unrooted D852! Thxsm
Click to expand...
Click to collapse
Happy to hear that
Btw
Can i flash with lg flash tool? And also if im flashing with lgup do i go into download mode
Officeryanki said:
Can i flash with lg flash tool? And also if im flashing with lgup do i go into download mode
Click to expand...
Click to collapse
Personally I had some problems with lg flash tool.
There is no need to enter download mode! LGUP will do it for you.
I read the heading in this thread and it said something about not downloading the D85230 file .. and my phone is D8530g as shown in the screenshot .. so is the D85220 file gonna damage my phone .... Sorry for the newbie question !
Sent from my LG-D852 using XDA Free mobile app
The D85220 file will not damage your phone. Instead, that file will install an older Android version on your phone, namely Lollipop (this step is required to gain root). You are currently on Android Marshmallow, and you will end up with Android Nougat if you complete all steps correctly. The procedure is meant to work like this, one step back, two steps forward.
The "20" or "30" in the file names (on that website hosting KDZs) have the following meaning:
"20" = it's a Lollipop file
"30" = it's a Marshmallow file
"40" = it's a Nougat file (I can only wish, there is no such Nougat file).
But seriously, the procedure requires more than a modicum of familiarity with flashing and with using various pieces of software. There is potential for bricking your phone.
No offense, but, judging from your question, I would suggest that you should enlist the help of a friend who is a bit more knowledgeable on this topic.
Guys .. Can I use the ROM on D855?! If not, so how to flash the ROM without getting any issues?!!
Thanks.
Do not flash the rom on the D855 it's only for the canadian variant.
Did this on my d852 and it's stuck booting on Oreo, Nougat, and stock Lollipop. Happened after I installed TWRP, any fixes?
edit: i think it was the roms.. got 3 bad ones i guess lol. fulmics worked.
Just an FYI, I followed the LGUP instruction for my Bell D852 but it was soft bricked, doing the flash using "refurbish" instead of "upgrade" did it for me and I was able to finish rooting my device!
How to root symphony i60.... please reply me
my phone no sound
I do not hear sound from my phone after installing CRDroid. the programs are working. YouTube is opening but I can not hear the sound of the media being played.
I do not hear the sound of the media played when I plug in the phone.
please help me.
Thanks alot man, this was super handy!
Edit: Seems I've got that problem where shutting the phone off bugs it and it won't turn back on unless you remove the battery and put it back in. It also resets the time. Kind of annoying. Seems to happen to some D852s after installing TWRP.
-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.
N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"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"
}
ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Josephdbrewer25 said:
Hello all!
I have a question concerning a device, I have a Cricket Dream 5G and the device is completely bootloader unlocked. However, I'm trying to figure out how I can obtain a firmware file for the device seeing as the Carrier or manufacturer hasn't released one. It is a MediaTek device running the MT6833 and efforts to make a scatter file in order to read with SP Flash tools have been unsuccessful,
I've also attempted to download an OTA update and see if it saved the file locally, as well as packet dump the update process via Wireshark. No Cigar.. it appears to be in the Cache partition which isn't accessible without root (which cannot be obtained without running TWRP with the device being Android 11). does anyone have any suggestions on how I might be able to get a copy of the system image or boot images for the use of making a working TWRP?
Thanks a lot!
Click to expand...
Click to collapse
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
SubwayChamp said:
It works for most of newer MediaTek devices, you could back up any partition from it https://github.com/bkerler/mtkclient eventually you could root it too.
As per a TWRP for your device, you should try to build it from source or porting it from a similar device (system image not needed though) or wait for some developer to do it.
Click to expand...
Click to collapse
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Josephdbrewer25 said:
I've successfully backed up the device and gained root access. Thank you so much for recommending this tool. It worked, just voided my warranty lol. Had to disconnect the battery which requires taking apart the device
Click to expand...
Click to collapse
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Josephdbrewer25 said:
Also do you know where the stock recovery is located. I can't seem to find it anywhere, like it doesn't even exist.
Click to expand...
Click to collapse
Newer devices doesn't have a dedicated recovery partition.
SubwayChamp said:
Usually when a device's software had been modified, it may lose the warranty, or not, depending on what the "small" letters on a contract says, anyway, you could restore to its original state at any time, as you see in the need to claim it.
Normally, this tool works only installing the USDK64 drivers, and connecting device when power off, pressing the two volume buttons, I never need to open the back cover as MediaTek devices have the preloader mode, that it used by this tool to bypass the DA/SLAA protection, it does in the first stage the same thing that this tool does https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement/ but without the need to use SP Flash tool but reading/writing directly onto the device.
Newer devices doesn't have a dedicated recovery partition.
Click to expand...
Click to collapse
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
My device is the Cricket Dream 5G EC211001. It's weird
Josephdbrewer25 said:
It wouldn't stay in preloader mode, after a few minutes it would just reboot. Disconnecting the battery worked.
As for the recovery, I know it doesn't have a partition but it's gotta be somewhere, right? I can boot into recovery. It's been awhile since I've dabbled in this. My last phone I rooted was the Moto X 1st gen but to build twrp I need the stock recovery, right? I've seen on the net it's in the boot.img but I've yet to see it.
Click to expand...
Click to collapse
It doesn't really need to stay in preloader, this is the whole purpose of this tool, preloader is, actually, useless for flashing, when you press the two volume buttons, the device enters to preloader mode
{
"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"
}
if you installed correctly the drivers, then, mtkclient detects the device, in the short time, and make it return to BROM mode through a handshake, to bypass the DA/SLAA authorization,
BROM mode is disabled by OEMs, similarly to EDL point, without this kind of tool, no more remedy that opening the back cover.
Moto 1st gen, it's a long time ago. It is placed in a tiny portion of the ramdisk, but you don't need to find where’s located.
If you think to port it, actually is not as easy due to newer implementations, A/B slots, virtual slots, a way to fix it permanently, etc., but basically what you need is in the boot image