Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
NUU X5
manutest said:
Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
Click to expand...
Click to collapse
I too have this phone and tried to root to no avail. Now my phone is in bootloop and i cant find correct firmware to flash to phone to fix it! Please someone help! All the firmware thats available for this phone on internet will not work for some reason. Very desperate...
manutest said:
Hi!
I recently bought a NUU X5 mobile from banggood. Sadly it went out of stock and they only sent me the Indian version instead of the Global one I originally ordered...
Anyway it worked ok but I wanted to root it by installing TWRP and then Magisk, which I have done a couple of times with other phones.
What I did was:
Code:
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 26.177s]
finished. total time: 26.179s
>fastboot flash recovery TWRP.img
target reported max download size of 134217728 bytes
sending 'recovery' (5944 KB)...
OKAY [ 0.274s]
writing 'recovery'...
OKAY [ 0.149s]
finished. total time: 0.425s
Sadly, I didn't backup the stock recovery before with the SP Flash Tool. I didn't think it was a big deal and I never had problems with it, though the TWRP is not an official release. But I thought in the worst case the recovery does not work but what really happened after that:
The mobile went into a boot loop. And I cannot get into the recovery or even fastboot any more!
I didn't know the recovery is even used during a normal boot!
I think what I would need is a stock X5-IN-01 firmware.
The guys at needrom.com only have
X5-AM-02 - full_hct6750_66_n-user 7.0 NRD90M
X5-EU-01 - full_hct6750_66_n-user 7.0 NRD90M
and they also want money for me to download it!
However I found in the internet
Nuu_X5_MT6750_20170308_7.0.zip
which turns out to be the X5-EU-01 firmware. I would pretty much even prefer this firmware over the indian version to get all LTE bands, but for now I would be happy if I even got the damn thing to boot again
So I started experimenting with the SP Flash Tool which can still access the phone.
The scatter file that is delivered with the firmware does not match the actual setup of the phone.
The EU firmware has an extra partition "persdata" which the IN firmware does not have.
I created a modified scatter file which matches my partitions. (I got the partition info from the GLB_xxx.log trace file from the SP Flash Tool). Then I backuped everything (too late for the recovery...).
Then I flashed only the recovery from the EU firmware. To my surprise, the firmware now displays the boot screen again (was totally black and no backlight before)! But it does not boot, after quite some time it resets so it's a much slower bootloop now.
I then tried to flash different partitions with the EU firmware stuff, I ended up flashing everything except the preloader and the md1dsp (which I read should maybe not be touched?). I'm not touching the preloader because I think if it is gone, I cannot get in with SP Flash Tool any more, is that right?
Anyway, when I flashed everything except preloader and md1dsp, the display was black (no boot screen), but backlight was on. The phone was actually booting! ADB was possible but no working screen.
Then I tried flashing back one by one the backuped IN partitions. It ended when flashing the "lk" partition. With the original IN "lk" partition in place, I have a boot screen but no boot. With the EU "lk" partition, I have a non-working screen and boot. What does the "lk" partition even contain?
Now I need your help guys!
What to do? I cannot find the IN stock fw anywhere. Is it possible to download it from the NUU OTA update server? Or does anyone have such a phone and can provide the stock recovery? Or should I erase everything reformat and put in the complete EU firmware including new preloader and persdata? To my knowledge the hardware is the same, at least it has exactly the same specs.
Any help is very much appreciated.
Manu
Click to expand...
Click to collapse
Manu, can you please upload and share your modified scatter file and stock firmware files...Please and thank you!
Still need the India firmware ver? i hv the latest update: X5-IN-23_20190114-1843.
Buy x5 Indian version
Hi. I need the Indian version firmware. Hope u can help me.
Maybe you can upload it to mega or Dropbox and I can download it from there.
Thanks
Avi
Related
Here is my issue, will try to explain as much as I can:
So I got the phone only booting to the LG logo and no further. So I read a couple threads which were mentioning about the LG Flash tool that I could try to use to restore the device, that did not work. So I tried to do Fastboot to see if that would help in any way. After trying, I was able to get Fastboot using @Lelus method ,now I cant get back the S/W upgrade mode, trying everything i could think of and still no progress. Would really love to fix this device and appreciate any help I can get.
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
mechen said:
days , I can help you. First download the drivers for your phone (if you have already remove them and re-load )
Next, download the LG Mobile Support Tool .
then go to your phone S / W upragade Mode (Press the volume up or down on the start)
then start the support tool as an administrator.
then press the Settings update recovery .
on the 90% of the phone restarts functional.
If you have any problem just say it to me!
-Mechen
Click to expand...
Click to collapse
Already tried all that. Phone does not boot or nothing. I can only access fastboot. I cant even flash the ICS u and x boot. When I try it says remote: partition doesn't exist.
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
trumpiks said:
Can you flash recovery through fastboot, and then acces it? I had similiar problem to yours, bricked my phone, barley made it to fastboot, i then flashed recovery using fastboot flash recovery recovery.img then booted to recovery and applied backup, or you might aswell flash a rom, if you don't have rom on your SD, use other phone to put ROM on sd, or card reader etc., the just install it. Just incase. i added recovery.img to my post.
Forgot to mention, after flashing recovery, try fastboot reboot recovery
Click to expand...
Click to collapse
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Liger878 said:
Will try it right now and let you know
DIdnt work. It says
C:\fastboot\bin>fastboot flash recovery recovery.img
sending 'recovery' (5898 KB)...
OKAY [ 3.070s]
writing 'recovery'...
FAILED (remote: partition does not exist)
finished. total time: 3.077s
Click to expand...
Click to collapse
Ok now thats strange, you have all the drivers? ADB, OMAP, FASTBOOT
Yeah, everything is installed and installed properly.
Sent from my SGH-T959 using XDA Free mobile app
I am trying to flash twrp or any custom recovery image so that I could root my LGv10, I am running Android 6.0.
When I boot my phone into fastboot mode I dont get the fastboot options just the options to exit or restart. However I still can run commands through adb, I try running the command to flash the custom image and I keep getting this.
Code:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (5158 KB)...
OKAY [ 0.160s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.185s
If I try to start up in recovery mode I get an android with a red error triangle, preventing me from rooting. Is there anyway I can fix this? any help will be appreciated as I've looked already and cannot seem to find a fix to this problem.
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
cyvr1 said:
Hi, which model of the V10 do you own?
Please note that bootloader unlock and installation of a custom recovery is only officially supported on the T-Mobile Version of the V10 and the European V10 with the model number H960A. On the H960A you need to unlock your bootloader first. Otherwise flasing recovery fails.
Click to expand...
Click to collapse
Thanks for the reply!
My LGv10 is the T-Mobile version, model number LG-H901. I'm running Marshmallow 6.0, My bootloader is unlocked I'm still getting the same problem.
Not sure what to try anymore
Same exact issue I have. Don't know what else to do.
I was getting that yesterday, though I found another method that seems to have worked, only issue with that one is that whenever I try I flash a ROM, it fails with error 7.
https://dottech.org/198032/how-to-root-lg-v10-t-mobile-h901-on-android-6-0-marshmallow/
This was the method I used, though I didn't do it properly since I couldn't figure out what to do with the kdz file. But I do have TWRP recovery installed to my phone now.
Hello,
After having flash KERNEL_B360a_TOUCH_FIX.img to solve a problem of mount with TWRP on my Honor 9 stf-l09, here I am completely blocked,
When i access TWRP, the screen hangs on teamwin, so I restart the laptop, I waited on "your device has been unlocked and can not be trusted", I do POWER to boot normally and I stumble upon Huawei eRecovery
He offers me: Download latest version and recovery, reboot and shutdown, when I go to Download latest version and recovery it connects to my wifi but still it marks that it does not work ..
I followed this tutorial https://forum.xda-developers.com/honor- ... k-t3696892
I took the last link STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1
I did as agreed, create the dload folder at the root of my sdcard with inside UPDATE.APP
I did Vol + and - + POWER to install and it marks: Software install failed!
What can I do ? Thank you
What firmware version were you on before flashing KERNEL_B360a_TOUCH_FIX.img ?
Nougat service repair firmware won't work over oreo.
You pasted wrong your link.
Hello,
I used this link https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Yeah, won't work if you were already on oreo.
For the firmware I think it's Android Oreo on Honor 9 (EMUI 8.0) so I have to redo the manipulation with this version ?
I' m guessing you flashed B360 kernel over a B362 kernel partition.
But you could have done something else wrong.
Would you have a link? What should I install?
Don't rush.
When you access TWRP, the screen hangs on teamwin, so you restart. Could you WAIT more when you fell it hangs ? and what twrp version are you using ?
About your kernel flashing ; could you post here the command you used ?
version twrp: stf-twrp-zxz-0.3.img
I waited 10 minutes but nothing.
For the kernel i used fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
So assuming you flashed B360 kernel over a B362 kernel partition ;
Just flash this stock B362 kernel over your kernel partition to solve your booting problems :
https://mega.nz/#!bdEgiIAJ!sfkzPeBBKVeDzB2ifsczFxJHrKF8JWY1WP1a8PH9fFg
with :
' fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img '
How to fastboot adb on my computer because normally I had to authorize the connection with my honor 9?
Connect your phone to computer via USB.
Hold Volume.down and keep holding it.
Power off phone, then power on while still keeping Vol.down held until you're in bootloader mode aka fzstboot mode.
This should boot you into fastboot mode where you can issue these commands :
fastboot devices
fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Deadfightmc said:
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone
Click to expand...
Click to collapse
fastboot is not adb.
adb is not fastboot.
Deadfightmc said:
but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Click to expand...
Click to collapse
So you successfully flashed via fastboot a C432B362 stock kernel over C432B360 kernel fix and it's still bootlooping...
Do you think your region cust may have been something else than European C432 ? Maybe : Japanese C635 ? Russian C10 ?
Download again stf-twrp-zxz-0.3.img and try to flash your non-working twrp with :
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
I downloaded and flash again stf-twrp-zxz-0.3.img but it still hangs on "teamwin" Should I test all possible kernels?
If your bootloops really appeared because you flashed B360kernelfix, flashing the stock kernel of your actual version will solve your issue.
But, before that, does twrp was working ? What do you call 'a problem of mount with twrp' ?
-I'll say user problem- [emoji14]
I wanted to install SuperSU with twrp so I put it on my sdcard, I installed it with twrp but there was an error so I looked at this link https://forum.xda-developers.com/honor-9/development/oreo-t3754483
problems:
Mount system rw
Custom kernel required because of Huawei MMC protection (check second post)
And there he said Download kernel http://www.mediafire.com/file/6n1wfb..._TOUCH_FIX.img
Flash with fastboot.exe kernel flash KERNEL_B360a_TOUCH_FIX.img
So:
1. system and twrp 0.3 were working.
2. you flashed a 'random' supersu via twrp and it gave you errors
3. you flashed B360kernelfix
Am I right ?
Yes that's it
So first we'll try to fix what you did when you flashed a bad supersu (which one ?) by flashing a stock B360 boot image :
fastboot flash ramdisk STF-L09_ramdisk.img
https://forum.xda-developers.com/attachment.php?attachmentid=4420592&d=1518680458
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/huawei-p20-pro/how-to/guide-erecovery-hisuite-failing-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
DankMemz said:
First, in TWRP, advance wipe everything! Now, you need a pc, connect the phone to PC with a USB, on pc, download any ROM you want (and gapps if you want) now transfer the files to your phone and then flash them, izi,
Thumbs up if I was useful.
Click to expand...
Click to collapse
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
benkiller47 said:
Hi thank you for your help , unfortunatly at the end of the ROM installation , my phone reboot back to fastboot mode , no matter wich ROM i boot in it
also good to precise i have a Huawei p20 pro
Click to expand...
Click to collapse
Try reinstalling stock firmware trough download mode...
Try reinstalling the twrp image. Helped me once
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.