Related
I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Bump. Any help is greatly appreciated. Thanks!
Google is your friend...
http://rapidgator.net/file/2ab3e0dc...om/att-galaxy-note-4-sm-n910a-stock-firmware/
Punker1234 said:
I love my Note 4 so much that I tried for about 2 weeks to fix it's constant rebooting issue. Went to ATT & Samsung repair center and they couldn't get it to flash. However, it stills turns on, I just generally need to pull the battery for a few minutes to get it to boot.
With that said, I'm not incredibly knowledgeable in this area. I've downloaded ODIN and found lots of resources for the exact steps to follow, however, I'm not sure where I can locate a version of 5.1.1 for ATT. To me, this seems like my only fix for my phone. I've tried clearing cache and factory resets etc. My phone is unlocked. Am I missing anything that you can think of? Can someone link me to a reputable source for the appropriate files?
You seriously cannot imagine how happy I'd be if I can get this thing working again. Thank you!
PS, if you think there is a more stable version than 5.1.1, I'm open to that too.
Click to expand...
Click to collapse
What is your Baseband? Maybe you can't go back.
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Punker1234 said:
Heya guys.
Thank you for the link! I seriously googled and browsed forums for days looking for it. I even went to the Android website with a slew of different version but they did not have the ATT versions. Anyway, I'm going to give this a go but still pretty green to it. I was going to follow the instructions from this post - should work right? https://forum.xda-developers.com/note-4-att/general/expert-phone-trashed-t3573110
And Norbarb, I have no idea what my Baseband version is. I did a quick google to see if I can locate it somewhere but couldn't figure it out. How can I check?
I do appreciate your help.
Click to expand...
Click to collapse
Can you reboot to recovery?? There's some info there regarding your current setup
Ironically, now I can't even get the phone to turn on. I bought a battery charger for the Note battery to see if that is the issue. I can't get the battery to charge even when it's plugged in. That arrives Monday so I'll update shortly.
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Popped in the charged battery from my new charger and it came right on. Had it on for a little bit just messing around with things. After rebooting it myself a few times, it now is reverting back to it not even turning on, even with a charged battery. I pull the battery 10-20 times, hold the power button without the battery to clearly out any remaining electricity and still no go. I have 2 batteries and neither work. So I'm going to let it sit and if I can get it to come on, install Wake Lock.
Does anyone know if I can revert back to 5.1? I'm not sure how my Baseband effects that. Thank you for all of your help! If I can't get this, I think I may go back to my S3 vs a Pixel.
Punker1234 said:
Quick update:
Baseband is N910AUCS2EPK3. I'm not sure if that means I can or can't roll back to Lollipop.
Click to expand...
Click to collapse
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Punker1234 said:
Holy crap, awesome man. Thank you. At this point, I can't even get the phone to turn on with 2 different batteries. Tried holding the power button down for awhile and letting it sit for hours and still nothing. Not sure what the deal is with this thing. I'll keep attempting.
Click to expand...
Click to collapse
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
ljjehl said:
Try holding power button, home button and volume up all at the same time while its powered off. If you can get to Recovery screen here, then you just may be getting somewhere. I would then wipe data/factory reset, then reboot again. If this doesn't work, you can then try holding power botton, home button and Volume down at the same time. This gets you in bootloader mode. Once you get there, only way out at this point is pulling battery (to start over) or get started on Odin flashing.
At least I have kept OTA from working, with this debloater from this link: https://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Click to expand...
Click to collapse
Thanks. Yea i can't get into recovery or the download mode. I bought a battery charger just thinking my phone wasn't charging them. The first time it started up perfect. Now I can't get it to come up at all. As mentioned, I'll keep trying. Wondering if something else has gone wrong, or if it's software related still.
ljjehl said:
If you have this, you can easily go to Odin and flash 5.1.1. I don't have the link to the LP Odin files, but heres the Odin link for the MM files in OP:
ODIN FILES to get back to EPH5 and latest ODIN
ODIN
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
https://forum.xda-developers.com/no...hmellow-att-server-link-installation-t3407308
Make sure you can be able to stay in Bootloader for a while before you attempt this, because if your phone dies before the Odin flash completes, you probably likely just created a brick.
Here's my How-To in that same thread. I've also used the newest Odin available with same good results.
https://forum.xda-developers.com/showpost.php?p=68620446&postcount=1180
In fact, I'm about to reflash back to 5.1.1 again from latest updates. MM is pissing me off on that battery issue again. I just wish I can keep it there and keep ATT from pushing OTA without me agreeing to it.
Click to expand...
Click to collapse
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Punker1234 said:
Got the phone to turn back on. Quick question. In your post, you mention 4 ODIN files. I only have an MD5 file and a PT file. Is there something I'm missing? I downloaded the stock rom from the top of my post. Thank you!
Click to expand...
Click to collapse
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
ljjehl said:
Marshmallow full odin file thanks to @mmaku
EPH5 ODIN FILE
There should be a zip in here that you have to extract four files to a folder. You will use the Odin exe program to look for those files. Just follow my howto notes I wrote in the link I posted. This is to the Marshmallow stuff. Forget the MD5 and pit file unless you know what you are doing. Since I don't know where that came from, I won't even suggest those 2.
Click to expand...
Click to collapse
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Punker1234 said:
Ironically I'm looking to get rid of Marshmallow because I think 6.0.1 screwed up my phone. It was working great prior to that. So the LP files I have are the MD5 and pit, supplied in the 3rd post. Is there somewhere I should look for LP files? And to be clear, are there "regular" rom files for general use, and then ODIN specific files? ie, you could have a "regular" 5.1.1 file, and then ODIN specific 5.1.1?
Click to expand...
Click to collapse
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
ljjehl said:
Well, I have the 5.1.1 Odin files also, but will have to zip it and upload, unless someone else has a link faster
Click to expand...
Click to collapse
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Punker1234 said:
Is there a way to use the files that I have? Not using ODIN? Or is that not recommended?
Click to expand...
Click to collapse
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
ljjehl said:
With the mess you have, I would think you want to Odin flash a whole new setup. You don't know what's wrong and a partition could be corrupted. If it's hardware, nothing you really could do about it anyways
Click to expand...
Click to collapse
Got it. I looked around and cannot find the files for ATT. I see them for others I think, but ATT is a ghost. Would you mind uploading if you can? If not I understand. I appreciate all of your help! Crossing my fingers that my Note 4 is still alive and well.
I'm really hoping someone can bail me out here before I...
I have made a mess of my new (to me) Note 4. I bought it as an Unlocked GSM. It arrived booting with a Sprint screen. I have Safelink BYOP service. When I switched from my Note2 to Note4, yesterday, an ATnT sim card was used to activate it with Tracfone. Everything seemed to work EXCEPT for MMS - I could not send nor receive pictures. I read -what I thought was- clear instructions here on the forum, I started downloading and attempting to root my phone, hoping that would solve the problem, since tech support had no answers.
I followed the instructions in this post - https://forum.xda-developers.com/note-4-sprint/help/rooting-sprint-note-4-pj1-t3495306 . Now the phone will only boot to download mode, or I can use the up volume button to get to the program to install, restore, etc. I have tried several times - with a couple of different .tar files. This last attempt - I tried to restore it - that also failed. My old eyes can not really see the tiny text but I did see in Odin3 that 1) No MDS found 2) Systemless mode Boot img support required 3) Boot Image Patcher Failed. When I attempt to install the SuperSU, from the thread, it gives me similar errors 1) NO MDS file found 2) (under Boot Image patcher it says FAILURE / Abort after extracting Ramdisk.
If anyone could help me out, I would be most grateful.
JadenEllis said:
I'm really hoping someone can bail me out here before I...
Click to expand...
Click to collapse
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Once you get phone back on stock. I'll show how to root!
Thank You
Thank you so much for the reply. I have downloaded the files you put in my post. I will attempt to do these things now, but I have a question. I stayed up fighting with the phone all night. I probably did some things I shouldn't have? I realized that I was getting stupid and quit, but I did (maybe) put some other stuff on the phone that night. Should I use the Clean or wipe function in TWRP before I do anything else???
Yes, I can boot to downloader or to TWRP. The phone (on its own) is now stuck trying to load with the Note 4 splash screen - but I can boot to either with the vol +/- buttons.
SamFirm did not work. It said Unable to fetch... please check data or enter manually.
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
First - THANK YOU all for the assistance.
Yesterday, none of the suggestions were working, but I kept at it. I was finally able to install the most current Stock tar that I could find. This phone had updated to the most current version available for the phone - it had Marshmallow 6.01. NOW, the red and yellow tamper errors appear to be gone from the Note4 splash screen - BUT, it boots to Sprint Activation so it won't fully load to OS. I read a post about removing the Sprint Hands Free Activation, but it gives two ways of doing so. 1 requires having a rooted phone (I am assuming it is not rooted now?) and the other uses ADN Connect, and I am not sure what that is.
I'm not really sure what to do from here? Any assistance appreciated. Can I start from step 1 of the original post to install SuperSU now?
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Well, the sun is about to come up - again - but I think I got it! This has been a learning experience to say the least. I wasn't really planning a crash course in Android, but thank you to all who responded. And to :Samep too!
I think I get it
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
JadenEllis said:
So, after a little rest I have a Note 4 with the most current stock tar. When I left it, at sun up, I had a slightly older stock version and rooted through TWRP 3.0.2.0 and rooted with the latest version of SuperSU. I spent a couple of few hours continuing to read and figure out how I would get it updates. If I could ask just a couple more questions??
If I put the TWRP 3.0.2.0 will the tamper warning come back to the flash screen?
Can I put TWRP on without rooting with SuperSU?
If not TWRP - is there a way to do a full backup without it? I REALLY want to get a good backup of what it has now - a fresh install of the latest 6.01 - and nothing else.
Thank you again.
Click to expand...
Click to collapse
Sorry bud. I'm so busy. Haven't been online since i message you. Glad you got it.
Rookie messed up..
aaron74 said:
I pm you also. Read it first, make sure I'm right.
Then download attached file samfirm.
Here's it's original post, to show how to use, https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
Use that program to download the stock firmware for your phone.
Use model number: SM-N910P
Use Region: XAS
Then use Odin to flash stock firmware. All should be good then!
Added Odin! Use this version!
Click to expand...
Click to collapse
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
meBn360 said:
Thanks in advance i appreciate your time
Hello. I have similar issue as described here on this thread. I purchased an unlocked note 4 to run on cricket/att was working fine. Except lte. I tried to root an add nougat an ive screwed up. Somehow ended up in hidden menu. And chabged something made me have no service so i reset didnt work i factory reset data reset switched from global to cdma to lte. An nothing phone says 3g when its in activate your phone menu but does not work. Also it now says im on sprint network in about phone. Please help. Thanks again in advance.
Click to expand...
Click to collapse
Sorry I don't get on here much lately. Just seen your post.
Without knowing exactly what you did. I'd say you lost your unlock. If you had an unlocked sprint phone. And tried nougat. I believe i remember that upgrading to nougat was messing up people's EFS partition. And that's where the unlock happens. Did you make a backup?
I always tell everyone, the most important thing you can do is have a full working backup of every partition.
Hope that sheds some light
Hi everyone, this all started when I tried to flash a patched boot image for root and seemed to get worse from there. There's no data on the phone that I care about so just wiping it and getting it to boot would be preferable.
I've tried using the skipsoft toolkit (I have the ultimate version if that helps any) to try and get it to flash a freshly downloaded stock image, but for whatever reason after answering all the questions it extracts everything, does all the checks, then says "device is not set" and just jumps back to the main menu.
I've tried downloading the factory image right and running the flash-all script, it goes through the entire process which looks promising, but then just reboots the phone, I get the nice "your device is corrupt" message, press the power button to continue, but then it just hangs at the white "Google" splash screen with the little unlocked icon at the bottom, and doesn't move past that.
I know the version that I had on here prior to the problems was 8.0.0 (OPD1.170816.010, Sep 2017), so that's the one I've been trying to work with.
Not really sure where to go next, hoping someone has some advice for me.
Thanks everyone.
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Never use a toolkit, they can hide error messages and displays that can help diagnose some issues. Always try the step by step methods to rescue provided by the excellent guides available here.
uicnren said:
how long are you waiting for it at the splash screen? let it go for about 20 minutes before you do anything else.
other than that, go into recovery, wipe and try to install factory images again
Click to expand...
Click to collapse
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
krash2k said:
Thank you very much for your response. I left it at the splash screen for a pretty long time.. probably about a half hour at one point.. nothing was happening.
However right now when I boot into recovery I get the little android dude on his back and it says "No command"..
Click to expand...
Click to collapse
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
uicnren said:
Thats correct, while on that screen, hold the power button and tap vol up, you will then be in recovery, do a factory reset.
Also, make sure your adb/fastboot are up to date.
I would recommend trying to install the latest 8.0 images as well.
If all else fails, wipe the devices, grab whichever stable system image you want, then manually flash all the files 1 by 1. See HERE for some guidance.
Click to expand...
Click to collapse
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
krash2k said:
Thank you again for all the advice.
- Downloaded 8.0.0 (OPD1.170816.025, Nov 2017)
- I believe my rookie mistake was using the previous versions of adb/fastboot that I've had for a while.. on google's SDK website it clearly says ***26.0.2 (October 2017) Add support for Pixel 2 devices*** in their changelog.
- Extracted the factory image and ran the flash-all script
Looks like a success, booted into the initial android setup right now after like 30 seconds. I appreciate all of the help.. I honestly wouldn't have thought of updating those binaries without being advised to.
Click to expand...
Click to collapse
:good:
uicnren said:
:good:
Click to expand...
Click to collapse
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
krash2k said:
Circling back to how this all began, do you think those old binaries would have caused this to happen in the first place?
What I originally did was push the stock boot.img to the device, used Magisk Manager to patch it, then pulled the patched_boot.img from the device. Then booted into the bootloader and did
fastboot flash boot patched_boot.img
I know it was an old version and it would be a complete assumption that that's what went wrong -- but do you think there is a chance of that? (asking because I'd still really like to root this thing)
Click to expand...
Click to collapse
honestly, Im not sure. But I also didnt think it would make a difference when flashing the stock images back, but it does. I guess anything is possible.
Yep.. it definitely did. I guess this is a lesson for knuckleheads like me who start messing around before properly updating everything.
I just did all of the same things I did earlier, and it booted fine, with root. Lots of wasted hours over a dummy move.
Thanks again for all the help!
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
State.of.mind said:
I am having the exact same issue, but I cannot seem to find a fix. I have updated my adb & fastboot. I am trying to update my device to the latest 8.1 image. Currently, my device is on 8.0. I ham not sure what I am doing wrong. Are you all unzipping .zip image file inside of the factory image zip as well?
Click to expand...
Click to collapse
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Badger50 said:
That zip inside the factory image needs to stay zipped. You can extract it for the purpose of getting the boot.img for use at a latter date. However, if your flashing the full factory image, then it needs to stay zipped :good:
Click to expand...
Click to collapse
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
State.of.mind said:
Thank you. I didn't know that I had to click and run the flash file. I thought I could just use the flash all command
Click to expand...
Click to collapse
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
On second thought I think that it didn't work because I didn't have the factory image unzipped inside of the platform tools folder? The good news is that I'm up and running
v12xke said:
It's the same thing (either way is doing the same thing). Just be sure that if you want to keep your data that you edit the .bat file and remove the -w switch and save before running it.
Click to expand...
Click to collapse
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
nickmilla15 said:
This always causes a bootloop for me. Happened from December to January, and just now January to Feb. WTF am I doing wrong?
Click to expand...
Click to collapse
Go back to the basics. Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december). Add that folder to your path statement/environment. Download the FULL image (not OTA). Open that zip file and extract into the same ADB/fastboot folder. Do not unzip the included, nested zip file! Open flash-all.bat and remove the -w switch and SAVE. Boot your phone to the bootloader, and then run the script either way (clicking or fastboot window). There are SO MANY better guides/tutorials out there to follow step-by-step. Maybe read/post in those if you have any further issues. Best of luck.
v12xke said:
Make sure you only have one copy of adb/fastboot on your rig, and that it is the very latest (december).
Click to expand...
Click to collapse
This was my mistake when I was having all of those problems. I was using older versions of adb/fastboot. Everything looked like it was installing alright but then it would just keep bootlooping.. was very frustrating. It was a relief when replacing those binaries with the updated ones worked flawlessly.
if you have managed to get it work then have fun otherwise just use deuces script as per the instructions provided in op.
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
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
adrian0883 said:
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
Click to expand...
Click to collapse
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
i can help you , if your device still soft break
Osamaaj03 said:
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
Click to expand...
Click to collapse
sahelkhan022 said:
i can help you , if your device still soft break
Click to expand...
Click to collapse
it is, I think the problem is with the super image but I'm not 100% sure. so if you can share a full mtk client backup it would be awesome. if not, a super image will do
your device stuck on logo ? or deadboot ?
842.92 MB file on MEGA
mega.nz
sahelkhan022 said:
your device stuck on logo ? or deadboot ?
Click to expand...
Click to collapse
every time I try to turn it on it bootloops to fastboot mode, I suspect that the issue is a super image I found online, flashed not knowing that it was corrupted (which I discovered later), and I foolishly didn't create a backup (why I went and downloaded the corrupted image in the first place) thinking that I will never go back to the stock rom but now after I have used a couple gsi's for a while found out that the og rom performance was much better and decided to go back
sahelkhan022 said:
842.92 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
so this is just a bunch of .bin files that I have to flash using mtk client to said partitions? just making sure
and just to let you know I might not be able to download the file today, the internet is pretty sucky where I'm rn, so I hope you don't have a problem keeping the file up till tomorrow. and just wanted to thank you for the incredible help, I've been trying to fix this phone for the last two weeks which was headache inducing say the least.
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
sorry for the late response, but yeah I've flashed all of the files using mtkclient and it didn't work Idk if I have messed things up, I thought reflashing all of the stock firmware would fix everything but it seems that there's still something wrong
sahelkhan022 said:
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
Click to expand...
Click to collapse
I've unlocked the bootloader and disabled boot verification, tried fastboot -w and fastboot format userdata and non of it worked, and I'm really sorry but I can't share my screen because as I've mentioned before my internet is bad and I had to go somewhere else to get the files. can I share anything else with you that might help, I have some recovery log files
IT WORKED!!!!! I don't know what was the problem, I've tried flashing the files again but this time using the terminal instead of the gui AND IT WORKED. THANK YOU THANK YOU THANK YOU
I'm going to upload the files later in case someone else encountered the same problem