Related
I do not have 10 posts yet, remove underscores from urls. I will edit this when I have 10 posts, I'm sorry for the slight inconvience.
Hi, new here! I recently acquired a Motorola G7 (xt1962-1/river_amz) from my sister. The device did not boot. It mentioned that the device did not start-up successfully, something in relation to slot/a and slot/b, and that I needed to utilize a Software Repair Assistant.
Non-Verizon devices cannot utilize this Software Repair Assistant, I tried and it hung at Processing Device Info. For Non-Verizon devices there's a piece of software called Lenovo MOTO Smart Assistant which can be found: https://support.lenovo.com/us/en/downloads/ds101291
This option did not work for me as the Bootloader did not for some reason allow the device to overwrite some of the content (permission was denied device side.)
The MOTO Smart assistant was good for downloading the devices software. So you do the following:
Download and install the smart assistant software
Click the flash option and then the rescue option
Click moto phone
Select moto g (7th gen)
Select xt1962-1 and then next to target and firmware name there's a download button press that and the firmware will start downloading
You can follow the onscreen instructions for that program, like I said however, it didn't work for me so I'm just going to tell you the steps I went through to get the device working. If you have other solutions, I, as well as the rest of the MOTO G7 users will be happy to hear what worked for you I'm sure.
I tried downloading the files from /moto-g7/development/moto-g7-river-xt1962-1-firmware-29-114-t3913673 on this site and flashing those with some of the below mentioned methods but, no dice.
The default firmware download directory is C:\ProgramData\LMSA\Download\RomFiles btw.
I didn't want to fuss with trying to get RSDlite working on Windows 10. I found that an older PC with a 32-bit install of Windows 7 was far easier to manage, so, that's what I went with.
To follow what I did:
Download RSDlite 6.2.4 from rootjunky's site via: http://rootjunkysdl.com/files/?dir=Android Programs
Download 32-bit drivers from: http://rootjunkysdl.com/files/?dir=Android Drivers/Motorola if LMSA did not install them already
Copy the firmware folder to your desktop or somewhere easy to work from
Ensure your device is in bootloader mode
Open RSDlite and your device should be detected
Select the firmware folder and open flashfile.xml with RSDlite and press start
Let the process finish and don't interupt or you will have to do it all over again
The phone should boot, you will more than likely have to sign into an google account that's already been in use on that device (due to FRP)
You can also use the XML to BAT method, that didn't work for me (remote permission denied/device side)
I hope this helps some people who struggled like I did. Also, sorry if some things are badly worded if at all. I'm autistic and have trouble explaining and expressing things.
Check out my stock resources thread: https://forum.xda-developers.com/moto-g7/development/riveramz-stock-resources-t3917937/
Worked perfectly!
Thanks! I had the same issue (my wife's Moto G7 stuck at the bootloader) and was able to follow your directions, so much appreciated.
The only change I made was to follow the directions at this video (go to youtube/watch?v=njXQYn53SPc) to perform the XML to BAT instead of using RSDlite (since I was on Windows 10).
It worked perfectly and fixed the issue--and the great thing was that by converting the servicefile.xml instead of flashfile.xml, I was able to retain all the data on the phone.
The overall sequence of steps (listed in detail, since this was my first time flashing. Remove underscores from URLs):
Download Lenovo Assistant from your link
In Lenovo Assistant, go to Flash, then Rescue, then select model of phone. Click to download the firmware (but do not actually click the "rescue" button).
Download Google's Platform Tools (to get fastboot and ADB)
Make a folder to hold everything (called "flash")
Copy the downloaded firmware folder from C:\ProgramData\LMSA\Download\RomFiles to flash folder. Copy the fastboot, adb, and adb dll's from the Platform Tools to the firmware folder (per the video).
Copy and edit commands from servicefile.xml to a new servicefile.bat, as described in the video. Place this file in the firmware folder.
Run batch file in command prompt from the firmware folder.
That got the phone running again, with all data intact.
Thank you so much, worked like a charm.
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Sent from my Samsung SM-G973U1 using XDA Labs
mattmsr82 said:
Mine doesn't seem to have any partitions anymore. All my phone does is fast boot mode. And it won't let me flash anything... Please [email protected]
Click to expand...
Click to collapse
May need to use a
Loader file or blankflash
See
https://forum.xda-developers.com/moto-g7/help/loader-file-to-unbrick-moto-g7-t3938342.
Sent from my mata using XDA Labs
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
start up failed
your device didn't start up successfully.
use the software repair assistant on computer
to repair your device
connect your device to your computer to get
the software repair assistant.
AP fastboot flash mode (secure)
no bootable a/b slot
failed to boot Linus.falling back to fastboot
Fastboot reason: fall-through from normal boot mode
USB connected
Click to expand...
Click to collapse
MrCabana said:
I followed sd86's guide and used servicefile.xml instead of flashfile.xml, as suggested by chi2.
No problems whatsoever installing RSDlite 6.2.4 on Windows 10 x64 (1909). The drivers were installed by LMSA and I have no idea why you guys said it was difficult.
Just for the record, my phone is a Motorola G7 (xt1962-4), that out of thin air started showing the following message:
Click to expand...
Click to collapse
I ended up sending my phone back to Motorola, they they fixed it and sent it back overnight...
Sent from my Samsung SM-G973U1 using XDA Labs
Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!
I don't have a Windows 10 PC...plus, if I screw up my phone, I'll catch hell from the wife...lol
SO...that being said, if someone has an XT1962-6 'River' RETIN phone running Android 10 w/June Sec. Patch....I'd be willing to 'donate' to their paypal for a copy of my phones fw! Anyone interested plz pm me. Thx!
Good day, your post was very useful for me, bring back my phone, Im very grateful, thanks, sorry for my english
switch off your phones and connect usb.
first install drives to your pc by searching where to find device drivers motorola
then download lenovo smart assistant and press rescue
Hi. Im new here too. Well been for a while just my second post and the first time iv actually been able to flash a rom. I have the same problem. No bootable slots. I know exactly what i did wrong. I knew it the moment i hit the reboot button. However, i run zorin 15 on my pc and the levono assistant don't support linux. Anyone know where i can acquire the assistant running linux? Greatly appreciated in advance.
Thank you very much sd86 and chi2 for your research and help
Sadly my phone can't boot after flashing clean OS
I don't want to erase UserData partition, but it seems error is there (as it's only left partition untouched).
As I still would like to keep my data (this is the most important thing on our mobile devices) the only one hope is to unlock bootloader, flash recovery partition (eg. with TWRP) and then perform a backup from recovery software.
Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.
I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
KaptinBoxxi said:
This is an untouched copy of the recent update for our devices. It has no file extension from TCL, but I'll leave info on how to download the firmware originally below, with it mirrored to Android File Host. Can just open this file like a Zip file
Original Link from TCL grabbed with LogCat
Code:
https://g2slave-ap-north-01.tclcom.com/64c9b63f5a85fdd27b552eec614f884add8fdb67/54/586054
Mirror Link: https://www.androidfilehost.com/?w=files&flid=322525
I have tried patching the Boot.img.p with Magisk, but it doesn't recognize the file format. Renamed it to just boot.img, still won't patch
Click to expand...
Click to collapse
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
JayTM said:
Completely new to this phone. Nice grab! I was able to use your download and 7z zip to extract boot.img from boot.img.p.
I tried to put this file into magisk but no luck.
Have you been able to unlock the bootloader yet?
I tried the fastboot OEM unlock and fastboot flashing unlock when in bootloader mode but it doesn't work.
With someone else's help I was able to locate where the boot.img is located on the phone but unable to extract it.
/dev/block/bootdevice/by-name/boot
Backup boot.img via terminal one-line command
I am trying to make an image backup of boot. The script must work on any android. I think on any Android the boot location is /dev/block/platform/???/by-name/boot My command line find /dev/block/
android.stackexchange.com
Screenshots attached.
Click to expand...
Click to collapse
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
KaptinBoxxi said:
I did the same thing you probably did to attempt to patch it with Magisk, no luck. I haven't had the time to try further recently. Enabling OEM Unlock and attempting to unlock the bootloader just leads to needing an unlock code, much like bootloader unlocking a Moto device.
I contacted TCL support a long time back when I first got the phone and they were 100% not willing to help with any USA based TCL 10 Pro unlocking. The customer service worker literally said they weren't allowed to help with US based devices. There's no downloads anywhere for the firmware either, which I think goes against Google's agreement to android on a device, but I'm not 100% sure on that.
Click to expand...
Click to collapse
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
JayTM said:
Android 11 for the TCL 10L has been being pushed in italy. This a large file about 2 to 3 GB. I really hope when we see it on our phones you are able to pull the link from logcat as well. This should be the entire rom. All we have now is OTA patch files. I've tried so many things. I have all drivers fully working even the Qualcomm 9008 Diagnostic driver. I can put the phone into EDL mode.
To put phone into EDL mode you need usb debugging enabled and type in secret code into the dialer *#*#3424#*#* which enables the diagnostic port via toast notification. Then turn phone off, hold both volume up and volume down and plug phone into PC. You will be prompted with the Download mode screen. Hold volume up to enter EDL.
There are ways to backup in EDL mode, I'm just not well versed in commands.
Click to expand...
Click to collapse
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
KaptinBoxxi said:
I'm wondering if I can pull some social engineering off, maybe be like "Hey my phone reset itself, can't boot it, but I read online something for a samsung phone called Odin and Fastboot and such? Some how you can install the system that way?" See what they say/link me to
Click to expand...
Click to collapse
Good luck to you.
I contacted TCL support myself with no luck. They immediately put my case in pending close status.
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
JayTM said:
Is there a way this ZTE tool can be modified to work for our device?
Axon 7 EDL Tool - Flash / Backup / Restore / Unlock in the EDL mode
Axon 7 EDL Tool BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode Qualcomm HS-USB QDLoader 9008 (COM ...) !!! Whatever you do, you do at your own risk !!!" !!! If you are not sure of yourself do not use this program ...
forum.xda-developers.com
All partitions are detected in EDL mode.
Click to expand...
Click to collapse
I'll check it out. If its possible to view the code in a tool like dnSpy or extract files from the exe with 7zip, its possible to use with our device, i'm sure as long as the commands are similar
Well you're in luck as it is just a .bat file program simple notepad++ will do.
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Tech101yt said:
I will be following this thread with intrest, root could be the deciding factor in me purchasing this device.
Click to expand...
Click to collapse
Have had the phone for less than 6 months and I'm already having LCD issues. When the display is off, just sitting on a table or something, it'll flash white randomly like its getting an electric signal at random. Its nothing I did. I've never hard dropped the thing. Everywhere I go pretty much is carpeted except work. If manufacturer warranty doesn't cover me, I'll stop recommending the phone to people
I actually switched to an Essential Phone recently. Way better experience, way cheaper too. I have around a dozen of them anyway and have been selling em on swappa (dunno if I'm allowed to say that here, but oh well) lol
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
mschoolbus said:
@KaptinBoxxi Sounds like you have Ambient Display on for notifications.
Click to expand...
Click to collapse
Nah its turned off. It flashes like a broken LCD would look. All snowy and stuff like an old TV. Its not notifications, just a bad LCD
that sucks... could try reseating the screen's ribbon cable :-/
can anybody share the full update rom about android 11?
top170 said:
can anybody share the full update rom about android 11?
Click to expand...
Click to collapse
I don't believe anyone has Logcatted the update process yet to get the firmware, but on the subject of this post, I do have some updates
I was digging through my Logcat from january and realized I missed something massive. I have yet to figure out the URL structure, but I have all the info for it.
So when you go to the following link, it gives a bunch of errors of missing info
https://g2master-sa-east.tclclouds.com/notify_new.php
For the firmware here on this post at least, each value from my device is
Code:
id = 0156260
curef = T799B-2ALCUS11
vk = 741ace917e3527af81412ca93b0fcce2de04a264
salt = 1611977254070885419
fv = 4DJ1LM10
tv = 4DJBLMB0
op = 1000
status = 999
mode = 2
cltp = 10
type = firmware
formatted from logcat
reportContent= {"id":"0156260","salt":"1611977254070885419","curef":"T799B-2ALCUS11","fv":"4DJ1LM10","tv":"4DJBLMB0","mode":"2","cltp":"10","type":"Firmware","op":"1000","status":"999","vk":"741ace917e3527af81412ca93b0fcce2de04a264"}
no matter what, I get the errors on the web page
Tried to root Tecno Spark 5 pro (KD7) with magisk and after unlocking bootloader everything was working smoothly until i rebooted with the patched magisk image and now its stuck in bootloop.
Pressing power button and volume up to access boot menu doesn't work nor does connecting it to pc and trying to use adb shell.
I thought maybe the solution would be to try to let it run our of battery and try again but that will take a hell of a long time.
PLEASE!!! If there is any help or suggestions just let me know. Its a brand new phone as well ****
vanc5 said:
Tried to root Tecno Spark 5 pro (KD7) with magisk and after unlocking bootloader everything was working smoothly until i rebooted with the patched magisk image and now its stuck in bootloop.
Pressing power button and volume up to access boot menu doesn't work nor does connecting it to pc and trying to use adb shell.
I thought maybe the solution would be to try to let it run our of battery and try again but that will take a hell of a long time.
PLEASE!!! If there is any help or suggestions just let me know. Its a brand new phone as well ****
Click to expand...
Click to collapse
Hint: Add Tecno Spark 5 pro (KD7) to this thread's title thus mainly owners of such device get addressed.
can you access fastboot?
no it just keeps looping back to the android start and turns off:
it displays:
orange state
your device has been unlocked and cant be trusted
your device will boot in 5 seconds
then it turns off and repeats
ineedroot69 said:
can you access fastboot
Click to expand...
Click to collapse
vanc5 said:
no it just keeps looping back to the android start and turns off:
it displays:
orange state
your device has been unlocked and cant be trusted
your device will boot in 5 seconds
then it turns off and repeats
Click to expand...
Click to collapse
Do you know how to access fastboot on your device?
Sometimes in life the most simple task are the hardest one when you are in distress
ineedroot69 said:
Do you know how to access fastboot on your device?
Sometimes in life the most simple task are the hardest one when you are in distress
Click to expand...
Click to collapse
Yeah, i accessed the fastboot to load the patched img file and then fastboot rebooted and it just got stuck in the loop
vanc5 said:
Tried to root Tecno Spark 5 pro (KD7) with magisk and after unlocking bootloader everything was working smoothly until i rebooted with the patched magisk image and now its stuck in bootloop.
Pressing power button and volume up to access boot menu doesn't work nor does connecting it to pc and trying to use adb shell.
I thought maybe the solution would be to try to let it run our of battery and try again but that will take a hell of a long time.
PLEASE!!! If there is any help or suggestions just let me know. Its a brand new phone as well ****
Click to expand...
Click to collapse
This tutorial linked here fixed mine (also tecno spark 5 pro, mediatek 6765). my phone was also in orange state bootloop. exactly as you describe.
https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
i had to slightly modify the instructions to suit the spark 5 pro. the only necessary changes are this
uninstall all usb vcom drivers you may have previously installed
FOLLOW THE TUTORIAL TILL YOU GET to where you have to download the bypass utility and exploits collection. please download the one with the mega link (ie Bypass utility compiled)
CONTINUE WITH THE TUTORIAL TILL YOU GET TO FLASHING FIRMWARE. here too my method deviated from the tutorial. even though my phone was detected as com9 by the bypass uility, i could not choose it in UART mode in sp flash tools. So just use usb mode in sp flash tools and it would still work.
CONTINUE WITH THE TUTORIAL. no need to load an authentication file. just load the scatter file and use "Download only" method
if you do this well your phone will be revived!
ptetteh227 said:
This tutorial linked here fixed mine (also tecno spark 5 pro, mediatek 6765). my phone was also in orange state bootloop. exactly as you describe. https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ i had to slightly modify the instructions to suit the spark 5 pro. the only necessary changes are this
uninstall all usb vcom drivers you may have previously installed
FOLLOW THE TUTORIAL TILL YOU GET to where you have to download the bypass utility and exploits collection. please download the one with the mega link (ie Bypass utility compiled)
CONTINUE WITH THE TUTORIAL TILL YOU GET TO FLASHING FIRMWARE. here too my method deviated from the tutorial. even though my phone was detected as com9 by the bypass uility, i could not choose it in UART mode in sp flash tools. So just use usb mode in sp flash tools and it would still work.
CONTINUE WITH THE TUTORIAL. no need to load an authentication file. just load the scatter file and use "Download only" method
if you do this well your phone will be revived!
Click to expand...
Click to collapse
ptetteh227 said:
This tutorial linked here fixed mine (also tecno spark 5 pro, mediatek 6765). my phone was also in orange state bootloop. exactly as you describe. https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/ i had to slightly modify the instructions to suit the spark 5 pro. the only necessary changes are this
uninstall all usb vcom drivers you may have previously installed
FOLLOW THE TUTORIAL TILL YOU GET to where you have to download the bypass utility and exploits collection. please download the one with the mega link (ie Bypass utility compiled)
CONTINUE WITH THE TUTORIAL TILL YOU GET TO FLASHING FIRMWARE. here too my method deviated from the tutorial. even though my phone was detected as com9 by the bypass uility, i could not choose it in UART mode in sp flash tools. So just use usb mode in sp flash tools and it would still work.
CONTINUE WITH THE TUTORIAL. no need to load an authentication file. just load the scatter file and use "Download only" method
if you do this well your phone will be revived!
Click to expand...
Click to collapse
ptetteh227 said:
This tutorial linked here fixed mine (also tecno spark 5 pro, mediatek 6765). my phone was also in orange state bootloop. exactly as you describe.
https://forum.xda-developers.com/t/repair-dead-hard-bricked-realme-3-3i-tutorial.4224255/
i had to slightly modify the instructions to suit the spark 5 pro. the only necessary changes are this
uninstall all usb vcom drivers you may have previously installed
FOLLOW THE TUTORIAL TILL YOU GET to where you have to download the bypass utility and exploits collection. please download the one with the mega link (ie Bypass utility compiled)
CONTINUE WITH THE TUTORIAL TILL YOU GET TO FLASHING FIRMWARE. here too my method deviated from the tutorial. even though my phone was detected as com9 by the bypass uility, i could not choose it in UART mode in sp flash tools. So just use usb mode in sp flash tools and it would still work.
CONTINUE WITH THE TUTORIAL. no need to load an authentication file. just load the scatter file and use "Download only" method
if you do this well your phone will be revive
Click to expand...
Click to collapse
How were you able to switch off your phone,which button combination worked?i have all the necessary things but i can't install the stock rom with sp-flashtool since its still stuck in bootloop and the phone must be completely off for the installation process
anger-Fist said:
How were you able to switch off your phone,which button combination worked?i have all the necessary things but i can't install the stock rom with sp-flashtool since its still stuck in bootloop and the phone must be completely off for the installation process
Click to expand...
Click to collapse
The phone doesn't need to be completely off. allow it to bootloop.
Just follow the process in the tutorial linked to and you should
be fine.
by the way am assuming your bootloader is already unlocked.
please send the link to download the auth file good sir
anger-Fist said:
please send the link to download the auth file good sir
Click to expand...
Click to collapse
what smartphone are you using?
what is the operating system of your computer? windows or linux?
so far what have you done?
if you are using a spark 5 pro, you don' t need an auth file. I revived mine without an auth file.
I looks like i would have to write a detailed step-by-step guide on how it worked for me
i followed the steps to the letter but gives me errors everytime
if you found mediatek driver for mt67xx or the one you used can you send me please,i've searched for it and keep finding for mt65xx
ptetteh227 said:
what smartphone are you using?
what is the operating system of your computer? windows or linux?
so far what have you done?
if you are using a spark 5 pro, you don' t need an auth file. I revived mine without an auth file.
I looks like i would have to write a detailed step-by-step guide onu how it worked for me
Click to expand...
Click to collapse
windows 10
tecno spark 5 pro 4gb ram/ 128gb rom firmware no. KD7-H6211FQRSTU-Q-GL-210520V392
anger-Fist said:
i followed the steps to the letter but gives me errors everytime
Click to expand...
Click to collapse
please send a screenshot of the command prompt after you run the command just In case of any errors (i saw a traceback error in one of the screenshots). you must run the command prompt as administrator
anger-Fist said:
if you found mediatek driver for mt67xx or the one you used can you send me please,i've searched for it and keep finding for mt65xx
Click to expand...
Click to collapse
you don't need one. I didn't use one
ptetteh227 said:
you don't need one. I didn't use one
Click to expand...
Click to collapse
if your tecno spark 5 pro is same as mine(4gb ram/128gb rom) can you send me the link you to download the firmware and da file please
vanc5 said:
Tried to root Tecno Spark 5 pro (KD7) with magisk and after unlocking bootloader everything was working smoothly until i rebooted with the patched magisk image and now its stuck in bootloop.
Pressing power button and volume up to access boot menu doesn't work nor does connecting it to pc and trying to use adb shell.
I thought maybe the solution would be to try to let it run our of battery and try again but that will take a hell of a long time.
PLEASE!!! If there is any help or suggestions just let me know. Its a brand new phone as well ****
Click to expand...
Click to collapse
work for kd7 tecno
new post
vanc5 said:
Tried to root Tecno Spark 5 pro (KD7) with magisk and after unlocking bootloader everything was working smoothly until i rebooted with the patched magisk image and now its stuck in bootloop.
Pressing power button and volume up to access boot menu doesn't work nor does connecting it to pc and trying to use adb shell.
I thought maybe the solution would be to try to let it run our of battery and try again but that will take a hell of a long time.
PLEASE!!! If there is any help or suggestions just let me know. Its a brand new phone as well ****
Click to expand...
Click to collapse
work my kd7 twrp recovery and root
new post
Hi all, I have an Alcatel Joy Tab that's all of a sudden decided to keep looping this error.
Error only pops up outside of the lock screen: on the lock screen, I'm able to swipe down the notifications bar and enter settings from there. Additionally, UI seems to be functional in the Camera app as well.
I've already factory reset once, and it was back to normal for a little while, but then it came back again. Any suggestions?
Specs:
Alcatel Joy Tab 1
Model 9027W
Android 8.1.0
Baseband version MT6739
Kernel Version 4.4.95
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
jwoegerbauer said:
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply, I've been looking for a stock ROM since I first had the issue. However I haven't been able to have any luck finding one. Do you have any suggestions on where to look? If I ultimately still can't find one am I SOL?
I've heard that you can just return to stock by using Alcatel's official Mobile Upgrade tool here but it keeps giving me a message saying that the version I'm using is the most updated version.
Software Drivers - Alcatel
Software Drivers
www.alcatelmobile.com
I would like to know more about this too. Same issue with poster. Any custom roms or anything out there for this?
No custom ROMs. There is one out there that is unlocked. But, I've lost the post about it. Used it to carrier unlock mine. Haven't had the time to see if it unlocked more.
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Edit: "SystemUI has stopped working" is solved with the latest firmware. If you can't get latest firmware (The alcatel mobile upgrade tool kept telling me I was on the latest or it would just crash) Do a google search for MTK Sugar Tool. Versions after 2018 will force the latest updates to the device over usb
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
cheger32 said:
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
Click to expand...
Click to collapse
Bootloader Unlock failed. Is there any solution?
Azukegi said:
Bootloader Unlock failed. Is there any solution?
Click to expand...
Click to collapse
Did you enable OEM unlock in developer settings first?
cheger32 said:
Did you enable OEM unlock in developer settings first?
Click to expand...
Click to collapse
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Azukegi said:
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Click to expand...
Click to collapse
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
cheger32 said:
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
Click to expand...
Click to collapse
Dude no way, I would love to get that TWRP from you if possible
Azukegi said:
Dude no way, I would love to get that TWRP from you if possible
Click to expand...
Click to collapse
TWRP 3.6.1 for Alcatel 3T 8 (Maybe also generic Joytab 1?)
I built this last night, seems to work well. Let me know if there are any issues. This will be my last post in this thread as I've gotten off topic. I'll create a new thread with a guide if I find the time.
This is built from a twrp compatible device tree generated from a recovery image with a few modifcations and corrections. The kernel was built from sources released by alcatel (it took me nearly a year and some legal threats to get them to release it to me.)
just flash that to recovery in fastboot mode:
Code:
fastboot flash recovery <img filename>
Be sure to make a backup of your original if possible.
I just remembered that there's a bypass method and a useful utility in existence (located here: http://www.mediafire.com/file/qtmkilaimympapf/mtk_bypass_rev4.7z/file) for enabling the use of spflashtool to make backups and even flash images without fastboot with this device. Sorry, I'm still dusting the cobwebs off of this project.
EDIT: 23 builds later and I fixed /data decryption. As I said this will be my last post here but in case I never make a formal thread, here is a fully working twrp.
Edit again: I realized adb push and sideload wasn't working so I fixed it. Here's the latest build
I've got a 3T that I use rarely and it seems if I leave it for a while I get the same lock screen issue. I've discovered mention of a T-Mobile update that might resolve this:
Does anyone know where I can get this build and if I can force it on to my 3T. My carrier has no updates available.
Android 8.1.0
Build number: 1AWKUMK0May 14, 2021Resolves issue preventing device unlockAvailable May 14, 2021
Devices that meet the update requirements can be upgraded to the current software version.
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
If it's too late to return it you can put it in recovery mode and try to restore it that way if that doesn't work then you can reflash it with SUGAR MTK SP
mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
You can try SUGAR MTK SP