Hi everyone, I need help, my phone stayed in the bootloop, I searched for the stock rom for the g5s xt1791, and I did not find it anywhere, I tried to flash a rom of the xt1792, but when I was flashing the system. pull error tells me "the image is too large", I have not been able to solve, in advance thank you very much for your help
hello, you tried with mfastboot?
your bootloader and unlock it?
lohanbarth said:
hello, you tried with mfastboot?
your bootloader and unlock it?
Click to expand...
Click to collapse
yes, the bootloader is unlocked and try it with adb 'fastboot', also looking in my backups, I had made a backup with the recovery twrp, that I have the system_image.emmc.wim, which weighs 3.5gb, no I know if I can take out the rom stock from there
you have followed my tutorial, the cmd starts well with mfastboot ......
because this rom and for all models.
lohanbarth said:
you have followed my tutorial, the cmd starts well with mfastboot ......
because this rom and for all models.
Click to expand...
Click to collapse
ok, I will try the process again following your tutorial, should it be with the last MONTANA_NPP26.102-49?, thank you very much for your help
@lohanbarth , Thank you very much, I followed your tutorial, and everything works perfectly:good::good:
Related
Hello guys,
this morning I've received the 4.3 OTA. The entire installation was ok, but my face unlock option is not working anymore.
When I try to unlock using FaceUnlock, i had this message error: "Face Unlock couldn't start".
I've already tried several changes in settings but without success.
Any suggestions to fix this?
Thanks in advance.
Hi I had the same issue, looked around but couldn't find anything. Managed to sort it out myself tho, if you have unlocked your bootloader and have fastboot on your computer then all you need to do is download the factory images for your phone from here https://developers.google.com/android/nexus/images extract the system.img file the boot into your bootloader and use the commands
1)"fastboot flash system system.img" then
2a)"fastboot reboot-bootloader"
2b)"fastboot format cache" (not sure if these two steps are necessary boot did no harm for me).
3) "fastboot reboot"
If your rooted you will lose root so will need to re root your phone
Thanks fezy.
It worked for me as well.
No problem, glad it worked for you too
fezy said:
Hi I had the same issue, looked around but couldn't find anything. Managed to sort it out myself tho, if you have unlocked your bootloader and have fastboot on your computer then all you need to do is download the factory images for your phone from here https://developers.google.com/android/nexus/images extract the system.img file the boot into your bootloader and use the commands
1)"fastboot flash system system.img" then
2a)"fastboot reboot-bootloader"
2b)"fastboot format cache" (not sure if these two steps are necessary boot did no harm for me).
3) "fastboot reboot"
If your rooted you will lose root so will need to re root your phone
Click to expand...
Click to collapse
Thank you very much fezy.
I had exactly the same problem on my Nexus 4 : your tip worked like a charm !
Can someone help me and explaine step buy step how to do this ..
thx in advance
Yakumoone said:
Can someone help me and explaine step buy step how to do this ..
thx in advance
Click to expand...
Click to collapse
Everything you need is here! GL
http://forum.xda-developers.com/showthread.php?t=1626895
syspanic said:
Everything you need is here! GL
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
thx
gonna have a try
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Pouni said:
Solved my problem by flashing the FULL firmware and not only the boot.img !
Could a mod delete the thread please ? Thanks !
Click to expand...
Click to collapse
Please don't ask mods to delete threads because of successful outcomes - post your solution instead. Leave the threads up as they are a useful resource for others (at least those who search before posting! )
Thanks
Sent from my SAMSUNG-SM-G920A using Tapatalk
joesee said:
How did you accomplish this? I can't get RSD Lite to detect my phone (although fastboot devices shows it listed) and I can't flash the full firmware via adb because I keep getting "Image not signed or corrupt". I'm really confused.
Click to expand...
Click to collapse
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Can't flash stock ROM, can you do a detail installation log?
Pouni said:
I kept getting the "Image not signed or corrupt" whenever I had to flash the boot.img but I ignored the error once to try and see if it had any positive outcome, and it worked fine !
Click to expand...
Click to collapse
Is ur bootloader unlocked or not??
If not try unlock ur bootloader than try it ll work
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
jon7701 said:
From what I can tell you will always get the "Image not signed or corrupt" error, but it works anyways. Idk why but it doesnt matter as long as it works . Motorola(Lenovo) has the instructions to flash stock firmware on your device, just download the firmware for your device and follow those instructions.
Click to expand...
Click to collapse
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Vitxlss said:
Jon, can you help me? already tried to flash stock rom in fastboot but it doesn't flash.... i'm tired of this
Click to expand...
Click to collapse
Did you only flash the stock rom or did you try to flash everything? If you didnt try to flash everything I would try that and make sure you have the correct stock firmware for your device before you do that. Theres not really much else you can do other than try flashing in twrp, but idk if twrp supports space chunks, but it does support images. If it really comes down to it, you can force flash the system partition in twrp, but you would need the whole system image and not space chunks.
I've unlocked my bootloader but now each time i try to use the bootloader it won't do anything !! it keeps showing me FAILED (remote: unknown command) ! does anyone facing the same problem ? because i cannot even stock flash my phone !
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Dielahn said:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
This guide should help you
Click to expand...
Click to collapse
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Did you unlock critical?
Khalid_am said:
I've done everything before and I rooted my phone but now I'm trying to stock flash 8.1 but it won't do it and neither will let me even flash anything ! I even tried to relock my bootloader and unlock it again it won't even let me do that ! all that it shows is the error that i've mentioned before
Click to expand...
Click to collapse
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
murphyjasonc said:
Did you unlock critical?
Click to expand...
Click to collapse
No and everytime i try to do that it keeps telling me the same error
Dielahn said:
Maybe you need to update platform tools. I just went from 8.0 to 8.1 and i couldn't flash the flash-all for some odd reason but i got it to work by sideload the ota zip.
Click to expand...
Click to collapse
i downloaded the latest version
Khalid_am said:
i downloaded the latest version
Click to expand...
Click to collapse
Can you explain exact steps you are taking so we can help you better?
Dielahn said:
Can you explain exact steps you are taking so we can help you better?
Click to expand...
Click to collapse
I downloaded the platform-tools and started the cmd from the platform folder then each time i try to flash anything or interact with the bootloader it just keeps showing me this message (FAILED (remote: unknown command)
Hello everyone i have a trouble with my poco f3.
I tryed to unlock the Bootloader with the xiaomi utilities, i waited 7 days and clicked on unlock everything was fine till the phone reboot and then did a bootloop.
i tryed to flash a rom stock with fastboot and xiaomi flash, but everytime after the flash my phone get stuck on the poco logo....
I tryed to install twrp but when i launch adb in cmd it say "device null not found"
i really need some help please...
Thank you
If you already unlock bootloader read this thread maybe helpfully
Bricked device?
I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3...
forum.xda-developers.com
Try to install another fastboot ROM
To flash a fastboot rom wich driver i need ? Bootloader ? Adb ? Qualcomm ?
Georgebabush said:
To flash a fastboot rom wich driver i need ? Bootloader ? Adb ? Qualcomm ?
Click to expand...
Click to collapse
U need adb ... To flash something bro respect from Georgia for trying to Unlock bootloader on f3
(Gugucha) said:
U need adb ... To flash something bro respect from Georgia for trying to Unlock bootloader on f3
Click to expand...
Click to collapse
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !
Georgebabush said:
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !
Click to expand...
Click to collapse
Good job nice to hear that where are u from ? anyways ?
Georgebabush said:
Well i tryed to flash syberia fastboot, i tryed like one hundred time and this time, it worked i dont know why.....
I'll maybe try to reflash the EEA rom if i dont like Syberia, it's the only rom that worked
Thanks for your help all !
Click to expand...
Click to collapse
Great to hear you solved the problem