Related
Hey Guys,
So I got a very weird situation here, I have my XT925 from Telcel. Several months ago I unlocked the bootloader and started playing around with ROMs. All of them worked fine.
A couple of days ago I flashed the SFR ROM: SFR Vodafone France Version: 9.8.0Q-97-XT925_VQU-18 FULL.
The flash went fine I loaded the 4.1.1 JB and immediately got the OTA alert. Since I had already tested and succeded doing OTA with unlocked BL. I said fine let's do it. It downloaded the 50 MB or so. Restarted to the default recovery, since this was a brand new flash, no CWM yet. Started upgrading and at the middle of the whole thing disaster occured!
The phone restarted and it couldn't get pass the fastboot. I get "update gpt_main version failed" and "failed to hab check for gpt_backup: 0x35"
The weirdest thing of it all is that now the fastboot claims that my bootloader is locked! It went magically after trying to OTA from UNLOCKED to LOCKED!
So this is what's really killing me, I've tried flashing all different versions of Stock ROMs, all via RSD Lite 6.1.4. They all come back with error. I tried removing not only the getvar line but also the 2nd and 3rd line after it but nothing.
And one more thing I said if the device is suddenly locked why not trying to unlock it again, and the weird thing is that if I request the "get_unlock_data" via fastboot it will come back with "Could not get unlock data!"
So I'm completely lost! What can I do know????
Any help will be appreciated!
Flashes retail brasil. Me paso lo mismo. Hice lo mismo y me paso lo mismo. Flash la última retail brasil y se soluciona.
No hablo ingles. Perdón jaja
Enviado desde mi XT925 usando Tapatalk 2
Gracias!
Juanpa123 said:
Flashes retail brasil. Me paso lo mismo. Hice lo mismo y me paso lo mismo. Flash la última retail brasil y se soluciona.
No hablo ingles. Perdón jaja
Enviado desde mi XT925 usando Tapatalk 2
Click to expand...
Click to collapse
Gracias Juanpa!
Una pregunta, a ti también te paso que se bloqueó el bootloader al intentar actualizar la version SFR? Eso es lo mas raro que me pasó a mi. Antes del problema habia desbloqueado el bootloader y probado varias ROMs hasta la CM 10.1 y siempre me dejó hacerlo bien porque al encender me aparecía UNLOCKED el bootloader.
Ah y le borraste algo especial al XML de la ultima retail de la ROM de Brasil? O solo la linea getvar? Y que paso con tu bootloader una vez que reviviste el telefono? Te volvio a aparecer como UNLOCKED o como LOCKED?
Gracias!!
adolfovm said:
Gracias Juanpa!
Una pregunta, a ti también te paso que se bloqueó el bootloader al intentar actualizar la version SFR? Eso es lo mas raro que me pasó a mi. Antes del problema habia desbloqueado el bootloader y probado varias ROMs hasta la CM 10.1 y siempre me dejó hacerlo bien porque al encender me aparecía UNLOCKED el bootloader.
Ah y le borraste algo especial al XML de la ultima retail de la ROM de Brasil? O solo la linea getvar? Y que paso con tu bootloader una vez que reviviste el telefono? Te volvio a aparecer como UNLOCKED o como LOCKED?
Gracias!!
Click to expand...
Click to collapse
Si si. Yo tmb había probado un montón y cuando instale de nuevo a 4.1.1 y actualice por ota lo bloqueo al boot.
Flashea por fastboot la última retail brasil y ami me lo soluciono de una. Para mi es porq no te deja hacer dowgrade a ninguna versión por el boot bloqueado y Tmp usar un software q no sea latam. Proba con cualquiera q tenga un kernel más nuevo. Lo mejor si es totalmente nuevo. Y si me aparece la palabra un lock y ya probé distintos rom de nuevo
Saludos
Enviado desde mi XT925 usando Tapatalk 2
Juanpa123 said:
Si si. Yo tmb había probado un montón y cuando instale de nuevo a 4.1.1 y actualice por ota lo bloqueo al boot.
Flashea por fastboot la última retail brasil y ami me lo soluciono de una. Para mi es porq no te deja hacer dowgrade a ninguna versión por el boot bloqueado y Tmp usar un software q no sea latam. Proba con cualquiera q tenga un kernel más nuevo. Lo mejor si es totalmente nuevo. Y si me aparece la palabra un lock y ya probé distintos rom de nuevo
Saludos
Enviado desde mi XT925 usando Tapatalk 2
Click to expand...
Click to collapse
Wow! Ya lo probé y listo, mi Razr HD ha revivido!!! :victory:
Gracias por el apoyo Juanpa!!!! Me había quedado tan impresionado con el locked en el bootloader que pensé estaba perdido! Tan fácil que era como descargar la versión mas reciente para que funcionara! No sabes cuantas versiones probé y nada... pero ahora que lo pienso todas las que probé eran más viejas que el OTA, seguramente se quedo a medias el upgrade y ya no iba a tomar ninguna excepto la más nueva!
De nuevo mil gracias! Eres un master!
SOLVED! Quick summary
Here's a quick summary for you non spanish readers!
So it seems that during the OTA the upgrade failed and due to this my bootloader appeared as LOCKED. So this meant that I had to treat my RAZR HD as locked, and flash a newer full version.
So I downloaded the latest Retail BR as suggested by juanpa123, thanks again man!
With the latest retail BR zip and RSD Lite 6.1.4 at hand I removed the "getvar" line from the XML, flashed and boom! Retail version flashed without issues! :victory:
Also once restored I went back into fastboot and my bootloader is again showing up as UNLOCKED. I already reflashed CWM through fastboot just fine!
Same problem... no solution.
Hi there! I came to this post after facing the same issue you guys described. My phone is locked in fastboot screen, showing that the device is locked. I've downloaded the latest firmware from Brasil (Vivo) and tried to flash it using RSD 6.1.4, but it is showing the following error on the screen:
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
... aaaaand, I'm stuck at this point. Apparently I've downloaded the correct version of the firmware for my XT925, but it simply doesn't flash! Any ideas of what I could do?
I'd appreciate any kind of help.
Thanks in advance! :fingers-crossed:
Hey playmolego,
So I can see you have the same issue I had. The problem is you tried to OTA, so now your phone base version is the OTA one, not the latest Brasil vivo one. My advice to you is to download the latest one you can find from the LATAM region. Wether it's Mexico, Brazil or other and hope it's the same or newer as the OTA that failed.
By the way the Vivo you tried to flash failed because it's older than the OTA that failed, therefore it's considered a downgrade, which a locked bootloader will not allow.
So a newer or same version is a must.
Give the Retail Brasil a try:
Branding: Retail Brasil
Version: 9.8.2Q-50-XT925_VQLM-21 FULL
From the Jelly Bean Firmwares thread.
Hopefully you'll find one. Best of luck!
A small improvement
Hey there! Thanks!
I noticed my lazy attempt while re-reading the topic... tee-hee. So I downloaded the correct version (4.1.2 - JB) for Brasil Vivo... and at this moment, I am desperately waiting for RSD to finish the flashing process, but it it stuck for more than one hour on 17/19 flash cdrom "cdrom_signed". The other phases didn't take this long, so I am getting a little bit concerned about what might happen... Any clues on why is it taking soooo long? :T What else could I do?
Thanks in advance!
adolfovm said:
Hey playmolego,
So I can see you have the same issue I had. The problem is you tried to OTA, so now your phone base version is the OTA one, not the latest Brasil Vivo one (9.8.2Q-50-XT925_VQLM-21 FULL). My advice to you is to download the latest one you can find from the LATAM region. Wether it's Mexico, Brazil or other and hope it's the same or newer as the OTA that failed.
By the way the Vivo you tried to flash failed because it's older than the OTA that failed, therefore it's considered a downgrade, which a locked bootloader will not allow.
So a newer or same version is a must.
Give the Retail Brasil a try:
Branding: Retail Brasil
Version: 9.8.2Q-50-XT925_VQLM-21 FULL
From the Jelly Bean Firmwares thread.
Hopefully you'll find one. Best of luck!
Click to expand...
Click to collapse
That's a lot of time indeed!
You could leave it some more time to see if it finishes. I'm not sure what could happen if you force restart the phone. In the meantime I recommend you to download the latest Jelly Bean "Brazil Retail" the one I mentioned on my previous post. It's a bit newer than the Vivo one and it might flash better if the Vivo fails.
playmolego said:
Hey there! Thanks!
I noticed my lazy attempt while re-reading the topic... tee-hee. So I downloaded the correct version (4.1.2 - JB) for Brasil Vivo... and at this moment, I am desperately waiting for RSD to finish the flashing process, but it it stuck for more than one hour on 17/19 flash cdrom "cdrom_signed". The other phases didn't take this long, so I am getting a little bit concerned about what might happen... Any clues on why is it taking soooo long? :T What else could I do?
Thanks in advance!
Click to expand...
Click to collapse
SOLVED!
So... I held my breath and unplugged the device after 2 hours stuck in the same stage. The phone rebooted and... ta-da! It was healthy again, running the OEM 4.1.2 JB from my carrier. :good:
Maybe it was luck... but at least I've got my Razr HD back (well, to sell it... actually... tee-hee).
Thanks for all the help!
Hi.
I have the same issue, let me tell you my history:
Motorola RAZR HD XT925 Telcel
it was bootloader locked, I unlocked from the Motorola website with the code that it was shown, so it is was bootloader unlocked.
I installed the lastest OEM JB from Brazil, it was working fine, it restarted and I had to configure it again, but suddenly there was an update message so I downloaded it, it rebooted and locked the bootloader again.
I cannot access to the Fastboot menu, normal mode, recovery, and all the menu that appears when the three botton reboot is done.
It says that Device is LOCKED, again, it was unlocked before I installed the brazilian firmware, after OTA update, it was locked again.
I have tried to unlock again the bootloader with the same tool, Motorola ha... 4.0 I do not remember the name exactly.
Batery OK
but the message appears
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup
failed to load gpt
CDI Read failure
Fastboot reason Invalid GPT
I have tried to install again the last firmware from Brazil, it was not successful
Also tried to install America Movil 4.1.2, does not work
I am not able to do anything right now.
Does anyone have any idea what should I do?
Thanks!
Hi, so yes your case is the same as ours. The only problem I can see is that you had already flashed the latest JB version available on the Pzyduck thread. The problem with this is that it's obvious that the OTA you downloaded and tried to flash is newer than the newest version on the Jelly Bean thread.
So this means that all the versions available on that thread are older than the OTA that failed, so you won't be able to flash them properly. Your only option is to flash the full version that corresponded to your OTA. Unfortunately I don't know were you can get this. Maybe you can try to contact "Pzyduck" from the JB Firmware threads. He could be of help with a newer version that could work for you.
Another chance is to flash one of the newer european versions, the ones that are V26 or V27 from the thread though I'm unsure if those will flash on a "locked" bootloader from LATAM.
djzothka said:
Hi.
I have the same issue, let me tell you my history:
Motorola RAZR HD XT925 Telcel
it was bootloader locked, I unlocked from the Motorola website with the code that it was shown, so it is was bootloader unlocked.
I installed the lastest OEM JB from Brazil, it was working fine, it restarted and I had to configure it again, but suddenly there was an update message so I downloaded it, it rebooted and locked the bootloader again.
I cannot access to the Fastboot menu, normal mode, recovery, and all the menu that appears when the three botton reboot is done.
It says that Device is LOCKED, again, it was unlocked before I installed the brazilian firmware, after OTA update, it was locked again.
I have tried to unlock again the bootloader with the same tool, Motorola ha... 4.0 I do not remember the name exactly.
Batery OK
but the message appears
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup
failed to load gpt
CDI Read failure
Fastboot reason Invalid GPT
I have tried to install again the last firmware from Brazil, it was not successful
Also tried to install America Movil 4.1.2, does not work
I am not able to do anything right now.
Does anyone have any idea what should I do?
Thanks!
Click to expand...
Click to collapse
Have you found any solution ?
Same issue here, been searching and trying for solutions. No luck so far...
Did ya have any progress???
djzothka said:
Hi.
I have the same issue, let me tell you my history:
Motorola RAZR HD XT925 Telcel
it was bootloader locked, I unlocked from the Motorola website with the code that it was shown, so it is was bootloader unlocked.
I installed the lastest OEM JB from Brazil, it was working fine, it restarted and I had to configure it again, but suddenly there was an update message so I downloaded it, it rebooted and locked the bootloader again.
I cannot access to the Fastboot menu, normal mode, recovery, and all the menu that appears when the three botton reboot is done.
It says that Device is LOCKED, again, it was unlocked before I installed the brazilian firmware, after OTA update, it was locked again.
I have tried to unlock again the bootloader with the same tool, Motorola ha... 4.0 I do not remember the name exactly.
Batery OK
but the message appears
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup
failed to load gpt
CDI Read failure
Fastboot reason Invalid GPT
I have tried to install again the last firmware from Brazil, it was not successful
Also tried to install America Movil 4.1.2, does not work
I am not able to do anything right now.
Does anyone have any idea what should I do?
Thanks!
Click to expand...
Click to collapse
same problem here
I have the same problem here, i will try with this one
Claro Puerto Rico 9.8.2Q-50-XT925_VQLM-24_AmericaMovil_PR_SIGNED_S12_USAVANQUCLAPRLA020.0R_VANQJBCLAPRLA_P008_A010_S1FF_CFC_fb.xml.zip
Hope this works, this is the last one i can try... any other firmware is older than everthing i check...
Solved
hi, I just want to confirm that, i solved this problem flashing with this more recent firmware
Claro Puerto Rico 9.8.2Q-50-XT925_VQLM-24_AmericaMovil_PR_SIGNED_S12_USAVANQUCLAPRLA020.0 R_VANQJBCLAPRLA_P008_A010_S1FF_CFC_fb.xml.zip
If you have unlocked bootloader for nothing try an ota update.
---------- Post added at 06:53 AM ---------- Previous post was at 06:43 AM ----------
cha_niembro said:
Same issue here, been searching and trying for solutions. No luck so far...
Did ya have any progress???
Click to expand...
Click to collapse
Try this one
Claro Puerto Rico 9.8.2Q-50-XT925_VQLM-24_AmericaMovil_PR_SIGNED_S12_USAVANQUCLAPRLA020.0 R_VANQJBCLAPRLA_P008_A010_S1FF_CFC_fb.xml.zip
It worked for my HD, same problem. Regards!
You Can Download it from sbf.droid- developers org google it, XDA dont letme paste the link
I have the same problem, United States (Verizon), developer edition (xt926). There was an OTA about 4 days ago (11-5-2012) that has bricked my device. I'm looking for this new firmware, but it seems to be too new.
I can try going to Verizon, since they'd have access to the firmware, but what a nightmare.
it works for me flashing the CLARO PR firmware
Flashed KK OTA now bricked
Can't seem to find any .sbf newer or equal the 4.4.2 OTA that bricked my device.
Any hints?
I have the original OTA file for my region (Brazil) but I can't flash it with RSD lite. Anybody found rsd lite flashable for 4.4.2?
Thanks
ricpf said:
Can't seem to find any .sbf newer or equal the 4.4.2 OTA that bricked my device.
Any hints?
I have the original OTA file for my region (Brazil) but I can't flash it with RSD lite. Anybody found rsd lite flashable for 4.4.2?
Thanks
Click to expand...
Click to collapse
im in the same stage cant flash any firm due to 4.4.2 base, what does the RSD says? could you please share your OTA
- I Entered Fastboot Mode
- Checked Bootloader And Says:
STATUS Unlocked: Status Code 3
Does this mean the bootloader is not unlocked properly? Or am I just being paranoid? Please leave a reply if anyone has any idea what this is!
I have the 41.18 bootloader and mine says:
Device is UNLOCKED. Status Code: 3
Don't worry. You've unlocked BL properly.
tengo un moto e y dice device is unlocked status code 3 que es y como puedo solucionarlo alguien puede ayudarme
tonyluis said:
tengo un moto e y dice device is unlocked status code 3 que es y como puedo solucionarlo alguien puede ayudarme
Click to expand...
Click to collapse
Primero, este foro es en ingles, si no sabes puedes usar el Traductor de Google. Dicho esto, "Device is Unlocked Status Code 3" aparece despues de desbloquear el bootloader, es normal. Code 0 es bootloader bloqueado, Code 3 es bootloader desbloqueado.
Finalmente, estas escribiendo en el foro de Moto G, te recomiendo usar mejor el foro dedicado al Moto E:
Motorola Moto E - XDA
Tienes algun problema?
First of all, this an english-based forum, if you don't know english you can use Google Translate. That said, "Device is unlocked status code 3" appears after unlocking the bootloader, is normal. Code 0 means locked bootloader, Code 3 means unlocked bootloader.
Finally, you're posting on Moto G forum, I recommend you use insted the forum dedicated to Moto E:
Motorola Moto E - XDA
Do you have any problem?
Hello friends, (Sorry for my English)
This is the first time I write, but, I'm afraid. I tell you:
I have bootloader and FPR unlocked, my original rom was NXT-L09AC69B105CUSTC69D004, I did flash with NXT-L09C605B131 (C900B120 cust), then I did flash with NXT-L09C605B131, then I did flash with NXT-L09C605B580, I finally did flash with NXT-L09C605B585 , In the end I stayed with nougat.
I did root with twrp-3.1.1-1-next and install superuser_noverify.zip and phh s SuperUser_v1.0.3.3.apk, so far so good, but ..... I wanted to use snapchat and hide root with magisk, then uninstall Phh s SuperUser_v1.0.3.3.apk, I made flash with Magisk-v12.0.zip, this causes bootloop.
Perform ROLLBACK via dload 5.0 to 4.0 (NXT-L09C900B500), all ok, and instead of doing dload NXT-L09AC212B120CUSTC212D002 (Unbrick), I did the nonsense to dload with NXT-L09AC69B105CUSTC69D004 / update.app, this caused me a brick totally.
Now my mate 8 does not turn on (power on), the screen always goes black, any command in adb gives FAILED (remote: command not allowed) error, the computer recognizes the smartphone as Android phone / Android Sooner Single ADB interface. Reviewing in ADB the OEM tells me fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). In ADB I can close and open the bootloader without problem, but the other commands do not work.
Please, help me, I can not restore my mate 8, is it that I already have a brick forever?
Many thanks and, again, sorry for my English, I only speak Spanish and I use Google translator.
"In Spanish"
Hola amigos, (Lo siento por mi inglés)
Es la primera vez que escribo, pero, tengo miedo. Les cuento:
Yo tengo bootloader y FPR desbloqueado, mi rom original era NXT-L09AC69B105CUSTC69D004, hice flash con NXT-L09C605B131 (C900B120 cust), despues hice flash con NXT-L09C605B131, luego hice flash con NXT-L09C605B580, al final hice flash con NXT-L09C605B585, al final me quede con nougat.
Hice root con twrp-3.1.1-1-next e instale superuser_noverify.zip y phh s SuperUser_v1.0.3.3.apk, hasta aqui todo bien, pero.....queria usar snapchat y ocultar root con magisk, entonces desinstale phh s SuperUser_v1.0.3.3.apk, hice flash con Magisk-v12.0.zip, esto ocasiono bootloop.
Realice ROLLBACK mediante dload 5.0 a 4.0 (NXT-L09C900B500), todo ok, y en lugar de hacer mediante dload NXT-L09AC212B120CUSTC212D002 (Unbrick), hice la tonteria de hacer dload con update.app de NXT-L09AC69B105CUSTC69D004, esto me ocasiono un brick total.
Ahora mi mate 8 no enciende, la pantalla siempre se queda en negro, cualquier comando en adb da el error FAILED (remote: command not allowed), la computadora si reconoce el smartphone como Android phone / Android Sooner Single ADB interface. Revisando en ADB la OEM me dice fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). En ADB puedo cerrar y abrir el bootloader sin problema, pero los demas comandos no funcionan.
Por favor, ayudenme, no puedo restaurar mi mate 8, sera acaso que ya tengo un ladrillo para siempre?
Muchas gracias y, nuevamente, disculpen mi ingles, yo solo hablo español y uso traductor de Google.
enriquebunbury666 said:
Hello friends, (Sorry for my English)
This is the first time I write, but, I'm afraid. I tell you:
I have bootloader and FPR unlocked, my original rom was NXT-L09AC69B105CUSTC69D004, I did flash with NXT-L09C605B131 (C900B120 cust), then I did flash with NXT-L09C605B131, then I did flash with NXT-L09C605B580, I finally did flash with NXT-L09C605B585 , In the end I stayed with nougat.
I did root with twrp-3.1.1-1-next and install superuser_noverify.zip and phh s SuperUser_v1.0.3.3.apk, so far so good, but ..... I wanted to use snapchat and hide root with magisk, then uninstall Phh s SuperUser_v1.0.3.3.apk, I made flash with Magisk-v12.0.zip, this causes bootloop.
Perform ROLLBACK via dload 5.0 to 4.0 (NXT-L09C900B500), all ok, and instead of doing dload NXT-L09AC212B120CUSTC212D002 (Unbrick), I did the nonsense to dload with NXT-L09AC69B105CUSTC69D004 / update.app, this caused me a brick totally.
Now my mate 8 does not turn on (power on), the screen always goes black, any command in adb gives FAILED (remote: command not allowed) error, the computer recognizes the smartphone as Android phone / Android Sooner Single ADB interface. Reviewing in ADB the OEM tells me fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). In ADB I can close and open the bootloader without problem, but the other commands do not work.
Please, help me, I can not restore my mate 8, is it that I already have a brick forever?
Many thanks and, again, sorry for my English, I only speak Spanish and I use Google translator.
"In Spanish"
Hola amigos, (Lo siento por mi inglés)
Es la primera vez que escribo, pero, tengo miedo. Les cuento:
Yo tengo bootloader y FPR desbloqueado, mi rom original era NXT-L09AC69B105CUSTC69D004, hice flash con NXT-L09C605B131 (C900B120 cust), despues hice flash con NXT-L09C605B131, luego hice flash con NXT-L09C605B580, al final hice flash con NXT-L09C605B585, al final me quede con nougat.
Hice root con twrp-3.1.1-1-next e instale superuser_noverify.zip y phh s SuperUser_v1.0.3.3.apk, hasta aqui todo bien, pero.....queria usar snapchat y ocultar root con magisk, entonces desinstale phh s SuperUser_v1.0.3.3.apk, hice flash con Magisk-v12.0.zip, esto ocasiono bootloop.
Realice ROLLBACK mediante dload 5.0 a 4.0 (NXT-L09C900B500), todo ok, y en lugar de hacer mediante dload NXT-L09AC212B120CUSTC212D002 (Unbrick), hice la tonteria de hacer dload con update.app de NXT-L09AC69B105CUSTC69D004, esto me ocasiono un brick total.
Ahora mi mate 8 no enciende, la pantalla siempre se queda en negro, cualquier comando en adb da el error FAILED (remote: command not allowed), la computadora si reconoce el smartphone como Android phone / Android Sooner Single ADB interface. Revisando en ADB la OEM me dice fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). En ADB puedo cerrar y abrir el bootloader sin problema, pero los demas comandos no funcionan.
Por favor, ayudenme, no puedo restaurar mi mate 8, sera acaso que ya tengo un ladrillo para siempre?
Muchas gracias y, nuevamente, disculpen mi ingles, yo solo hablo español y uso traductor de Google.
Click to expand...
Click to collapse
U can use Dc Phoenix to unbrick your phone if u can enter fastboot.
If Method 1 does not work try Method 2.
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Sent from my LON-L29 using XDA Labs
Mostar088 said:
U can use Dc Phoenix to unbrick your phone if u can enter fastboot.
If Method 1 does not work try Method 2.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
Thanks for your answer, just a few questions:
It is a requisite 15 credits, right?
No matter that the screen is not seen, ¡¡¡my screen always black!!!:crying::crying::crying:, the process will restore my smarthphone?
In this case. Which rom is right? I downloaded:
NXT-L09AC69B105CUSTC69D004 (Official Telcel) - (72703 and 72708)
NXT-L09AC212B120CUSTC212D002 (76065)
NXT-L09C605B131 (65032)
NXT-L09C605B580 (75932)
It is best to flash with the original (NXT-L09AC69B105CUSTC69D004 (Official Telcel)) to leave it as factory, right?
enriquebunbury666 said:
Thanks for your answer, just a few questions:
It is a requisite 15 credits, right?
No matter that the screen is not seen, ¡¡¡my screen always black!!!:crying::crying::crying:, the process will restore my smarthphone?
In this case. Which rom is right? I downloaded:
NXT-L09AC69B105CUSTC69D004 (Official Telcel) - (72703 and 72708)
NXT-L09AC212B120CUSTC212D002 (76065)
NXT-L09C605B131 (65032)
NXT-L09C605B580 (75932)
It is best to flash with the original (NXT-L09AC69B105CUSTC69D004 (Official Telcel)) to leave it as factory, right?
Click to expand...
Click to collapse
First i need to know can u enter fastboot mode on the phone?
Yes it cost 15 credit and u can use it for 72 hour, u should try with your Original firmware AC69 if it fail test C605.
Sent from my LON-L29 using XDA Labs
Mostar088 said:
First i need to know can u enter fastboot mode on the phone?
Yes it cost 15 credit and u can use it for 72 hour, u should try with your Original firmware AC69 if it fail test C605.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
I can not see anything on the phone. When I connect the phone, the PC shows Android phone / Android Sooner Single ADB interface and another PC shows TP-LINK Android Phone / Android Bootloader Interface. I can not upload images, but that shows.
If I can, I will install the C605 update.app.
Hola tengo el mismo modelo la cosa que haciendo no se que el teléfono me quedó vacío en blanco sistema operativo y no logro instalar nada que puedo hacer logro entrar en fastboot logro cargar un twrp pero al instalar son todos errores
My Dual sim Moto G3 hasn't any OS and I can't enter Recovery, there's only the Warning! Bootloader Unlocked message that has been there since I root my phone.
Todo este problema se desarrollo cuando estaba intentaba instalar una nueva rom, pero de casualidad borré el OS desde el Recovery y a la hora de bootearlo se estancó en la advertencia del Bootloader.
Everything started today when I was tryng to install a new custom rom, but I accidentally delete the OS from the Recovery menu and when I tried to boot it y got stuck in the Bootloader Warning
Help me pls
Important :
This will void warranty.
* I am not responsible for bricked devices, dead SD cards,or lost your Ferrari
* thermonuclear war, or you getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* as of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
* (hope in future we can get it working on tripped knox device)
* OTA likely won't work once you root device.
Click to expand...
Click to collapse
How to root your A307gn?
1 - Enable developer option
(by head on Setting/About phone/Software information and hit build number 7 times)
2 - Go back and look at Developper option
3 - Enable usb debugging
3 - Enable OEM Unlock
4 - Boot into download mode and follow intruction to unlock bootloader
5 - Flash the ROOT_boot.img with odin via AP tab button
6- Boot into system and install magisk manager
Please report because im stuck on MDM lock and cant find developper option
Is it good for the SM-A307G?
RAFRIKY said:
Is it good for the SM-A307G?
Click to expand...
Click to collapse
Alguien lo a comprobado?
Has anyone checked it?
Gustavo Lopez said:
Alguien lo a comprobado?
Has anyone checked it?
Click to expand...
Click to collapse
al parecer no
Does it work on a307fn
abuamr said:
Does it work on a307fn
Click to expand...
Click to collapse
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
RAFRIKY said:
Is it good for the SM-A307G?
Click to expand...
Click to collapse
I believe the firmware is different, so it wouldn't work.
You can download the boot image of your firmware then patch it with Magisk and flash it.
It did not work on my a307fn, had to re-flash stock firmware.
mine is the A307GT, should the magisk patching method work? i mean, is this how we get to root samsung phones?
Jerry8538 said:
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
Click to expand...
Click to collapse
Where can I find its boot img
Gustavo Lopez said:
Alguien lo a comprobado?
Has anyone checked it?
Click to expand...
Click to collapse
hola , yo lo comprobe y el root funciona perfecto en mi sm-a307g PERO hay un problema , una vez rooteado mi celular no detecta mi tarjeta SIM, repeti el proceso de root varias veces y siempre el mismo resultado , no entiendo a donde puede estar la causa de este problema ,
Aleale384 said:
hola , yo lo comprobe y el root funciona perfecto en mi sm-a307g PERO hay un problema , una vez rooteado mi celular no detecta mi tarjeta SIM, repeti el proceso de root varias veces y siempre el mismo resultado , no entiendo a donde puede estar la causa de este problema ,
Click to expand...
Click to collapse
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Gustavo Lopez said:
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Click to expand...
Click to collapse
hola, el IMEI esta perfecto , wifi tambien , solo que no detecta la SIM y en ocaciones se paso a modo avion AUTOMATICAMENTE, no entiendo por que ,.
con respecto al root , no tuve problemas , elimine varias app con LUCKY PATCHER , instale el modulo de VIPER4ANDROID sin problemas .
alguien sabe donde conseguir el chimera tool crack para poder repara imei , gracias ???
not working with samsung a307f android 9
please post root file for this model
You can always ROOT by patching the AP partition, as @Jerry8538 pointed earlier. If you see it as Un-successfull, after the procedure, try the following. Power Off the phone. Keep pressing VolUP+Power, and when appears the first screen, unpress both buttons. In this case phone shouldstart with ROOT Enabled. If you do a normal resart from mobile's menu, it will boot without ROOT. you need to restart it from inside the Magisk (from module). The problem i have (with both 20.3 & 20.4) is that also with these versions, mobile is losing SIM Cards (and quite possibly worsens much the GPS), i Have circles in the place of signal strength, os i need to reboot it normal to restart "un-Root", actually i'd call it a "Root-On-Demand"
Apologise..
Now i noticed that in Spanish Above is reported already the problem with the SIM
abuamr said:
Does it work on a307fn
Click to expand...
Click to collapse
Jerry8538 said:
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
I believe the firmware is different, so it wouldn't work.
You can download the boot image of your firmware then patch it with Magisk and flash it.
Click to expand...
Click to collapse
Terrandroid said:
It did not work on my a307fn, had to re-flash stock firmware.
Click to expand...
Click to collapse
technocaretricks said:
not working with samsung a307f android 9
please post root file for this model
Click to expand...
Click to collapse
@Jerry8538 , @papatsonis , @technocaretricks
is there anyone who has successfully rooted the SM-A307FN?
papatsonis said:
You can always ROOT by patching the AP partition, as @Jerry8538 pointed earlier. If you see it as Un-successfull, after the procedure, try the following. Power Off the phone. Keep pressing VolUP+Power, and when appears the first screen, unpress both buttons. In this case phone shouldstart with ROOT Enabled. If you do a normal resart from mobile's menu, it will boot without ROOT. you need to restart it from inside the Magisk (from module). The problem i have (with both 20.3 & 20.4) is that also with these versions, mobile is losing SIM Cards (and quite possibly worsens much the GPS), i Have circles in the place of signal strength, os i need to reboot it normal to restart "un-Root", actually i'd call it a "Root-On-Demand"
Apologise..
Now i noticed that in Spanish Above is reported already the problem with the SIM
Click to expand...
Click to collapse
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
will this work for the SM-A307G ?
Will this method work for android 10 ?
nelikp said:
How to root your A307gn?
1 - Enable developer option
(by head on Setting/About phone/Software information and hit build number 7 times)
2 - Go back and look at Developper option
3 - Enable usb debugging
3 - Enable OEM Unlock
4 - Boot into download mode and follow intruction to unlock bootloader
5 - Flash the ROOT_boot.img with odin via AP tab button
6- Boot into system and install magisk manager
Please report because im stuck on MDM lock and cant find developper option
Click to expand...
Click to collapse
Hi bro. Im new member here.
I have rooted phone with this method on android 10 a307gdxU4BTD1. I hope one of you will arrange new thread for rooting a30s with android 10. If you want boot.img patched, here the file:
https://www.dropbox.com/s/9auy9qcwiw70z1c/magisk_patched.tar?dl=0
Tanks you dev... :fingers-crossed:
---------- Post added at 05:26 PM ---------- Previous post was at 05:23 PM ----------
Xmaster111 said:
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
Click to expand...
Click to collapse
You can extract em with 7zip bro
---------- Post added at 05:26 PM ---------- Previous post was at 05:26 PM ----------
Xmaster111 said:
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
Click to expand...
Click to collapse
You can extract em with 7zip bro
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
Gustavo Lopez said:
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Click to expand...
Click to collapse
I dont understand, but if you want efs backup, nvram, radio image or stock recovery of a30s i can give you bro.