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
Related
i have to send my rooted acer a100 back to acer to replace a faulty screen i was wondering if my unlocked bootloader and leaked ICS void my warranty bc i dont wanna pay to ship this of and they send it back on some bullsh*t
YOUNGTWAN said:
i have to send my rooted acer a100 back to acer to replace a faulty screen i was wondering if my unlocked bootloader and leaked ICS void my warranty bc i dont wanna pay to ship this of and they send it back on some bullsh*t
Click to expand...
Click to collapse
Yes, your warranty is voided. You could downgrade to hc and re-lock your bootloader to get your device back to stock (so you can get your warranty back).
how do i downgrade and relock the bootloader
??
Restore HC firmware
YOUNGTWAN said:
how do i downgrade and relock the bootloader
??
Click to expand...
Click to collapse
1. Reflash to stock A100 ICS firmware. It will restore stock bootloader and recovery. And allow to flash the HC firmware.
2. Reflash to stock A100 HC firmware.
I noticed that Vache's site is down, and I needed to get the HC firmware as well. I was looking online and found this:
http://acer-club.ru/topic/13368-rom-acer-a100-200704-com-gen1/
Will post results after I have completed the downgrade.
when i get into cmw recovery i cant move or select anything ..
tryn to reflash the stock ics firmware it jus automatically loads the cmw recovery .. in which i cant do anything from there but restart the tablet .. can i do this fastboot
If memory serves me right you can fastboot flash a update.zip.
pintek said:
If memory serves me right you can fastboot flash a update.zip.
Click to expand...
Click to collapse
thought so bro now my only question now is what the adb command to do so i already tries adb fastboot update.zip and i put the update.zip in the same directory as adb ex platform tools
Theonew said:
Yes, your warranty is voided. You could downgrade to hc and re-lock your bootloader to get your device back to stock (so you can get your warranty back).
Click to expand...
Click to collapse
english:
thanks i dont need this, but in the future this may serve to rescue device and to use the warranty...
español:
gracias no lo necesito pero en el futuro esto puede servir para rescatar el dispositivo y usar la garantia...
Sorry for my BAD english =)
soo um can someone please tell me the fastboot commands to install the update.zip
YOUNGTWAN said:
soo um can someone please tell me the fastboot commands to install the update.zip
Click to expand...
Click to collapse
You could try:
Code:
fastboot update update.zip
ok trying now .. i managed to get it install via sd from inside cwm but then it restarts and jus hangs at preparing to install rom
doesnt work says archive doesnt contain android-info.txt android-product.txt lol dude im bout to seriously cry
YOUNGTWAN said:
ok trying now .. i managed to get it install via sd from inside cwm but then it restarts and jus hangs at preparing to install rom
doesnt work says archive doesnt contain android-info.txt android-product.txt lol dude im bout to seriously cry
Click to expand...
Click to collapse
You said you got it installed? Try deleting the file from your SD card
So is this the latest version of ICS for the A100?
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!!
Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?
flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !
porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does
flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well
Hi guys, I need help with this, I can't install the rom on my moto z play because of this error: Failed to load kernel. already installed more than 20 roms and nothing.
You need to go fully to stock first, try and see if that boots; if so then we can diagnose from there
marcost22 said:
You need to go fully to stock first, try and see if that boots; if so then we can diagnose from there
Click to expand...
Click to collapse
already installed the factory rom and nothing to boot. already tried to restore by RSA and it fails.
belkurs45 said:
already installed the factory rom and nothing to boot. already tried to restore by RSA and it fails.
Click to expand...
Click to collapse
Have you tried Lenovo's smart assistant? it can restore devices
marcost22 said:
Have you tried Lenovo's smart assistant? it can restore devices
Click to expand...
Click to collapse
already tested. rescue and smart
did it complete it's flash? If so, then im sorry to say but it seems like the phone is plain dead
belkurs45 said:
Hola chicos, necesito ayuda con esto, no puedo instalar la rom en mi moto z play debido a este error: Failed to load kernel. ya instale mas de 20 roms y nada.
Click to expand...
Click to collapse
Does changing the firmware from ODIN work?