Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2379833
you have this as a sure thing.
I have wondered if my restore method would work on a locked BL phone. Scroll down to near the bottom and I comment on the possibility of getting custom recovery and then root? Impossible! But you are borked already..... My wife won't let me try it on her updated & locked M.
http://forum.xda-developers.com/showthread.php?t=2391641
Click to expand...
Click to collapse
I did try that and that is how I obtained root. Didn't have a problem up until now.
Anyways, I managed to fix my issue on my own.
Long story short, RSD Lite was flashing the VZW_XT907_4.1.2-9.8.1Q-66_1FF I downloaded from droid-developers.
My phone kept rejecting the tz.mbn saying it was invalid.
Sooooo, I searched for a 98.18.78 OTA pull and I found one.
This is the one for reference.
I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it.
So, I won't delete this just as a reference for anyone who has the same problems as me.
Sorry for taking anyone's time.
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
aviwdoowks said:
cheno1115 said:
....QUOTE]
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
"I swapped the tz.mbn files between the two folders and it flashed it without a problem. Phone booted up as if I just unboxed it."
You got the file from the old OTA?
Click to expand...
Click to collapse
Yes, I just went in my phone settings and did realize this is a previous OTA. I checked for updates and my phone wants me to update to 98.18.78.
I am curious, that link is the prev OTA.
Even then could you share how an ota useful in RSD?
Click to expand...
Click to collapse
Well, Pretty much, my phone had no rom at the time. I ruined it by trying to flash stuff.
So I downloaded the bottom rom from
sbf.droid-developers.org/scorpion_mini_xt907/list.php
and was trying to flash it onto my phone. My phone kept rejecting the tz.mbn file, it said it was invalid. So I found that old OTA and swapped the two files, and to my surprise, my phone accepted that file. I don't know why it wouldn't take the original one.
Anyways, I'm updating my phone to OTA 98.18.78 right now, so all is good.
Click to expand...
Click to collapse
Samuri HL Downgrade Tool
cheno1115 said:
Alright Ladies and Gentlemen.
Background: (skip if you don't think it's relevant)
I just bought a xt907 with the latest OTA.
I wanted root, however after looking into it, I read that the bootloader was forever locked from the new OTA.
But, me being as stubborn as I am, and always have had a rooted phone, I tried anyways, and with my surprise, somehow, I actually achieved root using motochopper after only clearing the dalvik cache and trying it for shiggles.
No backups.
Even though I couldn't flash a new recovery or a full rom without safestap, I just decided to mod the stock rom.
Installed pimp my rom, es file explorer, some app uninstallers for bloatware (no i didn't uninstall any COM files or important things), etc etc.
Then I Installed a font, didn't like it, went to try a few others.
NOW.
After installing a font and rebooting, I was stuck at the droid boot logo with the red eye and sparks flying about.
I booted into stock recovery, cleared the cache. Nothing. Reset to factory defaults. Nothing.
I was still stuck on the boot logo.
Now, the dumb part of my actions.
I downloaded matt's utility 1.20. I tried option 1, Which failed. So I tried option 2, flashing the recovery. Which was "successful".
Tried option 1 again, it keeps saying
Code:
sending 'system' (30720 KB)...
OKAY [ 2.318s]
writing 'system'...
OKAY [ 2.798s]
sending 'system' (30720 KB)...
OKAY [ 6.569s]
writing 'system'...
OKAY [ 1.358s]
Over and over again.
Now I can not boot the phone. AP Fastboot comes up.
Code:
AP Fastboot Flash Mode
(blah)
Device is LOCKED. Code 0.
No Valid PIV block in SP for system.
PIV validation failed (system)
Fastboot reason: Flash Failure
Same thing comes up when I try to go into recovery. Every time I turn on the phone, this comes up.
I tried RSD Lite, to flash the old rom back on, it keeps failing. I keep trying to flash VZW_XT907_4.1.2-9.8.1Q-66_1FF
With no avail.
So, Anyone who can help me, I would be forever grateful. Thanks.
Click to expand...
Click to collapse
I lost root after the OTA update. Inused SamuriHL Downgrade tool to roll back to the stae my phone was in before update. then it gives instructions on how to retore and keep root. then yuo tkae the update again.
THANK YOU
I thought I was doomed to a bricked phone. This fix saved me.
Important to note for any other poor suckers who find themselves in the same spot - make sure you have an updated version of RSD Lite when you do this. My first (15) attempt(s) failed flashing system.img because I was running an old version of RSD Lite, but when I updated to 6.1.4 it worked fine.
cheno1115, THANK YOU!
I had the same issue with my xt907 after rooting with "DROID_RAZR_M_Utility_1.20" and after restoring my apps (including with framework mods.. stupid, I know) from xt890 via nandroid manager.
I thought oh my god, that is an expensive brick I have now.
I have just reflashed "VZW_XT907_4.1.2-9.8.1Q-66_1FF.xml.zip" via RSD (with "tz.mbn" file raplaced from "Blur_Version.98.16.1.XT907.Verizon.en.US.zip") and it did boot up, however it booted with all my "restored" apps. The problem is that I have tried to restore my home screen via nandroid backup manager and it failed, so I got only upper status bar, soft buttons and black screen... I'm lucky that Motorola placed a settings shortcut on upper drawer, so I was able to navigate to settings and do a factory reset. So this is how I got a fresh start again.
However if I launch "DROID_RAZR_M_Utility_1.20" with option 1 again, I get the same thing - many repeating "sending system.img", have to terminate it and then - a brick. So I had to repeat RSD reflash procedure once more. BTW flashing of "system.img" takes surprisingly long, like 5 minutes or so.
So that got me thinking... Isn't this repeating "sending system" and "writing system" just doing it in pieces and one should wait?
Anyway that has solved my problem. THANKS!
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
nifty101 said:
Does this mean you fully rooted your XT907 that had the latest OTA updates? Can you install other ROM's?
As far as I know, once you get the latest OTA update you're screwed and can't do anything.
I have a locked xt907
Click to expand...
Click to collapse
We have SafeRoot now. See the general section.
No custom roms though.
See my xt907 stuff
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
nifty101 said:
Can you send me a link to each the general section and your XT907 stuff? Not sure where or what you are referencing. Thanks so much.
Click to expand...
Click to collapse
You are on tapatalk or xda app?
Go here & take your punishment. Lol.
http://forum.xda-developers.com/showthread.php?t=2610531
Links
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3
SamuriHL has fix for "cannot load system img"
http://www.droidrzr.com/index.php/topic/37658-green-robot-after-using-house-of-moto/#entry400767
No valid piv
Mr hello I have this problem with no valid PIV on my motorola RARZ M can you help me?
Related
EDIT: Its amazing how typing everything help when asking for help can give you an idea on how to fix it. I downloaded the recovery image manually, unpacked it once, loaded it up in RapidCRC to figure out its MD5, restarted the factory reset program, and bam all working. Guess I was just being dumb and overlooking the obvious. Thanks anyhow all. Sorry for the trouble.
Hello all, I am in quite the pickle and I hope someone here can help me.
Not long ago I unlocked my Nexus 10's boot loader and installed TWRP recovery and a rooted copy of 4.2.2. I did all of this using the latest Nexus root toolkit, and I had zero issues. However recently I decided to revert back to stock completely. This brings me to the problem I am having.
So this morning these were my exact steps. Again, the current state of my Nexus 10 before I did anything was Unlocked Bootloader, TWRP Recovery, and 4.2.2 rooted installed. Nothing else.
I loaded up the Nexus Root Toolkit and connected my tablet to my computer making sure to use a USB port that worked last time. Made sure USB Debugging was enabled and clicked the "Flash Stock + Unroot" button. I followed all the steps and selected the latest (4.2.2) recovery image. Everything appeared to be going ok. I will now post exactly what I saw on the flashstock.bat window below.
sending 'bootloader' <1280 KB>...
OKAY [ 0.141s]
writing 'bootloader'...
OKAY [ 0.124S]
finished. total time: 0.270s
rebooting into bootloader....
OKAY [ 0.004s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 535248732 bytes
error: update package missing system.img
It then closed and showed the completion message in the console window and said something along the lines of "press any key to close". In the bootloader it said " fastboot status fail signature verification".
At this point I thought "well, maybe it did not send the reboot single" so I selected the reboot option from the bootloader and all it did was hang at the google logo. Nothing happened. Next I tried rebooting into the bootloader and selecting recovery. Here is where I got very worried as nothing happened except a black screen. Nothing at all. Its like it does not have a recovery system at all.
I tried redoing the whole process and the same thing happened. I hope someone can help me as I really have no idea what to do and am quite frightened I broke it. The only thing I can think that leads me to believe me I can salvage this is that I can still get into the bootloader and as a result I assume I can get into fastboot.
Any help would be greatly appreciated.
Thanks very much,
-S
Glad you got it solved.
My Razr M is in a state where all I can do is boot into fastboot. I was trying to fastboot back to stock Jellybean by using Matts Utility 1.20. I received the following when the utility ran:
[*] Simple Razr Restore
[*] Windows Version
[*] Created by mattlgroff
[*]
[*] Before continuing, ensure your Razr is in the
[*] "AP Fastboot" mode and connected via USB.
[*] WARNING: Do not do this at LOW BATTERY! You have been warned!
[*]
[*] Press any key to continue.
sending 'mbm' (512 KB)... OKAY [ 0.063s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
sending 'mbmloader' (42 KB)... OKAY [ 0.011s]
writing 'mbmloader'... INFOInvalid partition name mbmloader
FAILED (remote failure)
sending 'mbm' (512 KB)... OKAY [ 0.056s]
writing 'mbm'... INFOInvalid partition name mbm
FAILED (remote failure)
rebooting into bootloader... OKAY [ 0.008s]
< waiting for device >
erasing 'cache'... OKAY [ 12.865s]
sending 'logo.bin' (854 KB)... OKAY [ 0.102s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
sending 'devtree' (512 KB)... OKAY [ 0.069s]
writing 'devtree'... OKAY [ 0.325s
Everything fails?????? My phone screen says the following.
AP Fastboot Flash Mode (S)
10.9B(#) (sha-1e9f557, 2013-02-22 09:18:22)
eMMC Info: Size 8GB
Device is UNLOCKED. Status Code:3
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
When I reboot the phone whether connected usb or not it comes back to the fastboot screen and says Flash Failure! Any Ideas of what I can do? I have a factory cable and have tried it as well as standard USB cable. I tried booting into recovery and once I press volume up, it sticks on my bootlogo and will not go into recovery?
Update: I am a complete retard and was using the wrong Utility. WOW rookie mistake. Sorry. Using the Utility for XT912 not XT907
Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.
RikRong said:
Well, hopefully using this utility didn't mess with your bootloader. If it did, you might be out of luck. Either way, if you have a locked bootloader and you're on the latest update, you shouldn't use Matt's utility 1.20 for the M. It has the older update in it. To restore, you'll need to get the FXZ from Droid Developer's SBF and make sure you know what you're flashing, prior to flashing it.
Click to expand...
Click to collapse
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?
evocop said:
Thanks for the reply. I was not on the latest update and I am Unlocked. I restored with Matts Utility (the correct one this time) and flash was successful. However when I get to start up screen to select language. The screen is not responsive. I press the power button and Power off shows up but it to is not responsive to touch either. The only way I can reboot is to hold power and volume down. Any Ideas?
Click to expand...
Click to collapse
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.
RikRong said:
Okay glad you got it. The non-responsive screen makes it seem like you might have flashed the files for the wrong phone. Is it possible you used the Razr HD utility? Since the processors are the same, people have been able to get the phone to boot but they get a non-responsive screen like what you're running into.
Click to expand...
Click to collapse
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.
evocop said:
I downloaded the VZW_XT907_4.1.2-9.8 blah blah blah FXZ. I flashed this time using RSDLite. Flash was successful, and then at the select language screen, same issue. It is unresponsive to touch. Am I screwed?
I have gone into recovery and done factory reset, wipe cache, rebooted and still nothing. Perfectly good phone prior to my screw up of using the wrong utility. Gonna be heartbroken if it is done. Bootloader still shows unlocked. Just doesn't make sense.
Click to expand...
Click to collapse
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.
RikRong said:
Hmmm, I'm lost on this one. Hopefully, someone with more experience will chime in. I would try one more thing, though. Find a stock ROM on here or on DroidRzr and try flashing it in recovery and see if that gets you anywhere.
Click to expand...
Click to collapse
Well I downloaded Deadcalm rom and flashed. Booted to language screen and screen is unresponsive still. Is it done for?
A dmesg might be useful.
Maybe you could try flashing a non-stock based ROM (CM, Carbon, etc) and see if overwriting the boot.img with something completely non-stock might fix it...
It sounds like a driver (boot.img) issue, but that should be fixed with a simple reflash of a correct RSD XML...
EDIT: I really don't think you're done for, since we are booting the OS. May need some... Advanced fixing though
Sent from my Nexus 7 using Tapatalk 4
Hi I have the XT1570, running unlocked and with rooted but stock 5.1.1. I have run in to some issues with the recovery part.
Firstly I wanted to go back to the recovery and flash a stock recovery so I could get the OTA for MM, i did that using fastboot, and the flash worked fine according to fastboot, however once i rebooted into recovery it would not load, got an error message, I forget now something about dumping back to bootloader.
Anyway i fixed it got TWRP back on again, then tried a different stock recovery, same thing same error, so i thought I would easily get back to TWRP by the same method, flash again. I was wrong, now fastboot told me , target reported max download size of 536870912 bytes
error: cannot load 'twrp-2.8.7.1-clark': No error
Remember this is the exact same TWRP image i have just flashed not 5 mins before.
So i thought ok then, maybe an old image is in there taking up space or something.
C:\Users\David\Desktop\Mfastboot\Mfastboot>fastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.017s]
finished. total time: 0.019s
Now I get the message:
Invalid boot image header.
Error:failed to load kernel
Boot up failed.
I presume I have deleted everything in the recovery partition, and so messed it up good, but I dont know how to fix it at this point.
I also erased the cache along the way (via fastboot) as I tried to get the OTA update to work anyway just to see what would happen, so I had to erase the cache to cancel updates
I must reiterate, I can boot into Android and use my phone no issues, at all, just I have no recovery at all and this means updates arent going to work, also i cant seem to find a reliable source for a stock recovery.
Some step by step help would be appreciated, as I am not an expert by any means on this.
Thank you.
Also my device was bought in China as that is where I am, it does indeed have the code name XT1570, dual sim, I would assume it is basically the same as the XT1572 asian. I do also have an original backup of the phone after unlocking bootloader, before root, which was my next port of call after changing the recovery back to stock.
fixed it i was just being foolish, someone delete this thread it is of no use.
Can you explain how you fixed it? I too have deleted the recovery in an attempt to flash twrp, but now neither twrp nor the stock recovery are there?
Tapatalk'd from my Twisted, Racing Nexus 5
Moto g4 XT1625 install TWRP 3.0.2 fail, Image not signed or corrupt.
unlock boot loader ok,
Install TWRP 3.0.2 from official (twrp-3.0.2-0-athene.img 12.2M 2016-06-08 17:50:53 EDT) fail with these message:
(bootloader) Image not signed or corrupt
I tried again, not work. After that, reboot, try to enter recovery mode, only get "no command" message with a dead Android robot on the screen.
I wanna root this device, but can't install TWRP at all.
Please give some help.
1) Did you type in the right command?
fastboot flash recovery twrp.img
2) Did you download twrp from the official page? Did you try re-downloading the twrp file to make sure its not corrupted? Below is the link for twrp 3.0.2, directly from the official page of twrp.
https://dl.twrp.me/athene/
Please update me how it goes.
I had the same issue. Always got that message, but I reflashed it a few times until it eventually worked.
xtermmin said:
I had the same issue. Always got that message, but I reflashed it a few times until it eventually worked.
Click to expand...
Click to collapse
Glad to hear it worked
First of all, thanks for all the reply.
I will leave more detail and keep trying.
turn on usb debugging. --> ok
adb reboot bootloader --> ok
fastboot devices --> ok show devices
fastboot flash recovery recovery.img --> enter everything right but only got fail & pain T_T
// The message:
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12496 KB)...
OKAY
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY
// end
Here, it said sending 'recovery' (12496 KB)...
which means, I guess it get that img file, but still fail.
By the way, some other user got the same problem and message.
I tried on XT1625 Moto g4, again and again, fail. close unnecessary program.
If I can unlock bootloader, hardly believe things could go south like this.
Maybe the key problem is
1 (bootloader) has-slot:recovery: not found
something must wrong, but where?
2 (bootloader) Image not signed or corrupt
XT1625 Moto g4, Moto g4 plus need different TWRP? But there's only one from TWRP official website.
I tried everything I can do, download again compare with md5 before I post.
I can't find way out.
Anyway, thanks alot.
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
funplay said:
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
Click to expand...
Click to collapse
Custom recovery and root break OTA. You might still get the notification that an OTA is available, but it won't be able to apply.
it never worked for me.
But the next command works:
fastboot boot twrp.img
funplay said:
updated, I'm not sure, but as you said, I tried again, suddenly, I could enter TWRP, I will try whether it work or not.
Another question is, after unlock bootloader, install TWRP, root. Can I update system or patch with OTA?
Thank you for reply and help.
Click to expand...
Click to collapse
I was having the same problem. I tried the RootJunkyremove amazon bloat script, and I was having all sorts of problems, Even getting into a boot loop for a while.
I was running without a recovery until I ran Rootjunky's root script, which seems to have fixed most things.
So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.