Hey guys,
i've a massive problem with my G4. Today i flashed TWRP on the device, after i was unlocking the bootloader. After booting up into TWRP, and installing SuperSU, I just restarted it. Now it's dead. Seriously, it's dead.
I can't start it at all. If I plug in a USB-Cable, i just see the LED Light. I've Windows, and at my Device Manager, the G4 is recognized as QHSUSB_BULK.
I saw a Thread for the Moto G (1th), and i'm pretty sure, that i can't to this like in this tutorial:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Is there any option, what i can do?
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
__Madddy said:
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
Click to expand...
Click to collapse
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900M system system.img" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
I'll try to flash each files which are in the image.
Marwycy said:
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
Click to expand...
Click to collapse
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
__Madddy said:
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Click to expand...
Click to collapse
I tried it, i can't open system.img at all. So i can't extract anything..
Marwycy said:
I tried it, i can't open system.img at all. So i can't extract anything..
Click to expand...
Click to collapse
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
__Madddy said:
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
Click to expand...
Click to collapse
Sorry, i was a bit confused because of this large list of commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
And i figured out, that it's not necessary. All I had to do ist following the official way by just using "fastboot system system.img" , with the Image from the officla Motorola website. My first file was corrupt, that was the problem.
Now my phone is working again
Thanks for help.
Marwycy said:
Now my phone is working again
Click to expand...
Click to collapse
For Rooting, don't flash zip directly,
Follow this guide, https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Take BACKUP, if anything wrong then RESTORE it...
first upgrade to 7.0 bro then go ahead with rooting .
say me if want any help??
Sent from my Moto G4 Plus using Tapatalk
---------- Post added at 04:16 AM ---------- Previous post was at 04:11 AM ----------
http://cloud.tapatalk.com/s/586730a47ebfa/superuser.zip
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Sent from my Moto G4 Plus using Tapatalk
parth00790 said:
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Click to expand...
Click to collapse
Please, provide complete information, no root method is working on latest (official) Nougat, your half information can brick other's phone and can put them in trouble...
i have used with rooted nougat
just same method for Twrp
enable usb debugging and flash twrp using adb .
then flash superuser.zip provided in previous comment and install phh superuser from playstore .
you are done bro .
i have tried and working
Sent from my Moto G4 Plus using Tapatalk
moto g4 plus brick
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
djsusant said:
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
Click to expand...
Click to collapse
Calm down. Read this.
Wrong, delete please
Ayuda/Help
Hola me podrias ayudar tengo el moto g4 xt1621, lo que sucedio fue que estaba flasheando eol parche de seguridad de 7.0 no recuerdo si era de diciembre o de marzo pero cuando acabo le di en reboot system now pero no prendio mas, solo prende el led y la pc lo reconoce ya instale los drivers pero me da error quisiera saber si me podrias ayudar a fondo a recuperar mi moto g4, disculpa pero lo pongo en ingles y español pero no hablo ingles uso el traductor, ayudame porfavor
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
TioHenry said:
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
Click to expand...
Click to collapse
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
echo92 said:
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
Click to expand...
Click to collapse
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
TioHenry said:
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
Click to expand...
Click to collapse
Okay, point 3 indicates that you perhaps need to try resetting your phone with a blankflash: you may wish to have a look at this post https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 Please read all the steps fully before proceeding if you choose to follow that post. I recall you've posted in the hard brick thread too, which has similar instructions, perhaps this may work.
I do not know if this will work, but it's worth a try.
HELP me
Can you give me the link of stock rom for Moto G4 XT1624
Related
Hi there,
I tried to update my Moto G4 Plus and I think I made some big mistakes..
I can only start into Bootloader with the following text shown below:
AP Fastboot Flash Mode (Secure)
BL: B0.0E (sha-4986429, 2016-104-13 14:23:47)
Baseband: [bla] ATHENE_EMEA_DSDS_CUST
Product/Variant: athene_16mp XT1642 16GB P2A
Serial Number: [bla]
CPU: MSM8952
eMMC: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000007
DRAM: 2GB SAMSUNG LP3 DIE=8GB M5=01 M6=05 M7=00 M8=5f
Console [NULL]: null
Battery OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
Click to expand...
Click to collapse
- No TWRP or other Recovery
- No OS
- No Fastboot connection to my Win10 64bit anymore (
I think the problem is the "AP Fastboot Flash Mode (Secure)" Mode.
Any ideas how to solve it?!
thanks alot anyway
The AP Fastboot Flash mode(secure) seems okay to me. However it is highly possible that your drivers aren't installed on the phone. So in this case try to first connect the phone to the computer and see if it get's detected or not, and then you should manually install the fastboot USB driver. Download the driver zip from Google's repository and extract it, later choose the .inf file and then the Android Bootloader Interface.
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
PS: This driver and the fastboot adb binaries are completely different thing. fastboot won't work unless you have this USB driver.
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
The latest stock ROM is the NPJS25.93-14-10 (Sept 2017 security patch) build https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You'll have to flash the stock ROM in fastboot, which would wipe TWRP off your device again. You cannot properly flash stock firmware in TWRP (only can flash the system in TWRP).
Once you've flashed the stock ROM and TWRP, you can use ElementalX, I'm using the 1.0.4 stock version on the NPJS25.93-14-10 build with magisk 13.3 (to root) and it's running stably on my XT1642.
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
stefanhanz said:
Thank you! Now its working as it should with the newest updates!
Thread can be closed. Thanks
Click to expand...
Click to collapse
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
sersrendon said:
Hello Friend
I would like to know if you can explain how to fix it is that the same happens to me the ap fastboot flash mode * secure * because before I had already used the blanckflash to revive it because first soo turned on the white led
Click to expand...
Click to collapse
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Rog Ballester said:
Does anyone know what happened?
I updated the rom appeared this message.
Cell Phone: Moto g 4
Please help me :crying: :crying:
Imagens:
h t t p s:/ /goo.gl/nupYsT
h t t p s:/ /goo.gl/G8KNNV
Click to expand...
Click to collapse
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
echo92 said:
Looks like you've used the blankflash and your device is in the temporary bootloader, waiting for a stock firmware flash to repair.
You could flash the latest December 2017 stock firmware here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
You do not have to use the OEM lock commands whilst flashing. Also, be aware this flashing procedure will erase your device. As always, if this works please do not flash older stock firmwares if you can, else you may hard brick again.
Click to expand...
Click to collapse
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Rog Ballester said:
Não estou conseguindo, de uma olhada nessas imagens por favor
https: / /goo.gl/nupYsT
https: / /goo.gl/G8KNNV
Click to expand...
Click to collapse
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
echo92 said:
1) please post in English in these forums.
2) the images load up okay, you may require a Facebook account to access after removing the spaces in the link.
3) again, from what I see in the pictures, it appears your device has been flashed with a temporary bootloader and requires a full firmware flash. The above stock ROM should work with XT1626 devices, you may wish to check the stock ROM thread to confirm.
Edit: here are a couple of reports suggesting the ROM works on XT1626 devices. https://forum.xda-developers.com/showpost.php?p=75139620&postcount=538 https://forum.xda-developers.com/showpost.php?p=75263192&postcount=573
Click to expand...
Click to collapse
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Rog Ballester said:
When I pass the firmware flash, it comes back on the same screen
Gets stuck
:crying::crying:
Click to expand...
Click to collapse
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
echo92 said:
Can I ask how you're flashing the firmware?
Have you got your device connected to your computer via USB?
Does your device show on your computer, and do you have the stock ROM downloaded and extracted to your ADB folder?
When you flash, do you see [okay] after each command?
I'd like to see a copy of the flashing output if possible please
Click to expand...
Click to collapse
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Rog Ballester said:
Yes, I have the room files.
Yes, my computer recognizes
I had the bootloader unlocked, I went to update and it caught
please look at the pictures:
https://goo.gl/q7AHhL
https://goo.gl/QstpTS
https://goo.gl/JSz8r2
Click to expand...
Click to collapse
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
echo92 said:
Okay, what about the rest of the flashing output, from starting with the fastboot flash partition gpt... command? I only see the end of the commands with fastboot OEM lock and fastboot reboot, where's the important section?
Also, you may wish to replace the NPJS25.93-14-8 stock ROM you have with the NPJS25.93-14-13 stock ROM if you see pre flash validation or security downgrade errors.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
Do you believe you can recover your cell phone?
Click to expand...
Click to collapse
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
echo92 said:
I saw security downgrade errors, suggesting the stock ROM you are trying to flash is too old. Pre flash validation errors indicate the same thing, your downloaded stock ROM is not new enough to repair your device.
Please download the newest NPJS25.93-14-13 stock ROM as linked previously, delete the old stock ROM you have and replace with the newer stock ROM. Then try again. With a locked bootloader, especially, this is crucial. The bootloaders will block any attempts to flash old firmware if locked, hence why your device is still not working.
I've not bricked my phone, this process has been shown to work for others though. In some cases, flashing newer firmware than what you had could work. You have the June 2017 build, the NPJS25.93-14-13 build is December 2017.
Click to expand...
Click to collapse
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Rog Ballester said:
https://www.facebook.com/photo.php?...039.1073741830.100021461148601&type=3&theater
I wanted to thank you from the bottom of my heart. I got it sorted. Thank you so much for helping me. :good::fingers-crossed:
Click to expand...
Click to collapse
You're welcome
Please, in future, avoid downgrading your stock firmware if you can. If you do downgrade stock firmware, avoid OTA updates. Custom ROMs do not appear to matter in this regard.
I do not know if blankflashes will keep working as Motorola keeps updating the stock firmware. We may eventually need a new blankflash. Blankflashes are also rare as Motorola does not formally release them (luckily, we have a working one). So, do not rely on a blankflash to always bail you out of trouble.
stefanhanz said:
Thank you. When I connect my phone, I get the message on my phone "USB Connected" and in the windows device manager there comes an Android Device "Motorola ADB Interface" (official Lenovo driver). I also tried to install the *.inf file (downloaded it as you told), but there is no difference.
I tried the "blankflash" https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But I get the same message in cmd as always. < waiting for device > I dont know what to do..
edit: I got the message when I tried the blankflash.bat. Now I tried to install TWRP with fastboot and it worked!
Tanks alot!
Now, I want to install the lastest stock ROM. In the meantime I downloaded this version "ATHENE_NPJS25.93-14-8".
Do I have to install anything else like a boot.img? I made a full wipe..
Can I use the ElementalX Kernel?
Click to expand...
Click to collapse
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
ILLUSORYINK said:
How did you installed twrp can you help me out please i am stuck on ap fastboot flash mode (secure)
with no rom and no recovery can you please help me? how will i get out of this situation? Please!
Click to expand...
Click to collapse
How did you get into this state in the first place?
I see from your other post you installed AICP, so you must have TWRP on your device already?
If you need to re-flash TWRP, then boot your device to the bootloader.
Connect your device to your computer, preferably with the original USB cable.
Open the ADB terminal on your computer, and ensure you have the TWRP flashable image on your computer, in your ADB folder.
In the ADB terminal, type 'fastboot devices' without quotes, ensure you get a serial number response from your device.
If you get a response, then type 'fastboot flash recovery <name of TWRP image>' without quotes, where the <name of TWRP image> is the TWRP image file name as on your computer. Ensure the file name is the same, taking into account file name extensions.
You should have flashed TWRP to your recovery partition on your device - use the volume keys on your device to select 'Recovery' then press the power button to boot to recovery. You should be booting to TWRP recovery.
In there, you should be able to copy a custom ROM and flash that within TWRP. Alternatively, you could download a fastboot stock ROM and flash that within fastboot (not TWRP) to restore your device, but ensure it's the correct and latest stock ROM for your device.
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
sergioricardojsj said:
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
Click to expand...
Click to collapse
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
kudos1uk said:
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
Click to expand...
Click to collapse
I've done nothing. My bootloader is locked. Nothing is changed.
sergioricardojsj said:
I've done nothing. My bootloader is locked. Nothing is changed.
Click to expand...
Click to collapse
Looking at your previous posts that is clearly not the case, good luck.
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
sergioricardojsj said:
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
Click to expand...
Click to collapse
can you share the rom you flashed please
ccalixtro said:
can you share the rom you flashed please
Click to expand...
Click to collapse
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
thanks but i cant get into fastboot mode only blinking led.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
i have same problem, i was enable camera2 api for Gcam in my phone, by following tutorial in this forum, Using temporary twrp, unlock bootloader and lock back. And now i cant update with same problem in first post picture. Please someone give us solution for fix this. Thx
Sorry- ignore this message, wrong thread.
ltf_195 said:
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
Click to expand...
Click to collapse
You don't need to make any modifications, just mounting /system with rw in twrp will break ota.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Hola Sergio Ricardo, no entendí si es oem unlock o local y después los últimos pasos me perdí, podrías explicarlo en español?
sergioricardojsj said:
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Click to expand...
Click to collapse
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
barrack1 said:
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
Click to expand...
Click to collapse
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
hola,si quieres restaurar la imagen stock para actualizar,as recovery PERO NO EN TWRP y monta la imagen desde ahí, reinicia y listo yo estoy con parche de noviembre que acabo de actualizar y antes de eso tenía magisk con Gcam y mods de audio espero les sirva
Mod edit google translate added:
hello, if you want to restore the stock image to update, as recovery BUT NOT IN TWRP and mount the image from there, restart and ready I am with November patch that I just updated and before that I had magisk with Gcam and audio mods I hope serve them
try n flash original pie fastboot rom from here
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
rexendz said:
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
Click to expand...
Click to collapse
Having TWRP installed as the recovery and just booting into TWRP are 2 different things.
Hello,
Is anyone know how to install Unbranded (Unlock Version) firmware on Samsung Galaxy J7 Star (MetroPCS/T-Mobile) SM-J737T1 to SM-J737U?
I have tried this with J7 Prime SM-J727T1 with SM-J727U and it worked well but J7 Star failed with Odin flash.
SM-J737T J737TUVS3ARJ1
TO
SM-J737U J737UUES2ARK1
Click to expand...
Click to collapse
eManuka said:
Hello,
Is anyone know how to install Unbranded (Unlock Version) firmware on Samsung Galaxy J7 Star (MetroPCS/T-Mobile) SM-J737T1 to SM-J737U?
I have tried this with J7 Prime SM-J727T1 with SM-J727U and it worked well but J7 Star failed with Odin flash.
Click to expand...
Click to collapse
I am also looking for same solution. Please update if you succeeded. TIA
etool20 said:
I am also looking for same solution. Please update if you succeeded. TIA
Click to expand...
Click to collapse
I checked, with the new android update it is not possible for 2018 models.
Don't think the 2018 J7 is even exploitable/rootable yet. (waiting for it though)
interesting of this device has treble support
hello I used firmware combination J737T1UVU4ASB1 for j737t1, flash with miracle box and I see that I think OEM Unlock to enable it, I have not yet enabled.
now that it has combination I am thinking of converting j737t1 to j737u with OEM enabled I hope it works.
here is the capture: https://www.mediafire.com/folder/msm2fczpgcxgu/
Could I get you to please host J737T1UVU4ASB1 out there somewhere? I can't find that one anywhere.
You have to flash the combination file and then enable OEM and then flash the unbranded rom and then factory reset in that order
Raymond702 said:
You have to flash the combination file and then enable OEM and then flash the unbranded rom and then factory reset in that order
Click to expand...
Click to collapse
Did this work? Is it possible to root SM_J737T1?
Over a year later...any feedback from anyone?? Does this work or any other options to root the T1 variant?
I rooted my j737u by using a combo file to get OEM unlock, reflashed firmware, installed magisk, patched boot img I got from AP firmware, then used a tool called tar-tool to convert boot img back to tar.md5, then placed the boot.tar.md5 file in AP section of patched odin and it flashed just fine. Makes you factory reset but magisk is there when rebooted.
r1pp3d2 said:
Rooteé mi j737u usando un archivo combinado para obtener el desbloqueo OEM, actualicé el firmware, instalé magisk, parcheé la imagen de arranque que obtuve del firmware AP, luego usé una herramienta llamada tar-tool para convertir la imagen de arranque nuevamente a tar.md5, luego coloqué el archivo boot.tar.md5 en la sección AP de odin parcheado y brilló muy bien. Te hace restablecer los valores de fábrica, pero magisk está allí cuando se reinicia.
Click to expand...
Click to collapse
Hello, can you be more specific with the steps, the combination of roms is interesting
find your bootloader version combination file and put it in the AP slot in odin and flash it.
it should say factory binary when it boots up. go to settings and enable dev options and the OEM unlock should be able to be turned on. after turning OEM unlock on should turn OEM lock off.
after that you need to reflash your firmware in odin.
put magisk on the phone and I pulled the boot.img from the AP firmware with 7zip. use magisk to patch the boot.img. i found a tool on xda called tar-tool, which I used to put the patched boot.img into tar.md5 then flashed that boot.img in the AP slot of odin. you will have to factory reset after that flash, but magisk will be there when you're done setting your phone up. oh, and I used patched odin to do all the flashing. i hope this helps!
With this code that you enable, they gave it to me and they say that it solves that, activate debugging, put this code and that's it *#0808#
r1pp3d2 said:
I rooted my j737u by using a combo file to get OEM unlock, reflashed firmware, installed magisk, patched boot img I got from AP firmware, then used a tool called tar-tool to convert boot img back to tar.md5, then placed the boot.tar.md5 file in AP section of patched odin and it flashed just fine. Makes you factory reset but magisk is there when rebooted.
Click to expand...
Click to collapse
Where do you get these combination files for this?
X_shinobi.apk_X said:
Where do you get these combination files for this?
Click to expand...
Click to collapse
I believe I either got the combo file from easy-firmware or here.
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Lo siento por mi ingles. Tuve el mismo problema y lo resolví con comandos ADB. No recuerdo cómo. Estoy seguro de que tuve suerte ... Tal vez puedas intentarlo. Al menos, la PC debería leer el modo fastboot y comenzar a hacer algo.
I'm sorry for my English. I had the same problem and I solved it with ADB commands. I do not remember how. I'm sure I was lucky ... Maybe you can try it. At least, the PC should read fastboot mode and start doing something.
indian84 said:
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
Click to expand...
Click to collapse
I think I'll have to send it to OnePlus. But before that I would like to try to revive it. I can access fastboot, but the bootloader is locked, can I do something in fastboot or with the locked bootloader I'm out of luck?
Thanks.
Don't worry I understood you.
The problem is I can't access to adb because the stock recovery doesn't allow and I can't boot any custom recovery because my bootloader I locked.
Thanks.
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
ACB369 said:
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
Click to expand...
Click to collapse
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
amt911 said:
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
Click to expand...
Click to collapse
Try fastbooting the stock boot.img, follow the instructions below...
Reboot to Bootloader
Open up a command prompt in the folder with the boot.img
Enter the command
Code:
fastboot boot *insert boot.img name here*
Nothing, just wait for your phone to boot
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Is there any way that I could wipe everything in EDL mode? Is the only thing I think it could fix the phone.
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
amt911 said:
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
Click to expand...
Click to collapse
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
tech_head said:
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
Click to expand...
Click to collapse
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
amt911 said:
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Click to expand...
Click to collapse
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
amt911 said:
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
Click to expand...
Click to collapse
sometime flushing cache can solves this kind of issue.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
have you try "fastboot set_active other"
Click to expand...
Click to collapse
Yes, the same, because the bootloader is locked I can't do anything except "fastboot OEM unlock" which I can't use because I can't access os and I can't turn on oem unlocking.
Thanks.
vichao.s said:
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
sometime flushing cache can solves this kind of issue.
Click to expand...
Click to collapse
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
amt911 said:
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
Click to expand...
Click to collapse
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Mannan Qamar said:
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Click to expand...
Click to collapse
I tried that and it's still stuck on the boot animation, I think it's just a hardware problem because back then with my OnePlus 3T I did the same and it worked just fine. I contacted OnePlus and they accepted sending the phone to them. I'll see when they examine it what is their answer.
Thanks.
What I did to brick it was using this guide: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
And inside the manual flash section there are a lot of fastboot commands.
What I did was using only the fastboot ones and replacing "flash" to "erase" to delete every partition. After that I flashed the phone using msmdownloadtool right away. My question is: Could this be the cause that my phone is in bootloop?
Thanks.
Hello, my nokia 6 on oreo is actually stuck at the "Powered by android" screen after uninstalling Magisk, i can access to fastboot, so i can flash files, but my bootloader isn't unlocked and OST LA won't work and i don't know why, can someone help me ? I think i just need to flash a stock boot.img, but i can't.
Hello, i somehow managed to flash a stock boot.img, my phone is still stuck at the same screen, but it's now recognized by the pc (it wasn't before), can someone have an idea to help me ? Thanks.
Yakia said:
Hello, my nokia 6 on oreo is actually stuck at the "Powered by android" screen after uninstalling Magisk, i can access to fastboot, so i can flash files, but my bootloader isn't unlocked and OST LA won't work and i don't know why, can someone help me ? I think i just need to flash a stock boot.img, but i can't.
Click to expand...
Click to collapse
OST can flash Nokia phones if the bootloader is already unlocked.
I think you'll have to buy an unlocking key first. (on techmesto for example)
I can actually flash without OST LA, like I said, but normally flashing stock boot.img should have fixed the problem, but it's still stuck on the same screen.
Yakia said:
I can actually flash without OST LA, like I said, but normally flashing stock boot.img should have fixed the problem, but it's still stuck on the same screen.
Click to expand...
Click to collapse
Flash boot.img of stock rom and flash recovery.img of the same custom rom on which your phone is running maybe it would help you.
What are you talking about, I already flashed a stock boot.img, and my phone is not running on a custom rom...
Yakia said:
What are you talking about, I already flashed a stock boot.img, and my phone is not running on a custom rom...
Click to expand...
Click to collapse
I don't really understand how you installed magisk without recovery custom ?
I found this but I don't know if it works ^^
https://www.didgeridoohan.com/magisk/MagiskUninstallIssues
arl0ng said:
OST can flash Nokia phones if the bootloader is already unlocked.
I think you'll have to buy an unlocking key first. (on techmesto for example)
Click to expand...
Click to collapse
No you dont need an unlocked bootloader to flash with OST LA just make sure you flash with the older version as the newer version will hang but it works with my nokia 5 and the bootloader is locked
nintendobuster420 said:
No you dont need an unlocked bootloader to flash with OST LA just make sure you flash with the older version as the newer version will hang but it works with my nokia 5 and the bootloader is locked
Click to expand...
Click to collapse
yes but after i flashed stock boot.img i'm not able to boot in fastboot mode do you know how i can do that ?
arl0ng said:
I don't really understand how you installed magisk without recovery custom ?
I found this but I don't know if it works ^^
https://www.didgeridoohan.com/magisk/MagiskUninstallIssues
Click to expand...
Click to collapse
i did install magisk with the chinese twrp but uninstalled it from the magisk manager app and after uninstalling it it was just stuck at the powered by android screen
Yakia said:
yes but after i flashed stock boot.img i'm not able to boot in fastboot mode do you know how i can do that ?
Click to expand...
Click to collapse
Does your phone boot into EDL mode? If it boots to EDL mode then it could be fixable. If not then it could be hard bricked
nintendobuster420 said:
Does your phone boot into EDL mode? If it boots to EDL mode then it could be fixable. If not then it could be hard bricked
Click to expand...
Click to collapse
i don't think its on edl mode, how can i know that ? and how can my phone be hard bricked just because i just uninstalled magisk ? uninstalling magisk simply restore stock boot.img and remove root. and i don't think it would show a powered by android screen or a charging screen if it was hard bricked, and thanks for you help people by the way.
bump, i still have access to fastboot mode, so i can flash things, can someone help me please ?
Yakia said:
bump, i still have access to fastboot mode, so i can flash things, can someone help me please ?
Click to expand...
Click to collapse
Download Android nougat 7.1.1 nbo file from xda if your phone is able to enter in download mode connect it to pc via cable and hit on next button and flash firmware again
And if you flashed firmware successfully then always remember not to flash Chinese recovery again u should thanks to god , it's not hard bricked it's only soft bricked flash it through ost la tool patched ost for more you can search on search bar how to setup patched ost la
which ost la version do i need to use ? 6.1.2 or 6.0.4 ?
thank you for your answer btw.
Yakia said:
which ost la version do i need to use ? 6.1.2 or 6.0.4 ?
Click to expand...
Click to collapse
6.0.4 patched ost la
which nbo file do i have to use ? the one i'm using gives me this error : the update process failed, the software version of the updater is out of date please upgrade the updater and then try again
bump
Yakia said:
which nbo file do i have to use ? the one i'm using gives me this error : the update process failed, the software version of the updater is out of date please upgrade the updater and then try again
Click to expand...
Click to collapse
have you replaced the exe in windows drive:\program files (x86)\OST LA\ with the patched one