Related
Hi,
I have moto g 2014 dual sim. today I tried to reflash the os but got "Failed to validate system image" upon reboot. So I unlocked the bootloader and again reflashed the os but got bootloop.. Please tell me how to boot my moto G 2014?
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Sorry for posting in different section, but I need help
eksasol said:
Read the instructions and flash it correctly with the correct firmware. Also post your question in the correct section.
Click to expand...
Click to collapse
Let me tell you the series of events that led me to have bricked Moto G 2014:
1. I had X1068 Moto G 2-14
2. Wanted to reflash firmware and followed the steps provided in 4.2 section here http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
3. I got "Failed to Validate System Image" when I tried to reboot.
4. I was advised to unlock bootloader and reflash firmware. I did the same but got bootloop when I tried to reboot.
5. Now when I power on the phone, bootloader unlocked warning message comes and the screen blinks with the same message..
Please help Bro..
Who ever told you to unlock bootloader to flash firmware is giving bad advice. It is not required to unlock the bootloader to flash the factory firmware.
Make sure you're using the driver from here: http://www.mymotocast.com/download/MDM?platform=windows
(If you have other Android ADB drivers installed, uninstall them first, before installing this one.)
Make sure you are using mfastboot.exe, not the regular fastboot.exe.
Make sure your downloaded firmware is not corrupt and you got the correct version of the firmware for your device, there are different ones.
Download the firmware from here: http://sbf.droid-developers.org/phone.php?device=36
I believe your file is "Blur_Version.21.11.14.titan_retaildsds.retaildsdsall.en.03", but check on it.
After you reflash, make sure you boot into recovery mode and do a factory wipe.
The firmware for this phone is split into 3 files, so make sure you flash all three of them.
Issue Resolved
DillonFixDroids said:
If you have winrar or 7zip you can extract the firmware and take the "boot.img" file and flash it separate from the other firmware and it should work. That's how I do mine.
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks bro.. It was my mistake not to flash all files in the firmware folder.. apart from three system files (0,1,2), we also need to flash fourth system file (3) in the firmware folder... Thanks again bro...
MotoG 2nd Gen
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
4dglobal said:
Folks, I got a MotoG 2nd Gen (XT1068) I'm trying to root it but not successful. The main reason for rooting is that I want to record all my calls. Any solution?
Thanks,
Raj.
Click to expand...
Click to collapse
Please be more presice, have you unlocked bootloader, before trying to flash the recovery?
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
joserodriguezv said:
Greetings from Venezuela. Just recently, I bought a new Moto G since my old S3 got severly damaged which made it unrepairable. I loved the reviews about de Moto G, but sadly since I got it I've had no luck with it.
While being connected to a WiFi connection, just looking around the celphone's settings, the phone required a system update straight off the bat. I had noticed before the update that the phone was instantly rebooting once the inactivity timer went off locking itself. Obviously after some time I did notice it by locking the phone manually (pressing the power button). I'm not that geeky or experienced in the Android field, but by doing some research on the web I've read some stuff that makes me not lose all hope on the phone, making me want to fix it.
I've tried factory resets, recoverys and nothing has worked. It has made me really frustrated not being able to fix the issue. All I've really done refering to flashing is unlocking bootloader, but still without flashing anything yet to make sure what I'm doing is the right thing to do.
Specs
Android version: 5.0.2
Baseband version: MSM8626BP_1032.3112.97.00R
RETUSA_AWS_CUST
Kernel version: 3.4.42-gf18cb80
System version: 22.46.12.titan_retuaws.retuaws.en.US retus
Need help with this, and I'll be eternally grateful with anyone that can help me.
P.S: new to the forums. In any case that I'm missing something, let me know.
Click to expand...
Click to collapse
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
reefuge said:
SEE POST#3 USA AWS CARRIERS for latest update - READ INSTRUCTIONS
Click to expand...
Click to collapse
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
A New Problem
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Goutham_SRIRAM said:
I recently got an ~138mb OTA update, tried to install it, after downloading it, but it failed at default recovery installer, rebooting with an error message saying "Update installation unsuccessful". Hence, I tried it with a custom recovery TWRP installed in my mobile, with TWRP manager app for android (with my phone rooted obviously) So after downloading update, on giving install, it goes to TWRP recovery main menu, from there I dont know how to install the downloaded update, or where it is available to browse to... Being unsure, I rebooted it to normal boot up, but no matter what I do now, the phone after turning on in the home screen, automatically powers down(switching off) to TWRP recovery main menu, I am stuck here please help me, someone.
I dont wanna lose all my data!! Give me a suitable solution
Click to expand...
Click to collapse
ota can only be installed to non rooted stock roms with stock recovery
tbh you need to minimum factory reset
but I believe you will need to install stock rom from scratch
---------- Post added at 06:54 PM ---------- Previous post was at 06:52 PM ----------
joserodriguezv said:
I followed the inscrutions, successfully flashing stock rom. But the bug is still there since the phone keeps rebooting once the screen is locked. Still need to know if there's any fix. Thanks for the help!
Click to expand...
Click to collapse
Never had or seen this all I can suggest is a factory reset twice and a few reboots to see if settles down
Guys i need help! I have the european Dual Sim Moto 2nd gen, locked bootloader and i tried to install Android Marshmallow via the indian zip (soak test) that i found in XDA. After installing the update via internal storage, it got stuck in optimizing 157 apps/158, it bootlooped and now it stucked it 1/1 optmizing ... What can i do???
Please, anything.
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.
JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!
As in the title. I have an EVA-L09 running android 7.0 .
I am about to unlock the bootloader but from what I gathered on the forums here, anyone who proceeds with rooting on 7.0 either simply fails to do so or is stuck in a boot loop.
So: has anyone rooted on 7.0 and how did you do it?
Big thanks
The more important thing is what is your build number. I know for b38x and higher you need a twrp with loop support and flash able SuperSU with loop support. I'll post links later on how to do this.
I do have my phone rooted on nougat by the way.
benjamen50 said:
The more important thing is what is your build number. I know for b38x and higher you need a twrp with loop support and flash able SuperSU with loop support. I'll post links later on how to do this.
I do have my phone rooted on nougat by the way.
Click to expand...
Click to collapse
Yeah, sorry for not mentioning it before - it's b386.
Link
http://download.chainfire.eu/supersu-stable
Steps
Unlock BOOTLOADER
Install TWRP
Flash SuperSu via TWRP
I have B366.. do you have some procedure working?
Inviato dal mio EVA-L09 utilizzando Tapatalk
Okay, so, after shoveling through a huge amount of threads and then managing to comprehend what they say (I assume English wasnt the authors native language) I unlocked the bootloader, flashed TWRP and then Chainfire. Thanks to the corresponding posters anyway - I don't know if I would have been able to root properly without them.
I did NOT use the official versions of anything - neither SuperSU or TWRP:
Anyway, here are the threads I used:
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258 (for SuperSU, 1st link works for 386, I picked permissive SE for older builds go to the second link section)
https://forum.xda-developers.com/p9/development/twrp-t3565703 (for TWRP, this seems to be specifically updated to work on all P9s)
I had no issues during the whole process. As for the bootloader code, I had to contact Huawei support as they give out the codes freely without any nonsense (just had to wait 1 working day).
Also - HRK tool as far as I could tell ISN'T recommended on newer builds. If you use it, you run a huge risk of soft bricking your phone - it uses outdated versions of everything and that's why it breaks peoples phones.
How did you unlock your bootloader ?
Robert- said:
How did you unlock your bootloader ?
Click to expand...
Click to collapse
Used
Code:
fastboot oem unlock codehere
Got the code from Huawei support, you can email them and they're required to give you the code. Took a day to get it from support where I live but thats understandable as I contacted them at the end of a working day.
Can you (please,please) give me a full tutorial ?
Like,what do I need? ADB ? How do i set everything up?
How do I start my phone in fastboot?
I am kinda a noob when it comes to doing stuff manualy..
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...
Same problem and I didn't find any solution yet.
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli
It worked for me mate! Thank you
k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...
jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?
Worked for me too, thanks!
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader
wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?
k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.
Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse
whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
You didnt do it right. I would suggest youtube the magisk rooting process
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol
TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.
Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?
It's real like a $2 dollar bill.
bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.
Did a root today without issues on my S10 with ASG8
ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?
chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!
ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.
Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.