I have found threads where this was asked too but it didn't get solved or it did but for a specific device.
I have a OPX with OOS 3.1.4
In command prompt typed "fastboot oem device-info" it gives me this info "device unlocked true" typed "fastboot flash recovery recovery.img" i named my recovery file "recovery" obviously. i get info
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.844s
but when i reboot to my recovery it is still the stock OP recovery.
medick_ said:
I have found threads where this was asked too but it didn't get solved or it did but for a specific device.
I have a OPX with OOS 3.1.4
In command prompt typed "fastboot oem device-info" it gives me this info "device unlocked true" typed "fastboot flash recovery recovery.img" i named my recovery file "recovery" obviously. i get info
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.313s]
finished. total time: 0.844s
but when i reboot to my recovery it is still the stock OP recovery.
Click to expand...
Click to collapse
after flashing by "fastboot flash recovery recovery.img", boot into recovery directly by giving this cmd "fastboot boot recovery.img" this time it should overwrite your stock op recovery. try this and report back.
I'm assuming your trying to immediately boot into recovery after flashing because it will overwrite it. You can try the command "fastboot erase recovery" before flashing twrp. After flashing recovery completely turn off the phone. Then hold down volume down and proceed powering on into recovery. Sorry for the step by step if your not a noob just have to make sure we cover step by step. The above post is the proper way to boot after flashing try it first.
cva_kabil said:
after flashing by "fastboot flash recovery recovery.img", boot into recovery directly by giving this cmd "fastboot boot recovery.img" this time it should overwrite your stock op recovery. try this and report back.
Click to expand...
Click to collapse
Thanks for the reply
This is the the info i get:
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
And it stays in fastboot mode (guessing cause the dtb wasn't found)
medick_ said:
Thanks for the reply
This is the the info i get:
downloading 'boot.img'...
OKAY [ 0.531s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.578s
And it stays in fastboot mode (guessing cause the dtb wasn't found)
Click to expand...
Click to collapse
Which recovery u tried?
Exodusche said:
I'm assuming your trying to immediately boot into recovery after flashing because it will overwrite it. You can try the command "fastboot erase recovery" before flashing twrp. After flashing recovery completely turn off the phone. Then hold down volume down and proceed powering on into recovery. Sorry for the step by step if your not a noob just have to make sure we cover step by step. The above post is the proper way to boot after flashing try it first.
Click to expand...
Click to collapse
When i boot it stays stuck on the OP logo so I want to try other methods before ereasing my recovery. Cause I think this will give me another problem. Of course if you have more knowledge about this problem and say that it works then i will try it
cva_kabil said:
Which recovery u tried?
Click to expand...
Click to collapse
this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img.html
medick_ said:
this one https://dl.twrp.me/onyx/twrp-3.0.2-0-onyx.img.html
Click to expand...
Click to collapse
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
cva_kabil said:
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
Click to expand...
Click to collapse
thanks mate this twrp worked. Is there a way to see if the recovery version is compatible or not? Just for should i get another phone or when i update too nougat
medick_ said:
thanks mate this twrp worked. Is there a way to see if the recovery version is compatible or not?
Click to expand...
Click to collapse
Not exactly,but as of now there is no official twrp for onyx new bootloader.. Luckily we hv smart dev like @Nachiket.Namjoshi Thank for dem.. And not sure about other devices,but u can update to nougat using this unofficial recovery,all AOSP,CM based Nougat roms are compatible with this..
cva_kabil said:
The one u flashed ll not work in oos 3.x.x as u r in new bootloader,
Try flashing this one.. this ll work https://www.androidfilehost.com/?fid=457095661767115910
Click to expand...
Click to collapse
how do you edit the thread title so it's [solved] ?
medick_ said:
how do you edit the thread title so it's [solved] ?
Click to expand...
Click to collapse
Found Go to edit, then advanced edit :good:
cva_kabil said:
Found Go to edit, then advanced edit :good:
Click to expand...
Click to collapse
i know who to contact when i have another problem ;p Thanks a lot
medick_ said:
i know who to contact when i have another problem ;p Thanks a lot
Click to expand...
Click to collapse
Lol happy to help
cva_kabil said:
Lol happy to help
Click to expand...
Click to collapse
hahahah unbelievable phone won't boot after installing superSU any advice
medick_ said:
hahahah unbelievable phone won't boot after installing superSU any advice
Click to expand...
Click to collapse
Welcome back use this one https://www.androidfilehost.com/?fid=24591000424944601
cva_kabil said:
Welcome back use this one https://www.androidfilehost.com/?fid=24591000424944601
Click to expand...
Click to collapse
quick question how do i place this in my internal storage since it won't boot
medick_ said:
quick question how do i place this in my internal storage since it won't boot
Click to expand...
Click to collapse
Connect ur device with usb cable to pc while u r in twrp screen...
cva_kabil said:
Connect ur device with usb cable to pc while u r in twrp screen...
Click to expand...
Click to collapse
thanks, i had to boot recovery with out usb cable else it wouldnt find my phone. I tried deleting the supersu before i came for help but it wouldnt find my phone
SOLVED & THREAD CLOSED
Related
Hi guys
I bricked my OPX .I dont know whether it is soft or hard bricked.It is entering into fastboot mode though.
When it enters into fastboot mode..i try to flash the recovery.img after flashing it also i am unable to go into recovery mode...
Please help..i have a nandroid backup..but cannot enter into recovery even after flashing it..i have unlocked the bootloader...
sandipshah316 said:
Hi guys
I bricked my OPX .I dont know whether it is soft or hard bricked.It is entering into fastboot mode though.
When it enters into fastboot mode..i try to flash the recovery.img after flashing it also i am unable to go into recovery mode...
Please help..i have a nandroid backup..but cannot enter into recovery even after flashing it..i have unlocked the bootloader...
Click to expand...
Click to collapse
Since u can enter into fastboot, it's not hard bricked.
U can try flashing another recovery or stock recovery
With fastboot flash recovery recovery.img or maybe restoring stock firmware.
Press thanks if it helped you☺
youwave111 said:
Since u can enter into fastboot, it's not hard bricked.
U can try flashing another recovery or stock recovery
With fastboot flash recovery recovery.img or maybe restoring stock firmware.
Press thanks if it helped you
Click to expand...
Click to collapse
I tried flashing recovery with the above command also...but when i try to enter into recovery it just gets stuck at the oneplus logo screen....
sandipshah316 said:
I tried flashing recovery with the above command also...but when i try to enter into recovery it just gets stuck at the oneplus logo screen....
Click to expand...
Click to collapse
how to restore stock firmware??
I am unable to go into recovery
D:\User\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery twr
p.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10368 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.548s
D:\User\Downloads\android-sdk-windows\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.327s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.364s
D:\User\Downloads\android-sdk-windows\platform-tools>
sandipshah316 said:
how to restore stock firmware??
I am unable to go into recovery
D:\User\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery twr
p.img
target reported max download size of 1073741824 bytes
sending 'recovery' (10368 KB)...
OKAY [ 0.328s]
writing 'recovery'...
OKAY [ 0.219s]
finished. total time: 0.548s
D:\User\Downloads\android-sdk-windows\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.327s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.364s
D:\User\Downloads\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Dtb error occurs when u try flashing a corrupted recovery or a recovery meant for other device.
Make sure to check the md5 hash of the file before flashing anything on ur device.
Hit thanks if I helped please☺
youwave111 said:
Dtb error occurs when u try flashing a corrupted recovery or a recovery meant for other device.
Make sure to check the md5 hash of the file before flashing anything on ur device.
Hit thanks if I helped please
Click to expand...
Click to collapse
sorry...but i dont know how to check md5 hash
sandipshah316 said:
sorry...but i dont know how to check md5 hash
Click to expand...
Click to collapse
Try this recovery
https://drive.google.com/open?id=0B0pr-ZA5b-1pRkd1RW1kSDMzcnM
Rename the file to TWRP and copy it in ur fastboot or adb folder
Write command - fastboot flash recovery TWRP.img
Hit thanks if I helped please☺
youwave111 said:
Dtb error occurs when u try flashing a corrupted recovery or a recovery meant for other device.
Make sure to check the md5 hash of the file before flashing anything on ur device.
Hit thanks if I helped please
Click to expand...
Click to collapse
I did what you mentioned..but of no use..i still get "dtb not found"
D:\User\Desktop\Fastboot>fastboot flash recovery TWRP.img
sending 'recovery' (14852 KB)... OKAY [ 1.229s]
writing 'recovery'... OKAY [ 0.282s]
finished. total time: 1.511s
D:\User\Desktop\Fastboot>fastboot boot TWRP.img
downloading 'boot.img'... OKAY [ 0.972s]
booting... FAILED (remote: dtb not found)
finished. total time: 1.011s
D:\User\Desktop\Fastboot>
Can u boot into stock recovery ?
Hit thanks if I helped please☺
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Try booting into recovery with the hardware way.
Press n hold the power volume down buttons and release them when u see oneplus logo.
Hit thanks if I helped please☺
youwave111 said:
Can u boot into stock recovery ?
Hit thanks if I helped please
---------- Post added at 07:06 AM ---------- Previous post was at 07:04 AM ----------
Try booting into recovery with the hardware way.
Press n hold volume down button and release then when u see oneplus logo.
Hit thanks if I helped please
Click to expand...
Click to collapse
No i cannot
I tried the manual method also..it just boots into logo screen....android is displayed in the bottom of the screen and vanishes in a sec,and gets stuck at the logo screen
I tried the manual method also..it just boots into logo screen....android is displayed in the bottom of the screen and vanishes in a sec,and gets stuck at the logo screen
sandipshah316 said:
I tried the manual method also..it just boots into logo screen....android is displayed in the bottom of the screen and vanishes in a sec,and gets stuck at the logo screen
Click to expand...
Click to collapse
Have u tried flashing the stock recovery ?
Hit thanks if I helped please☺
youwave111 said:
Have u tried flashing the stock recovery ?
Hit thanks if I helped please☺
Click to expand...
Click to collapse
Yes i tried it...i still get the same errordtb not found)
D:\User\Downloads\android-sdk-windows\platform-tools>f
ck_Recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (16384 KB)...
OKAY [ 0.516s]
writing 'recovery'...
OKAY [ 0.307s]
finished. total time: 0.824s
D:\User\Downloads\android-sdk-windows\platform-tools>f
y.img
downloading 'boot.img'...
OKAY [ 0.516s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.555s
D:\User\Downloads\android-sdk-windows\platform-tools>
Well at last, u can follow this guide. It'll restore ur firmware to stock. Root access and twrp will also be lost
http://forum.xda-developers.com/showthread.php?t=3272108
Hit thanks if I helped please☺
youwave111 said:
Well at last, u can follow this guide. It'll restore ur firmware to stock. Root access and twrp will also be lost
http://forum.xda-developers.com/showthread.php?t=3272108
Hit thanks if I helped please
Click to expand...
Click to collapse
Thanks a lot for your help..my pc is not detecting it as a qualcom port though...
sandipshah316 said:
Thanks a lot for your help..my pc is not detecting it as a qualcom port though...
Click to expand...
Click to collapse
Is it detected as one plus ?
Hit thanks if I helped please☺
youwave111 said:
Is it detected as one plus ?
Hit thanks if I helped please
Click to expand...
Click to collapse
when i connect my phone in fastboot mode to the pc..it is displayed as "Android Bootloader Interface" under "Android Phone" in dvice manager
sandipshah316 said:
when i connect my phone in fastboot mode to the pc..it is displayed as "Android Bootloader Interface" under "Android Phone" in dvice manager
Click to expand...
Click to collapse
Try this recovery
http://forum.xda-developers.com/devdb/project/dl/?id=15783&task=get
And boot into recovery the manual way
by long press power with vol down upon the display of OnePlus logo release the power button but still pressing vol down and release it when u see twrp boot screen.
PS:- it's working completely fine on my device.
Hit thanks if I helped please☺
youwave111 said:
Try this recovery
http://forum.xda-developers.com/devdb/project/dl/?id=15783&task=get
And boot into recovery the manual way
by long press power with vol down upon the display of OnePlus logo release the power button but still pressing vol down and release it when u see twrp boot screen.
PS:- it's working completely fine on my device.
Hit thanks if I helped please
Click to expand...
Click to collapse
will check and revert....
sandipshah316 said:
will check and revert....
Click to expand...
Click to collapse
i tried the above manual process with the given twrp recovery also...it still wont let me boot into recovery...dont know what seems to be the problem...
Hi,
searched a lot of Threads but no one helped. is there an all in one Solution to get stock Firmware and Recovery back? I tried at last this one: https://forum.xda-developers.com/zenwatch-2/help/watch-update-failing-factory-image-t3573236 but as soon i try to reboot to twrp i get the Error
Code:
[email protected]:~# fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
So please help
Thanks in advance
no one?
Gesendrt aus der Tardis aus irgendeiner Zeit
Which model do you have? There's the WI501Q and WI502Q.
Lrs121 said:
Which model do you have? There's the WI501Q and WI502Q.
Click to expand...
Click to collapse
Ah sorry, its the "big" one WI501Q
KleinerKObold said:
Ah sorry, its the "big" one WI501Q
Click to expand...
Click to collapse
Try using this TWRP image. I keep it up to date so it might help you get through the guide.
http://lrsservers.org/downloads/devices/asus/sparrow/
Lrs121 said:
Try using this TWRP image. I keep it up to date so it might help you get through the guide.
http://lrsservers.ddns.net/download/devices/asus/sparrow/twrp-jenkins-sparrow.img
Click to expand...
Click to collapse
Thanks for the file but i coldnt get to twrp. as soon as i type
fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
i get the Errror
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
Is there a chance that i get the watch working again?
KleinerKObold said:
Thanks for the file but i coldnt get to twrp. as soon as i type
fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
i get the Errror
downloading 'boot.img'...
OKAY [ 0.369s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.757s
Is there a chance that i get the watch working again?
Click to expand...
Click to collapse
I'm not sure, it looks like they may changed something's in the boot that need addressing with twrp.
Lrs121 said:
I'm not sure, it looks like they may changed something's in the boot that need addressing with twrp.
Click to expand...
Click to collapse
Got it, i have to download another TWRP Image now i have my watch working again. But i nedd still a plain stock rom because i have still some that have dnot be there if i have a Stockrom (Advanced Settings and Wear Root check) but how do i get a stock rom?
KleinerKObold said:
Got it, i have to download another TWRP Image now i have my watch working again. But i nedd still a plain stock rom because i have still some that have dnot be there if i have a Stockrom (Advanced Settings and Wear Root check) but how do i get a stock rom?
Click to expand...
Click to collapse
https://forum.xda-developers.com/zenwatch-2/general/dump-zenwatch-2-sparrow-wi501q-build-t3578459
https://forum.xda-developers.com/zenwatch-2/general/m6e69n-twrp-backup-stock-boot-firmware-t3484961
Thread Closed
Thread Closed
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
hetor99 said:
Dude, this may work on the xt1772??
If no, you can port to it??
If you need something like the boot image, i can give upload one
Sorry for my english
Click to expand...
Click to collapse
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Francesco Franz said:
No, its not working in XT1772.
Please upload your device recovery image & boot image here.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
hetor99 said:
https://drive.google.com/file/d/1jbSjLAMabwDar9tcc_VCSlPCNFVizWt1/view?usp=drivesdk
https://drive.google.com/file/d/1tKGXsT4qSkSoXj17Ur-QsdgsGtl1Fz_Q/view?usp=drivesdk
Click to expand...
Click to collapse
Wait, until i upload a test version of twrp here?
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
RagChith said:
After installing stock rom,i m not getting any info(shows null) on SKU in fast boot mode.please help
Click to expand...
Click to collapse
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
---------- Post added at 06:47 PM ---------- Previous post was at 06:11 PM ----------
Francesco Franz said:
Wait, until i upload a test version of twrp here?
Click to expand...
Click to collapse
Sure guy, i will wait
@hetor99
You have to wait till this sunday.
Francesco Franz said:
@hetor99
You have to wait till this sunday.
Click to expand...
Click to collapse
It's fine dude, take your time
Im working on build LOS 14.1 for the mediatek variant, but i dont know how to build twrp
hetor99 said:
Me too, my device is the xt1772 and as you said, on the bootloader doesn't show any info, sku, model, imei and some other info, but the device is working well when it boot
Click to expand...
Click to collapse
Don't worry about it, it is kind of normal behavior in the fastboot mode
Sent from my Nexus 7 using Tapatalk
sir ............ can we flash using SP flash tool
rsmani1965 said:
sir ............ can we flash using SP flash tool
Click to expand...
Click to collapse
Yes, you can. But only when you have a working scatter file else use fastboot method.
#UPDATE
Click Here For TWRP Recovery For Moto E4 Plus XT1772 MediaTek Variant !
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Recovery mode is still the same No command with the dude on his back
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
DrunkenPanda2000 said:
DrunkenPanda2000 said:
I get the following
PS C:\adb> fastboot flash recovery twrp.img
target reported max download size of 134217728 bytes
sending 'recovery' (13618 KB)...
OKAY [ 0.339s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 0.745s
Nothing changes in my phone i think.
Boot to Recovery mode is still the same No command with the dude on his back
EDIT:
Apearantly i have a model 1762 And not 1772 Annyne got anny tips on how t proceed is this a fulitele task or will someone be a hero once again?
Click to expand...
Click to collapse
Already mentioned its for xt1772 not xt1762.
Upload your device recovery and boot image. i will make one for you.
Click to expand...
Click to collapse
hetor99 said:
@Francesco Franz
Well, i think that the recovery is working fine, i tried the functios of wiping partitions like a factory reset and works, it detects the adoptable storage, the unique "bug" is when the recovery boot and stuck on black screen like on other variants.
I tried to take sc from all the options but i dont understand the lenguage that have the recovery pre-selected.
sorry for my english and any misunderstood
Click to expand...
Click to collapse
Its not a bug anymore since it takes few secs to enter into recovery mode. Black screen issue not at all. since you have a working twrp in your device. if theirs a black screen issue you will be on default recovery.
will fix the language bug soon.
@DrunkenPanda2000
That is because this section of xda is for the moto e4 plus, not the e4
the moto e4 already have twrp and to many roms on development
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
pim8181 said:
Hi,
Last week I got my phone stuck in a bootloop which led to me making a lot of mistakes, I flashed a boot.img as a kernel, I deleted my entire software, and I lost a lot of files. I currently have my phone in an error mode, it says I have to update the system again. I have access to fastboot but I do not have access to twrp (flashing the recovery doesn't work).
Can anyone help me with this problem?
Click to expand...
Click to collapse
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
kilroystyx said:
Is a really fastboot mode or error mode?
If it is fastboot what you see, Phone unlocked and FRP unlock?
Click to expand...
Click to collapse
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
pim8181 said:
I can get in both fastboot and error mode, I think fastboot is the most useful. It says PHONE Unlocked and FRP unlocked.
Click to expand...
Click to collapse
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
kilroystyx said:
-Do you know exactly which files or partitions did you mess?
-What is your region code and build number?
If you don’t know run this command is fastboot mode => fastboot oem get-build-number
-Do you have a TWRP backup from your device?
Click to expand...
Click to collapse
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
pim8181 said:
I don't know for sure which parts I messed up, but I do know these thing: I don't have an OS installed, and my kernel is a boot.img.
I don't know my region number for sure, but according to this post: https://forum.xda-developers.com/8-lite/how-to/huawei-regional-codes-t3740473 it should be C432.
My build number is ANE-LX1 8.0.0.126 (C432) and I should have a TWRP backup on my sd card from the moment my phone was only bootlooping.
Click to expand...
Click to collapse
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
pim8181 said:
I can't install TWRP, I currently install it by flashing the file as a recovery_ramdisk.
After it is flashed I execute the command fastboot reboot and hold volume up whilst disconnecting my phone from my PC.
Do you have any tips?
Click to expand...
Click to collapse
No, you are doing right. Can you post the output from fastboot during the installation?
kilroystyx said:
No, you are doing right. Can you post the output from fastboot during the installation?
Click to expand...
Click to collapse
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
pim8181 said:
Code:
fastboot flash recovery_ramdisk TWRP_3.2.1-0_ANE-LX1_Full_01.img
gives:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24962 KB)...
OKAY [ 0.689s]
writing 'recovery_ramdisk'...
OKAY [ 0.122s]
finished. total time: 0.811s
Since I can't boot in TWRP by holding down the volume up button when rebooting I tried to use the boot command:
Code:
fastboot boot TWRP_3.2.1-0_ANE-LX1_Full_01.img
downloading 'boot.img'...
OKAY [ 0.690s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.695s
Click to expand...
Click to collapse
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
kilroystyx said:
I don't believe that fastboot boot can work...
That is strange...
Can you flash TWRP one more time?
After successful flash don't use the command fastboot reboot
Unplug the USB cable and press ON/OFF and VOL+ and stay pressings until you see TWRP screen.
Click to expand...
Click to collapse
It didn't work , maybe I can flash the stock system image from fastboot?
pim8181 said:
It didn't work , maybe I can flash the stock system image from fastboot?
Click to expand...
Click to collapse
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
kilroystyx said:
Yes, system, cust, recovery_ramdisk.... all partions that might be mess by you.
Click to expand...
Click to collapse
I don't know how to get these ones can you explain it to me?
pim8181 said:
I don't know how to get these ones can you explain it to me?
Click to expand...
Click to collapse
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
kilroystyx said:
Check this thread, this applies to recovery_ramdisk but for all other partitions is the same.
Click to expand...
Click to collapse
It worked, many thanks for your help!
For those that have issues with the programme, I had to uncheck the verify header checksum button in the settings file in order for it to work properly.
kilroystyx said:
Do you have currently TWRP installed?
-Boot in the TWRP recovery and restore your backup.
-If your backup don't have all partitions let me know and I'll send you what is missing.
If you currently don't have TWRP installed?
-Go to fastboot mode and flash this TWRP
If boot then should be ok.
If remains bootlooping then you can wipe cache and reboot
If remains bootlooping you can test flash B126 with HuRUpdater
Click to expand...
Click to collapse
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
pim8181 said:
I guess I spoke too soon, I can get my phone in TWRP but it continues to bootloop.
Click to expand...
Click to collapse
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
kilroystyx said:
Did you do wipes?
If didn't work use your TWRP backup or use HuRUpdater
Click to expand...
Click to collapse
My TWRP is completely lost and the tool doesn't seem to work, I wiped data cache and dalvik.
When you flash a rom aren't you just supposed to flash the rom itself, when I bricked my phone by installing Xposed I just reflashed the rom it's sytem image and a boot image. How should I do it?
Apologies if I should have searched harder. My understanding is that touch screen issues like this happen when the firmware you flash isn't quite compatible with your device. I've triple checked the stuff I downloaded, and I'm not seeing how it could be that. Maybe I did something else stupid? This is my first time rooting anything.
Product/Variant (as seen in bootloader): sofia XT2041-4 64GB PVT
The boot.img I downloaded: lolinet's firmware/moto/sofia/official/RETUS/ (the august 31 one. Currently trying with the earlier one, but the download is taking forever)
Magisk version: 7.5.1
I only have a linux laptop, so the rescue and smart assistant appears to be off the table
Here's what I did:
Downloaded the boot.img from lolinet
patched it using magisk
flashed it using fastboot
How I flashed it:
Code:
~/Downloads$ fastboot flash boot magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.376s]
writing 'boot_b'...
OKAY [ 0.069s]
finished. total time: 0.446s
I booted up after this, and I couldn't use the touchscreen. Then I noticed the boot_b thing, so I did the following to do both partitions (although I have no idea if this is what you're supposed to do):
Code:
~/Downloads$ fastboot flash boot_a magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_a' (12136 KB)...
OKAY [ 0.350s]
writing 'boot_a'...
OKAY [ 0.076s]
finished. total time: 0.425s
~/Downloads$ fastboot flash boot_b magisk_patched.img
target reported max download size of 805261312 bytes
sending 'boot_b' (12136 KB)...
OKAY [ 0.370s]
writing 'boot_b'...
OKAY [ 0.214s]
finished. total time: 0.584s
No dice..
Next, I tried to just use the unpatched boot.img to restore things.
Code:
~/Downloads$ fastboot flash boot_a XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_a' (65536 KB)...
OKAY [ 1.908s]
writing 'boot_a'...
OKAY [ 0.696s]
finished. total time: 2.604s
~/Downloads$ fastboot flash boot_b XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml/boot.img
target reported max download size of 805259264 bytes
sending 'boot_b' (65536 KB)...
OKAY [ 1.949s]
writing 'boot_b'...
OKAY [ 0.525s]
finished. total time: 2.474s
once again, no dice..this time I didn't even get to the lockscreen. Just stuck on the moto logo
Any idea what I've done wrong? Would really appreciate some help with this.
Update: I tried with the other boot.img from lolinet, doesn't get to lockscreen. Then I tried a factory reset with twrp, and flashing the earlier boot.img and I got to the setup screen, but still no touch.
Update 2: I managed to get omnirom flashed, and that's working so far! I am still curious to know why the touch screen issues popped up..will be useful next time I want to flash stock
check the forums for the g7 play, I've found topics about that kind of issue.
There's a few touchscreen vendors used for the same device, and they use different drivers basically.
Got a link by any chance? The ones I've seen are twrp related or because of the wrong firmware.
Any idea how to figure out which set is right for my phone?
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
mingkee said:
Here is solution: get full ROM through LMSA and flash components through bootloader and fastbootd
* boot, recovery, dtbo, vbmeta, super flashed in fastbootd (adb reboot fastboot)
* All other actions done in bootloader (adb reboot bootloader)
Click to expand...
Click to collapse
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
cnoevl21 said:
Can this be done without fastbootd? i stupidly flashed twrp (which doesnt work). so I dont have stock recovery to get into fastbootd. Can this be done using regular fastboot?
Or any way to flash a stock rom using just fastboot? the rom i have does not have 'flash all' so im not sure what to do from here.
Click to expand...
Click to collapse
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
mingkee said:
Solution:
Flash everything ***except*** those flashed in fastbootd
fastboot reboot bootloader
fastboot reboot fastboot
The last resort: use LMSA rescue, but your phone will be wiped
Click to expand...
Click to collapse
when you say flash everything. is it just flashing the .img files? or literally everything?
Sorry, ive never had to manually flash before.
---------- Post added at 09:17 PM ---------- Previous post was at 09:15 PM ----------
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
ill have to try this. thanks. Ive tried to just boot the boot.img and it hasnt done anything. so ill do this to try and get into fastbootd.
nero075 said:
If you get the recovery image from lolinet, you can boot that (or flash recovery) and then enter fastbootd
Click to expand...
Click to collapse
Ok. ive gotten into fastbootd but have no idea what to do now. I assumed it was like flashing with regular fastboot. but when i type commands like fastboot flash boot boot.img i get a failed result no such file or directory
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
PamelaGirl said:
Hello friend,
Did you ever resolve your issue with the touchscreen?
I've just down the same thing using Magisk. Everything was fine until I flashed the magisk.patched.img. The device booted up but the touchscreen doesn’t work no matter what.
Please let me know of your solution.
Thank you kindly.
Click to expand...
Click to collapse
hey did you fix it or something? i got the same problem, and idk what to do, can you help?
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
PamelaGirl said:
I never solved it.
In the end I was able to get a Moto G8 Plus that I was able to unlock the bootloader and root using Magisk.
Click to expand...
Click to collapse
sadly the phone i tried to root is the only phone that i have
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
PamelaGirl said:
I understand the frustration my friend. I tried and tried but it just doesn’t work with Moto G Power.
Click to expand...
Click to collapse
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
klninja said:
i think i got how to do it, u need to use LENOVO MOTOROLA SMART ASSISTANT and it works i think, i am going to try it, there is a tutorial in this forum, sadly only works if u have windows, but i manage to go to a place that has windows pc https://forum.xda-developers.com/t/moto-g-power-flashing-guide.4159301/
Click to expand...
Click to collapse
That’s a good find. Please report back with your success so I stand corrected.
PamelaGirl said:
That’s a good find. Please report back with your success so I stand corrected.
Click to expand...
Click to collapse
a person already did this
That’s good news!
Now its your turn.
PamelaGirl said:
That’s good news!
Now its your turn.
Click to expand...
Click to collapse
i would like to ask a question, when ur g8 wasnt working did the phone charge or not? cus mine dont show how much battery i have
Sorry I honestly cannot recall. I was so frustrated at that time, blinded to get the root to work that I did not notice.