If I update my nexus player from build mpa44I to build mra58k using a usb cable and flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system. Will i loose all my info on the nexus player? I did fastboot oem unlock so i could get the nexus player 6.0 betas when 6.0 was still in beta. I never relocked the bootloader using - fastboot oem lock. So everytime i restart the nexus player i see a lock sign that is unlocked on the screen as it is booting up. But now i see that nexus player is up to build mra58k. Every time i go to settings then about and click system update my nexus player tells me my system is up to date but i know it is not because here - https://developers.google.com/android/nexus/images?hl=en is listed build mra58k. I just do not want to lose anything or have to reinstall anything back because the update will make me lose it.
if you use the flash-all script, it will WIPE your data. Open the script up in a text editor and remove the -w flag in the last command and that won't wipe your data. (-w = wipe)
minotauri said:
if you use the flash-all script, it will WIPE your data. Open the script up in a text editor and remove the -w flag in the last command and that won't wipe your data. (-w = wipe)
Click to expand...
Click to collapse
Thanks alot!!!! Worked like a charm and i learned something!!!
Related
[N7 2012 - Wifi]
I don't have any rom flashed, just a working bootloader and TWRP 2.6.3.1.
Everytime I try to flash a rom (through adb or fastboot update) it doesn't work cause of the error:
"Unable to mount /system".
How do I solve it? (BTW: TWRP asks for a password everytime it gets started, but I've never set one...).
I really need help...
still in the need of help..
Have u tried to reflash twrp or use mskip or wug toolkit to recover factory image.
b3ltazar said:
Have u tried to reflash twrp or use mskip or wug toolkit to recover factory image.
Click to expand...
Click to collapse
Yup, but mskip not.
Try fastboot erase system or fastboot format system. You may also want to wipe data to remove the nonexistent password. Note that I mean wipe /data, not just a factory reset.
Sent from my Nexus 5 using XDA Premium 4 mobile app
korockinout13 said:
Try fastboot erase system or fastboot format system. You may also want to wipe data to remove the nonexistent password. Note that I mean wipe /data, not just a factory reset.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Fastboot erase system was successful, unlike wiping /data because it's "Unable to wipe /system"...
EDIT:
Flashed CWM and flashed a rom through adb sideload, but I think without your help (fastboot erase system) it wouldn't be successful, THANKS!
EDIT:
New rom (and Android version), old problem. The reason why I didn't have any rom installed was because I wasn't able to turn Wifi on..aaaaand I'm still not able to turn it on.
Ethested said:
Fastboot erase system was successful, unlike wiping /data because it's "Unable to wipe /system"...
EDIT:
Flashed CWM and flashed a rom through adb sideload, but I think without your help (fastboot erase system) it wouldn't be successful, THANKS!
EDIT:
New rom (and Android version), old problem. The reason why I didn't have any rom installed was because I wasn't able to turn Wifi on..aaaaand I'm still not able to turn it on.
Click to expand...
Click to collapse
What is the name of the ROM zip you flashed, and did you flash a custom kernel?
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
What is the name of the ROM zip you flashed, and did you flash a custom kernel?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Vanir, latest 4.3 version. I didn't flash any kernel, just the rom.
I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Found answer here:
http://www.theandroidsoul.com/fix-e...img-android-5-0-factory-images-nexus-devices/
The only missing (last) step for my setup:
flash latest TWRP, reboot into it, flash latest SuperSU, erase Dalvik and cache, reboot.
You can flash every partition for itself. No need to wipe. But I haven't done this so far so I can't tell if it will work.
But here is a guide.
http://highonandroid.com/android-sm...-android-5-1-manually-on-nexus-4-5-6-9-and-10
I always just manually flash all the images from the new factory image EXCEPT USERDATA. Never had any issues, and all my data stays the same as it was before flashing/updating.
And HOW exactly do you DO that (on a Zenfone 2e) because I cant find any Definitive Info on the phone variant. It seems that ASUS uses the same tools for the 2e as they do for the 2 (16 Gig) but they never say FOR Sure. I have a 2e and I'd REALLY like to be able to put the newer rom on it. I keep getting the same ...app_process32 Status 7 error.
So How would I go about GETTING the Factory Rom from ASUS ,
and 2 Where can I find the "Tools" i keep hearing about
Also, Im not a noob, I've used Fastboot and ADB before, I'm just not quite a "Pro"
hippopo said:
I have 5.0.2 (LRX22G) rooted + TWRP.
I flashed the original stock recovery from LRX22G, and still I cannot sideload OTA, I'm getting error "/system/bin/app_process32 has unexpected contents".
Is this because I'm rooted?
Is there another way to upgrade to 5.1 ? Can I just flash new bootloader, system, boot and recovery images (from the factory image LMY47D) and erase cache?
(Obviously I want to preserve my apps and data while upgrading...)
Click to expand...
Click to collapse
Hello,
you can flash yourself the content of the factory image.
Unzip the content , and then the newly extracted archive you will find.
you can do such tings ...
Code:
fastboot flash <partition> <path_to_img_file>
replace <partition> with system or bootloader
<path_to_img_file> should be the absolute path to your img fileSo if i were you I would simply flash the system partition and erase cache
As I flashed a wrong PURE NEXUS ROM... For my phone accidentally without properly noticing name now I have downloaded factory .IMG of nexus 6P so if do dirty flashing by just flashing system.IMG and boot.IMG through recovery will this change my full system configuration as I'm reverting my phone full unroot+stock android+re lock boot loader and NRT requires current system so will this flashing just system and boot give me original version of nexus or not....I will wipe system before flashing or just go in recovery and flash these 2 IMG files..
There is no such thing as a "wrong" build number with an AOSP ROM. They build from source so their build numbers may be different than the ones in the factory images but they have to use the same drivers and blobs in the factory images so that everything works. You are fine where you are.
If you still want to revert to stock, follow section 11 in Heisenberg's Unlock/Root/Flash guide in the General section (basically, wipe system, data, cache, and dalvik cache then flash the system, boot, and vendor images).
nathanchance said:
There is no such thing as a "wrong" build number with an AOSP ROM. They build from source so their build numbers may be different than the ones in the factory images but they have to use the same drivers and blobs in the factory images so that everything works. You are fine where you are.
If you still want to revert to stock, follow section 11 in Heisenberg's Unlock/Root/Flash guide in the General section (basically, wipe system, data, cache, and dalvik cache then flash the system, boot, and vendor images).
Click to expand...
Click to collapse
I'm just asking as I use NRT for reverting the phone to stock and it asks about android platform as it must be android 6.0.1(mhc19i) but currently it is 6.0.1(mhc19j) so there will be problem...that's the main think I want to ask
Mohit M'S said:
I'm just asking as I use NRT for reverting the phone to stock and it asks about android platform as it must be android 6.0.1(mhc19i) but currently it is 6.0.1(mhc19j) so there will be problem...that's the main think I want to ask
Click to expand...
Click to collapse
Not sure what you mean, clean install a rom, never dirty flash unless you're ok with expecting issues.
Doesn't matter which build. Choose the most up to date vendor, chose a kernel or stock with stock. Job done.
If you want to revert to stock, then as the above has said, follow the tutorial to do so. You can't miss.
OK, I played with Titanium Backup and removed some Samsung apps like S health... Now I am stuck at boot loop and phone wont start. I am on stock rom 6.01 rooted. tried everything I could read:
- installed TWRP - did not quite work, gave me an error "is not seadroid"
- installed CWM - I can boot into it, but not much I can do to fix the boot, I tried wiping the partition cache and dalvik, but not help
- installed root again with stock recovery, nothing..
If I install the latest version of stock firmware, will I loose my app data? All I care about is to preserve my notes from ColorNote I read somewher that if a rom does not have userdata img, it wont wipe. Does the stock firmware have that? I am just looking for a way to get back in, backup stuff, and then reflash properly.
I tried going the adb route, but nothing there either. In cmd it says now unlock your phone for the pull command to compete, which obviously I cannot do.
Any other options to save my ColorNotes and Pictures?
OK, I was able to execute:
adb pull / C:\Myfile
This copied system files pretty much. How do I copy the app data or personal data - that's what I actually need
Got lucky...
I had to flash the latest stock firmware, but because I was running it anyway, just not the latest security patch, I the system ended up upgrading and all my files were preserved. It is as if I simply got the monthly patch.
Heyyo, update on the lockscreen crashing bug! I figured out the REAL culprit!
Backup EVERYTHING important off of your device, as this WILL completely wipe your userdata (internal storage).
(optional) Remove the lockscreen security from the system and then create a TWRP backup of data.
Reboot to boot loader
Please ensure you have adb and fastboot installed on your PC's OS.
fastboot format -w userdata
Reboot to system
(optional) Reboot to recovery and in Settings enable "Use rm -rf instead of formatting" and restore a TWRP data backup.
Setup lockscreen security and reboot a lot of times and see if it works ok and then report back your results.
If you wish, you can then change device firmware via TWRP installation with one of these:
https://sourceforge.net/projects/lineageos-for-x2/files/Firmware Updates/
You can also change splash screen to something like the official LeEco ones via TWRP installation with one of these:
https://sourceforge.net/projects/lineageos-for-x2/files/Mods and Tweaks/
NOTES:
please use the official platform tools for Android adb and fastboot from here:
https://developer.android.com/studio/releases/platform-tools
I think the issue could be stemming from TWRP and the broken format function from the encryption footer days... Which could also explain why only some users who did format data were affected by this bug.
I know this fix has worked for both myself and lanciaogden
https://forum.xda-developers.com/showpost.php?p=79280116&postcount=652
Revisions:
Apr7, 2019 - switched to just fastboot format command since it turns out that's the real fix, no need for fastboot EUI ROM
Apr9, 2019 - added optional step to restore TWRP data backup
Apr11, 2019 - removed TWRP install step
Apr25, 2019 - droped "-u" from format instructions as older versions of fastboot doesn't seem to have it
Sept6, 2019 - added recommended version of platform tools for adb and fastboot from Google
Jan 30, 2022 - added removal of lockscreen security before creating a TWRP backup in that optional step
Works! Great job @ThE_MarD
Heyyo @kanagawaben , Yay! Bro I'm super glad it works for you too! Looks like we can put this nightmare of a bug in the past! :good:
pallavjparikh from X2 Telegram and Jorge from zl1 Telegram groups both confirmed it works for them too!
Amazing job @ThE_MarD , it worked for me as well!
My fastboot didn't know "-u" parameter, was it a typo?
I can also confirm it is possible to do it without having to do a fresh OS install. I copied Internal Storage files to a PC and made TWRP backup of Data partition and moved it to PC as well. After fastboot format -w userdata I did a another format inside TWRP to get my data partition back to f2fs I was using earlier. Then used TWRP to restore Data partition and copied back files that were in Internal Storage. Everything is as it was before, minus the dreaded lockscreen bug!
Can someone confirm we can get back to using hardware encryption now, without loosing all data after a lockscreen crash?
mjoach said:
Amazing job @ThE_MarD , it worked for me as well!
My fastboot didn't know "-u" parameter, was it a typo?
I can also confirm it is possible to do it without having to do a fresh OS install. I copied Internal Storage files to a PC and made TWRP backup of Data partition and moved it to PC as well. After fastboot format -w userdata I did a another format inside TWRP to get my data partition back to f2fs I was using earlier. Then used TWRP to restore Data partition and copied back files that were in Internal Storage. Everything is as it was before, minus the dreaded lockscreen bug!
Can someone confirm we can get back to using hardware encryption now, without loosing all data after a lockscreen crash?
Click to expand...
Click to collapse
Heyyo, indeed it works perfectly fine (please ensure you're using the provided TWRP version from the first post to be safe though). I've been encrypted, rebooted 20 times, changed firmware to x820 30s, rebooted another 10 times fine... then I formatted data with that TWRP 3.3.0 version from first post, encrypted again and rebooted another 30 times fine.
I did observe that when testing Pie OP3 Open Beta blobs for DRM/SEE/Gatekeeper/Keystore though? Our current TWRP based on 8.1 with Oreo blobs cannot decrypt Pie blobs haha oops... so I guess before I release a LineageOS test build with pie OP3 blobs? I'll also release an updated TWRP Pie build. :silly:
hello, for some reason I can't do this
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format -u userdata
CreateProcess failed: Impossibile trovare il file specificato. (2)
error: Cannot generate image for userdata
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format -w userdata
CreateProcess failed: Impossibile trovare il file specificato. (2)
error: Cannot generate image for userdata
Thanks
Ths
Heyyo @mariosbbs , please use official adb and fastboot.
https://developer.android.com/studio/releases/platform-tools
Questions
@ThE_MarD what is the best firmwire for le max 2 ? shall i flash firmwire as normal zips in recovery?
is the lockscreen fix trick needs to apply every time i change rom/twrp?
is it a better idea to move to f2fs if rom supports?which partitions supports f2fs?
sorry for a lots of questions
Heyyo @nageswarswain ,
The best device firmware is a bit subjective... Some say 466D is the best, some say 30s. I haven't really noticed much difference, so as long as your device firmware is 19s or newer? You're fine. Technically though, 466D is the latest as the time stamp is a newer date than 30s.
This lockscreen fix should only be a one-time thing. The cause seems to have been a faulty build of TWRP from a while back. I've formatted data on my x2 with the latest official TWRP and have not encountered the lockscreen crash bug.
F2fs tbh on kernel 3.18 isn't super great, as it suffers from long term performance degradation. I'd still recommend sticking with ext4. At most, maybe cache as f2fs since it isn't long term storage, but that's as far as I've gone on x2.