Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
N101BL said:
Hi gang,
I am back again. I sent my last phone it and got a next day warranty replacement.
Now the new phone after rooting successfully, for some reason I started getting 504 error. So I decided I would reload my backup which I made.
The backup loaded the first time but I still had the 504 errors when trying to install anything from Google Play Store
Now I am trying to load the back up again and my phone hangs on the Black Alcatel boot screen. (Not sure how long I should wait for this)
I went through all the steps again to root the phone.
The bootloader is unlocked
TWRP is booting fine (twrp-2.8.7.0-idol3-6045.img)
SuperSU was installed from TWRP (UPDATE-SuperSU-v2.46.zip)
Everything is working on the TWRP side.
But I am not able to boot back into system......
I am hoping there is a quick fix that I am just not seeing.
bootloader screen
----------------------------------------------------------------------------
C:\IDOL3_6045_ROOT>fastboot -i 0x1bbb oem device-info
... INFO Device tampered: false
INFO Device unlocked: true
INFO Charger screen enabled: false
INFO Display panel:
INFO Boot cpus: androidboot.earlyboot_cpus=3,4,5,6,7
INFO Big core max freq:
INFO Small core max freq:
OKAY
C:\IDOL3_6045_ROOT>
Click to expand...
Click to collapse
A 504 error is a network error and has nothing to do with your phone or it's backup. http://pcsupport.about.com/od/findbyerrormessage/a/504error.htm You should research these error's or post a question before doing things that end up making the situation worse. At this point you need to restore your backup and don't do anything till you read the tutorials on how to install TWRP (which has it's own built in way to root the device) or read a supersu tutorial on how to root the device after twrp is up and running correctly THEN if you have issues ask your question in the proper thread...you say you are "booting" twrp...booting twrp means it's not installed and you are running the fastboot boot command. If you meant "booting INTO twrp" by using the vol up key while the phone is booting then you should clarify. You should also be verifying your supersu zip file has the proper size/md5sum. If your backup is not valid (or you didn't bother to make one) then go to the stock image thread and download the most recent image for your model and flash that via twrp.
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
famewolf said:
go to the stock image thread and download the most recent image for your model and flash that via twrp.
Click to expand...
Click to collapse
N101BL said:
Is there a way to flash this from the stock recovery?
I am able to select
"apply update from ADB"
"apply update from scard"
"apply update from phone storage"
When I use "adb sideload 6045i_5.0.2-7SR4-UE40.rar" it starts loading however does not complete.
I get the following messages
Finding update package...
Opening update package...
Verifying update package...
E?footer is wrong
E?signature verification failed
Installation aborted.
--------------------------------------------------------
On Alcatel One Touch Idol 3 6045i
C:\IDOL3_6045_ROOT>adb devices
List of devices attached
81f4d01a sideload
----------------------------------------------
Click to expand...
Click to collapse
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
famewolf said:
No. They require you to go into twrp which is why they say they are TWRP images and is what you should have had flashed/installed before you rooted and bricked a 2nd device. You can try to see while it's in the boot loop if "adb reboot bootloader" gets you to the black Alcatel screen...if it does you can use fastboot to install twrp. (see the instructions in the twrp thread) Otherwise, you once again have a warranty repair. Rooting without actually installing twrp is silly..you lose the backup it gives via restoring a backup, rebooting to bootloader, using the full adb access, or using the built in file manager with root access to restore your device in the event of a bad flash, boot loop etc. It's been commented on repeatedly in the forum that the 6045i and 6045Y do not have a reboot to bootloader in their factory recovery which makes it very easy to "brick" your device until alcatel releases downloadable rom images installable via "download mode".
Click to expand...
Click to collapse
N101BL said:
Thanks for the reply. And whatever it takes to excuse my stupidity lol. It has followed me all my life. I suffer from the one step too many syndrome!
I did install TWRP before rooting. I did everything right. Not exactly sure when things started to go sideways this time.
But I do know for sure that I was still sitting with a bootable TWRP recovery working.
..... Then the one step too many syndrome set in. I thought it would be smart to install the stock recovery image onto the boot partition. That actually "worked"
I was able to boot into stock recovery (as boot) and/or TWRP recovery. So I thought well why don't I just install the stock boot onto the boot partition and flash the stock recovery onto the recovery partition.
Oh well...... No longer able to boot into system. But I can boot into stock recovery. Which of course doesn't help alot, as you have stated about not having a stock rom to install with the stock recovery yet. And I
also believe that since I did not uninstall SuperSu or Unroot my phone, that is why I can not do a successful wipe and reset with the stock recovery. lol
Anyway, the good news is that I have in fact ordered another warranty replacement! What a great warranty I have.
And the better news is that I will have it Tuesday, so please let me know what you need before I turn it on.!
I am not going to root this phone until everything gets stable. So if I can be of any assistance in perhaps helping you figure out a stock rom, please let me know.
I won't turn it on until I get your reply.
Cheers!
Click to expand...
Click to collapse
While your thought is appreciated we currently have all the versions of stock that we need for the 6045i. The next time start by flashing twrp (not just booting it) following the tutorial in the twrp thread step by step...after twrp is installed boot into it and make a full backup for your OWN use before trying to root. I can't emphasize this enough...follow the tutorials..don't just jump out and start running whatevr. Your system was fine when you had the 504 network error...it was also STILL fine when you restored your backup and "continued to get the 504 error". It was after that you went off on a tangent somewhere. If you cause Alcatel enough grief they can check your returns for the presence of modifications such as attempting to root and opt to void your warranty especially after multiple returns.
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
I had updated from my oneplus 2 to the oneplus 6. and with great ease was able to unlock,flash android P.
Bad to hear that you are facing such problems, as my switching was error free.
One of the solutions which you could try for the Zip signature verfication:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
inderjeet.c7 said:
- Use the correct/latest TWRP (I remember this fixing my issue on my previous device..)
- Try to adb sideload and flash the zip.
Click to expand...
Click to collapse
I have tried TWRP with both the current 3.2.3.0 and the previous 3.2.3.2, both downloaded from twrp.me. Sideloading failed, too. Same zip signature error.
I may have to wipe the device and start over yet again. I'd blame myself for doing something wrong, which may very well the the case. But the zip signature issue was there before I installed anything with the stock system.
maigre said:
I just got my OP6 yesterday and am having strange difficulties flashing zips from TWRP, including TWRP itself.
After a bit of exploring the stock device, I wanted to unlock, flash custom recovery, and root with Magisk. This is very familiar turf for me from Nexus devices, but the OP6 is a somewhat different animal, I'm learning. I unlocked without any problem, but couldn't successfully flash TWRP. I got a "zip signature verification failed" message. Redownloading TWRP didn't change anything. So, foolishly, I deselected the zip verification checkbox and installed it that way. This got me booting into TWRP when I was trying to boot to system. And in TWRP's file manager, my /sdcard was looking corrupted, though I think I may have had PIN security set up, so there would have been encryption that caused me some confusion without realizing it at the time. I'm not sure about that, though. In any case, I couldn't boot into the system, which I'd somehow seemed to be corrupt or wiped out. I was stuck at the animation where the red dot has two white ones orbiting it. Again, I've done this countless times on other devices. I'm only a newbie on this one.
So I was soft bricked. I got myself up and running again by following the steps at Stock Fastboot ROMs for OnePlus 6. I hope that was the right version of stock to be working with.
Then, after getting a little further along in setting up the device, I went to flash the xXx NoLimits ROM. Since I couldn't flash TWRP, I booted into it and tried to flash NoLimits. Again, I got the zip signature verification error. Later, I flashed a system image downloaded from the OnePlus site. I did that from within the Settings, not from fastboot/TWRP. Didn't change anything, though.
It turns out that I can't flash any zip file other than Magisk. I get the zip signature verification failure error with everything else, even a zip of OOS. The files are fine. They can't all be bad. I fear that my restoration from the initial TWRP debacle isn't quite right. But I couldn't flash TWRP without the error and that was with the factory installation of OOS on a device that I'd just received before anything else had gone wrong.
I've searched XDA and the internet and see lots of people getting this error over the years. But I'm not finding out anything that makes it clear why I'm having this happen with this device. I'll wipe the device and start over again if I have to, but the problem was there when it was stock.
I've spent hours today researching and experimentating with no progress other than what I've gained from all the reading and futility. If you have any knowledge about this, please share it with me.
Click to expand...
Click to collapse
Try this https://www.bouncegeek.com/fix-signature-verification-failed-oneplus-devices/. I don't know if it'll work for your device as this is for one plus 5t but they are similar in this regard. I would also download all files fresh to make sure there is no corruption. Also disable any lock screen security (finger print, Pin, face lock, etc.)
Among the things I've tried were that I had happened to find that article earlier. Some of it, I can't do. Like clearing the cache of System Update. I'm not seeing that listed in the Apps on Oxygen like it may have been on Hydrogen. One thing I did do, though, almost the only thing, before unlocking and rooting, was to let the system update with an OTA from 5.18 to 5.19. So that could have played a role based on the article's premise.
In any case, I can't sideload, I still get the zip signature failure in spite of what the article says. I tried the other approach. I'll try again later.
This is frustrating. I bought this phone in no small part because it can be rooted and there is a dev community for it. But if I can't do with it what others are and what I want, it may not be worth keeping. I wish I knew exactly this failure is occurring. That it's not rare, I get. But maybe there's nothing wrong with the files. Can all these repeated downloads be bad ones? I've tried both transferring from my Mac via ftp and downloading directly from the web to the phone.
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
helioXverse said:
Are you using "fastboot boot recovery.img" with out the quotes then installing twrp from that booted version of twrp or just trying to fastboot flash recovery.img?
Only the first will work as we don't have a true recovery partition any more.
Click to expand...
Click to collapse
Yes, I'm booting into TWRP via that command line. It's not permanent. I tried to flash the TWRP zip, but signature verification failed. That was the first of my various failures. If I can't find a way to get this straight, I may return the phone, or at least try and get them to trade it to me for another.
Is your oem lock checked?
netgar said:
Is your oem lock checked?
Click to expand...
Click to collapse
Do you mean is "OEM unlocking" toggled on in Developer Options? If so, yes, it is and has been.
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
NickStrupat said:
I had the zip verification error as well, this version of TWRP worked for me: 3.2.1-0
Click to expand...
Click to collapse
Interesting. I didn't try going back that far. I ended up abandoning zip signature verification and am just flashing without it. So far, no problems.
Good evening /hello/hi,
i own moto one power device (Ram: 4gb, Version: 9.0 pie, MODEL: moto one power, qualcomm snapdragon 626) and i was trying to root my device..
i was successfully able to unlock my bootloader without any error, then i installed and flashed twrp.img(latest version) after flashing twrp i was trying to flash the magisk file which initially landed with a pop up msg (FAILED). After trying it several times i tried to sideload it using adb and was then finally successful and tried to reboot my phone. After rebooting the device i was constantly stuck in the bootloop for almost 20 minutes, i tried rebooting it later but was still in bootloop, so i realized the rom is deleted.
NOTE: The mistake i made was not backing up my device thinking everything will be done fine but i was wrong and landed with this problem.
I also tried to fetch STOCK ROM from forum and flash it, but those zip files was not working. Some say's "invalid zip file" and or "signature not matched".
I also tried to fix the signature error by turning off the option for signature verfication from twrp but still was unable to flash.
i am currently using a custom rom to work with it, but the stock rom was really very good and i would just like to use it.
SO IN THE END I MAKE A HUMBLE REQUEST TO PLEASE, CAN SOMEONE PROVIDE ME THE STOCK ROM SO I CAN FLASH IT CAN START MY PHONE.
Hello there,
I´m stuck in fastboot with the message "Software status: modified" and "This device is corrupt. It can´t be trusted and will not boot." I have entered fastboot, then used temporarily TWRP 3.3.1.0 to flash magisk (root) and now i can´t boot. Stuck in middle between root and stock kind of... what steps are now possible to solve the problem of not booting. Do I have to do go back to stock by putting the ruu.zip on sd card and reflash in download mode or is there any workaround for the software status message. I don´t want to loose my encrypted user data by the full wipe of RUU. I also have to state that my U12+ was on the latest Pie Update (Android 9.0). At the moment I can enter fastboot, download mode and temporarily twrp, however i am not sure if that A/B security structure of the partitions cause that "corrupt" message. Thanks in advance!:good:
Since I ran out of solutions I decided to flash a RUU.zip and went back to stock. If anyone still finds a way to install magisk via temporary twrp on pie and to fix the "corrupt device" security message please leave a step-by-step guide.
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
sergio-bodyweb said:
Hello,
I'm stuck on TWRP, no way to load Android.
TWRP wasn't reading the partition so I tried to repair, pass to EXT2 and back to EXT4.
All got stuck on TWRP, I could only go to fastboot, at boot it goes back to TWRP automatically. The message on TWRP console is :
"Android Rescue Party trigger! Possible solutions?
Either :
1) Wipe caches, and/or
2) Format data, and/or
3) Clean - Flash your ROM
The reported problem is:
"init_user0_failed"
Unable to decrypt FBE device."
TWRP version 3.6.2_12-MI10Ultra_v3.7_A12
First ROM present on device: xiaomi.eu_multi_MI10Ultra_22.6.15_v13-12-fastboot.zip
Second time I tried to flash with fastboot and XiaomiFlash the same ROM, successfully installed, but I was still stuck in the loop.
Third time I flashed xiaomi.eu_multi_MI10Ultra_22.6.29_v13-12.zip with TWRP, successfully, but I'm still stuck on the same loop, Android won't load.
Please I need help, I use the phone for work and actually I've been without for a whole day.
How can i fix TWRP possibly without lose all my apps and data?
Click to expand...
Click to collapse
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
plegdroid said:
Afternoon matey, not to sure if this is helpful or not, may not be even specific to your device, but the error is the same error, so may shine a little light on the error.
Unable to decrypt FBE device
Plz anybody help this out... I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery. Initially console shows decrypted FBE device with default password. But Encryption status : Encryped So I went into wipe...
forum.xda-developers.com
Click to expand...
Click to collapse
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
plegdroid said:
Forgot to add, would recommend reading the whole thread, you can then judge what actually works or not before trying
Click to expand...
Click to collapse
Of course, thx.