Database Users

Anyplace to track CM7 issues for glacier and other phones

The official bug tracker for Cyanogen only lists up to version 6.1.2. It would be nice if there was a place where we could go that allowed us to search for open issues or problems by nightly build number, and phone platform.
Not necessarily a bug tracker for the devs to use since they have their own methodology, but something that end users could use to determine at what point they would take the plunge and install CM7.
Reading through hundreds of pages of posts and figuring out what is and isn't an issue is nearly impossible.
Thoughts?

dude....nightlies are for testing purposes only. no changelogs. no bug submissions. flash at your own risk. some of the problems are rom related some aren't. wait for an RC if you want something stable with a changelog.

I'm talking something unofficial. Reading through 300+ pages of forum posts to figure out if people are having good luck with a build is a huge PITA.
I'm fine with running nightlies, but I don't have the time to read for an hour+ every day to figure out whether or not it's worth upgrading to the newest nightly because something might work better, or if additional features were added. Or maybe some build just completely horks the phone...
I'll agree that it's all in one thread for the most part, but it's still extremely time-consuming to read through it all.
I guess even something as simple as:
- 3282 users like this build
- 234 users hate this build
-- 93% Positive
It would probably have to be split out by platform also.

signal15 said:
I'm talking something unofficial. Reading through 300+ pages of forum posts to figure out if people are having good luck with a build is a huge PITA.
I'm fine with running nightlies, but I don't have the time to read for an hour+ every day to figure out whether or not it's worth upgrading to the newest nightly because something might work better, or if additional features were added. Or maybe some build just completely horks the phone...
I'll agree that it's all in one thread for the most part, but it's still extremely time-consuming to read through it all.
I guess even something as simple as:
- 3282 users like this build
- 234 users hate this build
-- 93% Positive
It would probably have to be split out by platform also.
Click to expand...
Click to collapse
Its hard for a thread like this because it was likely be very inaccurate. For many reasons. Mainly because people are lazy and don't even read the FAQ that someone else put hard work into for these lazy people.... I mean that most problems can be fixed by a simple restart, and you still see idiots that post their problem in the CM7 thread, as if they are the first to encounter it, then they reboot and ALL FIXED! DERRRRRR! Anyways...back on topic... people like this would be misreporting issues with builds, and then you have multiple specific data and hardware that can cause an issue for one person but the exact same issue cannot be replicated on other devices. Problems, ETC cannot be pinned well enough to start a thread of the nature you are suggesting.

There are 300,000 new Android activations daily. If only 1% of those are MT4Gs, that is 3,000 new MT4Gs activated everyday. If only 10% of those people discover this forum, that is 300 people every day coming here.
Of those 300 new people coming to this forum every day, unfortunately, only 1% can actually search for anything at all. The other 297 post the same damned questions and complaints, over and over and over. And the next day, another 297 people who have never clicked a search button in their lives come here. And it starts again.
Drives me bonkers.

flashing cwm 3.0.0.5
I have an issue flashing to cwm 3.0 i located the file in zip and applied it but then when i go to all clockworkmod 2.5.1.4 it says an error occured while flashing my recovery what do i do i have tried flashin it through terminal and it says flash img not found i have tried several diffent forums my s=off so my phone is rooted someone please help me!!!!!!!

Perfect example. I note now that after hijacking this thread, ksw0080 did replicate the question in a new thread. But there are plenty of posts and threads on this issue ... for those who search.
Hint for ksw0080 -- if you like, you can try TrueBlue_Drew's current method. Click here.

ksw0080 said:
I have an issue flashing to cwm 3.0 i located the file in zip and applied it but then when i go to all clockworkmod 2.5.1.4 it says an error occured while flashing my recovery what do i do i have tried flashin it through terminal and it says flash img not found i have tried several diffent forums my s=off so my phone is rooted someone please help me!!!!!!!
Click to expand...
Click to collapse
Complete and utter fail.
Sent from my MT4G running Gingerbread

