Phone keeps booting with the old firmware after "successfully" flashing a new one
Hello,
I followed these instructions to flash a new stock ROM/firmware (XT1952-4 instead of the original XT1952-2) on my moto G7 play, but it keeps booting the old ROM/firmware... as if I have never flashed anything.
What did I do wrong? See more details on my post on the thread of these instructions. I though this forum my be better suited for my problem.
Thanks a lot !
Related
1st [Q] Did someone experienced bricking m2?
2nd [Q] Do you have a white spot on your m2? (not a dead pixel)
2nd: no visible issues
I!??!?! why!?!?!?!??!
Caelestiel said:
1st [Q] Did someone experienced bricking m2?
Click to expand...
Click to collapse
Depends on the definition of "brick".
As explained in this thread, I had a situation where the main ROM would not boot; it would just be stuck at the Mediapad M2 boot logo. However, I was still able to access recovery and fastboot modes. So I was able to recover from the brick situation by flashing the BOOT.img, DATA.img and SYSTEM.img from an 801L on my 802L ( I had not yet found an official 802L ROM). Even though my phone model became "801L", it still worked for me. Later, after much hunting around I found an official 802L ROM (B003), flashed it on my phone and got back to a standard stock phone configuration.
In another situation, I had a constant boot-loop problem after installing SuperSU 2.79 as the root app on Marshmallow ROM build B207. The phone would boot up, show the "Mediapad M2" boot logo, then reboot immediately. This kept on happening. However, like before I was still able to access recovery and fastboot modes so I was able to repair the situation in the same manner as described above. That is why I finally wrote this guide - to help other people who may be in the same situation.
I was trying to upgrade my firmware according to the main thread
everything looked ok but i noticed that it was very fast
after it completed i flashed the new recovery
tried to install the new viper rom but got into bootloader every time i rebooted the phone
i managed to restore previous rom from backup but i cant install new roms
anybody know how can i fix this?
thanks in advance
Try flashing firmware again. It probably failed with error 90, which just means you have to immediately flash again. If that doesn't work, post your terminal output from when you flash so we can see what error you're getting. Booting straight to bootloader screen indicates you're trying to use a marshmallow rom on lollipop firmware
I own a canvas A1 4GB variant, I had rooted my phone and flashed custom recovery(everything was finee), After a while my phone's battery started giving me problems(lasted only few hours), I considered flashing Stock ROM or any other trusted ROM, I had flashed RR M[07/07] based on android MM, The battery was still giving problem, A week later, My mom's phone broke and she had to use this(A1) temporarily, I formatted everything and thought of flashing stock ROM and handing over the phone to her, I tried flashing the official zip via TWRP, It gave me some error regarding unable to mount system, System partions or something(I don't remember). And after that, I could't flash any ROM, I tweaked some settings in TWRP and now my phone is totally dead, It does not boot up at all, No recovery mode turns on, Nothing except a black dead screen, I tried flashing stock firmware via SP flash tool, It completes and says successful but still nothing happens, Just wanna know if something can happen to this one? I really loved that device and would be great to have it back working.
Flash correct stock firmware in sptools
arunassain said:
Flash correct stock firmware in sptools
Click to expand...
Click to collapse
doesn't work. I have tried various STOCK Roms on mine but didnt work. Please post a link if possible which u think works.
Hi,
I am new here so pardon me if I make any mistakes posting this thread. So to start, I bought an HTC 10 several days ago, and as it turns out, it was one of HTC's test device and was running on unreleased developer firmware. So upon finding out, I wanted to flash another firmware or ROM into it so I can use it like normal. I'm a total noob when it comes to it so I kinda didn't know what I was doing. I tried flashing several different firmwares on it without success. So I decided to flash one firmware that I found on a website. When it was flashed, it encrypted the phone and I had to enter the wrong passcode 40 times for it to wipe the data. It did wipe the data. But now the download mode fails to boot and every time I want to boot into download mode, it goes directly into recovery and I can't flash anything anymore. Is there a way to reverse this? I desperatly need your help. Thank you
Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!
Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!