I recently exchanged my Nexus One for another guy's N-1 which works on ATT 3G. I had done a nandroid backup of my phone, and used that same image to recover the "new" phone to exactly how it was before the switch. It failed first, but after I moved my BCDS folder to the new HTPXXX folder, it went through.
However, now when I try to flash a zip from recovery (Amon-RA 2.2.1), I always get the "Signature verification failed" error. I tried flashing newer radio, after verifying the MD5SUM. I tried flashing the 0.35.017 HBoot. Both of them failed. I am wondering if it's because of the mismatched nandroid recovery I did.
Any help would be greatly appreciated -- thanks!
Edit: Needless to say, after disabling signature verification, everything flashes correctly.
Oops I just realised I should not be posting questions here -- sorry! Can someone please lock this thread?
How to update the Nexus Android 2.2 to Android 2.3.4? Need to unlock the bootloader?
How to update the Nexus Android 2.2 Android 2.3? Need to unlock the bootloader?
I tried but could not update or pro 2.2.1. It says update error and aborted.
I ask for help.
hello all,
I own lg g2 with updated 5.0.2 lollipop stock rom. now after a while that the phone is getting stuck all the time I finally decided I wanna move to cm 13.
so after working half a day on rooting, I finally succeeded, but now after another two hours of working I can't find a way to replace the recovery.
I tried lots of different ways (adb ways with loki, or flashing with flashify/rashr) but after successful flash and reboot into recovery I got error and the recovery couldnt start.
After some research I found out that I need to unlock my bootloader (something I done long back with my nexus 5), but I couldnt find any method of doing so, because all the methods I found was for the kitkat stock rom.
and worse of all I think I cant even downgrade because Im with the dead end lollipop...
so I would like to find out how can I manage to replace my phone's rom? in which part am I wrong?
have you tried to use AutoRec? it does the process automatically and works on stock lollipop. get it here only root is needed for it to work.
hey all, i am using xt1644 RETUS variant and on version 48 which is stock.. i have been trying to update to 64 version but whenever i try to sideload it.. it gives error of footer wrong and verification failed. My bootloader in locked and of course i am on stock recovery. I haven't messed with the phone at all. I am using the update from here https://mirrors.lolinet.com/firmware/moto/athene/official/RETUS/. I have never owned Moto device before so i have no idea how the update works. Any help would be greatly appreciated!
Should i flash using RSDlite?
The zip files you downloaded aren't OTA Updates.
These are full system images for fastboot flashing to restore Stock ROMs on unlocked devices and/or edit them.
So since the official 7.0 rom is due to be released soon I want to restore my device back to stock but I'm having issues with this. I'm getting the Preflash validation failed error when flashing the GPT.bin.
My device is the XT1572 EU model and I am trying to flash the latest build for it which is this I believe:
"XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5_cid7_subsidy-DEFAULT_CFC.xml.zip"
I have looked around for fixes but they are saying you have to flash the latest version since Motorola don't allow downgrades even though I'm confident I am trying to flash the latest version.
Any help would be very much appreciated, thanks in advance.
If you have "looked around" then you would know the answer that is given almost every time... Use the most recent you can find (usually one OTA behind) and skip gpt.bin if you get that error, and bootloader.img if necessary, you shouldn't have to skip anything else, then when it is up take the OTA and you should be good.
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
state_azure said:
Hey, so I am not really knowledgeable enough to help fix this, but I did notice one thing: Why are you using the wiki page from Lineage for the OnePlus 6 (enchilada) instead of the 6t (fajita)?
Click to expand...
Click to collapse
I didn't even notice it was for enchilada, but iirc the file I loaded was only to copy the contents of slot a to slot b. I could search for a fajita version of this. Still, thanks for your reply.
Hi there,
I have the exact same problem. After updating my OP 6T, the cell phone was broken. It's stuck in a reboot loop. Which surprises me, however, because the documentation for this device type recommends that the update be carried out using the system's internal update process. I also noticed that some OTA updates work and some don't. Unfortunately, this is the only way to make use of it very little fun because you never know if the phone is working again when you update. And the security weaknesses show that updates are also important for Lineageos. thanks for the feedback
Zak0r said:
Hi there,
So I unknowingly did something kinda risky and of course, it backfired. I used the in-system update feature of linage OS to upgrade my version on my Oneplus 6T. Can't exactly remember which one the old version was, but it was at least 4 versions older than the newest nightly one. Afterward, the phone got stuck in a boot loop. Also, in recovery, it can't bind/ mount the system, because there is no file directory. "E:Failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory." I tried the following:
- went into recovery, factory reset the device, then flashed new clean lineage os [multiple different versions]. Gets back to boot loop afterward. (note that Fastboot shows no bootloader version or baseband version)
- tried unlocking the bootloader via fastboot flashing unlock. It fails with error code: (remote: Unrecognized command flashing unlock)
- tried copying the contents of slot a to b, in case one was severely outdated as the cause for the soft brick as stated in this guide. Didn't change mentioned issue after flashing os.
- installed Qualcomm USB drivers, to get the PC to detect the phone as a USB device
- after that, tried using the ms-downloader tool to reset and re-flash the phone. It does not get detected and the downloader tool waits for the full 15s before returning the error for no detected device.
- tried unlocking the bootloader itself via fastboot flashing unlock_critical. same error as with normal unlock: (remote: Unrecognized command flashing unlock)
Maybe overwriting the possibly corrupt bootloader would be a good bet, but as mentioned, I cannot unlock the device to make the command for that useable.
Click to expand...
Click to collapse
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Prinçe çharming ap said:
Whatever you do in your device,they will not touch critical partition such as bootloader and many more of it, do u still have twrp or other recovery on your device?
Click to expand...
Click to collapse
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Zak0r said:
I still got the stock recovery. Booting from TWRP image didn't work on my last try, I don't remember the exact specifics anymore. I'll try again.
Click to expand...
Click to collapse
Tell me the exact problem you with your phone and maybe i can help
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
zero4one said:
once again,
today got informed via updater that a new update is available. I try do install it, but now i stuck again in recovery. And the only think i can do is a factory reset and everything is lost.
can anybody give an info if it is safe to update the 6T trough OTA? It doesn't look like that.
Click to expand...
Click to collapse
Oof, I thought mine only got bricked because I tried to upgrade across 4 versions. It seems as though even normal updates now cause soft bricks, neat.
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
zero4one said:
I tried again today but there seems to be a connection to the error. I had an update pending, which could be installed without any problems. After the restart, I was informed that there was another update, after installing this update there was a total failure again. Could it be that this is somehow related to slot A / B?
Click to expand...
Click to collapse
Why don't you try to flash Stock rom on both slots via MSM tool and then just try ota to update to latest build for you specific device
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
zero4one said:
How can i verify if there is an difference between slot a and slot b?
If i flash the stock rom i will be back on oos and that is not what i want i will continue using los, or do we have an idea missmatch there?
thanks for help
Click to expand...
Click to collapse
What do you exactly want ?