Hi,
I flashed CF-Root-XX_OXA_JW4-v4.4-CWM3RFS using ODIN and attempted to install CWM using ROM MANAGER but whenever I boot into recovery all I get is:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
About phone reveals:
Model number: GT-I9000
Firmware: 2.3.6
Baseband: I9000XXJW4
Kernel version: 2.6.35.7-I9000XXJW4-CL1043937 [email protected] #2
Build number: GINGERBREAD.XXJW4
I have read loads of different posts about fixing this but I do not want to screw up the phone. Can someone please help me before I go mad? I believe that I need a '2e' recovery but where exactly do I get it and install it?
I am not a rookie and had absolutely no problems with my HTC Desire or ZTE Blade but this Samsung is something else.
Cheers guys.
-valerebel
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Donovan662 said:
Check my posts in this thread
http://forum.xda-developers.com/showthread.php?t=1995831
Click to expand...
Click to collapse
Cheers, but I got there in the end.
My problem was that although I'd flashed the right Kernel with CWM 3, I kept trying to install CWM again from ROM Manager (v2.*.*.*) and this is what was causing the issue. I refashed the Kernel and got into Recovery Mode straight away. I have now installed a Cyanogen JB ROM.
Thanks,
-valerebel
valerebel said:
Hi,
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
-valerebel
Click to expand...
Click to collapse
I just got the above on everything I tried, after flashing "CWM".
Turns out I clicked the wrong link and downloaded a file labelled similarly, but was in fact not CWM recovery but a modified stock recovery.
That said, the CF-AUTOROOT package for my I9500 did work on it... I just had to go into recovery again, right away, and then install SuperSU from the market. I had to flash the proper CWM recovery to get all the other fancy ZIPs to work, such as the pretty Philz touch recovery.
Eureka!! Got answer!
Hi Dude,
I got the solution as I just faced it and came over from it.
The thing is simple. You have been trying to install the update.zip or superSU.zip from your default android recovery. thats y its showing error. That means the custom recovery has not been successfully installed on your mobile. so pls try again then it will surely install.
Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
The link which i got solution and u should consider it.
http://teamw.in/devices/androidone.html
Hope this helps you dude. let me know if u have any ques.
Thanks all.
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
TWERP failed flash message
blairan said:
i have been downloading CM nightlys to my pc, copying them to my phone's internal storage, then flashing the zip using recovery (twerp v2.6.3.0) successfully for 3 or 4 months. I found CM Downloader app on the app store and down loaded that. I set the setting to automatically check for a new build, and download it. it did download the new builds although they failed to flash. 3 days after this started happening, CM came out with a 'snapshot' version. that one flashed ok. but the 'nighly' builds no longer flash. I have uninstalled CM downloader, and tried downloading them to the PC and copying them to the phone, that no longer works either. I have reinstalled CM downloader no change. so I think there is something changed on the phone that needs to be fixed, or reset or something. I appreciate any ideas here, I am still entry level skill level, so be gentle
blairman
Click to expand...
Click to collapse
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
blairan said:
Updating partition details
Processing OpenRecoveryScript file
unable to locate zip file "/CyanogenRob_Downloa
E:Error installing zip file "/CyanogenRob_Downloa
Don processing script file
Installing ' /sdcar/CyanogenRob_Downloader/cm1
skipping MD5 check: no MD5 file found
E:Error executiong updater binary in ' /sdcar/CyanogenRob_Downloader/cm1
Error flashing zip ' /sdcar/CyanogenRob_Downloader/cm1
updating partition details
then under that in red letters "Failed'
Click to expand...
Click to collapse
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
i'm part way there...
tdhite said:
TWRP that works:
http://forum.xda-developers.com/showpost.php?p=50383573&postcount=3
Why (changelog):
http://forum.xda-developers.com/showpost.php?p=50383578&postcount=4
Click to expand...
Click to collapse
OK, I have downloaded the 2 files. placed them in a directory near my root directory on my pc. placed the phone in fastboot usb, opened a command prompt window from that directory. typed in fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014
and I get error: cannot load 'fastboot flash recovery openrecovery-m7wls-2.7.0.9-05-01-2014'
per a video showing how to flash recovery, I also tried the command adb reboot bootloader I get error : device not found
back to my pc, I open device manager, and I show a device labeled android device that is working properly.
stumped at this point.
is updating recovery the same as the initial install of a custom recovery?
do I need updated drivers for win 7? where are the latest? all videos say they are the latest, but that was when they were recorted.
thanks for help!
Yes u need updated drivers....any easy solution however is go and get the app flashify u will need root of course...it allows u to flash recovery that is on ur sd card. Just choose the img and flash recovery in the app then reboot into recovery and u will be good to go.
Sent from my HTCONE using Tapatalk
Thank you!
Thanks to both of you, updated TWERP did the trick and Flashify allowed me to install it without the fastboot, and PC hookup which was not working. Latest nightly installed, I am a happy camper!
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Slagathor01 said:
Ok, let me get this straight, snag this Flashify, then snag TWRP 2.7.1.1, flash it with Flashify and I am golden????
(I am unlocked and S-Off running CM-11)
Click to expand...
Click to collapse
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
luigi311 said:
All u have to do is update your recovery. So u can grab the latest TWRP and flash it any method u wish. Fastboot is best but flashify is the most convenient. After u flash your recovery the CM Rom should flash perfectly. Note: If u experience any failures in flashing any Rom that u know is good just downgrade your recovery via which ever method u prefer and that should flash fine now. You can always use the recovery zip floating around on the android development thread I'll see if I can find it for u.
Here u go bud http://forum.xda-developers.com/showthread.php?t=2656065
Note if the flash fails try a older zip until it works and flash the twrp by TD. Don't forget to thanks rootlinux for the zips. Might also want to keep the zips in handy on the phone storage incase the Note situation appears.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I got it with fastboot, I forgot I re installed windows since I did it initially, so I was pulling my hair out wondering why fastboot wouldnt see it, and I couldnt even get files to or from it till I installed HTC sync.....heh
thanks for the info.....
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
prdog1 said:
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
Click to expand...
Click to collapse
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash either, right? It certainly seems like an exploit worthy of my time to patch, but I was trying to avoid the data loss :/
rvrzl said:
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash, right? It certainly seems like an exploit worth of my time to patch, but I was trying to avoid the data loss :/
Click to expand...
Click to collapse
You can fastboot flash the corresponding factory images. Skip the userdata data image and will will not wipe data. OTA's are worthless if gonna run root and recovery. Someone may make a TWRP flashable. Would have to search for it.
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
rvrzl said:
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
Click to expand...
Click to collapse
If you're running root, fastboot flash the system.img only. If you don't run a custom kernel, you probably should also fastboot flash the boot.img too.
Keep supersu on your sdcard and after flashing system DO NOT boot the rom. Boot straight into TWRP and flash supersu
If you boot rom install-recovery.sh will install stock recovery on first boot. .flashing super su amended this script so that won't happen.
You can also flash the radio.img. Your choice.
rvrzl said:
I have an unlocked & rooted Nexus 6 (T-Mo, I My build number is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP,
Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Click to expand...
Click to collapse
For OTA's the device needs to be unrooted and complete stock. Including 'recovery'. So flashing with TWRP-recovery will not work.
An alternative is to flash only the new system.img with fastboot.
FWIW, recovery flashable updates are here:
http://forum.xda-developers.com/showthread.php?t=3066052
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
You can flash the OTA all day anyway you want but if you are not stock it won't take. Only other way is one of the flashable TWRP versions that were linked to. And right now looks like that thread is down for update.
danarama said:
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
Click to expand...
Click to collapse
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
rvrzl said:
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
!
Click to expand...
Click to collapse
Because of this, I did the update twice; different methods, to see of there are possible differences.
Differences between official OTA and flashing the new system.img only.
Update 1: Flashing only the new system image (1,7 Gb) with fastboot.
Update 2: Return to stock LMY47Z and install official OTA (24,2 Mb)
Both updates have the same results. Data and apps were kept but there were changes:
a. Changes in build.prop gone (DPI, Wifi interval);
b. Standard icons because the DPI value 384 was changed to 560;
c. BGN-launcher replaced. Google Now launcher became white again;
d. Root gone (SuperSu and Busybox);
(Update 2. Of course returning to stock, replaces the custom kernel).
After rerooting the N6 the following actions were needed after both update methods:
- edit the file: system/build.prop to change the dpi and wifi interval;
- reflash/reinstall: BGN-Launcher, SuperSU and Busybox;
- uninstall updates of the Google app to get BGN-launcher working;
- replacing icons from drawer to start screen.
So when you have made changes to the system, like DPI settings, an update will leave your data alone, but not the settings.
Clawz114 said:
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
Click to expand...
Click to collapse
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
That said, the only reason not to flash the rightbversiin is if the download link.is down or you have a local copy of a different version anyway.
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
How are you trying to flash the OTA?
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
What is the error?
danarama said:
[snip]
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
Click to expand...
Click to collapse
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
danarama said:
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
Click to expand...
Click to collapse
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
danarama said:
How are you trying to flash the OTA?
Click to expand...
Click to collapse
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
danarama said:
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Click to expand...
Click to collapse
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
efrant said:
What is the error?
Click to expand...
Click to collapse
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
efrant said:
What is the error?
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
Click to expand...
Click to collapse
I believe it changed for lollipop OTA's. I don't think it had changed for kitKat.
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Clawz114 said:
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
Click to expand...
Click to collapse
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
danarama said:
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
Click to expand...
Click to collapse
I'm going to have to do just that by the looks of it.
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.