ksw0080 said:
I have an issue flashing to cwm 3.0 i located the file in zip and applied it but then when i go to all clockworkmod 2.5.1.4 it says an error occured while flashing my recovery what do i do i have tried flashin it through terminal and it says flash img not found i have tried several diffent forums my s=off so my phone is rooted someone please help me!!!!!!!
Click to expand...
Click to collapse
i couldnt tell if this was serious or a joke

ksw0080 said:
I have an issue flashing to cwm 3.0 i located the file in zip and applied it but then when i go to all clockworkmod 2.5.1.4 it says an error occured while flashing my recovery what do i do i have tried flashin it through terminal and it says flash img not found i have tried several diffent forums my s=off so my phone is rooted someone please help me!!!!!!!
Click to expand...
Click to collapse
If for some reason the method in my thread wont work for you please leave a post there and I can help you. If you havent tried the method in my thread then WTF?

It looks like ksw0080 has not checked in with the forum since Feb 8, when their question was posted twice. Either s/he managed to solve the problem with the guidance provided, or s/he no longer cares, or s/he has no internet access.

Annoying Red Corruption warning screen!!

Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach

juicemane141997 said:
Hi everyone, new poster here but long time user!
I have recently rooted and installed twrp on my sprint lgv20. I also installed the stock international ROM to sim unlock for various uses. My only annoyance with the root is the red warning corruption screen, i was wondering if anyone had a work around or image to flash to get rid or hide the screen somehow with maybe an lg screen or anything.
Thank you for any suggestions,
Zach
Click to expand...
Click to collapse
Unfortunately there is no current fix for this. I am not sure what exactly is needed for this to be fixed, but I would assume that those people who are developing roms for the V20 have already exhausted what ever options there are.
Would be nice to have fixed, but since that screen is only during initial boot up I don't think anyone is terribly concerned with getting this corrected.
Hope this helps.

No fix
It is related to google
Not lg

I would imagine the reason for this is both for security and to let manufacturers know when a phone has been modified.
I don't believe there is a workaround for it either because it can't be done (doubtful as I am sure its software based) or people just don't care (honestly I am sure some developers were annoyed enough to look into it). I just don't think anyone has found a way around it.
This "feature" was introduced in marshmallow.
Edit: further research shows the Nexus 5x developers were able to work around it by replacing the image. So while it doesn't remove the function it hides it.
https://forum.xda-developers.com/nexus-5x/help/to-remove-corruption-warning-message-t3248441
Please note this is a marshmallow phone not nougat so I am not sure the same concept would work on our phone.
Sent from my LG-H918 using XDA-Developers Legacy app

That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk

Dark Jedi said:
That's what they did with the HTC one m7. Was to replace the image. It's just finding the way to do it. As Everytime the devs find a way around something. Then Google, the phone makers,or carriers patches it to make it harder next time. I understand why they make that tamper screen because to many people trying to root and bricks their phones lies about not tampering with their phones OS. They say don't know what happened I just turned it on and nothing. I am sure they will find a way to replace the image. It just takes time and it's low priority on the devs list of things to do.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.

androiddiego said:
It appears that the image is located within the bootloader. It would have to be extracted, changed, and put back in assuming there is not a signature check with it on boot up. From what I was reading it depends on which partition it is located in whether it can be done or not. If it is in aboot, Tilde has mentioned that we can't edit this partition. Unfortunately it doesn't sound like it's a simple case of replacing an image.
Click to expand...
Click to collapse
I can confirm it is located in aboot itself.

What LS997-compatible ROM contains *all* working LG Stock Apps?

So the whole reason I rooted this damn phone was to be able to install working stock apps. Not just the Music and Gallery apps either--ALL THE LG APPS. Which LS997-compatible 100%-working ROM can I flash and get them all, if any? I keep hearing one exists, but no one bothers sharing that info and when I search I find nothing.

Really? No one?

bgibson72 said:
Really? No one?
Click to expand...
Click to collapse
Look in the development section it's like the 5th one down has ls997 in the title

@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.

