I try to restore my phone from this thread http://forum.xda-developers.com/showthread.php?p=26039594
but I got failure after trying the T-mobile ICS update file.
It comes up like this on screen:
" error in /tmp/sideload/package.zip
(Status 7)"
I have many ways try to wipe and restore data before and after the update file from sd card.
bootloader/ kernel is 0A.6C one screen
I have try different ways for 6 hours with no luck, grrrrr
My phone is now bricked, maybe i must sendt him to rep...
Helpfor a possible solution will good. Thanks
Sorry for my bad english
Edit: I was on T-Mobile ICS before I try to flash the new ICS EU
TheMask1 said:
Thank, thank you
I'm back on stock ICS T-mobile again
I will try too go for ICs EU version later.
Click to expand...
Click to collapse
What have you done after that?
Gesendet von meinem XT910
HSD-Pilot said:
What have you done after that?
Gesendet von meinem XT910
Click to expand...
Click to collapse
In this morning I try to flash the new ICS EU again.
I Fastboot flash the boot_ne.img and ffastboot flash the system.img.
But got failure: error in /tmp/sideload/package.zip
(Status 7) when I try to update ICS from sd card.
After that I have try to restore too T-mobile version with no luck
Just in mind > You got 2 Update zips on your SD now. You tried the right one for the new Leak?
Gesendet von meinem XT910
TheMask1 said:
I try to restore my phone from this thread http://forum.xda-developers.com/showthread.php?p=26039594
but I got failure after trying the T-mobile ICS update file.
It comes up like this on screen:
" error in /tmp/sideload/package.zip
(Status 7)"
I have many ways try to wipe and restore data before and after the update file from sd card.
bootloader/ kernel is 0A.6C one screen
I have try different ways for 6 hours with no luck, grrrrr
My phone is now bricked, maybe i must sendt him to rep...
Helpfor a possible solution will good. Thanks
Sorry for my bad english
Edit: I was on T-Mobile ICS before I try to flash the new ICS EU
Click to expand...
Click to collapse
You must wipe cache, then install the zip again. Of course you must flash the new leak, not T-Mo.
Edit: Otherwise you could extract the t-Mo ICS zip to your harddrive. The pick the cdt.bin_signed, devtree_signed, and all mbm-files and flash them via moto-fastboot. Then flash the t-mo 2.3.6 system_signed again and reboot into recovery, perform a full wipe and cache wipe. Then apply the ICS update.zip.
Or if you want to try the newest leak, just do the same steps using the 2.3.6 26 fastboot and the new ICS zip.
dtrail1 said:
You must wipe cache, then install the zip again. Of course you must flash the new leak, not T-Mo.
Click to expand...
Click to collapse
So this is a way to go to a newer ICS leak from the T-Mo leak? Just flash the zip from recovery after wiping /cache?
stangri said:
So this is a way to go to a newer ICS leak from the T-Mo leak? Just flash the zip from recovery after wiping /cache?
Click to expand...
Click to collapse
Read my edit above. But in normal case you must not wipe anything, just flash the system_signed from the 26 fastboot and then apply the update zip from the new leak.
Edit: Also the boot_new.img has to be flashed before applying the update.
Here it is: http://www.mediafire.com/?rh4flyvuo5lej9w
HSD-Pilot said:
Just in mind > You got 2 Update zips on your SD now. You tried the right one for the new Leak?
Gesendet von meinem XT910
Click to expand...
Click to collapse
Yes I know about that , and have format the SD card i tried again
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
dtrail1 said:
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
Click to expand...
Click to collapse
I try again and again here, Must have a look at the battery status in between. Charge it from exit fastboot mode.
dtrail1 said:
Hey mate, I've tried by myself now. I got the same error like you described. Then I did directly a cache wipe and it succeeded!
Click to expand...
Click to collapse
Hey mate. Have you lost the root permissions? Could you create a step by step?
I tried also to flash the boot_new.img with sdk tools.
Commande: fastboot flash boot boot_new.img
But got this failurebootloader) Preflash validation failure
Failed (remote: )
Something is wrong but what???
Put the etrj fastboot on your Desktop and use the Windows Terminal (cmd)
Works flawless for me...
Gesendet von meinem XT910
TheMask1 said:
I tried also to flash the boot_new.img with sdk tools.
Commande: fastboot flash boot boot_new.img
But got this failurebootloader) Preflash validation failure
Failed (remote: )
Something is wrong but what???
Click to expand...
Click to collapse
Normal fastboot won't work. Use the moto-fastboot or the eprj-mfastboot.
---------- Post added at 08:22 PM ---------- Previous post was at 08:20 PM ----------
SoulGraphicsBrand said:
Hey mate. Have you lost the root permissions? Could you create a step by step?
Click to expand...
Click to collapse
There is already a step-by-step in the other thread wehere you can get the files. And I had no root before so there wasn't anything to loose If you running on rooted leak, you shouldn't flash this one. Search the forums, there is one guy who successful flshed the ICS nandroid backup to his device. This will persist your root.
dtrail1 said:
Read my edit above. But in normal case you must not wipe anything, just flash the system_signed from the 26 fastboot and then apply the update zip from the new leak.
Edit: Also the boot_new.img has to be flashed before applying the update.
Here it is: http://www.mediafire.com/?rh4flyvuo5lej9w
Click to expand...
Click to collapse
Thanks, got the boot_new.img you've linked, but just to be safe (and because I'm confused by the OTA numbering) can you please post a link to the newest OTA I can grab the system_signed from and then use it for the update from recovery?
Also, should I temp unroot and then re-root with the rootkeeper as with the T-mo 4.0.4 OTA update? Is there other way to keep root?
BTW, I've seen you refer to the .26 fastboot (and saying it doesn't have the best radio for Germany where I am at the moment), but the latest leak I've seen mentioned in the other thread is Blur_Version.672.180.17.XT910.Retail.en.EU (Tue May 22 17:20:36 CST 2012). Is it the same build as .26?
Sorry, hit the Thanks Button in Tapatalk
The Radio seems to be better on this ICS. I was on 651.167.26 for an while and the Phone quality was not really good. Tested it today on the Leak and all seems to be fine now.
you need the system_signed from the 651.167.26 to flash the new Leak.
Flash the boot_new.img & the system_signed in AP Fastboot and after that boot in Moto Recovery and flash the Leak.
http://www.handy-faq.de/forum/motorola_razr_forum/249903-motorola_ics_leak_retail_22_05_2012_a.html
Maybe it helps..
YES YES I finished with flashing the new OTA update eu ICS: Blur_Version.651.167.26.XT910.Retail.en.EU
System version 672.180.17.XT910 on my phone.
This is what i do to solved my flashing problems:
1. Used Andriod SDK tool to flash boot_new.img
Command: fastboot flash boot boot_new.img
2. Flashed the SPDREM_U_01.6.5.1-167_SPU-15-M2-3_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot
with Kholks:
EternityProject's RSD Alternative for flashing OFFICIAL Motorola ROMs
Was some failure during the flashing, but system_signed was flashed. .
3. Then I try to install OTA update Blur_Version.651.167.26.XT910.Retail.en.EU directly but failed.
- Then I erased cashe, tried agian, but failed.
- At last I Wipe data and restore then install the update with succes.
I'M so Happy now.
Big big Thanks to HSD-Pilot, DTrail1, Whirleyes, and Spryte
It's a top forum, thanks to all.
Regards
Jan
do you have root?
pty.ltd said:
do you have root?
Click to expand...
Click to collapse
Not now, I flash and reflash so many times before I was up and go, so lost my root
But I'm happy with the newest ICS eu, so I can wait for a root metode later
Related
Intro: Below are the instructions for 3 steps to get Kitkat 4.4 (140.44.3.ghost_att) running on the AT&T moto x with locked bootloaders:
Install full 139.44.44.ghost_att (leaked) rom
Patch the rom to 140.44.3.ghost_att (ota to leak)
Patch the modem to the 140.44.3.ghost_att version
The updates came in stages, otherwise it would not have been my intention for this to be so long and messy. I soon hope to create a single rom and simplify the instructions. Testers can help with the WIP items below...
WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE.
This rom is simply a flashable zip made from the ATT 4.4 leak which will install version 139.44.44. It is intended for the ATT moto x with locked bootloaders, however it should work with an unlocked bootloader if you fastboot flash the included boot.img. The flashable zip does not modify the bootloader or anything besides /system, but the full instructions will wipe out everything.
Prerequisite:
Att moto x with either the .51 (original) or .54 (1st OTA) stock rom
BACKUP ANYTHING YOU DON'T WANT TO LOSE. THESE INSTRUCTIONS WILL WIPE YOUR USERDATA AND SDCARD.
Instructions for ATT moto x with locked bootloader:
root with PwnMyMoto or RockMyMoto (for .51 or .54 respectively, thanks jcase)
install safestrap (thanks Hashcode and Team Win)
download rom to sdcard (motox-att-kitkat-leak-44.zip, link below)
download supersu flashable to sdcard (link below, thanks Chainfire)
enter safestrap recovery (TWRP) and activate the stock-slot
flash rom (motox-att-kitkat-leak-44.zip) to the stock-slot using TWRP recovery
immediately flash supersu using TWRP recovery
within TWRP reboot to bootloader
flash boot.img (included in ROM) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
erase cache: fastboot erase cache
erase userdata: fastboot erase userdata (This wipes everything) This is not necessary. Thanks HeroSon.
powerup normally and enjoy
Update 11/17/2013: I made a patch to safely apply the ota that was received by people running the att 4.4 leak. This will bring the system build up to 140.44.3.ghost_att. The patch script DOES NOT modify anything except /system, and should be safe. The updated kernel (boot.img) is included in the zip. In case something goes wrong, backup your data to be on the safe side. Here are the Instructions:
Complete the installation of the att 4.4 leak (above instructions)
Reinstall safestrap This is not necessary. Thanks HeroSon.
Download the patch to sdcard (motox-140.44.3.ghost_att-ota-safepatch.zip, link below)
Reboot into safestrap recovery (TWRP)
Install the patch (motox-140.44.3.ghost_att-ota-safepatch.zip)
within TWRP reboot to bootloader
flash boot.img (included in the patch) to boot: fastboot flash boot boot.img
flash same boot.img to recovery: fastboot flash recovery boot.img
powerup normally
Update 11/18/2013: I attached a link to the modem patch that will update the 139.44.44 modem to a 140.44.3 modem. I really wanted to create a fastboot flashable NON-HLOS.bin image, but I haven't tested the procedure. Here are the instructions for the modem patch that I have tested:
Download the modem patch to the sdcard (motox-140.44.3.ghost_att-modem-patch.zip, link below)
Fastboot flash NON-HLOS.bin (included within the zip): fastboot flash modem NON-HLOS.bin
erase modemst1: fastboot erase modemst1 (I've done these erases a few times. They are prudent when you flash a modem.)
erase modemst2: fastboot erase modemst2
Reboot into safestrap recovery TWRP
Install the modem patch (motox-140.44.3.ghost_att-modem-patch.zip)
Powerup normally
Notes:
I am running the modem from the .54 ota, and it works with kitkat. I am not sure about the original .51 modem. The 140.44.3 modem is necessary after running patch to 144.44.3. This fixes the settings->security force close.
The safestrap "recovery or continue" screen still appears when you boot. If you erased userdata, reinstall safestrap to get all of the program back.
You should always be able to flash back to stock, as this procedure does not modify your bootloader.
There is a new version of safestrap. These instructions work with either v3.63 and v3.65. (Thanks HeroSon.)
I get a FC in settings->security on the 140.44.3 (patched) version. So far this is the only problem I have noticed. This force close is fixed by the modem patch.
WIP: I would like testers to help with the following:
What happens if you skip step 12 and don't erase useradata (this will keep [more of] safestrap intact)?
How do you remove safestrap manually?
Safestrap has been updated. Does the original 139.44.44 rom now run in a rom slot with 4.2.2 running in the stock-slot? What about the patches? I tried it - doesn't work.
Once 4.4 is installed in the stock-slot, can you backup the stock slot and restore to a rom-slot? (I'm guessing it works this way.) I guessed wrong. This doesn't work. Apparently safestrap needs a bit of tweaking to work with KK.
Is it possible for Safestrap TWRP to flash boot.img to the stock slot? (My experience is that it did not flash boot.img when using a rom-slot)
To clean up this mess, I am considering making a single rom that includes the base 4.4 version with the safepatch included. PM if you want to help by testing this all in one rom once I have it finished. There is a new rom of the official att 4.4.
I have an 100MB ext4 image of /modem. I would like guidance making a fastboot flashable non-HLOS.bin image. (Otherwise I wont be able to combine the leak and the patch.) I see instructions that might work if someone wants to try it and report their findings: http://forum.xda-developers.com/showthread.php?t=1588461 The official att 4.4 SBF includes NON-HLOS.bin
Part of the stock modem procedure is to flash "fsg.mbn", but I have not done that because I have been able to confirm that you can downgrade after flashing it. Can anyone confirm that this is safe on the moto x? (http://forum.xda-developers.com/showthread.php?t=2529569) This works.
139.44.44 rom download : http://www.androidfilehost.com/?fid=23212708291677349
rom patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678076
modem patch to 140.44.3 download: http://www.androidfilehost.com/?fid=23212708291678561
supersu: http://forum.xda-developers.com/showthread.php?t=1538053 (download "CWM / TWRP / MobileODIN installable ZIP")
Original source files: http://rootzwiki.com/topic/107721-att-moto-x-44-leak/ (thanks designgears)
ooo yeah !! Nice job !!
Sa sens le Rooting icite !!
Wish mine was from AT&T, still have one year of warranty....cant see the time when kitkat comes global.
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
How do I do steps 9-12?
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Sent from my XT1053
rubiksmoose said:
Is there any reason why I would have to wipe the SD card? It seems unnecessary. I may test this, but I'm a bit leery given that my Moto X is my daily driver...
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It might work without the wipe. Honestly, I tried this so many times that I quit once I had something that worked... I attributed most of my failures to a incompatibility between safestrap and the 4.4 boot process, but each of those attempts was done to a rom slot and not the stock slot.
Hopefully someone else can 'give it a whirl' and report their findings.
penpen72 said:
How do I do steps 9-12?
Click to expand...
Click to collapse
These steps are done using "FASTBOOT" from a PC while the phone is booted to the bootloader in fastboot mode.
phositadc said:
Does this include the recent ATT 4.4 OTA as well? Or is it just the system images from the original leak?
Click to expand...
Click to collapse
The rom was made from the original leak. I have been thinking about the OTA, but I am unclear how to approach this.
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
penpen72 said:
I am in AP Fastboot Flashmode on the phone what do I need to do now to do the steps? Sorry but I am coming from Samsung and HTC that have never been this hard.
---------- Post added at 02:52 PM ---------- Previous post was at 02:46 PM ----------
Also, my bootloader is locked. I figured I wouldn't have to do the extra steps since you say that it doesn't change those.
Click to expand...
Click to collapse
I assume you are on windows. First you need to download the FASTBOOT.exe program for our Motorola phones, and make sure the fastboot drivers install on your PC. (Maybe someone can help with this link.) Then you can issue the "fastboot ..." commands 9-12 I listed above from your PC with your phone plugged into the PC.
You certainly need to flash /boot, and you should also flash boot to recovery to allow RW access to /system. It might be possible to skip the "erase userdata" step, but that is unclear to me at this moment.
How is the leaked ROM working for you? Worth it? Any bugs or anything?
rubiksmoose said:
How is the leaked ROM working for you? Worth it? Any bugs or anything?
Click to expand...
Click to collapse
Everything is working fine. Take a look here for other people's observations:http://forum.xda-developers.com/showthread.php?t=2517577
There are only two odd things I have noticed. 1) the recent apps screen acts a bit strange when you swipe away apps 2) the transparent status bar becomes less transparent when you go for a drive and the "driving" notification is displayed. It is almost not worth mentioning, and a reboot fixes this issue.
It is hard to answer the "worth it" question. Ultimately, it is a still a smartphone with the same core capabilities, but I enjoy the challenge and the opportunity to learn something.
[edit]I am starting to think that there is additional battery drain vs the .54 ota version. "Wakelock detector" doesn't work, and settings->battery shows "Android System" at the top. This is a 'deal breaker' for me. I'll try and figure out how to apply the 4.4 ota without modifying the bootloader.[/edit]
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
n1ckr0th said:
question. Do you have to reboot the phone into recovery for system write-protect to be turned off the way you do currently, or is it off by default?
Click to expand...
Click to collapse
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Ctrl-Freak said:
When you enter SS recovery (step 4), safestrap will reboot itself if necessary to make sure you are in system rw mode.
Click to expand...
Click to collapse
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
n1ckr0th said:
I'm referring to post install. Currently you must be booted into recovery (normal os with write protect off) for changes to system to stick. is this still the norm with the 4.4 leak, or is WP off while booting normally?
Click to expand...
Click to collapse
Yes. After you have 4.4 working, you must still boot to recovery to enable RW mode on /system. Step 10 ensures you have the 4.4 boot.img in the recovery partition.
(The stock bootloader is still enforcing RO mode for a normal boot.)
I install this and skip step 12 and don't erase useradata. Everything working and all the data still there.
So can I clarify a few things for myself?
You made this by taking the leak files and packaging them into the zip, and it just works with safestrap now? Can you explain what you did to make the leak imgs Safestrap-bootable?
j2cool2012 said:
You made this by taking the leak files and packaging them into the zip,
Click to expand...
Click to collapse
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Can you explain what you did to make the leak imgs Safestrap-bootable?
Click to expand...
Click to collapse
Nothing.
and it just works with safestrap now?
Click to expand...
Click to collapse
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Ctrl-Freak said:
I had to tweak and debug the script, but basically this is the only software part of what I did. To keep things simple, I left out the modem and simply included boot.img within the zip. The rom script does not flash boot.img.
Nothing.
I'm glad you asked these question. First of all I failed to get 4.4 running in a rom-slot - you can read about my methods on this forum...
Finally, it came to me. Hashcode's Safestrap intercepts the boot process so nicely on the stock-slot that the SS:TWRP recovery program is [nearly] as effective as TWRP or CWM running from the recovery partition. Nice work Hashcode! So I made a regular rom that you can flash via safestrap TWRP. This rom only formats and flashes /system to keep things simple.
The only other thing I did was describe a set of instructions that worked for me.
Click to expand...
Click to collapse
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
j2cool2012 said:
Thanks for taking the time to answer. I'm trying to figure out what has been done to see if I can try to do something similar for the VZW moto X using the T-Mobile leak.
Click to expand...
Click to collapse
the Att bloatware and carrier name in notification bar scared me away
Hello,
since last weekend I'm facing a problem on my Razr XT910 where I could need some help.
Configuration of my phone when I noticed the problem:
Jelly Bean 4.1.2 rootet
Safestrap 2.6.3 installed
@ ROM Slot 1: CM 11 4.4.2 installed
When running CM 11 I noticed that I wasn't connected to GSM or 3G I only had a empty symbol for my GSM/3G connectivity. On the first I didn't care about that, cause it happens sometimes that your carrier has problems with his infrastructure. I startet wondering as my wife called me on our home phone and she's using the same carrier as myself.
So I rebooted to stock rom and whoa there I had the same problem. Then I tooked a look into my settings and there I saw, that there is no information about:
- baseband
- imei
- imei sv
- serial number
- apn
Did a search on the net and found a lot of thread containing my problem, but not one with a solution in it.
What I tried so far is:
- Factory reset on both ROM Slot 1 CM11 and Stock Rom
- Deleting and set up new ROM Slot 1 with CM11
- Unbrick using the method of HSD-Pilot (afterwards rooted and installed bmm)
- Unbrick using the RSD Lite method (afterwards rooted and installed bmm)
- Flash bp using the methods bmm (zip and flash firmware method) and fastboot
with bmm (flash firmware method) I get the following error message while flashing:
assert failed: motorola.motoflash(getprop("firmware.path"))
E: Error in /script/radio.zip (Status 7)
Flashing aborted
with bmm (install zip method) I get the following error message while flashing:
E: Error in /ext/Toolz/Radio/Radio.zip (Status 6)
Installation aborted.
using the fastboot method (fastboot flash radio radio.img) seems to work. After rebooting I see the robot with the spinning atom (blue)? a long time with the indicator below then the lying robot with read triangle is shown really short followed by the first robot with the spinning atom - seem revoking the made changes.
I also tried the following cmd before executing the flash cmd
- fastboot erase cache
Right now I think that something with the radio partition (does one exist?) is not ok. Is there a way to reformat everything or what could I do to solve this problem.
Any help? Any more information needed?
Thanks in advance
gripsterg said:
Hello,
since last weekend I'm facing a problem on my Razr XT910 where I could need some help.
Configuration of my phone when I noticed the problem:
Jelly Bean 4.1.2 rootet
Safestrap 2.6.3 installed
@ ROM Slot 1: CM 11 4.4.2 installed
When running CM 11 I noticed that I wasn't connected to GSM or 3G I only had a empty symbol for my GSM/3G connectivity. On the first I didn't care about that, cause it happens sometimes that your carrier has problems with his infrastructure. I startet wondering as my wife called me on our home phone and she's using the same carrier as myself.
So I rebooted to stock rom and whoa there I had the same problem. Then I tooked a look into my settings and there I saw, that there is no information about:
- baseband
- imei
- imei sv
- serial number
- apn
Did a search on the net and found a lot of thread containing my problem, but not one with a solution in it.
What I tried so far is:
- Factory reset on both ROM Slot 1 CM11 and Stock Rom
- Deleting and set up new ROM Slot 1 with CM11
- Unbrick using the method of HSD-Pilot (afterwards rooted and installed bmm)
- Unbrick using the RSD Lite method (afterwards rooted and installed bmm)
- Flash bp using the methods bmm (zip and flash firmware method) and fastboot
with bmm (flash firmware method) I get the following error message while flashing:
assert failed: motorola.motoflash(getprop("firmware.path"))
E: Error in /script/radio.zip (Status 7)
Flashing aborted
with bmm (install zip method) I get the following error message while flashing:
E: Error in /ext/Toolz/Radio/Radio.zip (Status 6)
Installation aborted.
using the fastboot method (fastboot flash radio radio.img) seems to work. After rebooting I see the robot with the spinning atom (blue)? a long time with the indicator below then the lying robot with read triangle is shown really short followed by the first robot with the spinning atom - seem revoking the made changes.
I also tried the following cmd before executing the flash cmd
- fastboot erase cache
Right now I think that something with the radio partition (does one exist?) is not ok. Is there a way to reformat everything or what could I do to solve this problem.
Any help? Any more information needed?
Thanks in advance
Click to expand...
Click to collapse
Have you tried a FULL FLASH of Moto JB? Flash the latest firmware with RSD Lite and and before delete the parts including "emc..." from the xml file because this would erase your whole internal storage (or make a backup on your computer). After that you will have to root, install latest SS (3.72),etc.
Gesendet von meinem XT910 mit Tapatalk
dtrail1 said:
Have you tried a FULL FLASH of Moto JB? Flash the latest firmware with RSD Lite and and before delete the parts including "emc..." from the xml file because this would erase your whole internal storage (or make a backup on your computer). After that you will have to root, install latest SS (3.72),etc.
Gesendet von meinem XT910 mit Tapatalk
Click to expand...
Click to collapse
Do you mean that I use a fastboot file from here Droid Developers - Android 4.1.2 Blur_Version.982.124.14.XT910.Retail.en.EU and flash it with RSD Lite?
If yes, that has been done alreade with no effect
no more ideas for me?
gripsterg said:
no more ideas for me?
Click to expand...
Click to collapse
I had similar issue some months ago and I got if fixed by flashing a radio.img file from an xt912 stock rom I downloaded. I edited d xml file nd deleted all other commands except d line dat contains the flash radio command. Mayb u should give it a shot
Murphyung said:
I had similar issue some months ago and I got if fixed by flashing a radio.img file from an xt912 stock rom I downloaded. I edited d xml file nd deleted all other commands except d line dat contains the flash radio command. Mayb u should give it a shot
Click to expand...
Click to collapse
Did already tried this with the fastboot method and it didn't work - see my first post quote here:
gripsterg said:
using the fastboot method (fastboot flash radio radio.img) seems to work. After rebooting I see the robot with the spinning atom (blue)? a long time with the indicator below then the lying robot with read triangle is shown really short followed by the first robot with the spinning atom - seems revoking the made changes.
Click to expand...
Click to collapse
Hey, i have the same problem. Do you have a solution for this?
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!
Regards,
PoseidonKing
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
boa05 said:
Hello,
I've installed a custom recovery, SuperSU and the xposed framework on my Wileyfox Swift 2 Plus and yesterday I've received an OTA update with wich I was (as expected) unable to update my phone. (it just rebooted to TWRP and did nothing) On their website I was only able to find an older build. I think what I have to do is install the stock recovery(to install the update then switch back to a custom one), but I don't know where to get it from.
Click to expand...
Click to collapse
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
linuxct said:
Here you go. https://drive.google.com/file/d/0B1k2IwBoVgfFVVF1UEY3cUVVY28/view?usp=sharing
I grabbed this from cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87 - flash it via Fastboot preferably.
Click to expand...
Click to collapse
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
E: footer is wrong
E: Signatur verification failed
Installation aborted.
Click to expand...
Click to collapse
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
I haven't checked myself but linuxct seems to say its an img file. You need to flash img files with fastboot. Have you tried unziping the .zip file and seeing if there are img files (e.g system.img, recovery.img)
If you don't know how to use fastboot here is a good tutorial: https://forum.xda-developers.com/showthread.php?t=2277112
Hope this helps.
zerospaced said:
I flashed TWRP so I can install SuperSU for root access
Click to expand...
Click to collapse
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
zerospaced said:
... but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Cyanogen is no more, Wileyfox's switching to an AOSP-based ROM through the following OTAs, which will be Android 7.0 Nougat and will start rolling on february. You've more info here: https://forum.xda-developers.com/swift-2/how-to/official-wileyfox-statement-regarding-t3528844
linuxct said:
You can enable that inside Developer options > Root access. There's no need to either alter your system nor unlock your bootloader if your only concern is root privileges.
Click to expand...
Click to collapse
No, I think that is only there in CyanogenMod (the community based custom rom) not in the Cyanogen OS (the proprietary OS for businesses). As far as I know no OEM can release an android phone with Gapps and root. We have an option there called "OEM unlock" which will allow you to unlock your bootloader (from a computer) but nothing else that would grant root out of box.
zerospaced said:
Exactly the same here. I flashed TWRP so I can install SuperSU for root access, now I've flashed back the stock recovery to apply the update and it ends in "Error".
It's also not possible to apply the downloaded zip-package manually (not via TWRP and not via Cyanogen recovery).
Log file says:
It's not an option for me to do a full reset each time they (who ever it might be in the future) release an update.
I bought this phone because I thought it might be easier to update/ get root access compared with e.g. Samsung devices, but in the end I must say Cyanogen OS is really bad and I hope there will be some mods soon, so I can get these bad/restrictive stock-OS off my phone...
Click to expand...
Click to collapse
Just flashing back to the stock recovery does not remove SuperSU. Due to your error I'm assuming you have a non-systemless root. In order to remove SuperSU you must flash http://downloadmirror.co/Uot/UPDATE-unSU.zip (with TWRP), and if that doesn't work I would recommend flashing back to full stock cyngn from: https://cyngn.com/support.
Cheers!
linuxct said:
You mean, a Cid face? LOL
You can revert by flashing the system.img via fastboot from the very same zip I mentioned before. You can get it here: http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
boa05 said:
Thank you very much, I've installed the stock recovery and also uninstalled xposed framework and SuperSU so the System partition would be clean but when trying to update I get a derpy android with the text: ERROR. Does anyone know how can I fully revert to stock so I can install the update, would a factory reset solve my problem?
Click to expand...
Click to collapse
boa05 said:
Thank you very much, flashing the system.img with
Code:
fastboot flash system system.img
fixed the issue and I was able to update my system to the latest version and since it only changed the system partition, no data (files from internal/external storage) nor apps (not even their data) were deleted. After the update I had to flash TWRP, SuperSU and Xposed again.
Click to expand...
Click to collapse
Thank you, but unfortunately I've read this hint after trying the unsu method described here:
https://forum.xda-developers.com/showpost.php?p=63615067
I've installed the unsu-zip package and flashed the original boot.img via TWRP. It did not help, but since I did this I have another warning message when booting: "The dm-verity is not started in enforcing mode."
In the end I managed to get the update by installing the original zip package again and after this the OTA update worked.
What still remains is the new "dm-verity error message" right after booting....
Does anyone know if there is anywhere I can find the files to manually update to the new AOSP based ROM. Or has Wileyfox not released it?
(Or has anyone captured the PTA link?)
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
rivierakid said:
There is currently no new AOSP ROM. I've received only Cyanogen OS update (probably the last one?). According the Wileyfox statement on facebook, the new ROM (Nougat) will be released in the february...
Click to expand...
Click to collapse
Nah they are releasing an update first to transition to their new rom.
"We have been ruthlessly testing this and planning a distribution for this update, with a rollout to be released beginning today with immediate effect." -Wileyfox Facebook
Click to expand...
Click to collapse
Then later (between February and end of Q1) they will release nougat. Its an easy mistake to make as they aren't too clear about it.
Thanks anyway.
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
The new update
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
I don't think it'd be a good idea to mess with the bootloader for now. Also, I uninstalled SuperSU from the app. If you have xposed I suggest you uninstall that too (At least that's what I did). Sorry I can't help more I 'm still a little newby myself.
rivierakid said:
It is unclear what kind of ROM will they release. According the statement it should be bloatware free OS
AOSP, Lineage OS, something else?
I really like cyanogenmod, so I hope there will be Lineage OS ROM in the future...
Click to expand...
Click to collapse
Sadly, an OEM cannot rely on community-driven software, so it surely won't be CyanogenMod/Lineage. But, that doesn't mean that in the future we wouldn't be able to enjoy it thanks to custom ROM development
Jahane said:
Hi, I'm not in the least technologically minded so please don't take the mick when I ask, will the new update delete the cyanogen os? Or is that something I will have to do? If so, what is safe to delete without damaging my phone?
Wow, that was a couple more questions then I had thought!
Thanks all.
Click to expand...
Click to collapse
Welcome to the community!
This depends on what you understand about 'new update'. If the new update you're talking about is the currently rolling OTA, the one that's getting prompted on every phone right now, no, that won't delete CyanogenOS yet, but prepare the device to upgrade to a CyanogenOS-free Android 7.0 ROM, which will happen in a month or so. You won't have to do anything but let the phone update each and every single time it requests it. Cyanogen itself is not something you can remove as a user, unless you install what's called a custom ROM (this means, a different ROM software than the one provided by Wileyfox), so, you don't need to worry about it but keeping your device up-to-date as soon as it prompts you with an update ^_^
MCPoppa said:
Hello,
iam very frustrated by this OTA thing..
I had TWRP and SuperSU installed and i've tried everything but I can't install this OTA -.-" everytime i've tried it it gives me just an "ERROR".
1. I flashed the unSU zip in twrp.
2. I set the switch for stock recovery in developer options.
3 I fastboot flashed the stock recovery.img
4 I fastboot flashed the stock system.img
Then rebooted and did the update it just runs to like 20% and stops and then it shows me "ERROR" ..
Can somebody experienced help me pls This update is annoying I had to block it out of my mobile data use because it would eat up all my mobile data
EDIT: Maybe I have to relock my bootloader?
Click to expand...
Click to collapse
Try relocking like you said, but before, flash everything included in the latest CyanogenOS fasboot image zip (from here). To flash all of them at once, execute each and every of the following commands:
Code:
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash devcfg devcfg.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash keymaster keymaster.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash splash splash.img
fastboot flash tz tz.mbn
Once done, relock your bootloader by doing:
Code:
fastboot oem lock
Please note, this probably doesn't fully lock your bootloader, as some propietary DRM keys might've been lost during the unlock process...
Good luck and please, keep us posted!
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
matt1515 said:
https://android.googleapis.com/pack.../e7adc4a02314908bfdc7a3eea85214e67b4e8e39.zip
Enjoy
Click to expand...
Click to collapse
Is this a full or incremental OTA?!
I know that it's a big file, but still...
Sent from my Nexus 6P using Tapatalk
https://developer.android.com/preview/download-712.html
Still nothing...
Sent from my Nexus 6P using Tapatalk
xdatastic said:
Please could you post the build.prop. I'm interested in the ro.build.date of the beta.
Click to expand...
Click to collapse
Here you go
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Is this ota or full image?
I usually flash full images with flashfire
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
thegios said:
Is this ota or full image?
I usually flash full images with flashfire
Click to expand...
Click to collapse
OTA. There is a working TWRP flashable zip here.
Thanks but gonna wait for full image to be uploaded by Google on beta site
SubuHyd said:
I got the same error. I was hoping this build would get me out of the bootloop that N4F260 has me stuck in.
Click to expand...
Click to collapse
Try formatting cache and then factory reset in recovery and see if it boots (assume you have locked bootloader). If no boot try and sideload this again. Might work if not try full OTA zip when released good luck hope you get it figured out
matt1515 said:
Also I wasn't able to get this OTA to install via ADB sideload. Failed at
"serving: 'update.zip' (~47℅) * failed to read command: No error
Even after flashing stock system, boot, recovery, and vendor. Just wondering if anyone got it to work I noticed when installing the beta through Google's intended process it seemed to have a three part process and rebooted each step.
Click to expand...
Click to collapse
Those of you getting errors, did you happen to check the SHA-1 hash of the downloaded OTA file? It should match the file name (E7ADC4A02314908BFDC7A3EEA85214E67B4E8E39). I downloaded it just to check, not going to install myself due to no new features. Weird that Google is going with the SHA1 hash on this as recently Google has been using SHA256.
Also, are you using most recent version of Platform Tools, 25.0.3? https://developer.android.com/studio/releases/platform-tools.html
Flash this .zip ， need modify updater.script。fastboot lock couldn't flash it
When you sideload ,the script run
package_extract_file("recovery-two-step.img", "/dev/block/platform/soc.0/f9824900.sdhci/by-name/boot");
set_stage("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "2/3");
reboot_now("/dev/block/platform/soc.0/f9824900.sdhci/by-name/misc", "");
Click to expand...
Click to collapse
But after reboot . it isn't continue. I think because recovery couldn't find zip file.. but it is flashing recovery to boot .
Hi guys
Can't install any OS (tried via ADB commands and flashing custom roms via TWRP).
Whatever I try, it just boots to TWRP.
ADB commands do work because I managed to install TWRP 3.0 and 3.1 for the Moto Z Griffin
Bootloader is unlocked
This device was working fine on Stock Noughat (installed via ADB) and AOKP (installed via TWRP).
Problems began when the camera "failed to start" and in my frustration, I wiped everything via TWRP including system, so now I have no OS.
Not sure why I can't get anything to install.
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
grneyez said:
Follow this guide: https://forum.xda-developers.com/showthread.php?t=3506342
Sent from my XT1650 using XDA-Developers Legacy app
Click to expand...
Click to collapse
followed that guide
Had this working for months and needed to wipe so I did a factory reset and all my phone does is boot to twrp
I tried this process again and all goes good or so it seems but just boots to twrp
I tried a restore from my backup from twrp and get all the way done and it fails on "unable to wipe Fsg."
Above there is a bunch of red failed:
Could not mount /data and unable to find crypto foooter
Failed to mount '/data' (Invalid argument)
Unable to recreate /data/media folder
Failed to mount'/cache' (invalid argument)
failed to mount'/system'(invalid argument)
Failed to mount storage
failed to mount'/data'(invalid argument)
failed to mount'/cache'(invalid argument)
failed to mount'/data/media/twrp'(invalid argument)
unable to wipe fsg.
any ideas? right now just a brick here. i have tried flashing roms from twrp and still just boot to twrp
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
D13H4RD2L1V3 said:
I'm assuming you tried to flash the stock ROM via fastboot?
If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below;
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
And grab the firmware for your device here;
https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Make sure it's the correct firmware for your device. If you updated to Nougat via an OTA, you have to flash a Nougat ROM. You may also use the one linked in the XDA article, although I can't guarantee its stability.
Click to expand...
Click to collapse
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
royalflush5 said:
Maybe it's because I haven't had my coffee yet, but is there a US 7.0 file on that site? I can only find the 6.0 version. I'm on Rodgers nougat rom I flashed a couple weeks ago and I'd like to get on the US version since I've been having apn issues
Click to expand...
Click to collapse
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
D13H4RD2L1V3 said:
Sadly, no.
As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.
Click to expand...
Click to collapse
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
royalflush5 said:
Ah, thanks for confirming. Do you happen to know of a twrp flashable zip for retus 7.0 then?
Click to expand...
Click to collapse
Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS.
There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable.
https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
raymccoy said:
Thank you for this!!!!!!! It solved my boot loop problem too after installing stock via fastboot. Only thing that worked.
Click to expand...
Click to collapse
thanks for the Rescue same trick work for me though as i was been stuck on TWRP after flashing stock firmware via fastboot , so i manage to flash irfan v4 stock rom and booted to factory image to get it resolved , But now i want to move to complete stock without twrp as i think Oreo update is near by but i get the same issue again, Just wanna ask can u help me out with the process to go back to stock Rom
lovetatfitties said:
I know this thread is old but maybe this will help someone out. I had the exact same problem after a Factory Reset my phone went on a TWRP bootloop. To resolve it, just reboot into Bootloader and then select Factory Mode. My phone just started as new.
Click to expand...
Click to collapse
that worked for me also, but it's not a fix, its a workaround. is there an actual fix for this? I've tried the Verity_FE_patcher but that didn't work also.