Hello guys,
I own a nexus 4
i would require help in ota issues.
previously when google had launched the 4.4.4 update
my device showed me an error of code 7
the android with exclamatory mark stating update failed
then i had contacted google regarding the issue they told me to flash factory images
but inspite of backup i lost few data
now the same thing is happening with 5.0
i got notification saying update avilable and after download and install twice i get an error code 7
in 4.4.4 issue my device was non rooted with boot loader unlocked
in 5.0 issue my device is rooted with boot loader unlocked
i am on completely stock android only rooted no tweaks or changes to the rom
now if i flash factory image i loose my data for sure.
if at all i backup entire rom in cwm custom recovery
then move that .zip created by backup to my pc
then flash factory image
custom recovery then restore data
will it work
i am very concerned about my phone data as well as the ota
please guys need help
thanks and regards
-AK
hey i had also some error 7 problem.
this helped me.
http://forum.xda-developers.com/showpost.php?p=56916654&postcount=3344
The link says
I resolved the fingerprint Problem (set_metadata_recursive: some changes failed) by flashing the factory Images without the Wipe command
1. Download Factory IMG for Android 5.0 for*Nexus*4
2. Unpack the file and open the folder (make sure the zip file is in the same folder as your ADB/Fastboot folder)
3. Open the flash-all with an EDITOR (flash-all.sh for Linux or Mac flash-all.bat for Windows
4. Remove the -w option from the last line: The line should now read:*
fastboot update image-occam-lrx21t.zip
5. Reboot your phone to the bootloader and execute the flash-all file
But if I edit -w
And flash it
Will it remove all my data
Or its just a kind of ota
Also
Yesterday I tried to backup from twrp
And flashed all of lollipop without editing
Then flashed twrp and selected to restore only data
When rebooted it got into boot loop
Thanks bro fixed the issue with the help of that link without losing my data
Related
Hi there, i've got a problem updating, like many it seems and I'm pretty new to rooting etc. so please bear with me.
I have 4.2.1 stock rom, rooted and with twrp v2.4.1.0 recovery. I was originally rooted with CWM recovery (using n7 toolkit) but I have flashed twrp to try and update with no luck either.
Anyway I get an error (see attachment image) via ota or via downloading the zip and copying it to the n7 then browsing for it in recovery and installing it that way. I'm basically wondering if there's a quick fix to this problem and can you please help me with it even if there isnt a quick fix. I really don't want to reset my device and have to set everything back up again.
Also, i dont know if this is related, probably is, I cant boot into recovery using the power off hold volume down trick, getting into fastboot mode and then selecting recovery as it just brings up the google logo forever and I have to reset the tablet due to it doing nothing. The only way I can get into recovery is to clear data from google services framework and do an ota update (1970 thing) and that reboots into recovery. I then get the error 7 message in attached photo.
Plz help?!?!
Thanks in advance
Here's what to do.
First, look at those errors in the image you posted very very carefully.
2nd, use the search function on this forum: try the terms "OTA debuggerd" (without the quotes)
3rd, read those posts.
4th, decide if you want the hassle. You are not obligated to perform an upgrade.
5th, Download from Google the 4.2.2 Factory images and extract the "boot.img" and "system.img" files
(make sure you understand that nakasi == grouper == WiFi N7, and nakasig == tilapia == 3G N7)
Hint: search on Google for "Google Nexus Factory Images"
finally
fastboot flash boot name-of-boot-image-file.img
fastboot flash system name-of-system-image-file.img
This will remove root from the ROM, so you will need to flash a SuperSU or Superuser root kit.
Doing things this way is a band-aid. You need to learn how to make full backups & perform full restores; how to flash individual partitions - using both fastboot & the custom recovery; know exactly what the roles of each partition are; know the difference between a kernel, ramdisk, and boot image; understand how to retrieve a small number of files from prior backups; and to know where the installer scripts are located inside flashable .zip files & be able to read them so you can understand what they do.
Finally, you should understand what apps like Titanium Backup and Carbon are capable of, and how backup of System app&data has different consequences upon restore than similar operations for user-installed apps.
OK - get started.
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Could someone help me? It's really just the constant "You have an update" that is bugging me. I don't think anything fun happens in this latest OTA. Hopefully this is the last OTA for me as I want the predicted new Nexus come December!! And it would be great to get a Nexus phone I can actually get OTA updates for without issue!!
I haven't backed my data up in a while, I probably should do that too. (Also, regaining root after a flash, anyone have a reliable method for that? And for tethering on T-Mobile.)
thehyecircus said:
Hey guys, I have LTE enabled so OTA updates do not work. I need some help with my options for flashing.
In the past, I flashed my Nexus 4 with MinimalABD, taking the ROM apart and flashing over certain folders to keep my data intact. I don't know if that method will work on 4.4. I also don't know what we need to do to get LTE on this latest update (as in, if anything has changed.)
Click to expand...
Click to collapse
In case:
a. the bootloader is unlocked and you can start Nexus 4/7 in fastboot mode
b. N4/7 is connected to a PC
c. you can get response from N4/7 with a command in a Dosbox: fastboot devices
You could flash the update manually.
Download the required factory image and the Nexus Root Toolkit (NRT) of Wugfresh.
Install NRT and extract the required factory image in a directory of your choice.
In that directory you need the files: fastboot.exe - AdbWinApi.dll - AdbWinUsbApi.dll
Copy those files from the NRT.
From the extracted factory image you need the required zip file extracted from the factory image.
Example Nexus 4: image-occam-ktu84p.zip
Connect the phone to USB. Use NRT to put the phone in fastboot mode.
Open the above directory in a dosbox as administrator.
Type the required command to update.
For N4: fastboot update image-occam-ktu8p.zip
Remark 1.
After that root is gone. Reroot with the NRT of wugfresh.
Remark 2, flashing the radio.
When you extract the factory image for N4 there is also an update image for the radio.
You can flash the N4 with: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
But on my N4 the LTE tricks does not work. For LTE you need an older version of the radio image.
Remark 3.
I used this manually method to avoid the hassle of backup and restore.
I have got a very different situation here. I was using 4.4.4 (KITKAT). I skipped 5.0.0 (LOLLIPOP) OTA update cause there were lots of rumours about the device going into a bootloop. Last week I DIRECTLY (HOW IS THIS EVEN POSSIBLE??) got a "5.0.1" OTA. I mistakenly installed it. So basically I skipped "5.0.0" update and directly installed "5.0.1" and now my Nexus 4 "UNROOTED" device is bootlooping. What should I do?
1. Should I downgrade to 4.4.4 with deleting/editing "-w" thing in "flash-all.bat"? I read somewhere that downgrading wipes all the data. What are my options going back to KITKAT?
3. What should I do to backup? I don't want to flash all my data.
4. Will the deleting "-w" thing work on "5.0.1" factory image?
5. Will the deleting "-w" thing work on "4.4.4" factory image?
6. Do I have to download SDK to perform all the tasks?
Any reply would be greatly appreciated. Thanks in advance. Cheers!
First download official nexus 4 5.0.1 factory image from here https://developers.google.com/android/nexus/images and extract all files till you have separate img files like boot.img, system.img etc.
Then download and install Wugfresh toolkit and install all necessary drivers.
Finally use the toolkit to install all img one by one, except the userdata.img.
At the end you will have a full stock working 5.0.1 system, with no data loss.
I'm at my wits end here. I copied the contents the emoji zip from https://android.gadgethacks.com/how-to/get-android-nougats-all-new-emojis-right-now-0170328/ for Android N emojis on my L02 (Telstra Australia variant ALE-L52) on 5.0.1 into my system folder and caused it to bootloop, then I got TWRP installed and actually flashed it which let it boot but with a different font and Messaging and Phone among other things weren't working. So I reflashed with 5.1 variants of those files in that zip and flashed a 6.0 stock recovery and did a factory reset and now it won't even let me log in to a Google account so I can restore my app backups which means I'm locked out of several apps I need authenticators for.
Is there anywhere I can download the full image for ALE-L02C451B280? I have access to a second device but I do not want to void the warranty on that by unlocking the bootloader and replacing the recovery just to fix my phone, so is there a way to create a flashable backup of the system without root or an unlocked bootloader
Edit: Great, flashed the official 6.0 image like suggested in the updating thread and now it won't even get past the bootloader, can't even boot to fastboot or recovery. It's officially f**ked
Well, if you can't boot to bootloader/fastboot to install TWRP, repair the phone then your phone is kinda bricked
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Vinnipinni said:
What does your bootloader say? Enter it and unpack the UPDATE.APP using Huawei Update Extractor. Then flash System, cust, boot and mybe recovery with fastboot.
Click to expand...
Click to collapse
That's how it ended up bricked in the first place
mercom said:
I see the same symptoms as mine
https://forum.xda-developers.com/p8lite/help/help-bricked-p8-lite-t3522136
Any new suggestions?
Click to expand...
Click to collapse
I ended up fixing it by doing a nandroid backup of another L02 running the original Telstra firmware and restored that, fixed it with a few minor bugs (gave me the Balong bug, so I can't even download any Huawei apps anymore, and I can't disable the stock music app for some reason, and the lock screen is weird, I can't swipe to unlock anywhere it has to be from the circle in the middle). I've just given up hope that I can get the official 6.0 on my L02
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
hexahive said:
Hi everyone,
i hope someone has time to help me on this. I had some experience with flashing custom roms with Lenovo a6000 and some Samsung phones, but it seems there's some things that are different with p9 Lite (L21), or some things i don't understand.
First things first, i've followed steps on how to install LineageOS (LineageOS-14.1-20171228-hi6250-UNOFFICIAL-HassanMirza01) over stock Nougat rom (B381), so i've unlocked the bootloader, flashed Revolution recovery via fastboot, and then installed the rom, gapps, magisk... What happened after installing magisk is a sudden restart, and after that, i got stuck at the LineageOS boot logo (i've let it work for over an hour until i gave up)... Thinking magisk was a problem, i also tried SuperSU, but had the same situation - restart before it finnished. Afterwards i've tried flashing EliteTWRP and after success, i've flashed the Omni-7.1.2-20171201-hi6250-HOMEMADE-HassanMirza01.zip, which also got stuck at the Omni boot logo, but i was able to do installation both with magisk and then again with supersu. Reading through XDA gave me some suggestions, one of them being to format userdata, which gave me a message that the command is not allowed.
Then i made a huge mistake of accidentally formatting internal dalvik+cache+data+system+INTERNAL STORAGE via recovery... After that, the Omni boot logo stopped showing, and i've been trying to repair it since then.
What i've tried so far is:
- fastboot flash boot, recovery (stock), system:
from what i've read there's also a CUST.img that i need to flash, but when i extract update.app that i had installed before all this, it doesn't contain it. I've tried flashing cust.img from another package, but it gives an error.
- after flashing boot, recovery and system.img, i've tried copying various update.app versions to dload on sdcard, then forcing update via pwr+volup+voldown, but every single one gives me "Software install failed - incompatibility with current version - please download the correct update package"... the same happens with downgrade package update.app.
It seems that only B381 update.app, when copied to sdcard and executed in the same way, gives a somewhat different message, instead of "incompatibility with current ver..." it says "Get help from http:..."
- adb shell dd if=/external_sd/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo // re-locked my bootloader
- i can unlock the bootloader and install twrp again via fastboot oem unlock *************** and fastboot flash recovery
- i've also tried unbricking options via P9 Lite Toolkit app, no success.
- HiSuite recovery option says device is not supported for system recovery
Any suggestions ?
Click to expand...
Click to collapse
http://www.meticulus.co.vu/p/hi6250-custom-rom-installation.html
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
hexahive said:
Thanks.
I've managed to revert to stock by following one thread here on XDA. What I did was install L21C432oemInfo-DS.zip, then wipe everything via TWRP, and finally copy the L21C432B130 update app to dload folder on sd card, then the setup went without any problems.
I am now doing a full backup via Meticulus TWRP before i do anything.
There's one thing i dont understand about AOSP and RessurectionRMX roms, it says they're EMUI5 based - does that mean i'd have to update to EMUI5 based stock rom before i try installing it (prerequisites don't mention anything emui related) or that simply means the rom contains EMUI5 ?
Click to expand...
Click to collapse
You must already be on EMUI 5 to install EMUI5 based ROMs.