jerrycoffman45 said:
Look in the development section it's like the 5th one down has ls997 in the title
Click to expand...
Click to collapse
This one?
{ROMS}[LS997] Stock-ish Magisk+3minit+ModControl 3/10/17
Other than DirtySanta, this is the only other one with LS997 in the title on that page. I'll give it a shot, and thanks for answering.

Team DevDigitel said:
@bgibson72
Im the only person developing a STOCK LS997 rom currently.. It contains the LG base apps and all the removed ones that we didnt get shipped with out model . Includes a ton of extras as well, alternatively we have 3 or 4 aosp roms you can use, but make sure you use twrp and backup your efs before flashing as it tends to jumble your programming up and cause issues. Otherwise you can flash the stock rom the Dev who provided the dirty santa unlock method.
Theres a good bit of info here to locate everything you need to have a awesome experience with the LG V20!
My link
https://forum.xda-developers.com/v20/development/rom-ls997-stock-debloated-su-goodies-t3531923
READ THE ENTIRE FIRST 3 POSTS!!! A LOT OF TIME WENT INTO THIS TO CLEAR UP ANY CONFUSION!
I also itemized a list of 15 or so mods and add-ons that we can use to increase our enjoyment with perspective links to their home locations and the devs that built and maintain them.
Click to expand...
Click to collapse
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!

bgibson72 said:
Hey thanks--I was fairly sure this was the ROM in question. Thank you for providing this! I was hesitant to flash because I'm always a little skeptical about the amount of help I'll get should I get stuck. I'm not exactly a noob at this, but I have plenty to learn. It looks like you've done a lot of work to provide a positive experience, so I'll give it a shot and see how it goes. I promise to read and re-read the instructions on the first 3 posts, and to NOT bother you with questions that have already been addressed in the thread. . Thanks!!
Click to expand...
Click to collapse
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have

Team DevDigitel said:
if you made it through dirty santa the rest should be cake. 99% of the issues i covered for people were
after going to AOSP and not having a backup of their programing info in their efs and having to find a way to
manually go in and fix each fd up piece.
Click to expand...
Click to collapse
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
The other is being on older software and downloading a OTA and rebooting with it in your internal storage.
This one causes a endless boot loop into twrp, so be advised to delete the update if your on older software or be prepared to
hit my post # 3 for fixes and be near a pc as you need to fastboot erase the fota and misc directories to resolve the boot loop. A twrp wipe will not fix it and restores etc wont either lol.
Click to expand...
Click to collapse
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
Otherwise theres now a lil over 100 pages of chatting and troubleshooting, fixes and things that have gone on, and mostly its all outdated as ive provided the fixes for 99% of everything in the latest version 7.5
Click to expand...
Click to collapse
That's what I like to hear! :good:
Just be prepared to take 15-20 minutes for the phone to boot up the 1st time. My rom is deodexed, and the 1st boot is doing 298 things before you get to the optimization part. There is not boot animations as the phone will always have the static screen issue on reboots so i went ahead a placed a disabled command there to just save time/batt life. The setup wizard is stripped and only there to give you the notice its done booting and time to get to playing around.
Click to expand...
Click to collapse
Appreciate the heads up. Familiar with the long boot process from DS, lol.
Magisk is kinda finicy being its systemless design. It takes some time to get used to it, and be aware that some older apps that dont support exotic root or systemless root may not request root and not fully work. Titanium backup is one i know is getting attacked by googles app scanning and needs to have that turned off before it will work, most of my apps have a option to set "force root" so it asks for a root request regardless if it understands MagiskSu's root methods.
Click to expand...
Click to collapse
Magisk is a new animal for me, as I've had zero experience with it. I do have Titanium Backup installed, so I'll make a mental note on that.
just some food for thought. Hope everything goes well, and there is a ton of people on the forum here that have great knowlege and can help with troubleshooting issues you may have
Click to expand...
Click to collapse
Thanks again--I appreciate your hard work and dedication to this!

bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse

Team DevDigitel said:
bgibson72 said:
Yeah, I didn't have many problems there, although I did get stuck in the TWRP loop once.
I am on the ZV3 version of the software. I do have the ZV5 update in my cache folder--are you saying it's a good idea to delete the update.zip file?
YES, dont boot into twrp until you remove it, or its back into the twrp loop you go hehe
Click to expand...
Click to collapse
Weeeeeeeeeeeeee!!!
Will do!
Click to expand...
Click to collapse

