Database Users

updateing to cyanogenmod update-cm-4.2.7.1

Hallo,
I've been trying to install the updated to update-cm-4.2.7.1-signed.zip.
I've been able to install first the signed-dream_devphone_userdebug-ota-14721.zip and imediatly after that, without reboot, the update-cm-4.2.7.1-signed.zip. Only I was unable to sign in to google right after that so I rebooted and then I was unable to boot it any longer...
Ok so then I retried the whole process but now after flashing the first signed-dream_devphone_userdebug-ota-14721.zip, wich goes ok, the second update-cm-4.2.7.1-signed.zip aborts the installation...
Next to it the installation of signed-dream_devphone_userdebug-ota-14721.zip isn't stable at all... after max one minute the phone crashes, so I'm unable to do anything....
I'm feeling extremely NOOOOOOBY!!!...
Which is probably how I'm supposed to feel...
Uuuugh....
Anyways is there anyone with hints about what I'm doing wrong here?
Thanks!
Greetings,
Geert

did u do a full wipe from CM recovery before putting on the google updates then cyanogen??? i had this issue and it fixes it?

Sorry for the late reply...
I tried to flash the recovery image of cyanogen but itś not possible anymore....
There is no flash_image tool on signed-dream_devphone_userdebug-ota-14721.zip...

Also using fastboot, it says < waiting for device > till eternity...

my advice would be to start from scratch, get dreaming.nbh on ur sdcard. follow the instructions @ cyanogens wiki
i was having a world of **** on my G1 and just went back to RC29/RC7 and started again. if you have the files already on the SD card (CM recovery, official google, latest cyanogen mod) its simply a case of a few key presses.
dont forget to do the telnetd stage. i did and then wondered why i didnt have root access lol
ive never bothered with fastboot, usually just use ADB!
r|ktk|ng

[Q] N910F rooting/room issues

Sooo, I'm new to rooting a note 4. I have the the international version, rooting is no issue now... I can do that quite quickly.
My issue is flashing a new from via TWRP. No matter what I do it fails everything, last night I managed to load CM12 but it just stayed in a bootloop for over 30minutes. I just restored it to factory. I thought maybe I'm not destined to have cyanageonmod
Anyways I found another decent room called Beanstalk, it seems like a pretty solid room (thoughts?) but when I go to flash the zip file it just says it can't mouth the file from what ever drive.
What am I doing wrong? I wiping the four things I'm meant to delete before I flash and still nothing
My phone: N910F running on 5.0.1
Baseband:n910fxxuibob4
Ive looked at ever forum possible but can't see what's wrong? I've also tried 3 different versions of Cm12 from different developers that are meant to work...
So again where am I going wrong?
If this is in the wrong place I am sorry! Could I be pointed in the right direction

did you follow instructions for installing and what to do after installing the roms?

xdm9mm said:
did you follow instructions for installing and what to do after installing the roms?
Click to expand...
Click to collapse
Yes followed the instructions like I was doing brain surgery! After... With CM12 it booted up and just kept going around in circles or about an hour, I left it because I thought I needed to, I have up an reverted back. With beanstalk I just got a message in TWRP saying failed to mount on e:/ or something like that.

Anyone have a clue what in doing wrong? I'm going crazy not being able to flash anything. Even a stable build of something. I'm 100% sure what I've downloaded is compatible but still nothing. Either bootlooping or having mount issues.
(bumps are probably not allowed but I've been trying this for 3 days and I'm not where)

How to update from build MDA89D to MDB08K?

The moment I opened my phone I quickly unlocked the bootloader and rooted my device without realizing there is a newer build out.
I tried flashing in through recovery but every time I do it seems to corrupt my device and im forced to recover from my backup. Ive been out of the android modding for a little while so maybe im missing a step. Can someone point me in the right direction.

Avenue Blue said:
The moment I opened my phone I quickly unlocked the bootloader and rooted my device without realizing there is a newer build out.
I tried flashing in through recovery but every time I do it seems to corrupt my device and im forced to recover from my backup. Ive been out of the android modding for a little while so maybe im missing a step. Can someone point me in the right direction.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159 install this on pc press 06 then 11 then 4 let it do its thing and your good or just flash a rom

jaythenut said:
http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159 install this on pc press 06 then 11 then 4 let it do its thing and your good or just flash a rom
Click to expand...
Click to collapse
This brings me to the unroot menu but it seems that most of the options are disabled, option 6 which says it will unroot fails when booting into twrp
edit: spoke too soon, it worked the second time
now the ota is gone and it says my phone is update date. should I just proceed with flashing it anyways?
edit: when attempting to side load through stock recovery the toolkit stops detecting my phone is connected. This is annoying
edit: got it to side load but its failing now due to "E:footer is wrong" and "E:signature verification failed"

Please help

I unlocked my bootloader and rooted all went well. I flashed Z.A.D Rom and all was good. i decided to give CM 13 a try so I made a backup in TWRP (checked all boxes to back up everything) flashed CM13 played around with it for a bit didnt like it so I went back to TWRP wiped everything and restored my back up. When the phone booted back up got message NO SIM and my wifi wouldn't work. So I thought maybe a bad flash I'll try to restore my back up again. Same results no sim and no wifi. So I Tried to flash CM 13 again because that was the last thing that worked. That now freezes at boot then power downs the phone (tried everything to get it to boot). So I then tried to Flash the Boot stack again and stock rom. That will boot but again no sim and no wifi. I'm at a loss right now and dont know what else to try. Can someone please help me.

