I have installed a 7.0 rom to bypass frp, but can't get on 8.0 anymore. System update tell me that I'm using a modified version and I can't update. I tried to flash twrp or ruu, but fastboot continues to tell me that can't flash because S-ON. I tried to unlock bootloader once again, but can't flash even Unlock_code.bin. I'm stuck, can anyone help me?
Vow... Sounds Strange!
But do this, i think it would be fixed...
use sd card and flash ruu using just your phone! ( If u have updated your device to Android 8 before, you absolutely need to flash Android 8 ruu otherwise cause your device is S-ON you wouldn't be able to flash twrp and more!!! )
Mohammad_pd said:
Vow... Sounds Strange!
But do this, i think it would be fixed...
use sd card and flash ruu using just your phone! ( If u have updated your device to Android 8 before, you absolutely need to flash Android 8 ruu otherwise cause your device is S-ON you wouldn't be able to flash twrp and more!!! )
Click to expand...
Click to collapse
This stupide phone only have mini SD slot, not micro so I haven't tried it yet. I'll buy an adapter if no one knows another way
EDIT: it was a micro SD slot instead, solved by flashing ruu, thanks
Related
Guys please dont flame me i am having a pannic attack and cant think strait. i rooted and flashed twrp with moto g5 plus tool kit, then later used ex kernel, then got update ota notioce...i knew it wouldnt work but was suprised it downloaded and propt to restart..so i did thinking it would say no you cant.. instead stuck in twrp like there is no os! please help. I dont know how to reflash the stock os, my backup didnt work when i restored it, and besides that after trying to restore i ended up wipin g and formatu=ing data and looso=ing it now anyway. i am shaking help please
I have just tried to flash lineage zip and it said succesful but when rebooting it goes strait back to twrp, have i lost my boot img ? what can i possiblu do, i am concerned if i download the 1.6 gig stock rom file from g5 plus kits "factory rom kit" it wont be the propper rom for my region "australia" or wont even have a modem..what can i do.. god why dont i stillhave any xanax
when trying to flash stock rom with toolkit the log says bootloader slot suffix not found and bad key
So i finally drank enough scotch to calm down, and realized the "errors" were not actually preventing the stock rom from flashing... and i now have not only a working rom but a baseband..so my reccomendation goes out to anyone panicked to just flash the downloaded stock rom found in the links of the moto g5 plus toolkit
Never,take otas with custom recovery , the solution is flash whole rom
djzero86 said:
Never,take otas with custom recovery , the solution is flash whole rom
Click to expand...
Click to collapse
Yes.. I truly thought there would be a "wah wah wah" notice being rooted.. But it went straight in to it. Just didn't know where any stock rocks were and wasn't prepared.. And ended in a hyperventilating mess. At least I now have the files
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
djzero86 said:
Every day we learn something new, brick this phone is very difficult, all we need is the correct files and some of magic and come back to life ,?
Cheers..
Excuse my bad english...
Click to expand...
Click to collapse
true! My last phone I felt secure and that it was completely unbrickable all because I had all the necessary rescue files and backups. And I had learned from every previous disaster. Thank you for your kind words friend.
Can't get fastboot to recognize device
So I'm kind of in the same boat as you were. I unlocked the bootlader and rooted the phone before giving it to my wife. During that whole process, fastboot had no problems recognizing the phone (obviously). Then my wife tried to update via the OTA which got her stuck in TWRP. I'd like to reflash the stock ROM, but the problem I have is that TWRP won't just flash the zip file ("invalid zip file format"), and I can't use fastboot to do commands line by line since "fastboot devices" doesn't show my phone anymore. I was able to get her going on a custom ROM for now, but I'd like to put her back on the stock ROM so we won't encounter this problem again. I've reinstalled the Motorola driver several times, but no luck. ADB has no problems recognizing the phone when in TWRP recovery. One thing that happened recently was a big update to Windows 10, but I'm not sure if that is the reason for my fastboot issues.
Any advice would be appreciated.
Just a follow up, I tried uninstalling/reinstalling the Motorola driver and ADB on the original computer, but for some reason it still won't "see" the phone in fastboot. I was able to install ADB/Fastboot and the Motorola driver on a separate computer (also Windows 10) to get fastboot to recognize the phone so I could issue commands to reinstall the stock firmware. I noticed, though, that the following commands FAILED when I entered them:
fastboot erase customize
fastboot erase clogo
I'm not sure what those were for, but the phone seems to be working fine on the stock firmware now.
Hi guys i badly need your help with my asus, it is updated with nougat version and i did successfully root my phone without any problem however when i flash some zip files it was reboot and stock to asus logo, id tried to wipe and format through recovery but it didnt work i also tried to flash the nougat software but it was unsuccessful, see the attachment bow, i badly need your help please. :crying:
gregz17 said:
Hi guys i badly need your help with my asus, it is updated with nougat version and i did successfully root my phone without any problem however when i flash some zip files it was reboot and stock to asus logo, id tried to wipe and format through recovery but it didnt work i also tried to flash the nougat software but it was unsuccessful, see the attachment bow, i badly need your help please. :crying:
Click to expand...
Click to collapse
Follow this https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926 and you'll be fine.
Do not forget about "no-verify" file
stark_br said:
Follow this https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926 and you'll be fine.
Do not forget about "no-verify" file
Click to expand...
Click to collapse
hi sir i already did try this steps during the time that i root my device and it successfully worked for me, but i flash something through recovery and the phone is not turning its just stock on asus logo i have no option for me to connect my asus through pc becuase it was bootloop and the pc did not recognize my asus phone
Flash stock Recovery, copy stock ROM un external SD Card from PC, reboot in Recovery and install zip from SD Card, back to Stock ROM
Necrodaemon said:
Flash stock Recovery, copy stock ROM un external SD Card from PC, reboot in Recovery and install zip from SD Card, back to Stock ROM
Click to expand...
Click to collapse
but im getting failed whenever i flash the stock rom, it says rom zip corrupted
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
campeadore said:
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
Click to expand...
Click to collapse
Check this post.
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
campeadore said:
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
Click to expand...
Click to collapse
Try to flash the TWRP again with fastboot.
PS: I don't understand how you people end up like this. It never happened to me.
I cant, adb cant be connected to device. Says null operation.
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
campeadore said:
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
Click to expand...
Click to collapse
You need to install the other zip too which has the word "data_full" at zip's name or something like that.
EDIT: @campeadore, i suggest you to edit the thread name and add "[SOLVED]" at begin and write the way you've fixed your phone (the solution), so it'll help other people who might run into the same problem as you.
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
campeadore said:
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
Click to expand...
Click to collapse
Newer / newest firmware downloaded from Firmware Finder needs to be approved by Huawei and that can take some time. It's failing to install because it wasn't approved. I've read this in past somewhere.
Try B381 or B382 as i've always installed that one when i've went back to EMUI 5.
Yes, i did it now with can-l11c432b330. I think my mistake was trying to flash to EMUI5 with usb cable connected. With cable off all went fine like a charm. Now i do all approved updates with system update. Thank you so much man, really appreciated.
Seeking help: I have a smartphone huawei nova lite plus (TRT LX1) that fails to restart. It goes continuously in a loop. Entering recovery only the first 2 functions come out: wipe wash factory reset and wipe wash partition. Then using eRecovery from PC with the USB cable, proceed up to a certain point and then not continue. I think it's in soft brick. I definitely need the right software for flashing, stock roms and usb drivers. Where can I find them? Many thanks
Hello.
I did a mistake and totally wiped my phone with only a wrong ROM on my SD-Card (It was for the p8 2017 not foy my 2015).
So now I do not have any ROM installed but need to get the device working again. The problem is that, because of the age of the device, all links to ROMs are dead. The only thing I found is the stock-ROM but only in update.app format, which is used in the dload-folder. But the phone does not recognize it when booting.
Bootloader is unlocked, TWRP is installed!
Would be glad for every hint!
I managed to get a stock recovery back working, but flashing the stock roms (android5 or android6) via update.app file always stops installing at 90%. I tried several times and waited for hours. It never coninued!
Any idea what could go wrong?
The modded Rom in this thread works pretty well and was available on 11-18-19.
https://forum.xda-developers.com/p8lite/general/mod-c432b612emuipersona78-t3689367
You can install it either from sdcard or ADB Sideload
Lexington67 said:
The modded Rom in this thread works pretty well and was available on 11-18-19.
https://forum.xda-developers.com/p8lite/general/mod-c432b612emuipersona78-t3689367
You can install it either from sdcard or ADB Sideload
Click to expand...
Click to collapse
https://mega.nz/#!VIlgwY5Y!0DQTbM94a4BCsn0PsUHwhHZxzcW_8AUKXxoSWmQNCHo
https://forum.xda-developers.com/showpost.php?p=80943185&postcount=2295
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?