Hello,
I recently "upgraded" to Android 6 and I hate it. Not only do I not like it but my phone is very unstable and reboots and random intervals. Battery drain is also insane, lasting only 1 day.
Please let me know how to rollback to previous Android version. I am willing to donate for an answer that works.
Thanks!
UzY3L said:
Hello,
I recently "upgraded" to Android 6 and I hate it. Not only do I not like it but my phone is very unstable and reboots and random intervals. Battery drain is also insane, lasting only 1 day.
Please let me know how to rollback to previous Android version. I am willing to donate for an answer that works.
Thanks!
Click to expand...
Click to collapse
1: make sure you have stock recoveries in place (both "recovery" & "recovery2" partitions)
2: have the stock b029 full rom (links available @xda or needrom.com) in the following folder on your sdcard: dload/UPDATE.APP
Make sure this is the extracted file from the zip, not the zip itself
3: power off your phone, press volume down+up+power until you enter eRecovery mode
Happy flashing
In case your phone doesn't recognize the update package, you can download it directly from your phone:
when rebooting, ensure your phone is plugged in via USB to your PC
No luck, bro. Same as before. Phone checks the file, goes from 1 to 4% and then at 5% (when it says "Installing") it says Update Failed. Reboot now.
Tried with eRecovery also (volume+ and USB cable inserted). It connects to WiFi but can't find any package.
I think the only option is to sell the phone and buy a new one with the factory firmware.
Lol, that's not the only option. Download Huawei firmware extractor, extract boot.img, recovery.img, cust.img, cache.img and userdata.img from the B028 firmware (not b029)(you can skip system.img). Use adb and fastboot to flash those files. After you flashed then repeat the firmware flash procedure with firmware b028 in dload folder and vol- vol+ and Power buttons. Did a rollback several times, worked every time for me.
EDIT:
Also here is a more detailed description:
http://forum.xda-developers.com/showpost.php?p=66844093&postcount=2
Sent from my HUAWEI P8max using XDA-Developers mobile app
My phone is pure stock. No root, no bootloader unlock, no nothing. Will this still work?
UzY3L said:
My phone is pure stock. No root, no bootloader unlock, no nothing. Will this still work?
Click to expand...
Click to collapse
You need your bootloader unlocked. You can use dc-unlocker to do that. It will cost you 3$ or 3€ and 10 minutes of your time:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
Still more convenient that reselling the phone.
I was hoping that wouldn't be the case. But I guess there is no cure for stupidity, since every time I "upgraded" my phones ever since the Galaxy Note N7000 got Android 4, they always ****ed it up, every single manufacturer. They're not at fault here, I'm the idiot who never learns his lesson.
So yeah, selling my phone it is since if you unlock the bootloader, you lose the warranty and that will make my phone sell for dirt-cheap, since I cannot use it with Android 6.
Thank you all for your help but it looks like this is the only option.
The first chance I get (someone makes a similar-sized device) I will abandon Huawei. Hardware is great but the software is utterly horrid! No-name chinese phones have much better software support than they have.
Huawei - Make It Impossible To Use
UzY3L said:
I was hoping that wouldn't be the case. But I guess there is no cure for stupidity, since every time I "upgraded" my phones ever since the Galaxy Note N7000 got Android 4, they always ****ed it up, every single manufacturer. They're not at fault here, I'm the idiot who never learns his lesson.
So yeah, selling my phone it is since if you unlock the bootloader, you lose the warranty and that will make my phone sell for dirt-cheap, since I cannot use it with Android 6.
Thank you all for your help but it looks like this is the only option.
The first chance I get (someone makes a similar-sized device) I will abandon Huawei. Hardware is great but the software is utterly horrid! No-name chinese phones have much better software support than they have.
Huawei - Make It Impossible To Use
Click to expand...
Click to collapse
Unlocking the bootloader doesn't invalidate the warranty, so you're good to go. I for myself love the P8 max, hardware and software. The B029 works extremely good for me after customizing it a bit to fit my needs. There is no reason for me to update to Android 6 since everything works so flawlessly.
If you want to keep the size and don't go any smaller, one of the acceptable alternatives is the Asus Zenfone 3 Ultra, even thou I prefer the design of the P8 max.
Unfortunately, in my retarded country (Romania) I have to call Huawei to get the bootlocker unlock code, which by their terms in this ****ty country, invalidates the warranty. I've been through this nightmare before, with the DAV-701L in which I had to call in UK to get an unlock code, which they even said that I will lose the warranty.
These guys ****ed something up because, here's the kicker : you have to get the unlock code FROM Huawei, which invalidates the warranty. But to invalidate the warranty, you need permission from Huawei. **** logic.
The Zenfone is looking mighty delicious, you know. Thanks for the tip!
UzY3L said:
Hello,
I recently "upgraded" to Android 6 and I hate it. Not only do I not like it but my phone is very unstable and reboots and random intervals. Battery drain is also insane, lasting only 1 day.
Please let me know how to rollback to previous Android version. I am willing to donate for an answer that works.
Thanks!
Click to expand...
Click to collapse
I must admit that I'm not overhappy with 6.00.
In exchange of a few new feature I lost root and things aren't so smooth anymore. Gonna roll back as soon as I receive my Xiami Max as a backup phone. Asus Zenfone 3 Ultra will be my next buy, but waiting for a phone so long it's a pain in the ass.. they shouldn't announce models months before they can release them. Like HP Elite X3 (January and just coming to shops) or LeTv X910 (which never saw the light) ?
hi guys,
I apologize for resurrection of this thread but does anyone know the location of the stock b029 full rom file ?
I do remember I was running MM and I want to give my P8 max to my niece but unfortunately it's missing OS.
I could install twrp and I was searching for the file but the links are dead and I think this would be the best place to ask.
Anyway, thanks in advance and sorry for bumping up 2 years old thread.
Peace
77Eric77 said:
hi guys,
I apologize for resurrection of this thread but does anyone know the location of the stock b029 full rom file ?
I do remember I was running MM and I want to give my P8 max to my niece but unfortunately it's missing OS.
I could install twrp and I was searching for the file but the links are dead and I think this would be the best place to ask.
Anyway, thanks in advance and sorry for bumping up 2 years old thread.
Peace
Click to expand...
Click to collapse
needrom.com
Hirs_E_Fruit said:
needrom.com
Click to expand...
Click to collapse
I got it, thanks Fruit
Related
after i upgraded Mate7 it keeps restarting.
i tried many tools but none of them succeed
Mi flash tool - Miss match Image and device
Sp flash tool - null
HI Suit 4. - don't support your phone
when i used Huawei-Update-MultiLoader it says error opening serial port
the last rom i upgraded to is on the internal storage of the mobile
my fast boot is locked
can any one help plz
I'm in the same case bro i feel you... But my big mistake was to unzip the update.app from the marshmallow update.zip , then i placed it to dload, and now my phone is rebooting... my fastboot is locked too
same mistake here... my mate7 keep restarting. and i cant fix also in fastboot mode,, always failed.. any help?
I got the same problem - unzipped the update.zip and placed only the update.app in dload *facepalm*
TheGeosh said:
I got the same problem - unzipped the update.zip and placed only the update.app in dload *facepalm*
Click to expand...
Click to collapse
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!
wkharposh66 said:
i had that problem when tray to update it to MM tray it all the way no LUUUUUUUUCK
last i went to the Huawei Services the joke is they also can noooooooooooot do anything ??
last they decide it to change the main board of the phone then .. phone start with KK after that no problem
but i will never ever buy this brand again !!!!!!
Click to expand...
Click to collapse
How much money did you pay for that?
Phone ? under warranty so I didn't pay anything
Also I didn't tell them I was upgrading to MM
Just I said the phone its keeping restarting…
Not to offend anyone, but the fault is not from Huawei. You guys keep trying to install updates that may not be meant for your phone. Can only blame yourself. If it's not at OTA update, just don't risk it!
Mine runs great on B130 kitkat with unlock and root.
RobboW said:
Not to offend anyone, but the fault is not from Huawei. You guys keep trying to install updates that may not be meant for your phone. Can only blame yourself. If it's not at OTA update, just don't risk it!
Mine runs great on B130 kitkat with unlock and root.
Click to expand...
Click to collapse
I totally agree. But if there is any as*hole like me that wants to try a beta build, there should be a rollback alternative, right? Yeah, it's not very productive to blame the brand, but the brand should cover different scenarios in case people go full re__rd and install unverified software on their phones.
hi all!
i have been lurking around XDA for years, and until taday I have always managed to find solutions to probs with my android devices...like I said... until today
Yesterday I have been given a Honor 6 H60-L12 device stuck in bootloop.
I only have been told that it has failed and update from emui 3.1 to emui 4, "stuck at 5%" (on 3 button flash i suppose)
I do not have any other information.
I can access recovery and bootloader.
I tried to flash a EMUI 3.0 on 3button flash, but it doesn't even access the 3B update interface, while it does access it (screen with a red exclamation mark) if no microsd is in use
Bootloader is locked and i obviously can't access the system to retrieve the codes necessary to request an unlock password.
My question to Honor 6 gurus here : is the phone gone for good ?!
If you have the box now, it can have the necessary infos you need
aretheia said:
hi all!
i have been lurking around XDA for years, and until taday I have always managed to find solutions to probs with my android devices...like I said... until today
Yesterday I have been given a Honor 6 H60-L12 device stuck in bootloop.
I only have been told that it has failed and update from emui 3.1 to emui 4, "stuck at 5%" (on 3 button flash i suppose)
I do not have any other information.
I can access recovery and bootloader.
I tried to flash a EMUI 3.0 on 3button flash, but it doesn't even access the 3B update interface, while it does access it (screen with a red exclamation mark) if no microsd is in use
Bootloader is locked and i obviously can't access the system to retrieve the codes necessary to request an unlock password.
My question to Honor 6 gurus here : is the phone gone for good ?!
Click to expand...
Click to collapse
not quite..
there can be 3 possible scenes
1. you can find all the info needed for requesting unlock code
or you can use an app for pc (something called DC unlocker) which can unlock your phone without unlock code
2.try with another sd card (assuming that somehow sdcard has formatted and could not be used again for the purpose) , I know, sounds silly, but giving a try doesn't cost you anything
3. I think, during the update process, phone has copied the information from emui 4, and somehow aborted the installation, (most probably due to a faulty download), so phone recognizes itself as a marshmallow bootloader, so it might be wise to first flash a rollback package to emui 3 and then flash emui3 (freshly downloaded is recomemded)
or
you can try flash emui4 again, newly downloaded and extracted to any other sd card
if these three cant help it, then its the service center
and even that cannot help it
PHONE IS GONE FOR GOOD
HOPE I MADE SOME SENSE :fingers-crossed:, ALL THE BEST :good:.. PING ME HERE IF YOU HAVE ANY DOUBTS, first option has the highest success rate
thilak devraj said:
not quite..
there can be 3 possible scenes
1. you can find all the info needed for requesting unlock code
or you can use an app for pc (something called DC unlocker) which can unlock your phone without unlock code
2.try with another sd card (assuming that somehow sdcard has formatted and could not be used again for the purpose) , I know, sounds silly, but giving a try doesn't cost you anything
3. I think, during the update process, phone has copied the information from emui 4, and somehow aborted the installation, (most probably due to a faulty download), so phone recognizes itself as a marshmallow bootloader, so it might be wise to first flash a rollback package to emui 3 and then flash emui3 (freshly downloaded is recomemded)
or
you can try flash emui4 again, newly downloaded and extracted to any other sd card
if these three cant help it, then its the service center
and even that cannot help it
PHONE IS GONE FOR GOOD
HOPE I MADE SOME SENSE :fingers-crossed:, ALL THE BEST :good:.. PING ME HERE IF YOU HAVE ANY DOUBTS, first option has the highest success rate
Click to expand...
Click to collapse
thank you very much thilak for you suggestions, i was going to pay the 4 euros needed to unlock using DC unlocker, when i tried, one last time, using a different version of the emui 3.1: same name of the pevious one (H60_EMUI3.1_Android5.1_6.1.1) but this one was almost 2 Gb while the other one was like 1.2 Gb... I installed it with the 3 buttons reset and it worked like a charm!
aretheia said:
thank you very much thilak for you suggestions, i was going to pay the 4 euros needed to unlock using DC unlocker, when i tried, one last time, using a different version of the emui 3.1: same name of the pevious one (H60_EMUI3.1_Android5.1_6.1.1) but this one was almost 2 Gb while the other one was like 1.2 Gb... I installed it with the 3 buttons reset and it worked like a charm!
Click to expand...
Click to collapse
glad that it worked, and I'm happy to help
My partner from Chinese 7to forum had made TWRP adaption for Nokia 5, 6 and 8. Now it's time to find out how to install custom recovery and root Nokia 7.
To achieve that, I need the official firmware of Nokia 7 TA-1041.
That's it. It will benefit a lot for both XDA and Chinese Android communities.
Current version is 00CN_0_64C I think.
Thanks a lot!
UPDATE: I got the Nokia 7 firmware, filename is C1N-0430-0-00CN-B05.rar. But I won't release it until @blackpanther0582 or @Quixote78 got Nokia 2 and 7 firmware.
UPDATE IN Mar 12th 2018 (UTC+8): I released this firmware. You can find it from https://forum.xda-developers.com/nokia-7/development/nokia-7-stock-firmware-t3762166
Can you help me with this firmware bro
hikari_calyx said:
UPDATE: I got the Nokia 7 firmware, filename is C1N-0430-0-00CN-B05.rar. But I won't release it until @blackpanther0582 or @Quixote78 got Nokia 2 and 7 firmware.
Click to expand...
Click to collapse
Any specific reasons for not releasing it for others to download?
singhnsk said:
Any specific reasons for not releasing it for others to download?
Click to expand...
Click to collapse
I got this firmware from local Nokia Service center where I sent a bricked Nokia 6 to them.
To protect the employee who gave me the firmware, I won't release it immediately.
hikari_calyx said:
I got this firmware from local Nokia Service center where I sent a bricked Nokia 6 to them.
To protect the employee who gave me the firmware, I won't release it immediately.
Click to expand...
Click to collapse
That's sweet of you. I've just got my Nokia 7 and I might just brick it while playing with it. So, can I at least stay assured that if something wrong happens, you'll privately provide me with the firmware? ?
Phone won't boot
Some help would be fantastic and greatly appreciated. I received the phone brand new just yesterday and have turned it on to set it up but it will not go past the "Powered by Android" screen. I have tried so many times to enter reset menu to factory restore it but it is not possible. I think my only option left is to somehow flash the phone with the original firmware but as I've never used a newer Nokia before, I am unsure of that too. I contacted Nokia online support who refuse to help me because the phone is exclusive to China and I am based in Australia. I feel like I have been scammed with a brand new phone that I can not use.
asking for rom to unbrick Nokia TA 1041
Hello everyone.
I would like to know if you have the rom and firmware of TA 1041 CCN 4GB ram.
I bought it on AliExpress.
After 2 hours of using it , it stopped booting normally.
The phone stays on the Nokia screen.
I cannot turn it off!
When trying to hook it to the PC , the Android driver is there , but their no device detected!
I wonder if some part of the boot chips are dead?
Can someone help him please?
Best regards
hikari_calyx said:
My partner from Chinese 7to forum had made TWRP adaption for Nokia 5, 6 and 8. Now it's time to find out how to install custom recovery and root Nokia 7.
To achieve that, I need the official firmware of Nokia 7 TA-1041.
That's it. It will benefit a lot for both XDA and Chinese Android communities.
Current version is 00CN_0_64C I think.
Thanks a lot!
UPDATE: I got the Nokia 7 firmware, filename is C1N-0430-0-00CN-B05.rar. But I won't release it until @blackpanther0582 or @Quixote78 got Nokia 2 and 7 firmware.
Click to expand...
Click to collapse
Hello everyone.
I would like to know if you have the rom and firmware of TA 1041 CCN 4GB ram.
I bought it on AliExpress.
After 2 hours of using it , it stopped booting normally.
The phone stays on the Nokia screen.
I cannot turn it off!
When trying to hook it to the PC , the Android driver is there , but their no device detected!
I wonder if some part of the boot chips are dead?
Can someone help him please?
Best regards
Ausssie said:
Some help would be fantastic and greatly appreciated. I received the phone brand new just yesterday and have turned it on to set it up but it will not go past the "Powered by Android" screen. I have tried so many times to enter reset menu to factory restore it but it is not possible. I think my only option left is to somehow flash the phone with the original firmware but as I've never used a newer Nokia before, I am unsure of that too. I contacted Nokia online support who refuse to help me because the phone is exclusive to China and I am based in Australia. I feel like I have been scammed with a brand new phone that I can not use.
Click to expand...
Click to collapse
The same problem with "Powered by Android", only I'm from Belarus. Waiting for an answer from support.
Any update on this?
Got this phone recently from china (as it is unavailable yet in my country), its great but has a ton of software issues: setup screen constantly freezing, google play fires errors faster then a tommy gun, widgets and apps crashing, etc...
Really would like to be able to flash a clean rom.
Cheers!
I sent my phone back and going to claim a refund. I really want the phone because it has the specs that I want, the size that I want, the build quality that I want, and the look that I want. But it seems there is a software issue that means it doesn't function correctly out of China.
Voronko said:
Any update on this?
Got this phone recently from china (as it is unavailable yet in my country), its great but has a ton of software issues: setup screen constantly freezing, google play fires errors faster then a tommy gun, widgets and apps crashing, etc...
Really would like to be able to flash a clean rom.
Cheers!
Click to expand...
Click to collapse
I have the same problem as you, the phone hangs on download mode after I reboot or power down consecutively 5 to 6 times after flashing the rom.
I cannot force flash the ROM, with OST LA, it hangs on "hwcfg" (C1N-0-0430-hwcfg.img) after 117 seconds of attempting to flash.
Google Play Store has been flashed in the original firmware, it is buggy as it doesnt update any application.
I think google applications are causing the phone to hang out and to bug.
I cannot seem to find a clean rom for this phone!
sithounet3k said:
I have the same problem as you, the phone hangs on download mode after I reboot or power down consecutively 5 to 6 times after flashing the rom.
I cannot force flash the ROM, with OST LA, it hangs on "hwcfg" (C1N-0-0430-hwcfg.img) after 117 seconds of attempting to flash.
Google Play Store has been flashed in the original firmware, it is buggy as it doesnt update any application.
I think google applications are causing the phone to hang out and to bug.
I cannot seem to find a clean rom for this phone!
Click to expand...
Click to collapse
My biggest problem is updating/installing apps, as you said. I'm getting error 404 and no solutions from webs fix it. A funny related issue is that the phone is not showing up in the web version of Google Play (when you do a remote install). At least I think these issues are related.
Did you experience anything similar?
Voronko said:
My biggest problem is updating/installing apps, as you said. I'm getting error 404 and no solutions from webs fix it. A funny related issue is that the phone is not showing up in the web version of Google Play (when you do a remote install). At least I think these issues are related.
Did you experience anything similar?
Click to expand...
Click to collapse
Yes I have experienced the same thing.
I have asked the reseller on Aliexpress for the original firmware.
I am waiting for his answer ...
What concerns me , I cannot find ANY ROM available for this Nokia 7 and the bootloader is locked and cannot be unlocked on fastboot.
I hope one day a developer on xda could give us a clean ROM+GAPPS, with a TWRP recovery.
Support for the firmware is not responding. The theme on community.phones.nokia.com/support/discussions constantly removes.
Any update?
Mine got stuck in "Powered by Android"
To everyone who subscribed this topic:
I released this firmware. You can find it from https://forum.xda-developers.com/nokia-7/development/nokia-7-stock-firmware-t3762166
Hey Guys,
I have been googling for a while now and I seem to constantly come across conflicting and at times worrying posts which has very much left me stuck right were I am. I just recently purchased a Mate 9 in the hope I would be able to, like all my previous mobiles install a custom rom and tweak it to my specific needs. This however hasn't been the case.
Firmware:
System 8.0.0.046
Dataver MHA-L09 8.0.0.371(C34)
Things that have been tried:
1. No I didn't get a boot unlocker code from the Huawei
2. Yes I have contacted them personally via two different channels and both returned with a we are happy to give it to you, that's not an issue, but this code doesn't exist anymore.
3. DC-Unlock tool didn't detect my mobile in manufacture mode, in which I found another forum post stating to use HCU 3.22 client instead which worked to the point of detecting my mobile, but told me that the current security patch not supported.
4. Contacting DC-Unlock, told me there is no ETA on getting this patch level to work
5. I have read people downgrading to a previous version, unlocking and then installed the custom rom via HiSuite, this doesn't give me that option.
6. I have read people downgrading to a previous version, unlocking and then installed the custom rom via firmware finder.
6.1 Issues with this is that I seen someone claim to upgrade to version 8.0.0.3.75, which is higher then mine, which enabled the rollback feature, is this correct?
6.2 Issues with this is that I have read that gpu turbo has been enabled and many have warned that rolling back to a pre-gpu turbo enabled firmware will brick you mobile and would result in a motherboard needing to be replaced for nearly the cost of the mobile itself.
I am tempted to try another site which I can't remember the name of, which if you pay considerably more then DC-Unlock. at least if they can't get the code, would be refunded. but I think that site is down now as I feel they were playing on people who didn't know how to have done it for free via the Huawei site back in 2018.
So I want to know is there a safe way to unlock my bootloader I think my only option is option 6 but just want more details from others who have done it this way before, or have I pretty much exhausted all my option and just bite the bullet and upgrade to 9.0.1.187 and possibly further through the OTA update process and just enjoy the mobile for what it is and it's limitations?
Thanks again.
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
mucski said:
You can try the spoofing method here on xda I updated from 8 to 9 with that, as long as firmware finder says your imei is approved
Click to expand...
Click to collapse
Thanks for that, I can already upgrade to 9, my system updates app is just waiting for me to accept. The issue is that I don't want to go forward. I really want to go backwards, so I can unlock my bootloader first. I'm already at the stage where I have tried most if not all the safe ways to unlocking my bootloader, but with my currently installed android version I can't. The only way forward for me it seems is the firmware finder app and SD force flash back to EMUI 5 aka Android 7 to use DC-Unlocker to unlock it first, then that gives me the freedom of installing the official Android 9 or openkirin.
I just worried as some people have stated that if you attempt a downgrade after a specific point, something about GPU turbo being enabled in later firmwares, which will brick your mobile.
I just want to hear from others who have done this successfully or if it's not possible in my case.
I have an SM-A530F and had no issues flashing roms and TWRP. I eventually tried Saboor OneUI from and my phone got completely encrypted and would only allow official binaries to be flashed. I flashed Binary 7 (Pie) to my device and tried to flash TWRP but had come across the error and after researching realised I'd have to wait 7 days with the phone continuously booted up. I have waited 7 days with nothing changed. I'm now on my 25th day and still have a prenormal KG state. But in developer options my OEM states that it is already unlocked and I can switch the toggle. I cannot flash TWRP or magisk though.
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash
Click to expand...
Click to collapse
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Zefpoes23 said:
I've tried multiple binaries and nothing. Bootloader says its unlocked and even with adb commands I get an unlocked status but the RMM/KG remains prenormal. I'm wondering if anyone can repack TWRP for jackpotlte so the device and Odin THINKS it's an official recovery binary?
Click to expand...
Click to collapse
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
almeria53 said:
The same thing happens to me and I used the chimera program and nothing works. 12 euros in the trash.
they have returned my money
Click to expand...
Click to collapse
youdoofus said:
i see you started another thread about this, so take my previous reply in that thread with a grain of salt. I still dont think its the TWRP file thats the culprit. Try reflashing stock firmware and do the 168 hour method again.
Click to expand...
Click to collapse
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Zefpoes23 said:
I know TWRP isn't the culprit. But because of my predicament having waited well over 168 hours without a reboot (oem unlock toggle is available but still shows KG/RMM prenormal) I'm wondering if anyone can change TWRP to make the device think its an official recovery. That way I could flash it with a prenormal state as I can flash stock recovery no problem. If the device thought TWRP was official then that way I could still root and flash zip roms with a locked KG. I hope I'm making sense?
Click to expand...
Click to collapse
youre not going to get the phone to think that TWRP is official. If that was possible, we would all have root and without so much as unlocking the bootloader for that matter
manifesto- posted on another thread-sorry for the dupe
A bit of history gives a bit more depth/ Just when you thought it was okay to go back in the water. I'm Canadian you can probably tell by my accent. My journey with phones has always been Samsung simply due to availability s6 s7 s8 s8+ most recently the a530w.
In order for you to understand my joy finding the A8 and my horror is that the S8 series. in North America S8 uses a Qualcomm Snapdragon chip. g950u is SD g950f is the rest of the world (exnyos) This is probably due to some kind of World Trade Organization antitrust treaty {although qualcom makes great chips} or whatnot I don't care.
i do care about is their bootloader lock policy (g950u and up) so it is impossible to unlock an encrypted Snapdragon bootloader. When I ran into the a530w exnyos, I was like a three-year-old at Christmas now you have to understand I'm not a coder I'm more of a mason I'm familiar with bricks. I'm sure we've all watch the AP file upload and Odin like we watch paint dry. So when I first got the a530w pi version April patch I was able to TWRP install I believe at the time was Pixel project or something else added magisk, xposed you get the idea.
Eventually a file got corrupt (much like @Zefpoes23) and I had to common sense restock it. I think my mistake what is going with the most current pie version (hadn't read this thread yet from @corsicanu) which is binary 7 knowing what I know now I would have probably had the ability to go a binary 4 or so. I haven't done the 7 day challenge simply not to waste my sanity. my bootloader unlock never vanished, it like it's a light switch with no bulb. I've tried to backdated front dated. I refuse to wait 7 days to find out that I'm still at the same place. . The problem is all the fixes are zip files which you need TWRP to flash. I agree, it's not @BlackMesa123 version. it's the prenormal. No I'm certainly not a developer and some of them are mobile gods. My questions maybe Elementary logical. Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort. think we're all about to become in the same boat. we could start a movement lie "#meprenormal2" In Time will tell. As or now "prenormal" is the new "normal" All I can to the devs: help me odin 3 canmodme. your my only hope
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
jthibault27 said:
Is it possible to replace a recovery image in a stock AP and Odin flash it? Repack. Also is there any way to combo a stockfirm in order to downgrade from the B7. Alter it somehow so it's thinks it's a 7 but it's actually a 4 of some sort.
Click to expand...
Click to collapse
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
jthibault27 said:
I refuse to wait 7 days to find out that I'm still at the same place.
Click to expand...
Click to collapse
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
Youdoofus said:
i have no idea what youre on about for half of this post, so ill chime in with what i could decipher and know the answer to
nope, sorry man. you cant go backwards in bootloader revisions. if you have B7, youre stuck with revision 7
you wont have much say in this refusal as the 168 hour thing is quite normal. Every A8 owner ive seen come into these forums has had to do the 168 hour thing.
Click to expand...
Click to collapse
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
jthibault27 said:
If I'm violating XDA rules please let me know. You are obviously higher up on the rank that I am. Since my post on November 10th my findings on other threads have led me to believe that this is not just an A8 problem but an entire Samsung Fleet. A summer security patch upgraded knox guard to disable any attempts to flash TWRP. If you are lucky enough to get through that stay on it. My bootloader is like a light switch I can on and off it at anytime. 168 hours is a solution for an old problem that I don't have. I'm in permanent prenormal state with the sole ability to only flash official stock firmware and in one direction v7 or higher.. Which is what Samsung wants. i'm on V7, security patch July 1st 2019. I cannot flash anything else through Odin 13.3.1. I'm simply voicing the fact 168 hours fix is to have the ability to unlock the bootloader. I have the bootloader unlocked. My kg is tripped and I believe my fix will come in Time through a modified Odin or combo firmware emerges. i will also recluse myself from posting on this thread and open my own
---------- Post added at 19:35 ---------- Previous post was at 19:20 ----------
And to clarify what I meant as to replace the recovery file in the AP stock firmware specifically unpacking the lz4 format using 7-Zip 19 ZS v144, replacing the recovery image with the TWRP Recovery image and repacking it (the AP) and flashing it hoping the phone with think it's official. I've consulted a developer who tried it several times without any luck since he shares the same problem on a50.
Click to expand...
Click to collapse
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
@mchlbenner if you have a moment, could you lend a hand?
Youdoofus said:
naw man, youre good. i had an A8 for about a year and now the older kiddo has it and it seems to be working well as i havent heard any complaints as of yet.
I, by no means, am an expert on this device and i admittedly have not kept current on the 168 hour fix no longer being relevant.
There is a fellow who had this forum on point about a year ago, cant recall his alias. Ill tag him if i can find him. Hopefully he has kept current on this device more than I.
Click to expand...
Click to collapse
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
jthibault27 said:
I started in this thread because I had a8 after researching through a bunch of different search engines I found this link
https://forum.xda-developers.com/galaxy-note-9/help/rmm-prenormal-oem-unlock-android-9-0-t3952959
it ended to be a note link. The moderator is convinced that it's all in our heads but people have been flocking to this thread because the title is so specific that it brings in people from different Samsung devices. It's like Field of Dreams, if you can't mod it they will come. Anyway, there are interesting comments. I apologize if my redirect or hyperlink is off. I'm no expert in this web forum platforms.
Click to expand...
Click to collapse
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
mchlbenner said:
This issue is true I have seen this on other a8 plus.
It part of Samsung security and no mod can fix this.
Click to expand...
Click to collapse
there you are!! so, the A8 is now not rootable?
Youdoofus said:
there you are!! so, the A8 is now not rootable?
Click to expand...
Click to collapse
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
jthibault27 said:
It's very rootable provided that you don't do what 99% of the world do before selling it on Kijiji (Canadian version of Craig's list) is upgrade the latest OTA to impress the buyer. if you have an Oreo built Axxx or Sxxx (basically an Exynos chip) you are golden. not going to get into the whole North American snapdragon-Qualcomm thing. If you have a (guessing) Pre-June 2019 security patch however 9.0 I believe you can flash TWRP (all things being equal) you have a chance. however, if you have (I'm guessing most recent models) 9.0 security patch July 1 2019+ stock (previously tripped KG on a custom ROM-which say got corrupt), you are in the non-mod world. you are stuck with 9.0 official Samsung. you can't flash oreo (until someone develops a matching binary). since through my sammobile travels, I've yet to encounter a baseband/BL Oreo higher than 4. my phone (a8 9.0) is B7
Click to expand...
Click to collapse
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
mchlbenner said:
Well I'm on gsi ROMs this will never see a Samsung rom ever again.
Also slot of don't follow rooting directions I have been lock out once on Oreo never had a problem with Android 9.
Click to expand...
Click to collapse
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Youdoofus said:
so, between what you and the other fella are saying, the newest factory OTA prevents folks from rooting this thing now, correct? That would be a shame, locking down even the F devices? Come on Samsung!!
Click to expand...
Click to collapse
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
jthibault27 said:
note: This doesn't necessarily apply to everyone since my situation was that I had a custom ROM corrupt and I restock firmware to V7 on the A8. My original custom install using TWRP had triggered kg Knox. I should have not flashed the latest stock version of 9.0. This was simply just a bridge to a new custom firmware anyway. I did not realize that I was installing a security patch that Samsung would deploy. So the question is if you go and buy the latest a, n, s 9.0 (F) can you still TWRP? Or does it say pre normal as soon as you attempt to TWRP. Rooting is not even in the realm of possibilities if you can't install TWRP. Magisk now has a feature where it modifies the AP system file which you can Odin. I thought it would pass as official. Of course, it didn't. Those dam Samsung MIT grad security engineers probably think they're better than us. LOL. All I can tell you is the toggle for the unlock Bootloader is as effective as the close door button on an elevator, you're not sure if it's connected to anything. This has been an Android War since Jelly Bean.
Click to expand...
Click to collapse
yes, from what ive gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before i got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Youdoofus said:
yes, from what I've gathered from mchelbenner, the party is over. I trust his input as he is very well versed in the A8. More than I as he has had this forum on lockdown even before I got my A8 to begin with. If he said its no longer possible, thats what i will go with also
Click to expand...
Click to collapse
If you ever come across a forum specific to this issue ({completely extrapolating the date by guess} July 1, 2019 9.0) but not necessarily specific to the A8, please share. as it stands now, my findings indicate isolated conversations in different forums on various models, sharing the same problem. We must unite! lol. truth be told, it's challenging searching for such a specific problem relating to a patch on many models.