killathenoob said:
I unlocked my bootloader and rooted all went well. I flashed Z.A.D Rom and all was good. i decided to give CM 13 a try so I made a backup in TWRP (checked all boxes to back up everything) flashed CM13 played around with it for a bit didnt like it so I went back to TWRP wiped everything and restored my back up. When the phone booted back up got message NO SIM and my wifi wouldn't work. So I thought maybe a bad flash I'll try to restore my back up again. Same results no sim and no wifi. So I Tried to flash CM 13 again because that was the last thing that worked. That now freezes at boot then power downs the phone (tried everything to get it to boot). So I then tried to Flash the Boot stack again and stock rom. That will boot but again no sim and no wifi. I'm at a loss right now and dont know what else to try. Can someone please help me.
Click to expand...
Click to collapse
To answer your own question, a simple search in the Q&A section will help you.
You might want to grab version B20 and roll back, on the bottom left of the page select "Software Updates"
https://www.zteusa.com/axon-7#support
Then follow this thread to use the proper commands:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544

killer23d said:
To answer your own question, a simple search in the Q&A section will help you.
You might want to grab version B20 and roll back, on the bottom left of the page select "Software Updates"
https://www.zteusa.com/axon-7#support
Then follow this thread to use the proper commands:
http://forum.xda-developers.com/axon-7/how-to/please-check-wifi-flashing-bootloops-t3451544
Click to expand...
Click to collapse
I dont know how i didnt find that I searched every section of this fourm I was trying everything for about 5 hours last night. But thank you very much i will do this now.

OTA Installation Problem

So I rooted my phone following this tutorial :-
https://www.google.co.in/amp/s/foru...1-oreo-8-0-disabling-ota-magisk-t3728654/amp/
And then I subsequently followed the steps in the guide linked in that tutorial which tells you what to do when an OTA arrives. (Basically, it says to revert back to stock boot image from within magisk and then let the OTA install as is.)
The problem I face is - the OTA downloads normally but then as soon as it starts installation process step 1, an immediate error is thrown saying "Installation Problem". I'm sure that most of you are familiar with this error but then I don't know how to resolve it.
One thing I might have done which could have caused this but I ain't sure - I updated Magisk from within the app. In an earlier rooting tutorial, I remember seeing a warning to never update Magisk from within the app but I never got around to knowing why. However, this tutorial didn't mention anything of the sort, so I went ahead and did it.
As it stands now, I have the January patch waiting in the notifications panel but I don't know how to proceed. Flashfire doesn't work either, I tried.
Any fixes?

anirbannath said:
As it stands now, I have the January patch waiting in the notifications panel but I don't know how to proceed. Flashfire doesn't work either, I tried.
Any fixes?
Click to expand...
Click to collapse
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .

black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
Hi. I had already tried this before posting the question but the problem that occurred then was that the December 29 update is actually Android N as far as I remember. For some reason, whenever I try dirty flashing Android N from Android O, my phone goes into boot loop. The thing is I don't want to flash any more ROMs because that tutorial said that I don't have to. Otherwise, I am aware that that is the standard procedure.
I simply want OTA to work as it says in the tutorial. That's all. But thanks anyway.
By the way, I forgot to mention this - I am currently on the buggy (stable) version of Android O that was released on December 31st. The update that I am waiting on is the 89 MB patch that was released last week.

anirbannath said:
Hi. I had already tried this before posting the question but the problem that occurred then was that the December 29 update is actually Android N as far as I remember. For some reason, whenever I try dirty flashing Android N from Android O, my phone goes into boot loop. The thing is I don't want to flash any more ROMs because that tutorial said that I don't have to. Otherwise, I am aware that that is the standard procedure.
I simply want OTA to work as it says in the tutorial. That's all. But thanks anyway.
By the way, I forgot to mention this - I am currently on the buggy (stable) version of Android O that was released on December 31st. The update that I am waiting on is the 89 MB patch that was released last week.
Click to expand...
Click to collapse
Hello:
When I mean December 29th I was mencionating the compilation day (7.12.29 in this case) hovewer the December 31st is the same as the 29th just the release date or the compilation day are the difference. Anyway here you have the December 29th Oreo fastboot rom. It's the same that was release for a few hours in the official site if you want to give it a try. Good luck!

Exactly same problem here
So I restored original bootimage, relocked the phone through fastboot and tried again
But... Now the OTA disappeared
Just waiting a few days to see If It appears again
---------- Post added at 02:14 PM ---------- Previous post was at 01:39 PM ----------
black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
Could you install january patch successfully?

Fusquinha77 said:
Could you install january patch successfully?
Click to expand...
Click to collapse
Hello:
Yeah I have the january patch installed, I just fully unistalled magisk(boot image and app too) and flashed December 29th oreo patch saving user data with the .bat included in the fastboot ROM, when installed looked for the January Patch, installed it and I rooted my device an again.
If you don't have the Oreo image of the December 29th you can download it from here

black_arashi said:
Hello:
I had the same problem, exactly don't know why, I could fix it flashing december 29 again saving user data using the .bat gave in the fastboot rom (You can do it with MiFlash if you want), give it a try, maybe this solution could be your salvation .
Click to expand...
Click to collapse
black_arashi said:
Hello:
Yeah I have the january patch installed, I just fully unistalled magisk(boot image and app too) and flashed December 29th oreo patch saving user data with the .bat included in the fastboot ROM, when installed looked for the January Patch, installed it and I rooted my device an again.
If you don't have the Oreo image of the December 29th you can download it from here
Click to expand...
Click to collapse
Successfully fastbooted Dec 31 Oreo. But no OTA...
Will wait 2 days. Otherwise I'll install the TWRP version.

Still no January OTA here.
Does anyone facing the same problem?

Received the OTA today again
Jan patch, 89 MB
Fully uninstalled Magisk, rebooted, and updated successfully