Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
sergioricardojsj said:
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
Click to expand...
Click to collapse
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
kudos1uk said:
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
Click to expand...
Click to collapse
I've done nothing. My bootloader is locked. Nothing is changed.
sergioricardojsj said:
I've done nothing. My bootloader is locked. Nothing is changed.
Click to expand...
Click to collapse
Looking at your previous posts that is clearly not the case, good luck.
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
sergioricardojsj said:
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
Click to expand...
Click to collapse
can you share the rom you flashed please
ccalixtro said:
can you share the rom you flashed please
Click to expand...
Click to collapse
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
thanks but i cant get into fastboot mode only blinking led.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
i have same problem, i was enable camera2 api for Gcam in my phone, by following tutorial in this forum, Using temporary twrp, unlock bootloader and lock back. And now i cant update with same problem in first post picture. Please someone give us solution for fix this. Thx
Sorry- ignore this message, wrong thread.
ltf_195 said:
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
Click to expand...
Click to collapse
You don't need to make any modifications, just mounting /system with rw in twrp will break ota.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Hola Sergio Ricardo, no entendí si es oem unlock o local y después los últimos pasos me perdí, podrías explicarlo en español?
sergioricardojsj said:
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Click to expand...
Click to collapse
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
barrack1 said:
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
Click to expand...
Click to collapse
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
hola,si quieres restaurar la imagen stock para actualizar,as recovery PERO NO EN TWRP y monta la imagen desde ahí, reinicia y listo yo estoy con parche de noviembre que acabo de actualizar y antes de eso tenía magisk con Gcam y mods de audio espero les sirva
Mod edit google translate added:
hello, if you want to restore the stock image to update, as recovery BUT NOT IN TWRP and mount the image from there, restart and ready I am with November patch that I just updated and before that I had magisk with Gcam and audio mods I hope serve them
try n flash original pie fastboot rom from here
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
rexendz said:
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
Click to expand...
Click to collapse
Having TWRP installed as the recovery and just booting into TWRP are 2 different things.
Related
Hey guys,
i've a massive problem with my G4. Today i flashed TWRP on the device, after i was unlocking the bootloader. After booting up into TWRP, and installing SuperSU, I just restarted it. Now it's dead. Seriously, it's dead.
I can't start it at all. If I plug in a USB-Cable, i just see the LED Light. I've Windows, and at my Device Manager, the G4 is recognized as QHSUSB_BULK.
I saw a Thread for the Moto G (1th), and i'm pretty sure, that i can't to this like in this tutorial:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Is there any option, what i can do?
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
__Madddy said:
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
Click to expand...
Click to collapse
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900M system system.img" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
I'll try to flash each files which are in the image.
Marwycy said:
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
Click to expand...
Click to collapse
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
__Madddy said:
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Click to expand...
Click to collapse
I tried it, i can't open system.img at all. So i can't extract anything..
Marwycy said:
I tried it, i can't open system.img at all. So i can't extract anything..
Click to expand...
Click to collapse
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
__Madddy said:
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
Click to expand...
Click to collapse
Sorry, i was a bit confused because of this large list of commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
And i figured out, that it's not necessary. All I had to do ist following the official way by just using "fastboot system system.img" , with the Image from the officla Motorola website. My first file was corrupt, that was the problem.
Now my phone is working again
Thanks for help.
Marwycy said:
Now my phone is working again
Click to expand...
Click to collapse
For Rooting, don't flash zip directly,
Follow this guide, https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Take BACKUP, if anything wrong then RESTORE it...
first upgrade to 7.0 bro then go ahead with rooting .
say me if want any help??
Sent from my Moto G4 Plus using Tapatalk
---------- Post added at 04:16 AM ---------- Previous post was at 04:11 AM ----------
http://cloud.tapatalk.com/s/586730a47ebfa/superuser.zip
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Sent from my Moto G4 Plus using Tapatalk
parth00790 said:
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Click to expand...
Click to collapse
Please, provide complete information, no root method is working on latest (official) Nougat, your half information can brick other's phone and can put them in trouble...
i have used with rooted nougat
just same method for Twrp
enable usb debugging and flash twrp using adb .
then flash superuser.zip provided in previous comment and install phh superuser from playstore .
you are done bro .
i have tried and working
Sent from my Moto G4 Plus using Tapatalk
moto g4 plus brick
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
djsusant said:
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
Click to expand...
Click to collapse
Calm down. Read this.
Wrong, delete please
Ayuda/Help
Hola me podrias ayudar tengo el moto g4 xt1621, lo que sucedio fue que estaba flasheando eol parche de seguridad de 7.0 no recuerdo si era de diciembre o de marzo pero cuando acabo le di en reboot system now pero no prendio mas, solo prende el led y la pc lo reconoce ya instale los drivers pero me da error quisiera saber si me podrias ayudar a fondo a recuperar mi moto g4, disculpa pero lo pongo en ingles y español pero no hablo ingles uso el traductor, ayudame porfavor
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
TioHenry said:
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
Click to expand...
Click to collapse
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
echo92 said:
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
Click to expand...
Click to collapse
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
TioHenry said:
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
Click to expand...
Click to collapse
Okay, point 3 indicates that you perhaps need to try resetting your phone with a blankflash: you may wish to have a look at this post https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 Please read all the steps fully before proceeding if you choose to follow that post. I recall you've posted in the hard brick thread too, which has similar instructions, perhaps this may work.
I do not know if this will work, but it's worth a try.
HELP me
Can you give me the link of stock rom for Moto G4 XT1624
Hello Everyone, I wanted to share an easiest way to root our Xa Ultra phone.
Here are te requirements:
1. Xa ultra latest clean Nougat/Marshmallow Firmware.
2. Unlocked bootloader (Search the thread for a tutorial)
3. Fastboot (Search for any fastboot tutorial and drivers)
4. Download file from this thread
-This method is just for Rooting, you won't have TWRP recovery installed.
Tutorial
1.- Connect your phone to your computer in fastboot mode, (Volume up pressed while connecting usb to your computer, until blue light flashes)
2.- Open Fastboot folder, and press shift+Right mouse clic, and select "open command window" (another method if you don't have this option is to press Windows button+R then in the window write cmd and click run it will appear a command window, then go to your fastboot folder and copy the address of your folder, go back to command windows and write cd space your fastboot address and then enter, you will be in fastboot)
3.- Once you are in fastboot write this fastboot devices and it must appear your phone connected.
4.- now write fastboot flash boot magiskxaultran.img if you are on Nougat firmware, and then press enter.
4.1.- now write fastboot flash boot magiskxaultram.img if you are on Marshmallow firmware, and then press enter
5.- disconnect your phone once the process is finished and turn on your phone.
6.- Now the latest thing to do is to Install the latest Magisk manager.apk to your phone.
7.- open magisk manager and you are now rooted.
Any question please feel free to ask :laugh::fingers-crossed:
Nougat
https://mega.nz/#!qQoE3YwB!ru15jSgq2Vin1Qg-sPMMipa7jNG6SHJOT2CEo0b_HKA
Marshmallow
https://mega.nz/#!jRpylAID!3JOQ9If0nHbF6EftRE6HL0hW4mkzIMGZhy_BxRWurxs
@kiukirimas
thanks for the method bro. Can we root xperia xa ultra without unlocking the bootloader? is it possible? bcoz unlocking the bootloader leads to loose DRM keys, and even if we take TA back up, i feel the image enhancement for image and videos wont work properly. Does any disadvantage of unlocking the bootloader? Heard some camera features wont work????
Everything Will work ok, no such things on the camera, anyway you do lose the image enhancement, but it Will still work on YouTube and Facebook. This method is Just for unlocked bootloader, dont do it on a locked one, or you will be in logo's bootloop
Well, if only we could root with locked bootloader, kind of like a tethered root so we could remove bloatware and install Viper4Android.
Can't wait for a root that works with lb
boofman said:
Well, if only we could root with locked bootloader, kind of like a tethered root so we could remove bloatware and install Viper4Android.
Click to expand...
Click to collapse
Exactly this is what i want .. jus to use viper4android... :good:
jackxperiap said:
Exactly this is what i want .. jus to use viper4android... :good:
Click to expand...
Click to collapse
True..well, I could maybe compromise on a bit of bloatware and without root if we can somehow run Viper4android.
But the best would be achieving root so we can do whatever we want. F213 here, carrier-locked, no OTA updates since the phone came out of the box
Thanks for this guide, I haven't done it yet but looks straightforward.
What would be the procedure to use this method and also get TWRP installed?
btb55 said:
Thanks for this guide, I haven't done it yet but looks straightforward.
What would be the procedure to use this method and also get TWRP installed?
Click to expand...
Click to collapse
Use the other method here in xda.
Holly ****, this actually worked!!! Many thanks
Anyone notice high battery drain after rooting? I can't determine what causes the battery to drain so fast (app, services, alarms, wakelocks). This won't happen if i'm not rooted via magisk. Any help?
No se puede hacer algo parecido en oreo? No me interesa mucho el twrp..no hay ROM ni nada..no es indispensable
To Root your Mi A2 you will have to first unlock its bootloader, follow all steps correctly to gain root access on your Mi A2 device,
NOTE : All data will be wiped during bootloader unlocking, so make sure to backup each and every thing on your device.
first of all enable developer option & then enable OEM unlocking & USB debugging,
Now setup adb and fastboot drivers on your laptop/PC,
Now connect your Mi A2 (on state) and allow USB debugging popup.
now boot into fastboot mode (power off and press & hold volume down + power key simultaneously)
now connect your mi a2 to your laptop/pc,
now run fastboot oem unlock it will unlock the bootloader and reboot your device, also will wipe data,
now again setup the device and enable developer option, enable OEM unlocking, enable USB debugging, and connect to allow usb debugging.
now once again boot into fastboot mode (as described above), and connect your mi a2 to your laptop/pc
now download august months (V9.6.10.0.ODIMIFE, August 5 2018.) patched_boot.img (dont use if you are on any other month patch) use that months patched_boot.img file only.
now put the patched_boot.img to adb folder.
now again open the command or powershell window, and run fastboot boot patched_boot.img
it will boot your device, now just download the Magisk manager apk and install it.
open magisk manager and click on install, then direct install (recommended),
it will now download the magisk zip file and flash it at its own, after its done simply reboot your Mi A2 and voila we have successfully rooted our Mi A2.
let me know if you have any issues following this tutorial.
This should be in the guides section as this is nothing development related
Benjamin_L said:
This should be in the guides section as this is nothing development related
Click to expand...
Click to collapse
thanks, but how can i delete this post?
androwide said:
thanks, but how can i delete this post?
Click to expand...
Click to collapse
Report it and let the mods do it
Will this void my warranty? If yes, then does "unrooting" bring back my warranty?
pratyush2173 said:
Will this void my warranty? If yes, then does "unrooting" bring back my warranty?
Click to expand...
Click to collapse
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.
Benjamin_L said:
If rooting voids your warranty depends a lot where you live. It's just a disclaimer from the devs that they can't be held responsible for any damage.
Click to expand...
Click to collapse
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)
pratyush2173 said:
Depends on Xiaomi to be honest, I searched and found conflicting opinions about xiaomi being okay with rooting and still provide warranty on the device (hardware, that is). Technically, they shouldn't as rooting allows you do to things that can easily shorten your device's life. But I just wanted to use substratum on my new Mi A2 without losing the warranty on a brand new phone as it might have defects which I haven't noticed yet. (And as I've heard andromeda is **** so won't pay for that.)
Click to expand...
Click to collapse
Xiaomi does not stand above european law so not really. But as I said, depends where you live of course. A modified boot image should do no harm still.
Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?
estetico said:
Thanks for this guide, will I be able to update my phone after I use the patched_boot.img?
Click to expand...
Click to collapse
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
are you sure? If the OTA has check for modified system partition it will fail.
munchy_cool said:
are you sure? If the OTA has check for modified system partition it will fail.
Click to expand...
Click to collapse
I didn't have a chance to try it yet so I can't be sure. Will test when the September update drops
Benjamin_L said:
It will overwrite the patched boot image so you'll have to update the patched boot image for each update
Click to expand...
Click to collapse
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?
veeru1saini1 said:
And just in case, if I update phone with root will there be any soft damage like boot loop or device getting bricked? Or will it just overwrite and become like it was before?
Click to expand...
Click to collapse
Most likely the last yes.
I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.
Yaroray said:
I have a problem with my A2. I followed your rooting instructions and everything went well and I got a root. But then I wanted to install TWRP and I followed those instructions:
fastboot flash boot_b TWRP-3.2.3-jasmine-20180804.img
fastboot set_active b
fastboot reboot (with holding volume up)
It went to TWRP
I changed the partition to A and rebooted system
Now I can't boot OS anymore. It's loading all the time and nothing happens.
What can I do now? Please help, I am not the advanced Android user.
I still can go into Fastboot and TWRP, but I'm not sure what to do and I don't want to do something wrong more.
Click to expand...
Click to collapse
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot
T4Ump said:
Are you sure you change to a? go fastboot and fastboot set_active a and fastboot reboot
Click to expand...
Click to collapse
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?
Yaroray said:
Yes, I'm sure I changed partition to A, but I finally managed to fix it. I powered off phone from TWRP and then booted it again (after an hour ) and it worked.
Now I have one more question. When I boot from Fastboot with patched_boot.img, root is gained. But when I restart my phone normally the root is gone. Is it normal and how to get constant root?
Click to expand...
Click to collapse
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.
T4Ump said:
You dont need TWRP, because A2 has ****ing A/B and TWRP is not supported, because bootlooping after install twrp. Dowloand ROM from Xioami webpage and unpack original boot.img, flash to b and a (original boot)
try if mobile normal boot to system. Go fastboot and patched_boot.img flash to b / a.
Click to expand...
Click to collapse
Twrp just does not work properly currently. It will be supported in the near future
Benjamin_L said:
Twrp just does not work properly currently. It will be supported in the near future
Click to expand...
Click to collapse
Yea, i know. I tried first day when i got mobil, twrp root etc.
Hi!
I need some help rooting my Nokia 6 Mobile phone
The model number is TA- 1033
I have tried all kinds of different sources as a guide, but all failed for me.
I tried several one-click root tools as well. (Kingroot, Kingo Root)
I have tried to unlock the bootloader with Fastboot and ADB for the TWRP recovery flash
I have got developer options and also enabled USB Debugging and OEM unlocking ut the procedure still fail all the time.
I've tied to flash the TWRP without unlocking the bootloader but that ailed as well.
My device is not bricked yet.
Thank you for your help
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom (https://mega.nz/#!5ccRnb4b!VsgiKQ4CjxFyjbjcxR0esjeKmHZsUTnEz0FA_FMZQbM)
(To install it, you need the phone in bootloader mode.)
If it displays an error the first time, try again until the installation is fully successful.
Once the phone is turned on, the first thing you need to do is turn off automatic software updates. Know that if you want root, you should forget about OTA updates.
Once all written above is done remains to unlock the bootloader and installing TWRP.
For that..
Enter in bootloader mode.
Use Fastboot from your PC and enter this command to allow the partitions to be changed on your phone.
(To get MD5 of your serial number, use this website: http://www.miraclesalad.com/webtools/md5.php)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Example: fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e)
After that download this bootloader(http://pc.cd/xUFrtalK) and flash it:
fastboot flash aboot D1C-emmc_appsboot.mbn
(Make sure that downloaded bootloader is located in adb/fastboot folder)[Or you can type full file path of bootloader(Example: "C:\Users\Martin\Downloads\D1C-emmc_appsboot.mbn")]
(This to flash an unlocked bootloader.)
fastboot reboot-bootloader
(This is to reboot for using new unlocked bootloader.)
fastboot oem dm-verity [MD5_of_your_device_serial_number]
(Again to allow installing partitions.)
Download recovery from here: https://mega.nz/#F!K1k0gC5C!xpw3-AQvSQJ5p6VWX19gpA)
Flash it with this command:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
(Make sure that downloaded recovery is located in adb/fastboot folder)[Or you can type full file path of twrp recovery(Example: "C:\Users\Martin\Downloads\nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img")]
After that reboot to twrp recovery and flash Magisk ROOT.
All is done.
Magisk is built in recovery. You don't need to download it from internet. Flash magisk which is in recovery.
Warning: After opening magisk manager you can update app but you can't update magisk version (core). Because latest version cause bootloop on ours devices. Use 16.1 version which is in recovery build it.
I hope everything will be fine. Good luck!
Hi! I have some issues.
marto2013 said:
My attempts to root were successful only on Nougat (Not Oreo, because of bootloader)
Make a backup of all your important files in your phone.
Download OST and with it install this stock rom
Click to expand...
Click to collapse
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
VargaTibor1 said:
Okay
So when I tried to flash the rom you gave me it failed with a download error. I tried to use OST LA 6.0.4 and 6.1.2 but both failed.
Clicking on the "Edit phone information" didn't work either. Can you help me in this situation? I have tried to reinstall OST LA several times, but it didn't resolve the problem.
Click to expand...
Click to collapse
On which patch level are you?
ZeroPointMax said:
On which patch level are you?
Click to expand...
Click to collapse
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
ZeroPointMax said:
That means you cannot use OST LA or oem-veracity. Nokia changed the algorithm with August patch. You can basically not root your phone anymore using this method.
Click to expand...
Click to collapse
He can downgrade his bootloader using older OTA update.
=====
VargaTibor1 said:
I am on Patch Level: 1 November 2018
Android version 8.1.0
Build number 00WW_5_580_SP08
Click to expand...
Click to collapse
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
marto2013 said:
He can downgrade his bootloader using older OTA update.
=====
Make backup on anything! You will not have access to anything until you install the rom I gave you in the first post.
Go to recovery and flash this ota update.
https://my.pcloud.com/publink/show?code=XZYg1T7ZzpJwx2DdRo4wbpTUEXABAfnS9PgX
After all go to recovery again.
If it says that the Android version is 7.1, then everything is ready.
If it does not get the first time, flash ota again.
When I did it, I think I flash two times ota update.
If it's okay, try the Instructions from the first post again.
Click to expand...
Click to collapse
I thought this wouldn't work too
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
amt911 said:
Hi guys, I have kinda big problem.
Yesterday I was messing around with my device just to understand how the a/b partitions work. Then I decided to install a custom rom but TWRP was throwing me errors at the end of the installation (cannot mount /system (access denied) or something like that). After this problem I thought the best solution was to erase every partition (yes, I'm an idiot) throught fastboot and then reflash the phone with msmdownloadtool. I did exactly that and when the unbrick tool finished the phone rebooted and got stuck on the boot screen (the big red circle and the two smaller ones around it). I don't know what to do, I tried almost every version of msmdownloadtool (even the h2os one), I tried unlocking the bootloader, but the phone rejects it and I'm still stuck in a bootloop.
Please help me, I'm running out of ideas and I don't want to have a 570€ paperweight.
Sorry if my english is bad, this is not my native language.
Click to expand...
Click to collapse
Lo siento por mi ingles. Tuve el mismo problema y lo resolví con comandos ADB. No recuerdo cómo. Estoy seguro de que tuve suerte ... Tal vez puedas intentarlo. Al menos, la PC debería leer el modo fastboot y comenzar a hacer algo.
I'm sorry for my English. I had the same problem and I solved it with ADB commands. I do not remember how. I'm sure I was lucky ... Maybe you can try it. At least, the PC should read fastboot mode and start doing something.
indian84 said:
Try only MSMTool again. It is the ultimate solution for bricks.
If that doesn't help, then contact OnePlus and behave dumb. Just say your device stopped working
Click to expand...
Click to collapse
I think I'll have to send it to OnePlus. But before that I would like to try to revive it. I can access fastboot, but the bootloader is locked, can I do something in fastboot or with the locked bootloader I'm out of luck?
Thanks.
Don't worry I understood you.
The problem is I can't access to adb because the stock recovery doesn't allow and I can't boot any custom recovery because my bootloader I locked.
Thanks.
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
ACB369 said:
I have the same issue with oneplus x, and I followed this method, https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
So try to get stock recovery mode on you phone, then try to flash stock rom. Later you can go for the TWRP and Magisk Installation for Root access.
Click to expand...
Click to collapse
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
amt911 said:
The problem is the OnePlus 6T doesn't have an adb sideload option in the stock recovery so I can't sideload anything and the msmdownloadtool left me with the bootloader locked, so I can't flash anything in fastboot nor boot a custom recovery.
Thanks.
Click to expand...
Click to collapse
Try fastbooting the stock boot.img, follow the instructions below...
Reboot to Bootloader
Open up a command prompt in the folder with the boot.img
Enter the command
Code:
fastboot boot *insert boot.img name here*
Nothing, just wait for your phone to boot
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
1. Download full OTA to your pc and unzip https://androidfilehost.com/?fid=1395089523397891265
2. Edit flash-all-partitions.bat and put this line on the top "fastboot -w" and save
3. double click flash-all-partitions.bat
4. If step 3 still showing error. Edit flash-all-partitions.bat and add "fastboot set_active other" on the top and save then repeat step 3 again.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Is there any way that I could wipe everything in EDL mode? Is the only thing I think it could fix the phone.
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
amt911 said:
Please could you give me more suggestions. I don't know what to do, I flashed the phone with MSMDownloadTool at least ten times and still nothing, it only shows the boot animation and gets stuck there and fastboot doesn't accept any command because of the locked bootloader.
Thanks.
Click to expand...
Click to collapse
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
tech_head said:
Which version of the MSM tool are you using?
Is the phone fully charged?
How long are you waiting for the phone to boot? When you say stuck do you just leave the phone alone?
After MSM the first boot is a long time.
Click to expand...
Click to collapse
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
amt911 said:
I tried entering in fastboot mode and writing "fastboot -w" but it says "FAILED (remote: 'Erase is not allowed in Lock State')". I think it's because the bootloader is locked, I don't know what can I do next.
Thanks.
Click to expand...
Click to collapse
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
amt911 said:
I'm using the v4.0.58 one with OOS 9.0.11, yes the phone is at 75%.
I wait around an hour to see if it boots, but nothing.
When I said that my phone got stuck I meant that it got stuck in the boot animation and nothing else happens.
Yeah, I know, but I don't think it needs an hour to boot.
Thanks.
Click to expand...
Click to collapse
sometime flushing cache can solves this kind of issue.
Sent from my ONEPLUS A6013 using Tapatalk
vichao.s said:
have you try "fastboot set_active other"
Click to expand...
Click to collapse
Yes, the same, because the bootloader is locked I can't do anything except "fastboot OEM unlock" which I can't use because I can't access os and I can't turn on oem unlocking.
Thanks.
vichao.s said:
have you try "fastboot set_active other"
Sent from my ONEPLUS A6013 using Tapatalk
---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------
sometime flushing cache can solves this kind of issue.
Click to expand...
Click to collapse
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
amt911 said:
How can I do that? I tried wiping cache and factory resetting in recovery but nothing. Still in bootloop.
Click to expand...
Click to collapse
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Mannan Qamar said:
Dunno if this will work but after reflashing another time. Boot to stock recovery and factory reset. I dunno the exact procedure but I assume you boot to bootloader and from there boot to recovery and do a factory reset. I had something similar. I flashed OOS via TWRP after soft bricking my phone. And factory reset fixed it. Tho in my case it didn't even load the bootanimation. Just the Unlock Warning and reboot.
Click to expand...
Click to collapse
I tried that and it's still stuck on the boot animation, I think it's just a hardware problem because back then with my OnePlus 3T I did the same and it worked just fine. I contacted OnePlus and they accepted sending the phone to them. I'll see when they examine it what is their answer.
Thanks.
What I did to brick it was using this guide: https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
And inside the manual flash section there are a lot of fastboot commands.
What I did was using only the fastboot ones and replacing "flash" to "erase" to delete every partition. After that I flashed the phone using msmdownloadtool right away. My question is: Could this be the cause that my phone is in bootloop?
Thanks.