How I rooted my P8Lite 2017

I have rooted countless phones accross all different manufacturers but never found one as stupid to root as this phone!
There isn't an up to date thread about rooting the phone so I thought I'd share how I did it and got through various things that were not supposed to happen but did!
Firstly, unlocking the Bootloader - as Huwai don't provide a code anymore, I went down the https://www.dc-unlocker.com/ route. It is cheap at £4 and they take PayPal. The unlock code video is out of date which didn't help and I presse3d the wrong button first and got a unlock network code by mistake, so had to pay another £4 to do it again. I used this tool (minimal adb) from this thread (https://forum.xda-developers.com/showthread.php?t=2317790) to put the code in the phone but noticed that my phone wouldn't keep the USB Debugging active and had to slide it on each time I connected to the computer (even had to revoke the computer at one point and reconnect).
From an unlocked bootloader the biggest problem I had was finding a way to put TWRP on the phone. All the threads I could see contained the wrong code to flash and so it always failed. However Dru79 showed the correct form which was to connect in fastboot then use minimal adb (on windows 10, open from the start menu, not left shict right click and 'open window here') and use " fastboot flash recovery_ramdisk TWRP-3.2.3-0-Hi6250-Askuccio-v1.0.img " - the correct TWRP is here (https://forum.xda-developers.com/p8.../recovery-twrp-3-2-3-0-huawei-hi6250-t3859959)
HOWEVER - my phone would not keep TWRP and more often (over 75% of the time) would boot to stock recovery, SO after I flashed the TWRP I typed in "fastboot reboot" and as I pressed ENTER, I took the power cord out from the phone and used the volume UP and the Power key to get into TWRP. I don't know why my phone wouldn't keep TWRP but it didn't.
Getting root through SuperSU was IMPOSSIBLE no matter how I tried, eventually I downloaded Magisk from (https://www.xda-developers.com/how-to-install-magisk/) and flashed it through TWRP.
Once rooted, I downloaded the PixyOS from https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-pixysos-huawei-hi6250-t3852152 and flashed it...perfect!
Hope this helps someone.

The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).

proadi96 said:
The funny thing is, I actually wanted to post a thread about it in General Section as I had the same frustration as you whole trying to root and install custom ROM on this phone (I've done countless Root's, flashes, unlocking before on couple of phones) and just couldn't find a thread that explains this properly.
Anyway since you already done this, this should be moved to General Section so people can see this properly.
I've flashed Pixy's OS on my phone about 4 weeks ago and just one thing you didn't mention is that if you're on 7.1 nougat then you need to upgrade to Oreo and then install TWRP (I found that out when I tried getting it on nougat and then got errors while flashing and realised the TWRP was developed to work on Oreo). Just get a stock image of Oreo and flash it, the link for it it's somewhere around in the forum, I think it's some kind of Russian website but works well.
Anyway great job, if we can just ask Mod to move this to General section so that this guide can aid new users in rooting their phones properly and efficiently so that they can minimize their changes of encountering errors (as me and OP did).
Click to expand...
Click to collapse
I have asked

Question I've tried so hard and got so far.

Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.

Enzucuni said:
Hi, I've been struggling big time to update my device to Android 13. I bought mine when only 1.1.7 hotfix was out and therefore, now that I have unlocked the bootloader (yes, even unlock critical) and rooted the device, I'm not able to install 1.1.8, let alone Android 13. I have already bricked one and managed to get a new one but I don't want to risk it again. I've searched all over Google to a proper guide to update to Android 13, even with sideload, but it gives me an error regarding the payload file, at about 48% of the progress. Tried the *#*#682#*#* method but it stops with error code 20. I have tried flashing the stock boot file but same thing, code 20 from manual update. I'm pretty much desperate at this point and I'm even thinking about unrooting, lock the bootloader again and hopefully update it without an itch, but I really wouldn't want to wipe the device, so, if there's somebody there that could help me through a 100% working process, I'll always be in your debt.
Click to expand...
Click to collapse
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.

HermitDash said:
The best part of this whole thing is that you're rooted.
Do a backup with Swift Backup or what ever your backup app you prefer. Wipe it back to stock without locking the bootloader, make sure your sim card is not inserted then do your OTA updates.
As for the second device you bricked, there's a unbrick tool here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
Just need to get or make a EDL cable then flash and you'll be back in business.
Click to expand...
Click to collapse
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak

Enzucuni said:
First bricked device was replaced in RMA. But yeah, rooted, unlocked and yet nothing works. I was thinking about wiping it, even if I don't really want to because it's a pain every time. Man, Android modding when to ****e and I'm leaning more and more towards getting an iPhone and call it a day, maybe with a jailbreak
Click to expand...
Click to collapse
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.

HermitDash said:
Swift does their backups well so from wipe to setup depending on how many apps ya got took like 20 mins to do?
Once you get to A13 tho, my god the battery life is amazing. I don't use my NP1 as a daily driver but it sits in my pocket along with my daily OP7Pro and it out lasts it by a mile. Really hyped for the NP2 and what they bring optimization wise.
Or in your case you could carry both and see how you feel about it xD
Oh and it's likely the patched boot image (while rooted) that's causing the update errors. Once you restore the stock boot image you should be able to update without issue.
Click to expand...
Click to collapse
I actually restored it but to no avail. Same errors as described

Enzucuni said:
I actually restored it but to no avail. Same errors as described
Click to expand...
Click to collapse
Welp, back to stock you go then haha ADB it to EDL then run the unbrick tool and you should be at 0

I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there

Enzucuni said:
I might be actually lazy enough to wait for a hint of a custom twrp-like recovery and go from there
Click to expand...
Click to collapse
Might not be stable on first release but yea that's in the rumor pipelines

Yeah, I think I'll wait. A12 is still really nice. Some bugs here and there but perfectly usable and battery is basically infinite.

First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model

You could try flashing the fastboot ROMs made by @ot_inc (it's not 100% safe for your data so make a backup in any case).
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com

kriistofor said:
First of all, to jailbreak the iPhone and set it up correctly with all the needed software that jailbreaking provides nowdays ... is actually harder than it was a few years ago.
Secondly, if you had just read through the full topic containing the Nothing OS repo, you would have found several people with the same problem that u had, who had solved it successfully.
Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm. if you want to jailbreak. First, read through the posts of others to see if there are any problems that you would like to avoid, and if there are, don't do it.
You are lucky enough to have had your first device replaced by a new one just like that. Updating while rooted was always a problem for Android, and it always varied per device. it was up to the one who is rooting to check the situation regarding his/her specific model
Click to expand...
Click to collapse
Where is the step by step ? The one that actually works ?

hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something

kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
Umm.. no, you're not sounding harsh. And I've already done that: "google it" and stuff. This is why I post teh question here. This is not my first time at this lol !

kriistofor said:
hmm, honestly it may be on somewhere in the first few pages (not the first one) but you can also search the google, now there are several sites quoting options for updating nothing phone.
sorry if i sounded harsh
anyways, if you go back to stock, and update the device from 1.1.7 to 1.5 incl. all hotfix updates, it should go smoothly.
I also said if you want to jailbreak in one moment in my post when i meant to say if you want to root.
Rooting nowdays is easy and hard at the same time. easy to pull off, but hard to understand that now there are several different steps that need to be done to turn the rooted device into a fully functional one. and for many it is not worth it, but for those that are interested, I would just advise reading through all the posts carefully and learning to search efficiently. Not only will you find the answer yourself, thus remembering it more clearly, but you will also be introduced to facts you were unaware of.
good luck, the most important step is to go back to stock succesfully, read the whole nothing os repo thread just to make sure you are not missing something
Click to expand...
Click to collapse
You said, "Go back to stock, wipe, and redo the official step-by-step of updating, will work like a charm."
Where are you getting this from ?