Related
Hello ,
first of all i am a noob at this kind of things but i really wanted to try out the 4.3 android.
while i asked some people and told me to flash via odin as the previous firmwares, it stuck? i dont know what happened, and now my phone says
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only thing that is working is the Volume Down+Home+Power button to get to the download mode, there it says :
KNOX WARRANTY VOID:1
AP SWREV: A2
i dont know what these are and i know i shouldn't have done something like this because i am a noob and now i am paying for my mistakes, i beg you help me my phone doesnt even start.
One more thing, i read to flash the stock firmware via odin but i tried it and it stuck at NAND write start, nothing happens after that.
I am so sorry for being totally useless but i need desperately your help,
thanks
install new firmware
you shuold install only new firmware (rom) try to follow phonix rom instalation. there is an explanation to downgrade.
can you please be more specific?
thanks for your answer
JasonTik said:
Hello ,
first of all i am a noob at this kind of things but i really wanted to try out the 4.3 android.
while i asked some people and told me to flash via odin as the previous firmwares, it stuck? i dont know what happened, and now my phone says
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
The only thing that is working is the Volume Down+Home+Power button to get to the download mode, there it says :
KNOX WARRANTY VOID:1
AP SWREV: A2
i dont know what these are and i know i shouldn't have done something like this because i am a noob and now i am paying for my mistakes, i beg you help me my phone doesnt even start.
One more thing, i read to flash the stock firmware via odin but i tried it and it stuck at NAND write start, nothing happens after that.
I am so sorry for being totally useless but i need desperately your help,
thanks
Click to expand...
Click to collapse
uninstall all samsung drivers,kies and other phone drivers if any,restart pc
install the samsung drivers only http://d-h.st/a7H
download odin 3.09 attached
download the rom mk4 knox free http://forum.xda-developers.com/showthread.php?t=2531989
or odex dmg here my favourite to come out of trouble http://d-h.st/s9I
open odin as admin and disable antivirus if any now browse to the rom.tar file
now put your phone in download mode and now connect usb to phone then to pc in diffrent port best to the back port of pc ,it will install some drivers let it happen and then odin will detect your phone
now click start in odin.
if any error post the screen here of odin
shhbz said:
uninstall all samsung drivers,kies and other phone drivers if any,restart pc
install the samsung drivers only http://d-h.st/a7H
download odin 3.09 attached
download the rom mk4 knox free http://forum.xda-developers.com/showthread.php?t=2531989
or odex dmg here my favourite to come out of trouble http://d-h.st/s9I
open odin as admin and disable antivirus if any now browse to the rom.tar file
now put your phone in download mode and now connect usb to phone then to pc in diffrent port best to the back port of pc ,it will install some drivers let it happen and then odin will detect your phone
now click start in odin.
if any error post the screen here of odin
Click to expand...
Click to collapse
thank you, it worked , sort of
i tried that but the odin failed, then i looked up and found something about Philz Recovery, i flashed it, wiped out cache/ factory reset and then i booted into download mode and did what you said and it worked now works perfectly, thanks
JasonTik said:
thank you, it worked , sort of
i tried that but the odin failed, then i looked up and found something about Philz Recovery, i flashed it, wiped out cache/ factory reset and then i booted into download mode and did what you said and it worked now works perfectly, thanks
Click to expand...
Click to collapse
Please help me. I have the same situation, but could not do so as it is written
I've done Philz Recovery. I do AP_N7100XXUEMK4J9.tar.md5 installing Odin but phone will not turn on, it stays on the Samsung label
levanimas said:
Please help me. I have the same situation, but could not do so as it is written
I've done Philz Recovery. I do AP_N7100XXUEMK4J9.tar.md5 installing Odin but phone will not turn on, it stays on the Samsung label
Click to expand...
Click to collapse
Try pressing volume up home button and power button in the same time to enter recovery mode , there factory reset and wipe cache and your phone should boot.
Fygaroo said:
Try pressing volume up home button and power button in the same time to enter recovery mode , there factory reset and wipe cache and your phone should boot.
Click to expand...
Click to collapse
It's all been done. The phone does not turn on, it stays on the Samsung label
JasonTik said:
thank you, it worked , sort of
i tried that but the odin failed, then i looked up and found something about Philz Recovery, i flashed it, wiped out cache/ factory reset and then i booted into download mode and did what you said and it worked now works perfectly, thanks
Click to expand...
Click to collapse
Good that it works!
"i dont know what these are and i know i shouldn't have done something "
These I don't know sentences are not gonna earn any respect to you here. And for god's sake do not repeat these mistakes. Follow the XDA's most important rule : Search and Read the existing posts before you do something.
Need Help too.....Urgent
I am on stock 4.3 rom
Product Code: INU
PDA: N7100XXUEMK4
CSC: N7100ODDEMK1
MODEM: N7100DDEMJ9
I rooted my phone and stuck with knox .. I really want to get rid of knox and to downgrade to 4.1.2...
I saw somewhere that it is impossible to downgrade.... pls help me out
i really need help and if it is possible to downgrade tell me how
Is there anyone had the same problem and sorted that out....
ashishdelhi21 said:
I am on stock 4.3 rom
Product Code: INU
PDA: N7100XXUEMK4
CSC: N7100ODDEMK1
MODEM: N7100DDEMJ9
I rooted my phone and stuck with knox .. I really want to get rid of knox and to downgrade to 4.1.2...
I saw somewhere that it is impossible to downgrade.... pls help me out
i really need help and if it is possible to downgrade tell me how
Is there anyone had the same problem and sorted that out....
Click to expand...
Click to collapse
it is impossible to downgrade..you already know it mate.
I got the same issue right now. And have also voided warranty
shhbz said:
uninstall all samsung drivers,kies and other phone drivers if any,restart pc
install the samsung drivers only http://d-h.st/a7H
download odin 3.09 attached
download the rom mk4 knox free http://forum.xda-developers.com/showthread.php?t=2531989
or odex dmg here my favourite to come out of trouble http://d-h.st/s9I
open odin as admin and disable antivirus if any now browse to the rom.tar file
now put your phone in download mode and now connect usb to phone then to pc in diffrent port best to the back port of pc ,it will install some drivers let it happen and then odin will detect your phone
now click start in odin.
if any error post the screen here of odin
Click to expand...
Click to collapse
i have exact same issue i have knox void 1 and the phone had a bad firmware flash so it wont boot..
i followed the instructions above using every version of odin i can find and it fails at nand write or at boot.img
do you know of a way i can get any firmware flashed to just boot the phone again??
JasonTik said:
thank you, it worked , sort of
i tried that but the odin failed, then i looked up and found something about Philz Recovery, i flashed it, wiped out cache/ factory reset and then i booted into download mode and did what you said and it worked now works perfectly, thanks
Click to expand...
Click to collapse
how do you flash the Philz Recovery?
I would not flash philz because it is very outdated and new custom Roms need twrp.
Oi eu to com o tablete Samsung note 10.1 gt-n8020 de uma amiga, ele tá no loop infinito da Samsung, já tentei entrar no modo recovery e nn vai, já tentei instalar o cwm pelo odin, e da erro, já tentei instalar a ROM original e tmb da erro logo no início.
Ja pesquisei de tudo e nada da certo.
Alguem sabe como corrigir o erro?
---------- Post added at 01:43 AM ---------- Previous post was at 01:40 AM ----------
Oi eu to com o tablete Samsung note 10.1 gt-n8020 de uma amiga, ele tá no loop infinito da Samsung, já tentei entrar no modo recovery e nn vai, já tentei instalar o cwm pelo odin, e da erro, já tentei instalar a ROM original e tmb da erro logo no início.
Ja pesquisei de tudo e nada da certo.
Alguem sabe como corrigir o erro?
Hi, first of all sorry about mi little english... I have the following issue:
I bought my Find 7 from Telcel (Mexico), the model of my find 7 is shown as Model Number: X9076 and Version Number: X9076MX_12.
I've tried to update (using both project spectrum zip and ColorOS V2.1.5i) using the methods that oppo described in their community posts (flash with stock recovery) with no success. It fails to update and reboot and the only message I get is "Actualizacion Fallida".
Would you please help me with a solution for this problem? Any workaround? It is because of telcel firmware?
My current ColorOS Version, it is V1.2.1i, Android 4.3
Thank you in advance.
Flash the recovery update from this thread first, then try to flash the COS update again.
Please help on updating OPPO Find 7 Telcel-Mexico
AngryHapposai said:
Flash the recovery update from ... first, then try to flash the COS update again.
Click to expand...
Click to collapse
Thank you very much for your answer my friend.. sadly it didn't work.. it keeps telling me "Update Failed" message.. should i try flashing the recovery img using fastboot or unlock the bootloader first (if possible on find 7)? It is safe to install any other recovery like twrp and try to update from it? The phone isn't rooted, it has stock telcel firmware.
leonardoBlancoM said:
Thank you very much for your answer my friend.. sadly it didn't work.. it keeps telling me "Update Failed" message.. should i try flashing the recovery img using fastboot or unlock the bootloader first (if possible on find 7)? It is safe to install any other recovery like twrp and try to update from it? The phone isn't rooted, it has stock telcel firmware.
Click to expand...
Click to collapse
It's possible that the update .zip you downloaded just didn't download correctly; it got corrupted or something. Maybe try downloading it again, and then try installing it again. The first tutorial has worked fine for myself and many others.
However, it is safe for you to install TWRP. I'd recommend downloading it direct from their website here . Grab the latest version available and flash it using fastboot.
BG64 said:
It's possible that the update .zip you downloaded just didn't download correctly; it got corrupted or something. Maybe try downloading it again, and then try installing it again. The first tutorial has worked fine for myself and many others.
However, it is safe for you to install TWRP. I'd recommend downloading it direct from their website here. Grab the latest version available and flash it using fastboot.
Click to expand...
Click to collapse
Thank you again for your answer.. i managed to install the recovery and the COS update using fastboot flash and the recovery img (version 4.3) from the zip file... Now I'm setting up mi Google account on the device... so it's done...thank you so much for your assistance.
leonardoBlancoM said:
Thank you again for your answer.. i managed to install the recovery and the COS update using fastboot flash and the recovery img (version 4.3) from the zip file... Now I'm setting up mi Google account on the device... so it's done...thank you so much for your assistance.
Click to expand...
Click to collapse
No problem!
leonardoBlancoM said:
Hi, first of all sorry about mi little english... I have the following issue:
I bought my Find 7 from Telcel (Mexico), the model of my find 7 is shown as Model Number: X9076 and Version Number: X9076MX_12.
I've tried to update (using both project spectrum zip and ColorOS V2.1.5i) using the methods that oppo described in their community posts (flash with stock recovery) with no success. It fails to update and reboot and the only message I get is "Actualizacion Fallida".
Would you please help me with a solution for this problem? Any workaround? It is because of telcel firmware?
My current ColorOS Version, it is V1.2.1i, Android 4.3
Thank you in advance.
Click to expand...
Click to collapse
Hola hermano! hace mucho vengo intentando actualizar mi telefono, es exactamente las mismas especificaciones que el tuyo, pero no entiendo eso del flashboot, podrias explicarme por favor!! gracias!!
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
cirenj said:
As the title states... I am in a bootloop with this message...I am on a Google purchased XL.... what are my options at this point... the device isn't showing up in ADB either....
Click to expand...
Click to collapse
I am assuming your boot loader is unlocked.
Power it down. Then hold power and volume down to boot into recovery mode. Download the latest factory image. Then use the flashall bat file to flash it back.
Edit the flashall bat file to remove the -w so you save your data and apps and flash it.
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
cirenj said:
Yes...bootloader is unlocked...I was trying to root/install TWRP....and ended up here...as long as I don't relock my bootloader...I didn't screw anything up....correct?
Click to expand...
Click to collapse
With the bootloader unlocked you can always get out of these bootloops but it a lot of times requires flashing a new factory image. I have gotten out of bootloops by going back into twrp and doing the factory reset but of course you lose all your data with that. It just depends on what sent you into the bootloop but they can all be fixed by flashing a new factory image. So far, I've never hard bricked a device but I've been in many bootloops!
PS: if you're on the May edition of the OS, then you need the verified boot signer to install twrp or root.
It went into the bootloop trying to flash TWRP...lol
cirenj said:
It went into the bootloop trying to flash TWRP...lol
Click to expand...
Click to collapse
If you're on May, download the verified boot signer, go into bootloader mode, flash the twrp.img so you get to twrp again and reflash the twrp.zip along with the verified boot signer. If you're on June, then that's not the problem but if you have mismatched slots (a/b not the same) you can get into these problems as well.
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
cirenj said:
Im flashing/fixing it with the latest one (June 2017)... guess I need to figure out how to root/custom recovery better.....its no like any of my other Nexus phones...lol
Click to expand...
Click to collapse
This one is definitely different than my nexus 6 was, the 2 slots, etc. But after you flash it with June, you don't need the boot signer. You've seen some guides about the temp twrp.img first from adb/fastboot, then the permanent twrp.zip next flashed from within the temporary twrp, SU 2.82 is what I install next from twrp. You can find the guides. Having the June factory image on both slots can avoid a lot of problems (at least it did for me).
I can boot the phone up now... But still get the message at startup....
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
cirenj said:
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
Click to expand...
Click to collapse
No, that "can't be checked for corruption" stuff is because you have an unlocked bootloader. It'll always say that when the bootloader is unlocked, just ignore that!
Oh.....what happened to the days of just having a little unlock icon and that's it....lol...
I'll try flashing twrp when I get home... Hope the guide works lol
cirenj said:
I assumed flashing the stock image would have given me the stock recovery, so I wouldn't get that message anymore..
Click to expand...
Click to collapse
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
jhs39 said:
You're always going to get that message as long as the bootloader is unlocked. I wouldn't worry about that message. My Nexus 6P always booted up with that exact message when the bootloader was unlocked even if I was otherwise running full stock. Google thinks unlocking your bootloader is by itself a serious enough security concern that you can no longer pass safety net on full stock with the bootloader unlocked.
Click to expand...
Click to collapse
Does anyone know a trick to disable that notification?
When every boot will appear, does anyone know a trick to disable that notification? +1
blackjackEX said:
When every boot will appear, does anyone know a trick to disable that notification? +1
Click to expand...
Click to collapse
Only one way.... Lock the bootloader :laugh::silly:
chaco81 said:
Only one way.... Lock the bootloader :laugh::silly:
Click to expand...
Click to collapse
Yes, i am forget lock the bootloader, then lock the bootloader my phone cache will be clear, anywhere thank you
cirenj said:
It went into the bootloop trying to flash TWRP...lol
Click to expand...
Click to collapse
I've found that if you fastboot reboot bootloader, then fastboot boot twrp.img.
Then flash twrp installer zip in twrp and then boot into system, I should work. Then you can download Magisk zip into phone and flash it in twrp. You will have root as super su doesn't work anymore. I'm on a Pixel XL with January 8.1 update. Good luck
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?
Mod edit Google Translate :
Hi, I happen to the same thing but I want to root it, someone has a tutorial to continue with the procedure, because the sign says that it is only unlocked and not rooted, no?
toti23 said:
Hola: a mi me paso lo mismo pero quiero rootearlo , alguien tiene un tutorial para seguir con el procedimiento , porque el cartel dice que solamente esta desbloquedo y no rootedo no ?
Click to expand...
Click to collapse
inglés solo en el foro
English only on the forum.
The message is because the bootloader is unlocked, not because it is rooted. Fastboot boot or flash twrp and flash magisk if you want it rooted
hi, i have i nova , and its hardbreaked, and i realy need the L01C432B131CUSTC432D001 full rom, i had tried the frimware finder, but didnt find it, i have tried other sites, but found some firmwares ( not the one im looking for), always fail, can someone help? thanks a lot!!!!
Thanks!!!!!!!!!!!!!!!!
tarekboukaf said:
hi, i have i nova , and its hardbreaked, and i realy need the L01C432B131CUSTC432D001 full rom, i had tried the frimware finder, but didnt find it, i have tried other sites, but found some firmwares ( not the one im looking for), always fail, can someone help? thanks a lot!!!!
Thanks!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
If it is hard bricked, I think that even with the full ota it'll be hard to fix your device.
If it is soft bricked, then you can flash twrp, then flash los or RR rom (you can find them in our device development threads) and fix your phone. Then you can take your time to find an official rom (if you want)
Hope you manage to fix it
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
If it is hard bricked, I think that even with the full ota it'll be hard to fix your device.
If it is soft bricked, then you can flash twrp, then flash los or RR rom (you can find them in our device development threads) and fix your phone. Then you can take your time to find an official rom (if you want)
Hope you manage to fix it
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
thanks for ur reply .................. , i did a twrp backup before this problem, and when i tried to restore, the processue stopped at the custum file restore......
tarekboukaf said:
thanks for ur reply .................. , i did a twrp backup before this problem, and when i tried to restore, the processue stopped at the custum file restore......
Click to expand...
Click to collapse
Oh I recommend you to try grarak twrp. You can find a link for it the op of nova los or rr thread
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
Oh I recommend you to try grarak twrp. You can find a link for it the op of nova los or rr thread
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
thanks, ill try .....................
Vinnom said:
Oh I recommend you to try grarak twrp. You can find a link for it the op of nova los or rr thread
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
hi again, i know there is fastboot commands to flash cust, boot,recovery,system to my device, but the system and cust cant be flashed bcz they are too large, i had tried mfastboot, but have same problem!
tarekboukaf said:
hi again, i know there is fastboot commands to flash cust, boot,recovery,system to my device, but the system and cust cant be flashed bcz they are too large, i had tried mfastboot, but have same problem!
Click to expand...
Click to collapse
When that happened to me, it was because I was using emui 5 and tried to apply a system.img from emui 4. It won't be possible.
The trick here is: search in forum for bluesmoothie's backup (the original link is down. Search for the bluesmoothie's backup that Henkate uploaded) and then restore it via twrp. When you do that, twrp will reformat your system partition. Then you can try to flash via fastboot the system.img
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
When that happened to me, it was because I was using emui 5 and tried to apply a system.img from emui 4. It won't be possible.
The trick here is: search in forum for bluesmoothie's backup (the original link is down. Search for the bluesmoothie's backup that Henkate uploaded) and then restore it via twrp. When you do that, twrp will reformat your system partition. Then you can try to flash via fastboot the system.img
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
thanks for help, but i already downloaded blues backup, but failed, i have the error 255 in twrp, maybe ill makea flashable zip since i have backup ,but need meta-inf file
I need help because my MI A2 lite went to bootloop.
I successfully unlocked bootloader and flash TWRP.
After that phone booted correctly but asked me for a Pin to unlock home. As I formerly set a pin to unlock I tried to enter my usual pin but phone said me it was uncorrect.
After a few trials with different pin I thought to do a factory reset doing a Wipe in recovery mode but after that phone entered in bootloop.
Now I still manage to enter in TWRP and I would like to reinstall stock rom but I'm afraid to not follow correct procedure.
Please, could someone tell me:
- if I still could recover bootloop using twrp or if it's safer to use Miflash?
- which steps I have to follow to flash stock rom in both mode (TWRP and/or Miflash) and where I can download correct image?
Thank you in advance for your answers
Zilath said:
I need help because my MI A2 lite went to bootloop.
I successfully unlocked bootloader and flash TWRP.
After that phone booted correctly but asked me for a Pin to unlock home. As I formerly set a pin to unlock I tried to enter my usual pin but phone said me it was uncorrect.
After a few trials with different pin I thought to do a factory reset doing a Wipe in recovery mode but after that phone entered in bootloop.
Now I still manage to enter in TWRP and I would like to reinstall stock rom but I'm afraid to not follow correct procedure.
Please, could someone tell me:
- if I still could recover bootloop using twrp or if it's safer to use Miflash?
- which steps I have to follow to flash stock rom in both mode (TWRP and/or Miflash) and where I can download correct image?
Thank you in advance for your answers
Click to expand...
Click to collapse
Hello,
You Can Flash Your Device With MIFlash Tool.
Stock Image Can Be Downloaded From Given Below Link
https://en.miui.com/download-354.html
Thanks,
MUHAMMAD Asif Qasim
aasiaasi said:
Hello,
You Can Flash Your Device With MIFlash Tool.
Stock Image Can Be Downloaded From Given Below Link
Thanks,
MUHAMMAD Asif Qasim
Click to expand...
Click to collapse
Hi, mine is still stuck in bootloop after MIFlash tool. Any ideas how to fix this?
Se cambio el PIN de mi xiaomi por intentar salir del bootloop
Hola bro, tambien me pasó que al cambiar la partición de arranque para intentar solucionar el problema (fastboot –set-active=a), se me cambió el PIN y ya no ingresa el que tenía antes. Intenté con 1234, 1111, 0000 pero no funciona. Alguna solución? Tengo el Xiaomi MI A2 lite y ya no tengo ganas de volver a comprar a los chinos. Me dañaron el teléfono de la nada. Gracias