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?
Related
I have Z2 D6503, I had once rooted and installed recovery on my phone and left it that way, few days ago I tried to install a rom from recovery, phone wasn't booting to recovery, since then I tried any guide to root and install recovery even till version 17.1.2.A.0.314. and none was working, anybody had this problem?
what can I do to fix it, the phone was already formated from data so any solution is a good one,
thanks in advance, Amir.
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
convict_moody said:
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
Click to expand...
Click to collapse
found one, but I get an error:
Code:
downloading 'boot.img'...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.003s
not boot.img, recovery.img
download twrp recovery image from their site, and use that one. boot.img is the kernel not the recovery
convict_moody said:
U can try entering fastboot and boot into custom recovery without flashing it by using command:
Fastboot boot recovery.img
After command success the phone will reboot to desired recovery automatically.
Where recovery.img is the name of the custom recovery file, then flash custom firmware from the recovery.
Enjoy.
Click to expand...
Click to collapse
ticktock666 said:
not boot.img, recovery.img
download twrp recovery image from their site, and use that one. boot.img is the kernel not the recovery
Click to expand...
Click to collapse
I get this error while i'm doing the command:
fastboot boot recovery.img
Click to expand...
Click to collapse
when recovery.img is the twrp recovery image.
CosTuMe said:
I get this error while i'm doing the command:
when recovery.img is the twrp recovery image.
Click to expand...
Click to collapse
Did you try using another PC, or another pc port?
convict_moody said:
Did you try using another PC, or another pc port?
Click to expand...
Click to collapse
true, forgot about it, but now getting this:
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
CosTuMe said:
true, forgot about it, but now getting this:
downloading 'boot.img'...
OKAY [ 0.381s]
booting...
FAILED (remote: dtb not found)
Click to expand...
Click to collapse
I believe in this case if u used command:
Fastboot flash recovery boot.img
It will work, I think the recovery u are trying to boot is twrp,
If u got an error that the image isn't a boot image or something like that, redownload the recovery and try again.
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
raystef66 said:
Hi, back again
As i can see, try not to mess with the names :revocery...
When you want to flash the boot.img don't change that name.
Just flash it like : fastboot flash boot boot.img
Use my last boot.img which i sent you. That's a good one out of my backup.
For the FRP (perhaps edit your thread tiltle ) i have no answer in a minute. Did the "fastboot oem unlock" gave anything better ?
Click to expand...
Click to collapse
I have try also boot , try everything, not matter if youhave FRP lock fastboot oem unlock is only to unlock bootloader, which i have, that is not a problem.
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
joyrida12 said:
See if this method works for you
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
michalss said:
You cannot use this method since i have only FastBoot feature, adb is not possible to use, since phone never boot. This method can be used only for phones what can boot correctly, so unfortunately useless for me. but thx for link
Click to expand...
Click to collapse
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
stiggu said:
i have exactly the same problem. FRP is locked but my phone doenst boot. so how can i unlock the frp with the fastboot mode?
Click to expand...
Click to collapse
same problem on my mate s
good to know that adb is not working for others
i thaught it was just me
I've the same problem , any idea ??
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Hey , the problem is the device won't boot , so how can we enable developer option?!!!!
Sent from my iPhone using Tapatalk
There was a time when xda where the place to get the right answer and quick!
nowadays most topics are full of people with same problem and no dev to come to help, pity.
on topic: I have the same problem, ( mine is a Y6 pro) and before bricking it I had debugging and oem unlock enabled but now can't flash boot etc using fastboot ( error , denied ..) and can't use spflashtools either : preloader vcom appears for 1 second and then disappears and phone turns on.
tried many drivers, 3 Os'es (7, 8.1 ,10) still no luck.
porcha18 said:
activate "Developer options"
playing several times "compilation"
go to options and enable developer
"Enable OEM unlock"
Click to expand...
Click to collapse
Danke!!!!!!!!!!!!! Nach ewigem Suchen diese einfache Lösung. Vielen Dank!! Tag gerettet
the same issue
Good day, i have the same issue on my p9 EVA-L19.
FRP lock. And i can't do anything...
My warranty says that they cannot recover data from the phone, but the information is very important. I need to unlock FRP and somehow boot into TWRP or something to recover my data.
Please help someone if you had a same issue and results.
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Runner85sx said:
For the Huawei Y6 you can return to Stock.
Try to fastboot boot recovery-twrp.img and put your stock firmware (dload) folder to the rootdir at your sdcard.
Reboot your device to bootloader and hold down vol+ + vol- and use the command: fastboot boot stockrecovery.img (keep the keys pressed until the stock recovery comes up and starts installing your stock rom.
You will see an emui logo and the recovery will install the complete stock rom if you did everything right.
Retry to boot the stock recovery with this way if it is not working at the first try.
EDIT: after i wiped /system and and all the other stuff i was able to flash stock recovery via fastboot.
Click to expand...
Click to collapse
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
anditan said:
Is there a way to do this on a mac?
Ive got adb enabled on terminal and I have a recovery.img file in my downloads though Im not sure if its the right one.
I typed in fastboot devices and then fastboot flash recovery recovery.img but it said cannot load recovery.img
Click to expand...
Click to collapse
your recovery location in adb is wrong probably. try changing it to the correct path. atleast thats what worked for me
man u can'T do anything because FRP is ACTIVATED !!!
No solution till now
Use the Huawei Swype bypass Method
michalss said:
Hi all,
I have a small problem, my phone does not boot and hanging on Logo. Now i can boot to fastboot menu, but i cannot really use it since i have FRP lock . Is there any chance to baypass it to make possible to flash recovery boot.img ?
When i try any command getting this error :
Code:
target reported max download size of 266338304 bytes
sending 'revocery' (4096 KB)...
OKAY [ 0.142s]
writing 'revocery'...
FAILED (remote: Necessary to unlock FRP! Navigate to Settings > Develope
finished. total time: 0.154s
Since my phone not booting i cannot use this option Please help
Click to expand...
Click to collapse
Try to do:
fastboot boot recovery.img
This will boot up the device with the given image. With that you can put a custom rom to your sd-card and flash it.
I will upload a Nandroid (stock system, recovery, boot) from my Y6 SCL-L01 soon.
With that you can restore boot and recovery with twrp. For this way you don't need to have a frp unlock.
Procedure:
fastboot boot recovery-twrp.img
Put your stock firmware (dload folder) to the sdcard.
Put my Nandroid to your sdcard.
Restore my Nandroid, reboot your device with Vol+ and Vol- pressed.
This way only works for SCL-L01 up to SCL-L04.
I need to create an extra recovery.img that includes a dt image that fits for all SCL variants.
Work in progress...
I have just removed frp today, but its not free method, unfortunately
Hi,
i've a little (big?) problem with my xperia tablet z (wifi; pollux_windy). 2 years ago i've rooted the stock-rom (4.2 or 4.4) and installed dual-recovery. a while a did nothing with the tablet. later i installed cyanogenmod 11 using the installed recovery. someday in 2016 i updated to cyanogenmod 12, but i can remeber how i did this exactly - maybe with a update-app? after the update to cm 12 the dual-recovery was overwritten with a cyanogenmod-recovery.
i don't know whether the bootloader is unlocked. i've unlocked i to root the device for the first time. when i search for the imei in "about tablet / status / imei" there is only "unknown". so at the moment i can't unlock the bootloader again.
when i boot the device in fastboot mode and try to flash twrp with
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
i get this error
fastboot flash recovery twrp.img
sending 'recovery' (10688 KB)...
OKAY [ 0.359s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.359s
Click to expand...
Click to collapse
maybe this is because the bootloader isn't unlocked anymore? how can i find out that? how can i unlock the bootloader again without the imei or how can i find out the imei?
a user in a german forum said i can use the sony tool emma, this should reset the tablet. but WHAT will emma reset? can i flash twrp after that? can i root it again?
pieremallao
From fastboot you have to type
fastboot flash boot twrp.img
Click to expand...
Click to collapse
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
PiereMallao said:
what is the different between
Code:
fastboot flash recovery
and
Code:
fastboot flash boot
?
Click to expand...
Click to collapse
as far as I have understood they are two different partition, Sony devices have the recovery in the boot partition whereas other phones, such as my OnePlus One, have a dedicated partition.
But what I'm sure is that when I flashed TWRP in my OPO I used the "fastboot flash recovery twrp.img" but in my pollux_windy I had to use "fastboot flash boot twrp.img"
doesn't work. i tried this on ubuntu 16.04 and in terminal i see the message
Code:
sending 'boot' (10688 KB)...
since 30 minutes. maybe this is because the bootloader isn't unlocked? but i'm not sure about that? how can i check this?
I remember very well the code I entered to get TWRP, now I'm also thinking you have somehow a locked bootloader...
PiereMallao said:
how can i check this?
Click to expand...
Click to collapse
if you use a stock ROM try: contacts/press three dots/Settings/press a place above home knob for few sec/it will appear Enter service Code/type *#*#7378423#*#*/Service info/Configuration
no, i dont use a stock, i use cyzanogenmod 12. i dont have the contacts app on mz tablet installed. i have tried to install google apps but the cyanogen recovery cant install the gapps. can i tried the service codes with an other app?
PiereMallao said:
can i tried the service codes with an other app?
Click to expand...
Click to collapse
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
With the same app try
Code:
*#*#759#*#*
and I have "OEM mode = off" but I'm not sure if it means that your bootloader is unlocked.
Or download Secret codes, the app's icon is a magick stick with a star at the and it shows some codes and you can lauch them from the app itself. I think it only shows the codes available to your phone/tablet because it doesn't show 7378423.
-Pepe said:
Try to download ExDialer - Dialer & Contacts and launch the code from there. I tried with it but it didn't work (probably because I'm on RR) so I doubt it will work for you but give it a try.
Click to expand...
Click to collapse
On CM there is no service menu, so it won't work.
Unlocking is possible with Flashtool or fastboot commands.
deleted
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.
Hello guys...
So, without going too much into details of how I idiotically f-ed up pretty much everything... I just want to say that I've already lost about 12 hours reading through the forum trying to solve the problem and to understand how everything works, and by what I understood... I bricked the phone?
Firstly, I managed to unlock the bootloader with the HCU Client (Phone unlocked, FRP unlocked). At some points I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
I've tried hard but never managed to boot any of the Custom ROMs available, especially the LineageOS 16 which I wanted but later on, through a specific TWRP which gave an error information that it's meant for Hisilicon, and not for Kirin SoC...
I also had no idea when I was booting into recovery, and when into erecovery, because I flashed TWRP over both of them... I have really no idea what was the last thing to happen, but now it seems as if I can't boot into eRecovery anymore, and whatever I try flashing to the recovery_ramdisk over Fastboot, I just always get the same error when trying to boot into recovery
Error! Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Now I'm also having an issue because my battery has drained and it doesn't seem to turn on without it being connected to the charger or a PC.
Is there anything that I can do to make it work with any Custom ROM?
returnedinformation said:
I've managed to boot into TWRP's, but I flashed them without understanding that I should have installed the recommended ones by the guys on this forum instead of the official one, with which I wiped System and Data partition.
Click to expand...
Click to collapse
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
-Alf- said:
This is the result of some people posting nonsense here.
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
As I said before
-Alf- said:
some people posting nonsense here.
Click to expand...
Click to collapse
Totesnochill said:
Alf is right:
Gather info about your phone with the fastboot commands -Alf- provided.
Using this info, find TWRP that 100% supports your phone. TWRP that is recommended in the "p20 lite basics" thread on XDA.
Start phone in fastboot mode. Use the fastboot boot twrp.img command to TEMPORARILY boot into TWRP (twrp.img must be in the same folder as fastboot.exe)
If TWRP hangs, reboot, try another TWRP
Once you are in TWRP, perform wipe and advanced wipe to clean up EVERY PARTITION (except sdcard) that you've messed up in the internal memory.
wipe data again to enable USB file transfer
Find a ROM for your phone. USE THE INFO FROM STEP 1 to figure out if the rom is REALLY for your model AND hardware revision of the phone. Pay attention to the device serial number and codename! ROMS developers use device codenames to indicate what model is compatible and what isnt. Huawei p20 lite has a total of 7(!!!) hardware revisions, and ROMS for each are different and likely NOT cross-compatible, which means if you install the wrong one, you will end up with a brick or a bootloop.
While TWRP is still on, Transfer ROM.zip to the phone.
In TWRP, use "Install" option to flash the ROM.
DO NOT FLASH TWRP PERMANENTLY! LET THE STOCK RECOVERY BE. FLASHING TWRP TO A/B (DUAL SLOT) DEVICES WILL 99% RESULT IN A BOOTLOOP. MOST MODERN DEVICES ARE A/B.
Flash Gapps if you need.
Reboot. Will take longer to start on the first boot.
Click to expand...
Click to collapse
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
Sorry, but I'm already stuck at step 3:
PS C:\adb> fastboot boot twrp.img
Sending 'boot.img' (15652 KB) OKAY [ 0.411s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
I see. Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons:
1. Bootloader isnt "fully" unlocked, please check with the unlocking guide/service provider (if unlock was a paid service)
2. Bootloader is in "retail" mode, not a "service" mode. Some manufacturers do not intend for bootloader to be unlocked, and ship the devices with a restricted "retail" version that blocks certain commands.
also, why is your fastboot sending the "boot.img" while the command had " twrp img" as a payload?
I take it the bootloader still lets you use the "flash" command? If true, flash TWRP temporarily by "fastboot flash boot twrp.img", restart teh phone using the recovery menu keycombo
returnedinformation said:
> fastboot oem get-build-number
(bootloader) :ANE-LX1 8.0.0.126(C432)
> fastboot oem get-product-model
(bootloader) ANE-LX1
> fastboot getvar vendorcountry
vendorcountry: hw/eu
> fastboot oem oeminforead-CUSTOM_VERSION
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :ANE-LX1 9.1.0.132(C432E5R1P7)
Click to expand...
Click to collapse
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Totesnochill said:
Some phones have this issue. where bootloader will not allow the "boot" command. Can be for a number of reasons
Click to expand...
Click to collapse
No, there is only one reason - on Huawei devices we do not have a "boot" partition since Android 7.
-Alf- said:
you've mixed apples and oranges nicely .
Try this way out, using HuRupdater
Guide
Downloand TWRP
Here
Click to expand...
Click to collapse
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Personally i had a xiaomi poco f2 pro 6/128 and then i bought another same model phone but 8/256 from a fellow who almost bricked his phone..it was just blinking, when i restarted the phone, it went straight into blinking whenever i tried to boot into recovery, and it wouldnt boot into system anyway cos there was nothing there. so i figured it was stuck in recovery loop.
i was fortunate that i was able to hook up to it using my pc...then using command prompt, i was able to switch to fastboot mode..then i tried downloading and flashing different twrps, over 10 different twrps, and finally one worked..then it was smooth sailing from then on..and presto, that became my daily use phone.
returnedinformation said:
Thank you, I've put them in blender and set it to "lightspeed" mode
I'm sorry, but flashing that TWRP gives me the exact error I've been getting before when trying to boot into Recovery... the fact that the phone can't charge also gives some headache to actually even try to boot into the recovery. I just can't get into.
Edit: The furthest I can get to is that recovery error message.
Click to expand...
Click to collapse
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
flashgordon65 said:
hi there..was reading about your problem..i'm not sure if the same rules apply to all or most phones with regards to flashing twrp or using fastboot..i'm assuming that they do.
So, are you able to boot into fastboot and/or recovery?
if no to recovery, i guess it may be the wrong twrp, i hope you can at least boot into fastboot without any issues.
Click to expand...
Click to collapse
-Alf- said:
Can you boot into eRecovery (into TWRP installee over eRecovery)? If so, try to flash eRecovery_ramdisk.img in TWRP,
download Here for EMUI 9.1
or Here for 8.0 (I'm not sure what is your current version).
In eRecovery mode you can charge the phone ( charging should also work in TWRP which is installed instead of eRecovery).
Click to expand...
Click to collapse
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
returnedinformation said:
I can boot to the Fastboot, but unfortunately I can't boot to either recovery or erecovery... When trying to boot to the recovery by holding the power+volume up button until I see the "Your device has been unlocked" warning message + 2 seconds (which is when I see the recovery error message), or when trying to boot while plugged into USB also holding the power+volume up button just leaves me at "Your device is booting now...." forever
Click to expand...
Click to collapse
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
-Alf- said:
doesn't look good bro, try the following :
in fastboot mode run commands
fastboot erase user data
fastboot reboot
Click to expand...
Click to collapse
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
returnedinformation said:
PS C:\adb> fastboot erase user data
Erasing 'user' FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Click to expand...
Click to collapse
Sorry!
fastboot erase userdata
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
returnedinformation said:
PS C:\adb> fastboot erase userdata
Erasing 'userdata' (bootloader) success to erase cryypt info in oeminfo
OKAY [ 0.215s]
Finished. Total time: 0.236s
PS C:\adb> fastboot reboot
Rebooting OKAY [ 0.024s]
Finished. Total time: 0.024s
Okay, what can I do now? I've tried flashing twrp right after that but solely rebooting get's me stuck at "Your device is booting now...", and trying to boot to recovery gives me the same error again
Click to expand...
Click to collapse
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
-Alf- said:
Download stock Recovery Oreo
Link
Flash it in fastboot
fastboot flash recovery_ramdisk RECOVERY_RAMDISK-ANE-8.0.img
- fastboot reboot
Then try to boot into Recovery.
What exactly did you do after unlocking your phone? Did you upgrade back to A9? If so, then flash recovery_ramdisk A9
Download here
Click to expand...
Click to collapse
I've tried both, they give me the same error.
After I flash the recovery I can't really reboot straight into recovery because of the issue with the battery... somehow I gotta hold the Volume UP key, while catching exact moment when I can unplug USB after the low battery status page passes, and before Huawei logo appears...
After unlocking the phone I flashed TWRP over either recovery or erecovery (idk anymore)... then I probably installed Pixel Experience 13 ROM (https://github.com/ponces/treble_build_pe/releases)
And after that... I tried too many things I can't even remember anymore.
returnedinformation said:
then I probably installed Pixel Experience 13 ROM
Click to expand...
Click to collapse
Under EMUI 8 ??? Which TWRP?