I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
HopperPlaysMC said:
I have a Moto G (XT1032) and it seems to be stuck somewhat in a bootloop. The reason I say this is because I can get into fastboot, go into recovery, and sometimes it will get to the "M" but nowhere past that. On a normal boot up, it will get to the "BOOTLOADER UNLOCKED" screen (yes I have unlocked bootloader and rooted), and that's it. I believe this happened because I was trying to flash Android 5.0.1 to the device because it wasn't available yet. Thanks in advance for any help, and if you need more information just ask. The last thing I want to do is have to send it in.
Click to expand...
Click to collapse
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
dustcollector69 said:
What did it say when you tried installing 5.0? Have you tried clearing cache/dalvik?
Click to expand...
Click to collapse
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
HopperPlaysMC said:
I have tried installing cache/dalvik, and when installing 5.0, it would have an issue installing because of updater-script. On my phone (in recovery mode sideloading from adb) it would say "Installation aborted"
Click to expand...
Click to collapse
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
dustcollector69 said:
Hmm, im not sure why it would say that.. Did you format system before flashing?If you don't mind losing data you could always reflash stock firmware through fastboot in the bootloader
Click to expand...
Click to collapse
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
I'm also going to try sideloading 5.0 again after clearing dalvik/cache again.
HopperPlaysMC said:
I formatted before installing. I know it's problem with my phone because the Android 5 is for GPE and I have a falcon version Moto G. I know there is a way to bypass it though. I don't mind losing data either as I had to anyway to unlock the bootloader.
Click to expand...
Click to collapse
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Will give it a try, but if not I will tell you what I see after trying to sideload to 5.
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Got GPE 4.4.4 running, I shall now try 5.0.1
dustcollector69 said:
oh, if your device isnt converted to a GPE edition then that is probably why because it uses different filesystems. follow this guide to restore your firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
HopperPlaysMC said:
Ok, so at least my phone is working, but I can't sideload 5 onto my device. Here is what I see on the phone after the CMD reaches 100%:
Code:
Restarting adbd...
status 0
Finding update package...
Opening update package...
E: Can't open /tmp/update.zip
(bad)
Installation aborted.
If you can help me with this, I would be grateful.
Click to expand...
Click to collapse
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
probably its corrupted, try download the ota from settings menu and tell us
esd316 said:
probably its corrupted, try download the ota from settings menu and tell us
Click to expand...
Click to collapse
OTA isn't showing up, but it may be corrupted
dustcollector69 said:
thats good you at least got your phone working, can you send me the link to the zip your trying to install? are you sure its not corrupted?
Click to expand...
Click to collapse
Here's the link: goo.gl/zDJG9q (That'll directly download it)
HopperPlaysMC said:
Here's the link: goo.gl/zDJG9q (That'll directly download it)
Click to expand...
Click to collapse
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
dustcollector69 said:
im downloading now, will check it out in a bit
why dont you flash one of these zips instead and through a custom recovery though?
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
I have clockwork recovery, I will attempt to flash one of those later.
All of the ROMs for my phone on http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 are Brazilian.
Yep flash a stock rom for xt1032 (try a optimized) and that should work
esd316 said:
Yep flash a stock rom for xt1032 (try a optimized) and that should work
Click to expand...
Click to collapse
Can you link me one? Or do i just do a Brazilian one?
Tried installing the Brazilian one and... my phone is messed up again and I have no idea how I fixed it. Help again?
Related
The phone is a normal first gen moto g 8gb which i tried to turn into a gpe phone to get lollipop but failed....
This is the boot loop: http://i.imgur.com/LXHY7D3.jpg
Lucky i can still get into fastboot: http://i.imgur.com/869jRVD.jpg
And recovery is: http://i.imgur.com/CV0QuOw.jpg
i have the right software and firmware i need to flash i just can't get into adb mode something is wrong with recovery.. i guess..
To fix the issue, I recommend using fastboot commands to flash a stock 4.4.4 ROM and then check for 5.02 OTA updates for the stock ROM.
Awesome idea any decent guides on here for this? My searches fail
Flashing stock: http://forum.xda-developers.com/showthread.php?t=2542219
Possible source for ROM: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
audit13 said:
Flashing stock: http://forum.xda-developers.com/showthread.php?t=2542219
Possible source for ROM: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1
Click to expand...
Click to collapse
should i use:
XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml
or
XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml
i'm in England (so both eu and gb apply) so really not sure which.... i guess i'll try gb first
You could try either one if they are made for the xt1032 you have.
audit13 said:
You could try either one if they are made for the xt1032 you have.
Click to expand...
Click to collapse
I chose 'gb' and excellent i'm now on a working firmware for the first time in a month+ so i thank you for that i really do
next problem is it's 4.4.4 and not lollipop and says it's 'up to date' when i check for an update boo.. how do i get lollipop?
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
audit13 said:
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
Click to expand...
Click to collapse
no i did not... doing that now :fingers-crossed::good:
audit13 said:
Did you log into the Play store and update all Motorola apps, particulary Motorola Update services? You must be unrooted and running stock recovery in order for the update to install.
Click to expand...
Click to collapse
i sure did i had stock recovery and logged into my Google account and updated ALL apps in the play store and rebooted a couple time but still no update when i checked
i then manually searched for 'Motorola Update services' and it guess what? it needs an update yet it's not in the 'my apps' list in the play store? odd.. but anyway i updated it... then tried a manual update and boom 5.02
let see if it all installs ok.. is there any xposed for lollipop/art yet? even alpha/beta/etc?
Everything worked perfectly thank you
http://i.imgur.com/qGnVRmj.jpg
one last problem it seems no mater what recovery i install it just causes 'wavy lines on the screen' :/
my phone: http://i.imgur.com/fHs9rrD.jpg
The lines are due to the custom recovery not fully supporting the lollipop bootloader. Keep checking the recovery thread for updates.
The lines should not appear with stock recovery.
Sorry to be a pain but do you have links to both? I'm on mobile atm
Sorry, I don't have a link for the stock recovery.
Here's a link for TWRP: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Link for Philz Touch Recovery: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon/
I got it working then i broke it again
I got everything setup and played with lollipop extensively and really liked it although 'over the hood' very little has changed (mostly the notification panel)
I then decided I'd try to install the xposed alpha and boom dead phone :/
No big deal i thought I'll just do the same 4.4.4 install i originally did via fastboot but now I'm stuck at a boot loop
I think the flash memory is corrupted
Fastboot and custom recovery if course still work but when i try to do simple things like clear cache/dalvik i get file system errors like crazy: http://imgur.com/a/wc75k
Any ideas what i can do next?
Edit: added pics
Sorry. Maybe it's brick.
Fastboot commands don't work to re-install stock 4.4.4?
Maybe u fixed it already but here is a guide to repair ur phone. http://forum.xda-developers.com/showthread.php?t=2542219 worked for me too.
HI all, I have CM12 installed on my rooted phone and this morning when I switched it on, I got a message saying:
"WARNING: Update Cyanogen recovery is disabled. This may cause issues with updating your device. Please enable Update Cyanogen recovery in developer options"
Now, that option is off because I have my custom recovery TWRP installed on the phone, I'd like to keep that and I don't want to reinstall it after the update, so I believe I should ignore the message, but what I wanted to check with you guys is whether ignoring it will in fact cause any issues as this is the first time ever I've seen this message (this update by the way I think is the first one after installing CM12).
Any idea?
thanks
Disregard the message.
Thanks Heisenberg,
I did that but when the phone restarts trying to install the update, it goes straight into recovery mode (TWRP) and from there I don't think I can install the update, as none of the options seem to allow me to do so, see screenshot http://s23.postimg.org/6d6s7wyq3/IMG_20150625_135453.jpg
All right, I downloaded the zip from here http://cyanogen-ota-bacon.somee.com/ and tried to flash it from TWRP, but I get an error, screenshot here http://s28.postimg.org/zb06wtcpp/OTA_error.jpg, any idea why?
Same here, got an error in TWRP logs that prevented the update to install.
I'd like to avoid reflashing stock recovery only to install the update...
Heres the log: http://s29.postimg.org/njqqqlfc7/Screenshot_2015_06_25_08_49_42.png
Seems something related to outdated "build fingerprint" my device has currently 12.0-YNG1TAS17L
I guess the alternative would be to do it thru Cyanogen Recovery, but let's see what more knowledgeable members have to say as, like you, I don't want to have to reinstall TWRP and SU just for the sake of the update
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Thanks for clarifying that davebugyi, then so be it, I'll do it thru cyanogen recovery and then reflash TWRP and probably SU as well
thanks
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
davebugyi said:
Looks like you cant use the official update with TWRP. Either flash it via cyanogen recovery then flash back TWRP, or use a differnt zip for update not the official
Click to expand...
Click to collapse
duratto said:
Ah, sorry forgot to ask, is there an unofficial update? If so where do I get it from?
Click to expand...
Click to collapse
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
thanks! Ah OK I see so that's the whole ROM there as opposed to just an update
davebugyi said:
For example here: http://forum.xda-developers.com/showthread.php?t=2810365
Click to expand...
Click to collapse
Do you mean flashing only this update found at the end of the first post?
YNG1TAS2I3 Radio, etc - Mirror - Same as YNG1TAS0YL
md5 - 6d5db5af6c92b814b9a0ebd18341dd8e
Click to expand...
Click to collapse
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Yes, but if I'm not mistaken, judging from the file size, that's the whole ROM
tsnake said:
Do you mean flashing only this update found at the end of the first post?
Is it safe to flash only that zip from TWRP over the stock Cyanogen OS?
Click to expand...
Click to collapse
The file I quoted is not a whole ROM, it's 31 MB.
AH OK, sorry I thught you referred to the 500mb file
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
I'm having the same issue. Anyone?
Got the same problem. Any idea?
duratto said:
Apparently even by enabling cyanogen recovery, I still can't get the updated installed as the phone keeps rebooting in the TWRP recovery, which is very odd.
Click to expand...
Click to collapse
Bump for a fix?
Juergen1337 said:
Got the same problem. Any idea?
Click to expand...
Click to collapse
The solution seems to be installing the new ROM provided. Related problem here http://forum.xda-developers.com/oneplus-one/help/twrp-cm-android-version-mismatch-t3147658
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
The only error I got, was that it's impossible to boot. I'll try your guide asap
Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.
This guy has the exact same problem.
erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help
The latest update, it seems, can be rooted using the recowvery method. Dirtycow was patched by Google in a Dec. 5 security patch, but it seems LG didn't include that in their latest security update, which was created Dec 1! In any case, my phone is rooted with TWRP, and working just fine. So, for now we can still root with the update! I'd also like to point out, that this means we now have an official KDZ released version of rootable stock to roll-back to with LGUP!
Glad I forced ya to do it huh
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Norcal232001 said:
What method are you trying?
Follow instructions on this thread https://forum.xda-developers.com/v2...owvery-unlock-v20-root-shell-t3490594/page118
It works as kibmikey stated.
Click to expand...
Click to collapse
Ive been using easyrecowvery but ive tried that also. Maybe I messed up somewhere during the command line process thingy. Ill give it another go. Thanks
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
dimm0k said:
curious, if I'm currently rooted on H91810d, how can I get to a rooted H91810i? would like to make the move without getting my /data encrypted once root is lost...
Click to expand...
Click to collapse
I was on 10i last week after i got phone back from service. I flashed NotSoStock Rom which said i was on the 10d base. Then flashed Overdrive Rom which put me back to 10i. I didnt have any problems switching basebands within custom roms if that helps.
ahq1216 said:
How? I've tried multiple times and it would go through but upon booting into recovery i would get a 'no command' error
Click to expand...
Click to collapse
I have same error even I tried to enter recovery using "adb reboot recovery"
---- edit ----
Done.
You must do it manually according to the instructions
https://github.com/jcadduono/android_external_dirtycow#running
https://forum.xda-developers.com/v20/development/h918-recowvery-unlock-v20-root-shell-t3490594
Note: make sure you rename your TWRP to twrp.img, and put SuperSU file into memory card (your TWRP cannot open internal storage).
how do you unroot and go to full stock
dudeawsome said:
how do you unroot and go to full stock
Click to expand...
Click to collapse
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
mingkee said:
Since I have required 10i kdz and dll, I just flash it with LGUP as upgrade.
Click to expand...
Click to collapse
Wil it remove twrp also and have you tested it
dudeawsome said:
Wil it remove twrp also and have you tested it
Click to expand...
Click to collapse
100% bone stock
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC