Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
Related
Introducing the ...
Matt Unbrick Service!
If you have a problem with your HTC One (M8), and just don't know what to do, don't despair! I can help.
With over 3 years experience with Android phones, we exist solely to help you enjoy your phone, and prevent you from experiencing the inconvenient HTC return process, which can take several weeks.
Services I offer:
Rooting
Unrooting
Unlocking Bootloaders
S-off
Updating Firmwares
Flashing RUUs
Fixing unbootable phones!
Service is free, however donations are welcome and appreciated
How it works!
To request a repair, simply post here on the thread.
I will then get back to you as soon as possible and we can then arrange a TeamViewer session or I can write up a guide for your situation, for you to follow independently.
People I have helped:
Eswog
Crazhy
nolinuxnoparty
mattoffshore
dayze0
bteljuice
Amrut223
bamidrol
ringrover
ElunChen
slicetherice
darktyroll
IT4ALii3EN
malavan
ProxiStyx
natzakaria
sly101s
smaug8821
dlnas
sardor
SoftHd
dh2311
royoshukrun
mathrania
adichandra
sfjeep
Thanks for reading, and I hope to be able to help
i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!
Question Please Help
I was installing some roms on my vzw varient of the HTC One M8 can the install failed and so i recovered to nandroid backup and finally get data back but only have 3G any way or thing that you know that might help?
Iconic Bullet said:
I was installing some roms on my vzw varient of the HTC One M8 can the install failed and so i recovered to nandroid backup and finally get data back but only have 3G any way or thing that you know that might help?
Click to expand...
Click to collapse
Try a simple sim pull if you haven't already. Often times if you are stuck on 3g, a sim pull will enable LTE when you reboot the phone. on Verizon.
I tried that i am still having a problem can i try at revert to stock and fix it if so can you please help me...
delete
Thread cleaned.
When posting always try to provide as much information as you can.
Ghost
So I have the att varient and I tried to flash the Venom rom 1.2 version from stock rooted S-On and after flashing I am now stuck at the splash screen and cannot access the bootloader, any suggestions?
EDIT: I have figured out the problem and solved it please disregard this post.
Sent from my LG-E980 using XDA Premium 4 mobile app
Hey Matt, I wonder if you can help me out. I flashed the GPE rom, it was working fine until i decided to edit the build prop. I changed the density value from 480 to 320. It worked but it was too tiny. Then i would readjust the value to 400 but upon restart the value wouldnt change. So i tried changing it back to 480 and saved it and directly went to reboot, not my phone refuses to load up. When i hold power and volume up the HTC logo screen comes up and then it turns back off, I cannot get into bootloader by pressing volume down and power. I am stumped. If you can assist me, id be sure to tip you some BTC your way.
Thank you in advance
---------- Post added at 09:49 AM ---------- Previous post was at 09:13 AM ----------
yas1987 said:
Hey Matt, I wonder if you can help me out. I flashed the GPE rom, it was working fine until i decided to edit the build prop. I changed the density value from 480 to 320. It worked but it was too tiny. Then i would readjust the value to 400 but upon restart the value wouldnt change. So i tried changing it back to 480 and saved it and directly went to reboot, not my phone refuses to load up. When i hold power and volume up the HTC logo screen comes up and then it turns back off, I cannot get into bootloader by pressing volume down and power. I am stumped. If you can assist me, id be sure to tip you some BTC your way.
Thank you in advance
Click to expand...
Click to collapse
Never mind Matt, It eventually Loaded, Sigh what a relief. Il be sure to keep you in mind!
Hi @Matt !Got an m8 with that whelp message on firewater, u said above u can s off?
Prompt 24 hour service.....haven't seen Matt here since the 15th. Hmmm :sly:
th3lawmak3r76 said:
So I have the att varient and I tried to flash the Venom rom 1.2 version from stock rooted S-On and after flashing I am now stuck at the splash screen and cannot access the bootloader, any suggestions?
EDIT: I have figured out the problem and solved it please disregard this post.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have an issue similar to this.
Phone gets to the HTC powered by android screen and then dies. I cannot access bootloader using vol down and power. It won't respond.
S-Off, unlocked boot loader.
Phone also periodically turns on by itself, then procedes to shut down after it gets to the HTC Powered by android splash screen.
EDIT:
Managed to get into recovery using the advice in this post:
Tikerz said:
When you plug it into the computer does the computer make a ding sound that it's connected? If so, then press power and volume up until the disconnect ding sound which indicates it's rebooting and then immediately press volume down and see if you can get into fastboot. The timing is tricky so I've found using audio cues from computer can help if the phone is messed up.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Leaving this here in case anyone else has the same issue. Mods delete if you see fit.
Prompt 24 hour service? but how?
SimplyNando said:
i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!
Click to expand...
Click to collapse
copy your custom ROM into a flashdisk. then use USB OTG, search on youtube about the tutorial.
Mr Hofs said:
Prompt 24 hour service.....haven't seen Matt here since the 15th. Hmmm :sly:
Click to expand...
Click to collapse
It usually is, I've just got back from holiday and ran up a large phone bill so been trying to sort that out.
People should private message me so that I get the notification email as I thought I was subscribed to this thread yet when I checked just now, there's loads that I hadn't seen.
Sorry!
Matt said:
It usually is, I've just got back from holiday and ran up a large phone bill so been trying to sort that out.
People should private message me so that I get the notification email as I thought I was subscribed to this thread yet when I checked just now, there's loads that I hadn't seen.
Sorry!
Click to expand...
Click to collapse
That's no problem and could happen to all of us. But some pointers from my point of view :
When i look at your O.P you give the tendency to look like a non profit company/organization which indeed offers a free service, that's all fine but please give the users the hint when it will be "offline" when you are on holiday or at least "offline" without a reason to stop the reactions users like me posted before. It looks like a 24 hour service promise which is not there.
I have been a helpful member on the hox section of xda the last 2 years and never had the need of such a thread/service. I think it won't make that major difference because users will always make new threads with their problems anyway.
This is not ment in a bad way, just my personal opinion !
Cheers.
SimplyNando said:
i really need help! My HTC one M8 has been completely wiped, no OS installed. Not I can only use TWRP and i can't boot up!
Click to expand...
Click to collapse
kinda ran into the same problem. problem is i dont have an usb otg cable. i tried installing viper rom from but it would fail towards the end. would really like to have my phone back up and running.
exocetdj said:
Hi @Matt !Got an m8 with that whelp message on firewater, u said above u can s off?
Click to expand...
Click to collapse
He can help with this? Matt, you can help with this? hahah
Hi @Matt, i read that you can help with s-off?
I'm using a european WWE m8 (CID htc__e11) and i can't seem to get it working, you would be my personal hero if you could help me out with this one.
Greetings,
Incapable
incapable said:
Hi @Matt, i read that you can help with s-off?
I'm using a european WWE m8 (CID htc__e11) and i can't seem to get it working, you would be my personal hero if you could help me out with this one.
Greetings,
Incapable
Click to expand...
Click to collapse
If firewater isn't working for your device, then this service nor any other can help you gain S-Off, like it's been started in many threads already. You'll have to wait until firewater suports your phone.
Hello everyone,
So I've looked around on this topic and it's still an issue, albeit a minor one. I have the T-Mobile HTC One M8 phone........ unlocked/rooted, and S-OFF'd. I am currently using ViperOne M8, which is awesome!
When I boot to HBOOT after installing new firmware the OS line is filled in, but after booting to Recovery and going back to HBOOT, the OS line is now blank. I've been told this is a bug in TWRP, and not a bug or issue anywhere else. I've tried 2 different approaches to fixing it. One entailed flashing a new ZIP (or flashing something), but the instructions stated that I needed to boot to Recovery while in Stock Recovery, which my phone does not do. It's only when I use a TWRP Recovery that I am able to go into any Recovery Menu. The other one had to do with flashing a zipped firmware, but even though that flash worked just fine, it still didn't resolve the OS issue. I have tried looking all around, but either I'm missing something, or it's just not knowing enough about what I'm reading to recognize the right answer.
So please, will someone tell me HOW do I get rid of that pesky TWRP bug that causes the OS line in HBOOT to blank out after only 1 visit to recovery post-firmware update?
I would appreciate ANY info you can give me.
Thank You,
RockStar2005
The Answer!!
IGNORE this post!! Scroll down to my "2nd September 2014, 5:17 PM" post instead for what you're really looking for!
RockStar2005
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
RockStar2005 said:
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
Click to expand...
Click to collapse
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
The True Fix
RealZac said:
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
Click to expand...
Click to collapse
Hey Zac,
Forget about that TWRP. It wasn't good. Please DELETE any backups you made using it and the twrp image file itself as they are all corrupted and won't boot up (I found this out after my initial post here). Read this post I put elsewhere for the real deal Holyfield lol:
So I ended up finding a RELIABLE fixed current version of TWRP on xda you may wanna check out. You can find it here: http://themikmik.com/showthread.php?16278-SPRINT-RECOVERY-TWRP-Recovery-(UNOFFICIAL)-v2-7-0-4 (Go to that link then Control + F this: "Downloads TWRP Recovery 2.7.1.0 (DH) | Mirror (AFH) - build date: July 13, 2014". I downloaded from the Mirror link.)
Don't worry about it saying Sprint...... the dev CONFIRMED it works for all variants/carriers. So after creating a new backup using the standard twrp, I went back to stock recovery, re-flashed my most recent firmware (2.22.401.5), and then switched over to that new version of twrp........ created a new backup and then restored it using that new version. Worked like a charm!! And the "blank OS" issue........... gone! I highly recommend it!!
If you have any other questions Zac, please post here and I will respond.
RockStar2005
Thank you for this detailed answer!
I will test it.
RealZac said:
Thank you for this detailed answer!
I will test it.
Click to expand...
Click to collapse
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
RockStar2005 said:
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
Click to expand...
Click to collapse
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
RealZac said:
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
Click to expand...
Click to collapse
Zac,
Ok cool.
Have a good one!
RockStar2005
RockStar2005 said:
I needed to boot to Recovery while in Stock Recovery, which my phone does not do.
Click to expand...
Click to collapse
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
BerndM14 said:
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
Click to expand...
Click to collapse
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
RockStar2005 said:
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
Click to expand...
Click to collapse
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
BerndM14 said:
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
Click to expand...
Click to collapse
BerndM14,
Ok I see.........so TAPPING not holding Power and holding Volume+Up. Got it.
Thanks for the clarification!
RockStar2005
RockStar2005 said:
Zac,
Ok cool.
Have a good one!
RockStar2005
Click to expand...
Click to collapse
Works great & flawlessly! Thank you for the help!
RealZac said:
Works great & flawlessly! Thank you for the help!
Click to expand...
Click to collapse
Zac,
Sweett!! You're very welcome!
RockStar2005
Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
@BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.
Be aware, and backup before doing this or everything you're dubious about.
Cheers
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them
RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
almogsad said:
So after a few months of using my google pixel 2 xl, while I was using it I randomly got a black screen with the message:
"Your device is corrupt. It can't be trusted and may not work properly.
Visit this link on another device: g.co./ABH
PRESS POWER BUTTON TO CONTINUE".
Now it happens every time I turn on my phone. :/
I Have tried doing a factory reset and it still appears.
My phone is not rooted, I have the official OS that I got it with it (updated it through the phone's updater).
The phone was purchased directly from the us google online store.
I've tried to contact their support but they didn't have a solution.
Please help me!!
Click to expand...
Click to collapse
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
First of all thanks for the response!
yes my bootloader is still locked.
Badger50 said:
have you tried side loading the March OTA
Click to expand...
Click to collapse
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
almogsad said:
First of all thanks for the response!
yes my bootloader is still locked.
How do I do that? ^^
and it seems like the phone still functions properly, but I guess only time will tell
Click to expand...
Click to collapse
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard
Click to expand...
Click to collapse
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
almogsad said:
Thanks! I'll try that...
Do you think it might fix the problem?
Edit:
it says in the guide:
"find the appropriate driver for your device from the OEM drivers"
but I don't know which one is mine ^^
Click to expand...
Click to collapse
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Badger50 said:
Once you choose the proper OS version for your pc, and install SDK, when you plug your phone in, it should automatically update your device drivers :good:
And yes, there's a good chance it'll fix your problem. Never any guarantees with this tech stuff though
Click to expand...
Click to collapse
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
almogsad said:
Hey! It seems like it worked!!!! Thanks!!
I only wish I hadn't listened to the google support team , and hadn't done a factory reset to phone before lol they don't seem to understand too much about their phones, the guy told me he thinks it's just an add
Thanks again man!
Click to expand...
Click to collapse
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!??????
Badger50 said:
Oh sweet! Glad to hear it my friend, well done. Now you can help others out with the same issue if it comes up :good: Yeah, the Google folks are kinda funny sometimes. The factory reset is their standard MO! And right, an add on the boot up screen....yeah that's funny! I'd be willing to bet most of them use iPhones!!
Click to expand...
Click to collapse
How ironic! lol ???
Badger50 said:
Sounds like one of those non harmful, annoying messages at boot up. Is your bootloader still locked I assume? If so, have you tried side loading the March OTA. I think sometimes during the OTA updater process that some files don't always make it to the system, which is why you get those messages. Is your phone still functioning properly??
Click to expand...
Click to collapse
Thanks!! I also had this issue and following your suggestion to sideload the latest OTA, it appears to have fixed the problem.
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Are adb/fastboot tools the very newest?
Apsel said:
I've been getting the same corrupt error on reboots on my xl 2(also not rooted), but I have not been able to get the latest OTA to sideload. It nearly completes but aborts last second and gives a Status 1 error. I'm not sure what I'm doing wrong here. Any help will be appreciated.
Got a similar run-around with Google support. When the factory reset was unsuccessful, they've recommended replacing the phone since it's under warranty, however they think replacing my virtually brand new phone with a refurbished phone is appropriate.
Click to expand...
Click to collapse
Unlock then re-lock your bootloader(/s) maybe?
Great job guys, this solution with sideload latest OTA worked for me too with no need to unlock bootloader! :good::good::good:
I can confirm this working again. Pixel 2 XL with 9.0 and November security update.
Thanks!
I just had the corrupt message pop up (bootloader locked), and the sideload ota update seems to have worked!
michaelbsheldon said:
Are adb/fastboot tools the very newest?
Click to expand...
Click to collapse
I'm experiencing the same problem as Apsel, yes the adb/fastboot are the latest.
Error applying update: 15 (ErrorCode : kNewRootfsVerificationError)
E:Error in /sideload/package.zip (status 1)
Badger50 said:
Just follow these instructions if you want to side load an OTA. It's really not that hard ??
https://developers.google.com/android/ota
Click to expand...
Click to collapse
I know this is an old post but I'm having the same issue. Also cannot connect to pc due to, I'm assuming daughterboard issue this and previous pixel models have. I have been rooting phones since the S3 and am no virgin to the sdk. I tried to take it to ubreakifix which was a 4 hour round trip for me. I was told I would have to sign a waiver since the screen is glued to the phone and that was the only way to get to the internals. When I arrived I watched 4 bozos poke at the charging port for 20 min and then contradicting what I was told the night before over the phone that they were not comfortable doing the repair and then they tried to sell me a new device. I just got off chat with google and they want to charge me 270 dollars to fix even though I went to an authorized service center when it was in warranty. Will fastboot work over wifi?
Toolmighty said:
Will fastboot work over wifi?
Click to expand...
Click to collapse
'fraid not. Both the bootloader and recovery have stripped down hardware support, limited essentially to the display and storage. Neither has WiFi support that I know of, thus you have to use a USB cable.
I figured it out after I figured out how to fix the daughterboard issue w/o replacing the daughterboard. Verizon are some sneaky *^&$^s. Thx for the reply tho. I'm sure ur quite busy.
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
TheKnux said:
So I was thinking last night about this app that I used to have and use that allowed you to show logcat/dmesg as your boot animation and after a quick Google search I finally found it!
Here is the link if anyone is interested.
https://forum.xda-developers.com/android/apps-games/liveboot-t2976189
Looks amazing on the OP6T. ??
Click to expand...
Click to collapse
I tried it, but it just hangs while trying to load resources. I think I'm just unlucky lol
I installed it but got a boot loop. I could only start the phone by flashing latest oos without magisk but even after uninstalling live boot, magisk still kept the liveboot00001 file or whatever so I had to remove it manually in twrp in /data/adb/magisk/ (somewhere around there.. ) Just in case someone else has this problem..
No problem here, using it since 4 weeks, several OOS updates never had an issue
TheKnux said:
Looks amazing on the OP6T.
Click to expand...
Click to collapse
It sure does! Thanks for the share. Works great on beta 2, even though I have the McLaren Magisk mod running (which replaces boot animation with McLaren's).
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Ironic said:
Installed it on a Oneplus 6. Bootlooped immediatly after the next restart. I already deleted the file located in /data/adb/magisk/post-fs but it still doesnt boot properly.
What can i do? I also tried uninstall Magisk via TWRP and using an unpatched boot image. Nothing works.
Click to expand...
Click to collapse
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
TheKnux said:
That's weird that it doesn't work for you. All I did was open the app, grant su access and rebooted and it worked. Magisk v18 user.
Click to expand...
Click to collapse
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
tech_head said:
It worked for my on my 6T running 9.0.11.
I'd like something a little less verbose so you can actually read some stuff as it goes by.
Click to expand...
Click to collapse
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
TheKnux said:
Just change the lines of code that are shown on screen, I haven't tried it but I'm sure that would help. I'm not really worried about reading anything, if I wanted to do that, I'd just pull a log. It's more of an asthetic kind of thing.
Click to expand...
Click to collapse
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
tech_head said:
I don't really want to read it.
I want it to scroll by slower so it looks a bit more convincing when it boots.
Click to expand...
Click to collapse
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
TheKnux said:
Did changing the lines of code displayed on screen work at all? Not sure of any other way to slow it down. Seeing how an OS is thousands of lines of code. Seemed pretty convincing to a few coworkers of mine.
Click to expand...
Click to collapse
I didn't change it. No real incentive right now.
This app was my old favorite and I miss it, I hope it still works as I havnt tried... Just wanted you all to know this is the best app ever and the scrolling text (if your developing) is actually SUPER helpful... I remember I would use the filter to find specific debug lines only and it was so usefull... I only installed it because Im a huge nerd so it was an extra awesomeness to have it be super usefull!
2023 BEST APP EVER!#[email protected]#