Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
irontaco1 said:
... so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Click to expand...
Click to collapse
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
irontaco1 said:
Hello,
Thanks for taking the time to look at this. I ran into a bootloop issue after updating my nexus 6 to a higher version of android. After I flashed the new version everything worked just fine but I kept getting the error message "Google play services has stopped" so I decided to re-flash something I thought I needed but after I flashed the file called "Modem firmware" it made me get stuck in a bootloop. The error I got during flashing in FlashFire was "IOException: write failed: ENOSPC (No space left on device)" and then after that infinite bootloop. I have TWRP installed but for some reason, I can't access my backup because it's asking for a decrypt code I didn't even setup. So is there a way to fix this? Possibly wipe the phone and install a custom ROM?
Thanks.
Click to expand...
Click to collapse
Read this for information on how to bypass the password that your backup is asking for https://www.google.com/amp/s/www.ho...fter-restoring-from-twrp-android-backups/amp/
Strephon Alkhalikoi said:
Wipe the phone, connect the N6 to your PC, and using ADB flash a stock ROM. Where the components are mismatched, flashing a stock ROM will resolve that issue and probably all your others. You will however need to flash your recovery and then your custom ROM - if you use one - as well as your root solution. Finally, whatever you do from now on, don't use Flashfire for the baseband.
Click to expand...
Click to collapse
Hey thanks for the help phone is running just fine now. I grabbed the factory image from the Google dev page and flashed it the hard way. For some reason ADB wouldn't mount /system after it was finished so I used fastboot to flash system, boot, radio, etc. Guess I won't use Flashfire for baseband anymore :laugh:
ktmom said:
Since I "routinely" flash modem zips through FF, I'm wondering if what you did was try to extract the modem img from the full software update? That is not a direction I would go in [emoji4]
There are modem flashable zips for the N6 that can be flashed through FF.
I also think the issue with accessing your back up is due to the user data partition being encrypted. What version of TWRP are you using? If not the newest (as of this writing 3.1.1-0), then that can also give you trouble.
Click to expand...
Click to collapse
Phone is working fine now. The files were encrypted because the stock kernel I was using was obviously non-permissive so it automatically encrypted my files upon reboot before it bootlooped. Really appreciate the help though.
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
mohiminul said:
Is there anyway to flash TWRP as official binary? Gets blocked due to OEM lock
I messed up my Note8 SM-N950F, locked OEM flashed with odin to stock now in bootloop. Says EFS cant be mounted. DM-Verity error. I dont know what to do. :crying:
Click to expand...
Click to collapse
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
sefrcoko said:
No you cant flash twrp as official binary. Can you get back to download mode and flash stock firmware?
Click to expand...
Click to collapse
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
mohiminul said:
Yes, but as soon as flashing is finished the device reboots to recovery and shows error failed to mount efs nd dm-verity verification failed. Downloaded firmware with Samfirm tool.
Click to expand...
Click to collapse
Ok I see. Hmm not sure...I googled and found this thread that has a few solutions (Kies, Smart Switch, etc.) that seem to resolve the issue. If someone knows for sure they can chime in, but in the meantime I would start here (even though it's for Note 4...might still work, or at least point you in the right direction).
https://forum.xda-developers.com/note-4/help/dm-verity-verification-failed-recovery-t2945531
This thread may help.
https://forum.xda-developers.com/ga...-hard-bricked-note-8-sm-t3735009/post75195355
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
m4gicvn said:
PLEASE HELP Note8 hang the logo
The problem is as follows:
When I make a software update for the SM-950f / DS, the phone hangs on the samsung logo
I searched and flashed again with Odin but the result was an error
At startup the error message: kernel rev check fail device 2 binary 1
I flash twrp-3.1.1-0-greatlte_V3 the error: flash fail
Flashing TWRP-3.2.3-TwrpBuilder-greatlte-2018-08-21_17-30 similar results
Now I do not know how to start
Click to expand...
Click to collapse
For the TWRP error, are you wiping data (where you have to type yes) first? If you do not do that TWRP won't work. There is also newer versions of TWRP available.
Logel said:
I think you use the wrong Odin Version. You need Odin v3.13.1.
You used twrp already before your Software Update? Or why you want to flash TWRP?
Normally it's enough to flash a 4 part stock firmware to get your device working again. Use the "home CSC" file to don't lose your own files.
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Logel said:
Edit:
on your first try it looks like you tried to flash an older firmware version. You can't downgrade the bootloader. Flash the same or a newer firmware.
Don't be afraid to hit the "Thanks" button if someone helped you. It don't hurts
Click to expand...
Click to collapse
m4gicvn said:
Previously my phone was not rooted or installed TWRP, everything original.
The phone announces a new software update, I make updates and the result is a phone hang on the samsung logo
I downloaded a stock rom, I made Flash with Odin 3.13.1 but the result was a bug, now I do not have a Bootloader. I found out that I was flashing an old version.
So I need Flash recovery, I was trying to find a new version but as a result I could not successfully flash.
I have been trying to find a newer Fimware (such as Android 8) but now I'm still not successful
Click to expand...
Click to collapse
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware here (same firmware for n950fd and n950f) - use samfirm program for faster download (only latest ver).
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware .
Click to expand...
Click to collapse
Very thank you
I downloaded the android version 8, I successfully flashed. But this time it was like the beginning. the phone is moving, into the upgrade and error, android child back
Then the phone automatically enters recovery mode
I implemented the wipe cache and wipe data but could not change the result
bluecub1st said:
What do you mean you cannot flash and you don't have a bootloader?
"kernel rev check fail device 2 binary 1" means your device is binary 2 and you're trying to flash binary 1 onto your device.
e.g the latest version firmware for note 8 is N950FXXU4CRGA - U4 shows this firmware is binary 4. On the bootloader - SWREV B:1 - this should show if your device is binary 1.
You will need to first oem unlock the device to flash TWRP/custom img. Warning- flashing TWRP will result in KNOX 1.
Note - bootloader should still be there (you might just have drained all your battery) unless the flash failed during flashing bootloader (bootloader is download mode).
Download firmware
Click to expand...
Click to collapse
How to oem unlock the device?
To oem unlock (like all the new samsung devices) you must enable it in the developer options in settings.
As your phone would not boot oem unlock is not available. you must first ensure the phone can boot to stock firmware
Hi, I think i've kinda bricked my honor 5C (nem-l51), and I really need help :
A few years ago I rooted my phone to make otg work.
It worked a little while, but then a system update came up, could not update because of the twrp, so I tried to unroot it (from supersu) to do the update, and the twrp stayed after the unroot.
I stayed with the phone like this, twrp installed and update pending (still trying to install the update from time to time) and then I had to use OTG again and tried to re-root my phone.
I tried to flash the supersu files I used the first time, but, even when the flashing worked, I couldn't see the supersu app on the phone, still unrooted.
Then I tried to change the twrp (via fastboot) and I realised that I couldn't : I get the "command not allowed" failure when the recovery should get written. I tried with numerous twrp versions, and stock recovery.
So my twrp right now is the twrp-3.1.1-0-venus "OpenKirin edition" one.
The phone says it's unlocked and the frp is locked, but I can't remember if it was already the case or not when I first rooted.
I unfortunately don't have anymore the bootloader unlock code that huawai gave me originally. I have no idea how to get it again, to try to re-lock/unlock the bootloader.
Back then when I first rooted my phone, I made a back up, so I tried to restore that back up. It failed, first with "cannot wipe the cust partition". Then I tried to restore without restoring the cust partition, and I got "extracttarfork() process ended with error 255" while the system was restoring.
After that, the phone wouldn't boot into android anymore. It would be stuck at the unlocked bootloader warning message and then reboot after a few minutes.
So, lastly, I tried to install the unofficial lineageOS port from here : https://forum.xda-developers.com/honor-5c/development/rom-lineageos-14-1-honor-5c-t3713911 with my twrp.
The installation went well, but the phone is stuck while first booting in lineageOS (I let it overnight, restarted it, re-installed it, tried with the first release, nothing).
TL;DR: My phone isn't booting and I can't flash any new recovery.
Please, help me to get my phone working again
Give me the
old build number on emui
Update build you received..
Twrp working?
Fastboot?
Erecovery?
I got access to erecovery, even if the "download latest version and recovery" doesn't work. (erecovery connects to wifi, and the first thing it tries to check/download fails)
I can boot into fastboot but can't flash recovery from there because of the command not allowed problem.
I can boot into twrp, but the back up I tried to restore and the lineageos rom I tried to install both failed, so maybe the twrp has a problem?
I'm sorry I'm not sure about the build number, I'm pretty sure I was on EMUI 5.0 and android 7.x, and I think I remember comparing current build number vs the update, and it was something like B350 or B351 for the current, and B355 or B375 for the update.
I've found this in my backup file 'recovery.log' ro.omni.version=6.0.1-20160703-nemo-HOMEMADE and ro.build.id=MOB30M . So, that mean that I had android 6.x when I did the backup, way back at the beginning.
I thought the update never got installed because each time the phone would reboot to complete installation, it would reboot into twrp. But I've still updated from android 6 to android 7 somehow ?
NEM-L51C432 or NEM-L51C10 ?
NEM-L51C432 and I'm sure of that ^^
Zhyrclew said:
NEM-L51C432 and I'm sure of that ^^
Click to expand...
Click to collapse
Flash this via twrp
http://update.hicloud.com:8180/TDS/...-L51_hw_eu/update_data_full_NEM-L51_hw_eu.zip
Once done, boot to twrp and flash this
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1581/g104/v82938/f1/full/update.zip
Reboot.
If you are unable to flash the 2nd link then just use the dload method to flash this. If you are not aware of dload method, link is given in my signature.
Note, this 2nd firmware will replace your twrp with stock recovery. You should boot to b350 version and it will be full stock. Reason for flashing data file first is it doesn't replace the recovery to stock but just flashes your data, settings, apps. And 2nd link is main full firmware which will replace your boot, recovery, vendor everything and should boot.
Good luck
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Zhyrclew said:
I flashed the first one, no error.
The second one had multiple errors :
"[...]
write radio image...
32k crc checked failure
E:unknown command [errno]
update_huawai_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/update.zip'
Updating partition details...
...done
"
So I tried the dload method, and the installation started and ended at 5% with this error :
"Software install failed!
Incompatibility with current version.
Please download the correct update package."
I guess it's because I couldn't tell you the exact build number, I'm sorry for not taking note of it.
If there is a way for me to get the build number despite the status of the phone, i'm ready to do it.
If not, I'm ready to try as many versions as it takes to find the good one.
PS: I've still access to the twrp, thank god ! That was my biggest fear, because I can't flash any recovery in the current state.
Click to expand...
Click to collapse
You may try other higher versions like 360, 370 etc and see your luck. Twrp will be replaced only if the installation os successful for the main firmware. Its just a trial and error for you now but I am 99% sure you should be able to revive the phone via dload method
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Zhyrclew said:
Thank you, it's reassuring. I will not give up until I test all the versions ^^
Could you help me a little bit to find other versions, please ? The only place I know where there is update packages for my phone is there : https://forum.xda-developers.com/ho...lota-upgrade-packages-models-nem-l51-t3473110 and there is only two versions.
Click to expand...
Click to collapse
Firmware finder website
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Zhyrclew said:
Wow, thank you, I downloaded the firmware finder software, it has everything.
Should I flash the firmware in two steps like you first made me, or should I just try with only the dload method with the fullOTA firmware ?
Click to expand...
Click to collapse
Check dload guide in my signature. You can follow that now. Good luck
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Zhyrclew said:
I tried b355, b361, b375, b377, nothing changes, same error.
I noticed that I have something related to an update in my sd card AND internal storage->HwOUC->140783->( update.zip[1.32GB], update_data_full_public.zip[344MB], update_full_NEM-L51_hw_eu.zip[412MB] )
I don't know whether these files were there before I did all these attempted updates.
Could it be that my phone is not trying to install the files I put in sdcard->dload, because he finds these files in the internal memory first, and each time try to install these ?
Should I delete them, move them, unzip them in dload folder ?
Click to expand...
Click to collapse
Copy them on PC and then try dload of files you downloaded from Firmware finder website.
These are files your phone downloaded for OTA update but as you were on twrp, they never installed it amd stays there
I copied the updates my phone downloaded on PC and then deleted them both on internal storage and sd card.
Then I tried dload method with b355,b375&b377 from firmware finder, and also with the update.zip I found in the updates my phone downloaded.
Nothing worked, all of them got the error "Incompatibility with current version. Please download the correct update package."
Should I try even more firmware versions, or should I try something else ?
Btw, I noticed my phone, when connected to my PC, is labeled as huawei-P9-lite, and I don't think it was always like that, but it's probably just because the twrp-3.1.1-0-venus.img is originally for the P9 lite.
I came accross this thread, where somebody recommends to flash stuff from fastboot.
I have not tried it yet, I only tried to flash recovery from fastboot, and it is failing with the "command not allowed". But maybe I could try to flash some other things ? Any advice ?
For now, despite all my attempts to install stock OTA via dload method, the phone is still trying to boot into lineageOS, and failing.
I came across the "current" firmware version with a check with DC-unlocker : "NEM-L51C432B120"
So I downloaded full OTA firmware b120 on firmware finder software, and the dload method worked !
The installation went well, and after a few minutes of the first boot, I got into phone configuration.
I have one last problem, though : the phone configuration is looping.
There is only 4 languages to choose, so I have to choose english(US), then there is a weird list of countries, none in the EU, where I feel i have to choose united states, then after some steps I have to register to huawei ID thing.
If I try to skip it, it loops to the language selection.
If I try to log in to my original account, it says "device not supported for your location" and then loops to languages. (my original account is in french/France)
If I try to create a new account with new address mail, it works but then at the end says again that "device not supported for your location" and then loops to languages.
I tried with other countries it still loops.
The other languages seems to be Chinese and Japanese, but the configuration is looping too if I choose them.
I tried with/without sim, with/without wifi connected...
Dload the next firmware now and see if it works. Then set the phone
I downloaded and installed with dload method (by removing sd card and copying directly on it the files, because I don't know how to have access to the phone internal & external memory now) the next firmware (b130 version)
The phone booted, it launched a "system optimization" that was a few minutes long, and then the EMUI configuration poped up and looped through language selection, region(country), wifi connection (successful), terms and conditions, and WLAN+(switch between wlan and mobile data automatically).
I feel like the phone is working, the notification led is even blinking when I receive sms, but I have access to nothing because of this damned configuration.
Note: the connection to huawei ID isn't prompted again in the loop once I log in, from the original or the new account. In order to be prompted again to log in to the huawei ID, I have to go to erecovery and reset to factory the phone.
Hi,
I've installed a custom rom, but now i can´t install updates, Pie for example.
How can i unroot and go back to stock rom?
Thanks
aalmeida1972 said:
Hi,
I've installed a custom rom, but now i can´t install updates, Pie for example.
How can i unroot and go back to stock rom?
Thanks
Click to expand...
Click to collapse
I'd suggest HurUpdater: https://forum.xda-developers.com/ho...h-official-firmware-recovery-t3769279/page111
OTAs do work with an unlocked bootloader, but not with root or custom kernels.
Does this works with the P10? In the post i ddin´t found the P10.
And if it works, wich zip file i have to choose? And i have root
Thanks
Try my guide (Tutorial #2, Oreo to Oreo)
After that do a factory reset with eRecovery (boot with Vol+ and connected USB).
What also should work is flashing the system.img manually via fastboot.
For this extract the system.img from the correct firmware version with Huawei Update Extractor.
Connect your phone to your PC, boot into fastboot and flash with "fastboot flash system PATH\TO\SYSTEM.IMG".
After that do a factory reset with eRecovery (boot with Vol+ and connected USB).
Note for the next time: backup your system partition via TWRP before flashing the custom rom.
Also note that a factory reset is needed, without your phone won't boot, so backup your personal data before doing it.
aalmeida1972 said:
Does this works with the P10? In the post i ddin´t found the P10.
And if it works, wich zip file i have to choose? And i have root
Thanks
Click to expand...
Click to collapse
Yes, it works on the P10. You can download the files with the firmware finder app. I'd recommend the newest oreo version for your customisation (e.g. B382 for C432).
But Jannomag's solution should work equally well.
Wich Jannomag´s thread?
Do you have the link, please?
Thanks
aalmeida1972 said:
Wich Jannomag´s thread?
Do you have the link, please?
Thanks
Click to expand...
Click to collapse
The fourth message in this thread
I am sorry, maybe i am just dumb but i can't find it
I followed the guide but know i am i an bootloop. I get the message "your device has failed verification and may not work properly"
It restarded, but as D188-L29!!! I download the VTR-L29 on https://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29C432&firmware_page=0
Now i can't update or nothing
aalmeida1972 said:
It restarded, but as D188-L29!!! I download the VTR-L29 on https://pro-teammt.ru/firmware-database/?firmware_model=VTR-L29C432&firmware_page=0
Now i can't update or nothing
Click to expand...
Click to collapse
Possibly you renamed the wrong customisation file (i did it once for the 09 while I needed the 29).
Which one did you download? And did you flash manually or did you use my script?
Download my oeminfo, it's from VTR-L29C432 Version 8.0.0.380, while the version doesn't really matter.
Flash it via TWRP using "Install" and "Use Image". Flash it to oeminfo partition. Then do my update script again.
I followed the guide to do Oreo to Oreo - basically wanting to get from custom Rom (fRomFuture B370) back to stock, so I chose the same firmware version to extract. Flashed everything with the script and it went fine and it boots and works.. but
The resolution seems to be off, too low and the right side of the screen is unresponsive to touch (about 1cm )
EDIT- Rolled back to fRomFuture B370 for now - need to find a way to get back to stock, as want to move on to Openkirin ROM instead
HI, i have a vtr-l29 root, i want to unroot(version oreo), how do i do it? what do i need to flash?. thank you Alex