Related
So, I was just told that I was -actually- posting my error that I was getting from my Captivate Glide in the wrong area, I was actually posting it in the Captivate area... so... I'm just gonna quote myself here:
Hazarath said:
Ok, so, first off, yes, as I keep being told by the forums I read, I am a noob. I understand, and respect that. That's not the issue.
So, I have followed the guide that's found here, and I have the Clockwork mod installed, as when I turn on my phone, and press down, it says I have it.
I -had- my phone rooted in the past, and then -finally- the official 4.0.4 update came out. I upgraded from my old rooted image to the new image, and figured I'd wait to see if someone would post instructions on how to update this version, unless I am doing something wrong.
I am sure that I am, or I missed something somewhere. Again, I have -no- idea what I am talking about. I don't claim I do.
So... I try to install Superuser-3.2-RC2 -and- RC3-ARM-signed.zip, as I was advised that may work via pressing power+down, I get this:
E:failed to verify whole-file signature
E:signature verification failed!
I am not sure what I am doing wrong. I copied the file over to the root of the SD card, and all that jazz.
So, is someone ready to point out the error in my method, or more likely, tell me I am an idiot?
-Haz
Click to expand...
Click to collapse
The only solutions offered on that forum was to try SuperOneclick, and I simply get a pop-up after clicking 'Root', a dialog letting me know I have missing drivers. It asks to allow me to install them, and it just goes 'No data Found'. ..amusing error if I ever saw one! Oh, it's better... it repeats the same thing, and I get no further. The application just locks up, all done.
So, as stated as I quote myself... am I an idiot, or is something borked?
-Haz
Try to flash ur phone with proper cwm image file:
http://forum.xda-developers.com/showthread.php?t=2007198
Else, try to install some different ROM, stock is boring
The file signature error generally means a bad download. Try redownloading it. If you don't mind potentially hosing your installed ROM and having to reflash, you could try disabling the signature check.
You did install CWM first, right? IIRC the official ICS update clobbers recovery so you have to reinstall it.
Just a thought, why not flash straight to CM10.1? It comes already rooted.
roothorick said:
The file signature error generally means a bad download. Try redownloading it. If you don't mind potentially hosing your installed ROM and having to reflash, you could try disabling the signature check.
You did install CWM first, right? IIRC the official ICS update clobbers recovery so you have to reinstall it.
Just a thought, why not flash straight to CM10.1? It comes already rooted.
Click to expand...
Click to collapse
What's CM10.1? Forgive me, a newb here. I already did the who re-download thing, from a few sources, no good.
szulco said:
Try to flash ur phone with proper cwm image file:
http://forum.xda-developers.com/showthread.php?t=2007198
Else, try to install some different ROM, stock is boring
Click to expand...
Click to collapse
I followed those steps; it seems that, looking upon my working directory, I already used the recover image provided in the link. So, I already have this tool installed. So, that's that. >.>
I am not against installing a custom ROM, as long as someone here can actually attest to it working! I am a stickler when it comes to operating systems. I don't just go, 'Hey, that looks cool!' *install...* '..wait... it does THAT? Screw that!' *restores stock*
-Haz
Dude I got errors because when I downloaded cm10 I downloaded it 11 times because all ten of the downloads where (bad)
Sent from my SGH-I927 using xda app-developers app
Erm... I just wanted to kinda bump my own thread here... and just FYI:
dude52 said:
Dude I got errors because when I downloaded cm10 I downloaded it 11 times because all ten of the downloads where (bad)
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
If the file I had was damaged, it likely would not have took the first time I flashed the file when I had a different version of 'droid on it. So, that's likely not it.
Any other ideas?
-Haz
Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.
Zook024 said:
Currently my phone cannot boot up, get's stuck at the HTC white screen. I am trying to follow the directions here but I'm having some trouble. I can get into the recovery screen and by doing so it automatically starts loading the PG32IMG.zip file but does not do anything after that and I am unsure how to proceed. So far I have tried installing the .zip using the ClockworkMod Recovery but when I attempt to do so it says it can't open and just says (bad), installation aborted. Currently it is S-ON and I do not know if I can change it to S-OFF if I cannot boot it up. Right now I am waiting for the download to finish for this guide and I will hopefully be able to switch it but in the meantime if anyone has any ideas I would certainly like to hear from you.
Click to expand...
Click to collapse
What happened before it got stuck at the white screen? Were you trying to flash a rom?
gtdtm said:
What happened before it got stuck at the white screen? Were you trying to flash a rom?
Click to expand...
Click to collapse
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.
Zook024 said:
yes. I managed to root it last night and was attempting to add this rom this morning. I don't remember what steps I took exactly (I knew I should have written it down!) and now it refuses to boot up. I am able to get into the recovery mode and access the SD card by mounting it to my PC but that's it.
Click to expand...
Click to collapse
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.
gtdtm said:
So you are HTC dev unlocked but not s-off if I'm understanding correctly. The flashing steps are a little different. You need to look around for flashing instructions for dev unlocked phones. I believe the Viper rom thread has the instructions, and they work for any rom.
Click to expand...
Click to collapse
yes you would be correct in that understanding, is this the one you are talking about?
Zook024 said:
yes you would be correct in that understanding, is this the one you are talking about?
Click to expand...
Click to collapse
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1
gtdtm said:
Yes, his install instructions from that OP are:
Be s-off (or dev unlock)
Install a custom recovery (twrp/4ext)
Download the ROM and place it on your external SD card.
Do a nandroid backup!
Start rom install process and make sure you select to wipe data in aroma
Select your desired setup in aroma, and finish
Reboot the device and enjoy!
If you are dev unlock, you need to pull the boot.img from the rom zip and fastboot it in hboot
I'm not dev unlock, so I've never actually done this, which is why I'm not being more specific. The boot.img is already in the zip you downloaded for the rom.
If you look in this thread, the phone is different, but the flash steps should be identical according to my understanding:
http://forum.xda-developers.com/showpost.php?p=28301167&postcount=1
Click to expand...
Click to collapse
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.
Zook024 said:
well I managed to install the ROM successfully but it still refuses to boot up, I've run out of ideas at this point, no idea why it refuses to boot up.
Click to expand...
Click to collapse
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?
gtdtm said:
More details will be very helpful to any of us that might be able to help you.
What rom are you trying to install?
What do you mean by won't boot up. Are you getting past the HTC screen now?
Click to expand...
Click to collapse
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.
Zook024 said:
my apologies, I had originally attempted to install this ROM. I thought I had followed the directions to the letter, obviously I screwed up somewhere. I then attempted to perform a factory reset from the ClockworkMod Recovery which yielded no results. I then attempted the Viper ROM, again wiping the data and that said installation was successful. Still it refused to boot. I then tried this return to stock and with that, the .zip folder is automatically loaded but then does nothing. As of right now I cannot get past the HTC screen.
Click to expand...
Click to collapse
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?
gtdtm said:
Well don't panic first of all. It's not super easy for me to figure out what's going on because your setup is quite different from mine, but I'm willing to offer any knowledge I have gleaned from reading these forums (a lot).
When you tried to go to stock, you went to the bootloader and it found the PG32IMG? Or it just stayed on the options screen of reboot, recovery, factory reset, etc?
If it found the PG32IMG did it give you any messages? Did you check the md5 sum before trying to load it?
Click to expand...
Click to collapse
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?
Zook024 said:
haha too late for that, I'm already freaking out. It does find the PG32IMG automatically as I said and proceeds to load it. I was able to catch the message it flashes before it goes back to the default list, "wrong zipped image!" That doesn't sound good. I had not checked the md5sum prior to this, just did so now, says the codes do not match. Pardon my utter cluelessness but what on earth does that mean?
Click to expand...
Click to collapse
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?
gtdtm said:
You need to post the md5 sum from the return to stock thread, it is right below the download. If it doesn't match after that, you have a bad download and need to download it again on a good connection. I can't see the md5 very well in your screenshot, but it looks like it is correct. Then the other thing to check is that windows didn't add an extra .zip to the file name. You'll have to go into folder options and make it show known file types then see if it says it is PG32IMG.zip.zip or something. I'll keep looking around to help, but I'd suggest reading through a lot or all of that return to stock thread.
Is the file in the root of your microsd or in a different folder like downloads?
Click to expand...
Click to collapse
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"
Zook024 said:
Ok I corrected myself with the md5sum checker and now it confirms the codes match. I then doubled checked the file extension and it looks good as far as I can tell, I did not see a double .zip.zip anywhere, even after I selected "show file extensions of known files". I just tried again and got the same message,
"Checking....[PG32IMG.zip]
Wrong zipped image!
Loading...[PG32IMG.nbh]
No image or wrong image!"
Click to expand...
Click to collapse
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app
gtdtm said:
Well, I'm running out of ideas. Hopefully someone else can chime in. I'd try downloading again and make sure the md5 is good, put it on the root of the microsd, and try one more time. Other than that my knowledge is spent.
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
well I certainly appreciate you trying to help anyways. just on a hunch I tried running through the steps of the HTCdev bootloader which I had originally done and after doing so, it now says the following,
"Main Version is older!
Update Fail!
Press <POWER> to reboot."
that is interesting, should I try the VIPER ROM again and see what happens now?
Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.
Zook024 said:
Well I am happy to report now I have figured it out! I managed to find this video and by following his steps, I was immediately able to get the Viper ROM up and running. So I guess that is what I was doing wrong, trying to follow the S-Off Method when I had already gone halfway with the HTCDev method. Very glad I was able to get it done tonight, another case of "if I can break it, I can fix it!" case closed.
Click to expand...
Click to collapse
Awesome. I'm glad you figured it out.
Sent from my Incredible 2 using xda app-developers app
My problem started some months ago, when a friend tried to root my phone, he told me that he rooted it but every app that checks for root told me that it wasn't rooted and i couldn't use apps that needed root also, the downside to all this is that i couldn't use apps that do not allow root, like the banking app, or Pokemon Go, but i used the phone like that for some months until last week when i decided to try and fix it. I thought that if i flash a stock firmware everything should be fine and the phone should be as new. On the phone, it says that the model is SM-N910F(behind the battery), in the settings it also said SM-N910F, so i tried flashing a rom for this model at first and it kept failing with me not knowing why. After trying different thing and googleing some time, i finally noticed that in "Fast Download", it says that the phone's model is SM-N910P, so i started searching about this, i didn;t understand why there were 2 different models on my phone, then i found out about searching my IMEI on imei.info, so i tried it and here it was SM-N910C, i had no idea what all this meant, but at this time i already got stuck into bootloop. Eventually, i found this thread: https://forum.xda-developers.com/note-4/help/help-sm-n910f-sm-n910p-bootloader-t3299285 and did what cam_bob22 said, it worked, i finally flashed the firmware on my phone and it worked, i could use the bank app, pokemon go, everything was fine except the fact that i couldn't select or change my mobile operator, when going to mobile networks, the mobile operators options was greyed out and couldn't be pressed(i want to mention that i did have service and that data worked but the internet would work only in roaming and i couldn't get 4G). So i tried updating the software from 5.1.1 to 6.0.1 like it was said in the instructions and hopping that this update would fix the issue, but unfortunately for me after the update i somehow lost service completely, the signal sign was in the shape of a triangle with no bars, and the mobile operators setting was exactly as before.
So far i tried going back to 5.1.1 but besides the Hands Free activation that i can't make to go away, i still can't use the mobile operators setting and my data only works with roaming activated and doesn't get 4g. One thing that i forgot to mention is that the IMEI with the 5.1.1 firmware was of a samasung Galaxy S5 not a note 4, i checked it on imei.info.
I was wondering if there is any way for me to go back to the OS i had before my friend tried to root my phone, when it said in the settings that it was SM-N910F and everything worked as it should have.
Thank you for reading and i really hope someone can help me.
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
aaron74 said:
@robert11arad
There is no way to go back unless he made a backup. Which is why you should always do this before you flash anything.
I'm not sure if this will help but you could try flashing a international custom Rom after you have correct firmware. But if your phone is a Sprint version, you'll have to use a special data fix and kernel.
What firmware did you end up using to flash? Was it Sprint? If so, and you use gsm service, try flashing my Gsm stock Rom for Sprint phones. It's in post 2.
https://forum.xda-developers.com/no...t/05-15-17-debloated-deodexed-rooted-t3607029
You'll first need to be on current marshmallow firmware. So flash firmware with Odin first, then install Twrp with Odin. Then install Rom with Twrp.
Click to expand...
Click to collapse
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
robert11arad said:
Thank you for the reply, i wanted to say that with the Sprint firmware i used, after doing all the updates it unlocked the mobile operators option, but it couldn't find any.
Click to expand...
Click to collapse
Oh ok. So do you have service?
aaron74 said:
Oh ok. So do you have service?
Click to expand...
Click to collapse
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
robert11arad said:
No, the network operators is unlocked but there's still no service, when i try scanning for an operator it just stops with no message, and nothing happens.
I forgot to mention this, but before all this happened, I made a back-up of the phone with smart switch, is it possible to get back to how it was using that? And another thing is that when using the backup, it only restores music and photos, no contacts, no apps.(From what i've noticed so far)
Click to expand...
Click to collapse
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
aaron74 said:
You would have needed a system backup with twrp.
What country you in? What network you on? What firmware you on?
Click to expand...
Click to collapse
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Ok. About the best advice i can give is, because your on pure Sprint Rom, something is messing up with csc or something.
All i can suggest, is maybe try updating to QC1 with Odin and then try flashing my gsm Rom. Which is essentially just a tmobile rom.
And if that don't give you the function you you need. Then maybe try an international Rom.
It's hard to say what the last person did to the phone.
robert11arad said:
I live in the UK, i'm on giffgaff and the firmware is N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5
Click to expand...
Click to collapse
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
aaron74 said:
Also. You stated your phone first showed as a 910f. So maybe flashing a international F rom, will provide the correct csc settings for your phone to work. Only problem your gonna have, is because it's Sprint hardware, you'll have to pair the Rom with a kernel that'll work and some lib files for data.
I can help you by putting together some files to flash. But the main question would be, Do you want a stock note 4 Rom?
Also before any of this happened, do you know what firmware you were on? Marshmallow? Lollipop?
Click to expand...
Click to collapse
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
robert11arad said:
I would really appreciate if you helped me put the files together cause i have no idea how any of this works, i'm new. But i wanted to ask, is there any chance for thia to brick my phone?
When it had sm-n910f on it i couldn't update it after 5.1.1, when i pressed update it wouldn't do anything.
And yes, if possible i would like it to be a stock firmware, but if it is not possible i don't mind using something else as long as it works properly.
Thank you for all your help, i don't know what i would do otherwise.
Click to expand...
Click to collapse
Well, first, let me state,about bricking device. I have to state that it's not impossible to brick. But after hundreds of flashes never had problem. These devices are hard to brick. What hard bricks a device is messing with boot loader and partitions that shouldn't be messed with, like trying to unlock lte bands. But just flashing roms is fine unless you flash a Rom not for your phone and it over writes wrong partition.
All snap Dragon note 4s have the same layout so all you need is correct kernel, csc, and some ril lib files to get data working.
Now, mine main worry is that the phone is still unlocked,because I don't know what possible changes were made to it.
But with all that being said,I'll move on. With another post.
---------- Post added at 05:52 PM ---------- Previous post was at 05:13 PM ----------
@robert11arad
Before we go too deep into this and upgrade and stuff. I'd like to just test a custom Rom on your phone and see what works.
So what firmware are you on right now?
5.01, 5.1.1, or 6.0.1?
I'm gonna take a guess and move on. You last stated you were on OG5 which it's 5.1.1. So if that's true, let's try the following.
First I'm gonna assume you already used Odin to flash that firmware. So now we need to flash Twrp. So download this on pc https://eu.dl.twrp.me/trlte/twrp-3.1.1-0-trlte.img.tar
1 . Put phone in download mode. Open Odin and plug in phone.
2. In Odin options make sure everything is unticked except Reset Flash Counter.
3. Now click on AP and select the Twrp file.
4. Flash it. Let it flash until it states it's completed. Once done. Unplug phone. Pull out battery. Put back in and boot to recovery by holding power+home+vol.up
5. Now you should have Twrp. Just reboot phone so we can continue to next post.
PM sent
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
aaron74 said:
@robert11arad
Ok, here you go. If your where we left off, you should be on stock QC1 and have Twrp installed.
Just download this file, boot into recovery, and install. This file will delete dalvick/cache, so phone will take a few minutes to boot up.
I actually recommend before flashing, you do a factory reset in recovery then install.
Anyhow here you go. Let me know if it fixes what your looking for. If not, my only others option is to install a custom n910f Rom. I'll gladly walk you through if need be. But try this first.
Click to expand...
Click to collapse
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
robert11arad said:
Alright so i just tried it and when starting my phone, i can't even set it up because i keep getting a message that com.android.phone has stopped. After about half an hour of trying to start it, i finally managed to get to setting and to app manager, there i looked for com.android.phone and it was nowhere to be found. Apart from this i noticed a N with some signal bars where my phone signal should've been and i didn;t get the hands free activation anymore, but that's all...
Click to expand...
Click to collapse
Ok. I must have forgot something in csc. Sorry. I'll get back with you.
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
I have a oneplus 7t, on straight talk using verizon towers.
So since I got the android 12 update, I have spent several hours on the phone with customer service, and haven't been able to fix every issue.
We did fix the problem where I had no data, customer service walked me through updating the APN and that was fixed.
-I still can't receive MMS pictures through the standard app, I can work around that using the google messages app, but that's frustrating since I know something isn't working correctly.
-I randomly get call failed when I try to accept a phone call. This happens very often, but i'm not sure why it doesn't happen every time. I seem to be able to make outbound calls without any issues.
Not being able to fix the call issues, and MMS issues makes me want to roll back to android 11. the phone worked great until this android 12 update. I tried a factory reset, and still have the same issues.
I've tried searching for instructions but all of them are lacking thorough instructions. They say "pick the matching file for your phone", but mine is 1905, but only 1901 and 1903 are listed. I'm sure one of those are supposed to work, but which one?
"download this apk"...... ok, now i have a .apk.zip file that i don't know what to do with.
-delete .zip and i don't know how to make the .apk file install or open
-unzip, and i have 500 files that i don't know what to do with.
"move this to the root storage".... how?
I used to be more tech enabled, but it's been so long since i've rooted a phone or something else this involved. I really just want my phone to work properly again.
Well I can get the local update apk to open, but I can't figure out where to place or what to name the roll back file for that apk to find it. This is frustrating and wasting many hours of my life
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
HueyT said:
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.I.31_OTA_0310_all_2112101928_downgrade_327348e7ed1f4427.zip
Click to expand...
Click to collapse
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found
dempseyjosh said:
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found
Click to expand...
Click to collapse
Does the file contain something called MSM tool? If so you will need to do this from a Windows PC (or VM).
EDIT: nevermind disregard this post.
dempseyjosh said:
Thanks, but that's not super helpful. I'm at the point where I'm struggling to get local update to find it, because I'm not sure where or how to move it to make it be found
Click to expand...
Click to collapse
Move it from \sdcard\downloads to \sdcard root
I Need a little more specific help than that. Do I need to be hooked to a computer to do that? Does it mean to be changed at all? .zip.jar is correct? Because I've tried moving it from the downloads folder to device storage. It feels right to me, but it's not finding the file to update with.
dempseyjosh said:
I Need a little more specific help than that. Do I need to be hooked to a computer to do that? Does it mean to be changed at all? .zip.jar is correct? Because I've tried moving it from the downloads folder to device storage. It feels right to me, but it's not finding the file to update with.
Click to expand...
Click to collapse
No on pc. Yes to rename jar file to zip
HueyT said:
No on pc. Yes to rename jar file to zip
Click to expand...
Click to collapse
Thank you, that was the last bit of help I needed with that. I've successfully rolled back and my phone is working correctly, as far as I can tell.
Well you answered my question. "Do not take this upgrade"