Related
YEAHHH, FINALY MOTO G5 AND 5+ ARE ROOTED!!!! :highfive:
IMPORTANT UPDATE: HERE
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Guys after some attempts without success, a few minutes ago I got a stable way to root it, and the lot of people was getting trouble to make it I decided to create this post. If you want to root yours too, then follow and read (read all step line and understand it before doing) CAREFULLY this:
1. Unlock your bootloader
2. Download all files in the end of this post
3. Backup your data and files, all will be lost
4. I recomend you make a clean install, then flash stock ROM again(you can do this or not), so flash it(let the phone start)
5. Turn off the mobile, then go to bootloader screen and flash TWRP
Now the steps that people was getting trouble
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
Now TWRP is rebooting
9. "Swipe to Allow Modifications"
10. Plug your phone to PC (as TWRP is not reading sdcard yet)
11. Copy "no-verity-opt-encrypt-5.1.zip"(FLASH IT) and "Magisk-v11.6.zip"(NO FLASH IT YET), and flash "no-verity-opt-encrypt-5.1.zip", NO ROOT YET
12. Come back to TWRP main menu, go to REBOOT, then SYSTEM, then DO NOT INSTALL
13. After that, turn off the phone again
14. Go to bootloader screen and open TWRP
15. "Swipe to Allow Modifications"
16. NOW flash "Magisk-v11.6.zip"
17. After the setup, come back to TWRP main menu, go to REBOOT, then SYSTEM, then DO NOT INSTALL
18. When the Phone starts, go to Magisk App( it will ask for an update, then update it)
19. Open Magisk.......
20.BOOOOMMMM YOU NOW HAVE ROOTED PHONE!!!!
SOME EXPLANATIONS
*Why not SuperSU or Phh superuser??
SuperSU didn't installed, and Phh broken system!!
*Which Stock Version??
Build NPN25.137-33
Build NPN25.137-35
DOWNLOADS
no-verity-opt-encrypt-5.1: http://zip.net/bftGRg
Magisk-v11.6: http://zip.net/bdtHnv
Stock ROM: http://zip.net/bmtGMs
TWRP: http://zip.net/bktGV9
SPECIAL THANKS :good:
@topjohnwu for the root
@Santhosh M for the TWRP and for the tips for Bootlooping solution
@abdyasar for the no-verity-opt-encrypt-5.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you for this guide.
Thank You
Johny Cipeli said:
YEAHHH, FINALY MOTO G5 AND 5+ ARE ROOTED!!!! :highfive:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Guys after some attempts without success, a few minutes ago I got a stable way to root it, and the lot of people was getting trouble to make it I decided to create this post. If you want to root yours too, then follow and read CAREFULLY this:
1.Unlock your boot loader
2.Download all files in the end of this post
3.Backup your data and file, all will be lost
4.I recomend you make a clean install, then flash stock ROM again, so flash it(let the phone start)( If you don't want, then OK)
5.Turn off the mobile, then go to bootloader screen and flash TWRP
Now the steps that people was getting trouble
6. In the Description screen, press cancel, then "Swipe to Allow Modifications"
7.Go to WIPE, then "Swipe to Factory Reset"
8.Go to TWRP main manu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
Now TWRP is rebooting
9."Swipe to Allow Modifications"
10.Plug your phone to PC( as TWRP is not reading sdcard)
11.Copy "no-verity-opt-encrypt-5.1.zip"(FLASH IT)and "Magisk-v11.6.zip"(NO FLASH IT), and flash "no-verity-opt-encrypt-5.1.zip", NO ROOT YET
12.Reboot System
13.After that turn off the phone again
14.Go to bootloader screen and open TWRP
15."Swipe to Allow Modifications"
16. NOW flash "Magisk-v11.6"
17. After the setup, reboot your phone
18. Go to Magisk App( it will ask for an update, then update it)
19.Open Magisk.......
20.BOOOOMMMM YOU NOW HAVE ROOTED PHONE!!!!
SOME EXPLANATIONS
*Why not SuperSU or Phh superuser??
SuperSU didn't installed, and Phh broken system!!
*Which Stock Version??
Build NPN25.137-33
DOWNLOADS
no-verity-opt-encrypt-5.1: http://zip.net/bftGRg
Magisk-v11.6: http://zip.net/bdtHnv
Stock ROM: http://zip.net/bmtGMs
TWRP: http://zip.net/bktGV9
SPECIAL THANKS :good:
@topjohnwu for the root
@Santhosh M for the TWRP and for the tips for Bootlooping solution
@abdyasar for the no-verity-opt-encrypt-5.1
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=udA6UNKitOQ link for video tutorial
Thanks! Done using the video tutorial, everything looks good and my bootloader screen is not with the warning message anymore! I did everything and did not have a bootloop anymore! Thanks for the Tutorial Johny Cipeli. And thanks to Mr. Smith (video tutorial). Let's have fun with root now!
Npn25.137-15
Johny Cipeli said:
*Which Stock Version??
Build NPN25.137-33
Build NPN25.137-35
Click to expand...
Click to collapse
Should I take the risk if I have the NPN25.137-15 compilation?
Leodev said:
Should I take the risk if I have the NPN25.137-15 compilation?
Click to expand...
Click to collapse
No prob over here, I had -15 version and now working 33 without issues
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Johny Cipeli said:
YEAHHH, FINALY MOTO G5 AND 5+ ARE ROOTED!!!! :highfive:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Guys after some attempts without success, a few minutes ago I got a stable way to root it, and the lot of people was getting trouble to make it I decided to create this post. If you want to root yours too, then follow and read (read all step line and understand it before doing) CAREFULLY this:
1. Unlock your bootloader
2. Download all files in the end of this post
3. Backup your data and files, all will be lost
4. I recomend you make a clean install, then flash stock ROM again(you can do this or not), so flash it(let the phone start)
5. Turn off the mobile, then go to bootloader screen and flash TWRP
Now the steps that people was getting trouble
6. In the Decrypt /data screen, press cancel, then "Swipe to Allow Modifications"
7. Go to WIPE, then "Swipe to Factory Reset"
8. Come back to TWRP main menu, go to REBOOT, then RECOVERY, then DO NOT INSTALL
Now TWRP is rebooting
9. "Swipe to Allow Modifications"
10. Plug your phone to PC (as TWRP is not reading sdcard yet)
11. Copy "no-verity-opt-encrypt-5.1.zip"(FLASH IT) and "Magisk-v11.6.zip"(NO FLASH IT YET), and flash "no-verity-opt-encrypt-5.1.zip", NO ROOT YET
12. Come back to TWRP main menu, go to REBOOT, then SYSTEM, then DO NOT INSTALL
13. After that, turn off the phone again
14. Go to bootloader screen and open TWRP
15. "Swipe to Allow Modifications"
16. NOW flash "Magisk-v11.6.zip"
17. After the setup, come back to TWRP main menu, go to REBOOT, then SYSTEM, then DO NOT INSTALL
18. When the Phone starts, go to Magisk App( it will ask for an update, then update it)
19. Open Magisk.......
20.BOOOOMMMM YOU NOW HAVE ROOTED PHONE!!!!
SOME EXPLANATIONS
*Why not SuperSU or Phh superuser??
SuperSU didn't installed, and Phh broken system!!
*Which Stock Version??
Build NPN25.137-33
Build NPN25.137-35
DOWNLOADS
no-verity-opt-encrypt-5.1: http://zip.net/bftGRg
Magisk-v11.6: http://zip.net/bdtHnv
Stock ROM: http://zip.net/bmtGMs
TWRP: http://zip.net/bktGV9
SPECIAL THANKS :good:
@topjohnwu for the root
@Santhosh M for the TWRP and for the tips for Bootlooping solution
@abdyasar for the no-verity-opt-encrypt-5.1
Click to expand...
Click to collapse
Wow! That was quick
Can some one explain me how do people find out how to root other than reading others posts?
Thanks for the guide, but it did not work for me. Any chance I can get some help please?
I managed to get TWRP installed, wipe data, factory reset, reboot to twrp and install no-verity.
I then reboot to system, shut off and boot to recovery. Then Install Magisk.zip which seems to be successful.
Then reboot to system, do initial phone setup, open Magisk app, update on play store, and then get told that phone is not rooted.
I tried again, but first flashed stock boot.img with fastboot, but I get the same result, not rooted.
What am I doing wrong?
glight0 said:
Thanks for the guide, but it did not work for me. Any chance I can get some help please?
I managed to get TWRP installed, wipe data, factory reset, reboot to twrp and install no-verity.
I then reboot to system, shut off and boot to recovery. Then Install Magisk.zip which seems to be successful.
Then reboot to system, do initial phone setup, open Magisk app, update on play store, and then get told that phone is not rooted.
I tried again, but first flashed stock boot.img with fastboot, but I get the same result, not rooted.
What am I doing wrong?
Click to expand...
Click to collapse
It should be working... Margisk has just get a new version, maybe you can Try again
Thanks for the reply, I was using v12 of Magisk, but I found that earlier versions were attached to that thread also.
I will give it another shot with uninstaller and then v11.6.
EDIT: success! Uninstaller, then v11.6 worked. Was worried I would have to wipe data and start over but not needed.
Thanks again for the help OP
glight0 said:
Thanks for the reply, I was using v12 of Magisk, but I found that earlier versions were attached to that thread also.
I will give it another shot with uninstaller and then v11.6.
Click to expand...
Click to collapse
Use Magisk 11.6, I used the same and rooted, updated to Magisk 12 and root gone!!!, so again flashed 11.6 to get back root.
Thanks, v11.6 did the trick!
Quality Video tutorial for this guide
Bro, Thanx for your guide and here is a quality video tutorial for this guide and I hope it helps https://www.youtube.com/watch?v=ZWLR8JnZ7z0
Excellent guide. Trying it now.
Edit: bang on, it worked. Thank you.
Guys help me hiding root cos snapchat n other apps stopped working cos they check root…. Magisk - rootcloak - Autohide not working to hide root…
Sent from my ONE A2003 using Tapatalk
Though we can root with Magisk, it has got problems. May be it has got something to do with twrp.
Amazon version?
Will this procedure work on the Amazon version of the G5/G5 Plus? It seems like the G4 version with Amazon ads could not be rooted, so I'm wondering if it's the same situation with the G5. Thanks!
Can anyone tell me if the amazon version is rootable? I can't get past the unlock bootloader part cause it's not letting me via motorolas website.
danieljoseph929 said:
Can anyone tell me if the amazon version is rootable? I can't get past the unlock bootloader part cause it's not letting me via motorolas website.
Click to expand...
Click to collapse
You know clearly the answer... Amazon bootloader can't be unlocked
Enviado desde mi Moto G (5) Plus mediante Tapatalk
Is... this sarcasm?
Hi,
My oneplus 9 pro is stock, Never rooted or unlocked.
The last update fails : the phone is in bootloop now.
i think it goes to the bootloader, where i can reboot, wipe cache, wipe date, or see What is the error.
i’ve tried to reboot 25 Times, i’ve wiped cache , And here is the error message:
Boot reason : init_user0_failed
Unable to parse kernel log. For more debug information ,
Adb pull /mnt/vendor/op2/rbr_log
Or pull op2.img
i have had the same issue the OTA before this one, And the problem has ben resolved after 40 or 50 reboots, i dont Know how. The phone rebooted normaly,i dont know how
could you please help me?
Thanx in advance
Sorry to see you're experiencing so many issues, would you consider contacting OnePlus directly? The customer service phone line
OnePlus Support (France)
www.oneplus.com
If you want to try fixing it yourself, MSM back to factory settings is probably your best bet for a clean slate. However, doing so will wipe data, so if you can get it to boot first and get your files off it, that's obviously ideal (unless you already have a good backup).
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
So weird ... As last time, the phone rebooted normally after 40 or 50 tries ...
misteurz said:
So weird ... As last time, the phone rebooted normally after 40 or 50 tries ...
Click to expand...
Click to collapse
Sounds like a good opportunity to back everything up and prepare to reset with MSM, in case next time it doesn't boot up.
Excellent advice ... do this in case it happens in the next few updates while you're waiting for One Plus customer service to help you.
Yes, I'll save everything before the Android 12 update.
OnePlus contacted me : their solution is to erase my phone, and install clean os.
I don't want to do this
"This can be resolved by performing remote session on the device where support staff will install a new OS.
FYI : Please back up the data as the procedure will wipe out all the data."
misteurz said:
Yes, I'll save everything before the Android 12 update.
OnePlus contacted me : their solution is to erase my phone, and install clean os.
I don't want to do this
"This can be resolved by performing remote session on the device where support staff will install a new OS.
FYI : Please back up the data as the procedure will wipe out all the data."
Click to expand...
Click to collapse
The problems you've experienced so far are on a fully stock and unmodified device. This may suggest that there is a hardware issue. I'd be asking for a brand new sealed device.
I think I have a corrupted partition.
Every OTA, the phone may trie to install the update on the corrupted partition.
I don't know why, but after 40 or 50 bootloops, it boots on the other partition.
This is my theory
I got a used LG G3 D852 yesterday, it's the first unlocked phone I've had. I know my way around a PC pretty well, but I'm nearly a complete luddite when it comes to phones specifically, so I was surprised when the phone wouldn't allow me to update its Android version from 6 to a newer one. I started looking into how to update the OS manually, and then ended up in a rabbit trail of bootloader unlocking, device rooting, custom ROM flashing, etc. I'm fully capable of reading a tutorial and following it, but I can't seem to figure out where I should even start with the process. Also, given that LG's website discontinued the official bootloader unlocking service, I'm not sure it's even possible to do anymore.
All I'd really like is for the phone's OS to be updated. Is that possible anymore, and if it is, what do I do first in that whole process?
KelpTheGreat said:
I got a used LG G3 D852 yesterday, it's the first unlocked phone I've had. I know my way around a PC pretty well, but I'm nearly a complete luddite when it comes to phones specifically, so I was surprised when the phone wouldn't allow me to update its Android version from 6 to a newer one. I started looking into how to update the OS manually, and then ended up in a rabbit trail of bootloader unlocking, device rooting, custom ROM flashing, etc. I'm fully capable of reading a tutorial and following it, but I can't seem to figure out where I should even start with the process. Also, given that LG's website discontinued the official bootloader unlocking service, I'm not sure it's even possible to do anymore.
All I'd really like is for the phone's OS to be updated. Is that possible anymore, and if it is, what do I do first in that whole process?
Click to expand...
Click to collapse
1. search for kingroot, kingoroot, whatever, download and install the apk, follow the app’s instructions to root your phone
KingRoot (Android)
Root your Android device in a matter of seconds
kingroot.en.uptodown.com
2. search and download and install flashify apk on phone
and download this TWRP in .img format
[RECOVERY] Unofficial TWRP for LG G3 (Discontinued)
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included...
forum.xda-developers.com
in flashify click install recovery from phone storage and select your twrp img and grant root access and after installing it will ask you to click reboot to recovery, press yes, you will now in TWRP mode, swipe to allow modifications
3. download your LineageOS zip on computer depending on model
LineageOS Downloads
download.lineageos.org
then download your opengapps google apps package
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
use ARM (not arm64) , android 11, pico
transfer to phone with USB
press wipe in twrp mode then factory reset (backup your data first!) the confirm
then press install then find your lineageos zip
swipe to flash
after complete press back, press install again, find opengapps package, and swipe to flash
then after complete press back, reboot, uncheck install twrp app and install as system app, reboot system
All right, thanks for the list of steps I need. I'll give it my best shot, if you don't hear from me again in this thread then assume everything went well!
Edit: I've run into a snag right away. In the description of the KingRoot link you provided, it says that the "operating system [must be] between Android 4.2.2 and Android 5.1." My phone is Android 6. Is that an error in the description, and it will actually work to root Android 6, or should I search for another root apk like kingoroot that specifically says it works with Android 6?
KelpTheGreat said:
All right, thanks for the list of steps I need. I'll give it my best shot, if you don't hear from me again in this thread then assume everything went well!
Edit: I've run into a snag right away. In the description of the KingRoot link you provided, it says that the "operating system [must be] between Android 4.2.2 and Android 5.1." My phone is Android 6. Is that an error in the description, and it will actually work to root Android 6, or should I search for another root apk like kingoroot that specifically says it works with Android 6?
Click to expand...
Click to collapse
maybe yes maybe no just try
you can also try kingoroot and many others until one eventually work
I don't think I'm going to use Kingoroot, as Malwarebytes flagged it as malware and quarantined it, and checking the file through VirusTotal confirms that it's not a safe file.
Reading the official xda guide here says that none of these root programs are recommended, so I'll follow their guide and see how that goes.
Okay... to install and use Magisk, the rooting method recommended by XDA, it says that the phone must have an unlocked bootloader first. On that same page it says to search on the forums for a specific method for your device to unlock its bootloader. This is the only bootloader unlocking guide I can find for the LG G3, and it says that to use this method, the device must be rooted first.
I can't root without an unlocked bootloader, I can't unlock the bootloader without rooting? Now what?
I found another bootloader unlocking guide. Now my problem is that even though I've installed ADB and Fastboot, ADB isn't recognizing that my phone's connected. The phone itself says that USB debugging is connected and available, and my computer detects that the phone is connected, but ADP can't see that it's connected.
EDIT: Solved that problem by switching the phone's USB connection from MTP to PTP. Now ADB is correctly showing the phone.
any problems so far
LR7875 said:
any problems so far
Click to expand...
Click to collapse
Haven't been able to work on it for a few days, will probably be able to do so later this week. Thanks for checking in!
Double posted accidentally, ignore this
Hey, I am still planning on working on this. Life's just slammed me hard lately and I haven't been able to spend time on it.
One problem I'm having that's probably unrelated to the whole unlocking thing is that I can't get the phone to connect to mobile data. I can make calls and texts, but it won't connect to mobile data. I tried the SIM card in another phone and it works, so it must be some issue with this particular phone and connecting to data. I'll have to do some troubleshooting for that before I proceed with unlocking; I don't want to waste time on unlocking the phone if it won't work with data at all.
KelpTheGreat said:
Hey, I am still planning on working on this. Life's just slammed me hard lately and I haven't been able to spend time on it.
One problem I'm having that's probably unrelated to the whole unlocking thing is that I can't get the phone to connect to mobile data. I can make calls and texts, but it won't connect to mobile data. I tried the SIM card in another phone and it works, so it must be some issue with this particular phone and connecting to data. I'll have to do some troubleshooting for that before I proceed with unlocking; I don't want to waste time on unlocking the phone if it won't work with data at all.
Click to expand...
Click to collapse
tried factory reset?
even if that don't work you can still proceed as it may be an issue in stock firmware and can be fixed by a custom firmware lineageos etc, I mean you couldn't conclude that it's mobile data is kaput and throw in trash because of this before you even tried a custom firmware
LR7875 said:
tried factory reset?
even if that don't work you can still proceed as it may be an issue in stock firmware and can be fixed by a custom firmware lineageos etc, I mean you couldn't conclude that it's mobile data is kaput and throw in trash because of this before you even tried a custom firmware
Click to expand...
Click to collapse
Yeah, you're probably right. I'll go ahead with the process and hope that it connects to mobile data after I get it all done. If it doesn't work then at least I'll have learned how to do it, and I'll have a pretty decent custom phone that I can just use on wi-fi.
I'll try getting back to working on this as soon as I can... which probably won't be as soon as I'd like to... =P
Dear community,
An old XDA member here, who forgot everything about flashing or fixing a broken phone system.
My Poco F3 just went into an infinite bootloop, and I have no idea why is that since I didn't perform any custom modifications to the system, absolutely none!
I can access the recovery menu, which was useless as Safe Mode or any other mode didn't help, the phone can't boot.
Connecting with MIAssistant doesn't work as well, I can see the phone is connected in hidden USB devices on the PC as an Android ADB interface, but the MI software can't see it.
I can also access FASTBOOT, but I have no idea what to do with it. MIAssistant detected it but it asked to connect in normal mode?
A strange artifact is showing on the bootscreen every time, some random colors on the logo, something corrupted? I have no idea...
Is there anything I can do without wiping the phone? It's my daily driver and I need the data saved on it.
I will be monitoring this thread for the next few hours, please don't hesitate to suggest potential fixes or ask questions.
Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update:
The phone finally made it into Safe Mode, I am backing up my data, can't reboot it yet until the 125GB are on the PC.
Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.
heybaybee said:
Is the bootloader locked? Has the phone suffered any physical damage?
The logo looks as if either the screen, its connector or the motherboard were broken. I hope to be wrong.
Maybe try the steps from here except I wouldn't wipe data nor do a factory reset (yet). I hope someone more knowledgeable and experienced than me can advice something better.
Click to expand...
Click to collapse
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.
sos_sifou said:
Thank you for the effort,
No, the phone didn't suffer any physical damage, I also have no idea about the bootloader as I haven't flashed or try to flash anything on it.
I managed to copy some of my important data when it decided to boot up, then it went into bootloop again.
I wiped it, as I had no other way to confirm that the phone is broken at the hardware level. After the wipe and reinstallation, it went into bootloop again.
I will have to throw it somewhere and buy a Samsung.
Click to expand...
Click to collapse
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3
johnr64 said:
Hi,
Samsung's are Yuk, expanding batteries and the dreaded KNOX,
my F3 was brought from the UK and came with 2 Years Warranty,
As mentioned above, have you unlocked your bootloader, if not why not, if your not fussed about your F3 then you have nothing to loose, you could try installing a new rom, i use EVO-X and its amazing,
I love the F3
Click to expand...
Click to collapse
You're right, I was a bit angry, all phones can break, including iPhones and Samsungs.
Claiming warranty is a bit tricky for me, as I purchased the phone during my short stay in the UAE, and I won't be going back until next year.
Now I think there is a part of the system files that has been corrupted, because when the phone reboots, it will go into bootloop, but if it boots after some 30 to 40 minutes of bootlooping, it will stay running for a certain period of time.
If system files are corrupted, I don't think a wipe can fix it, as it deletes user data and apps, but I don't think it fixes system files used to boot the device.
Do you have a link to a step-by-step tutorial to unlock the bootloader and flash a stock ROM. I don't really need any special features from custom ROMs, other than the phone to work for the next 3 to 4 months without problems.
Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.
Dear all,
After more testing, it seems the phone doesn't have corrupted boot files, but it just can't run when the CPU is under load.
I have made several tests, when the phone is relaxed, battery saver option is ON, it doesn't reboot, but once battery saver is OFF, and I push the CPU a little using a benchmarking software or a CPU stress test, it reboots.
Thus, the problem is with the hardware, I wonder how many people are suffering from such an issue or is it isolated and only a handful devices are affected by this?
The broken boot logo makes it look like a hardware problem as well. Did you buy it new? Did you game on it or keep it at or above 40-50 degrees C for prolonged periods of time?
I've had Poco X3 Pro that would freeze when using navigation in the summer once in a while. Happened few other times as well.
Trying to flash the (newest) stock ROM may be worth trying. Maybe selling it for parts is an option.
ferreol-fr said:
Hi,
You can try fastboot update.
First download and decompresse the latest fastboot ROM for your device you can find here.
Then download latest android platform tools copy all it's content into the ROM folder.
Finaly run flash_all_except_storage.bat (this will preserve your data), if no sucses you can try flash_all.bat, but this will erase all your personal data.
Click to expand...
Click to collapse
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
I struggled a bit in the early days moving away from my LG G7,
you could try my post on the Evo-X thread,
[A13]Evolution X for POCO F3/Mi 11x[alioth][OFFICIAL]
Evolution X 7.0 for the POCO F3 [alioth] /* * Your warranty is void. Or vaild, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following *...
forum.xda-developers.com
following parts 1 to 1b,
you could also try Temporary Recovery using part 6.
None of this will work unless you have a unlocked bootloader and FASTBOOT working on your PC.
You could also try Miflash to install the correct drivers and see if your device is detected in FASTBOOT,
A word of warning never choose "clean all and lock" in miflash unless you are running the correct stock firmware for your device as you could end up with a BRICKED device.
zalm_98 said:
Hi, i've tried your method but it doesn't seem to work for me, after i run flash_all_except_storage.bat it doesn't do anything and stays in fastboot. Is there something i may have missed that is required for this to work? i am a bit fresh in this kind of things and i only have the experience of flashing two devices long time ago, my phone it has been in bootloop for a few day already, and i've been trying everything i find that doesn't wipe my data, and it doesn't seem to work, thanks in advance!
Click to expand...
Click to collapse
Hi,
Are your device drivers correctly installed on the computer?
After plugging your phone into fastboot mode on your PC, look in the Windows manager if the device is installed correctly. Otherwise, go to Windows Settings-> Windows Update-> Optional Update. And see if there is any driver update that can help you.
Hi,
I flashed TWRP on my unlocked Redmi Note 8T with MIUI Global 12.5.5. Everything was great until I rebooted it and saw Bluetooth error which pops every time I try to turn Bluetooth on or just randomly during usage of the device. I also tried to re-flas TWRP with Orange fox but it unfortunatelly did not help. Now I have no idea what to do but there are also some other people with this problem (for example:
https://www.reddit.com/r/Xiaomi/comments/y9zsak
).
Does anybody know any solution? Thanks!
Btw Orange fox is for ginko devices, I did not find version for willow
I had the exact same problem when I tried to root my stock rom in ginkgo. I was getting a lot of "app keeps stopping" pop ups, and that also included bt. My bt was completely broken until I changed rom. Also I'm guessing this had happened when I had rooted my phone with magisk, not by flashing recovery itself. Perhaps you could try to uninstall magsik, and see it it resolves the issue for you. If that would be the case, then you would have found your problem, and maybe you can flash a custom rom to safely root your phone.
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
So now it tried one of my ideas, which was to install Magisk (root) and uninstall it but it also did not help (I expected that)
vasik006 said:
Thanks for reply, but i did not have magisk flashed on my phone. I only had installed the app, prepared apk file and did nothing in TWRP (Orange fox) , just flashed a recovery with my PC, checked that it is working and rebooted device. Anyway I tried to do it only because of acces to NFC and Gpay which is now blocked.
As you also said, I would like to try custom rom (like LineageOS) because it seems like bad idea to have a stock room on an unlocked phone. Only the problem is how to backup data like data from apps, games etc.
Click to expand...
Click to collapse
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Yeah, that's true. But don't you know how to backup data from these "offline" apps? I was trying to solve this also before unpocking bootloader like a year ago but unsuccessfuly.
Also, which rom should I choose? I'm deciding between LineageOS and Pixel experience.
So I have LOS installed but I can´t install other zip files (like Google apps). Im only getting error: signature verification failed while. Im using LOS recovery so where is the problem?
Solved it!
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Thanks, this might help someone else with this problem. I have already formatted my phone, installed Lineage OS and everything is ok
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Jatin Verma x821 said:
Hey @vasik006 ! I know this is very late and you might have found the solution yourself, but I found the solution to this problem. Since yesterday I was trying to root my ginkgo with twrp, using magisk delta and had exact same issue. Joyose and bluetooth keeps stopping, and don't work. Simply factory reset ( I also formatted data) in twrp, and in next boot bluetooth should work. Then you can simply install the magisk apk and let it do its thing. No need to flash again since it has already made changes to boot file that can't be overriden by resetting phone.
Click to expand...
Click to collapse
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly? Tks
ennev said:
I have the same problem with the Redmi note 8. Did you unroot first or did the factory reset directly?
Click to expand...
Click to collapse
no need to unroot. simple factory reset the device and you're done.
Jatin Verma x821 said:
To backup data simply copy your personal files in pc or sdcard. And to backup data in apps, take back-up of only those apps and where you need to backup. Don't take a complete backup using some app. That consumes a lot of space and make the newly rom feel "not so new". Most apps don't require you to take back-up offline these days. I usually backup only my personal files before flashing rom.
Click to expand...
Click to collapse
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Alpha_Geek1 said:
TWRP is invaluable for backing up the system before making changes like theming etc. and I can take a TWRP backup to any of my (all the same) devices and restore the whole thing in just a few minutes. So convenient! I really couldn't imagine life without TWRP. TWRP enables me to clone my device in case of hardware failure. All my settings and all my apps and all my custom configurations which would otherwise take hours/days to setup - BAM! Presto! on the new device and running perfectly.
TWRP + NeoBackup are essential. TWRP as described, and NeoBackup to roll back breaking updates to apps when devs butcher them, break them, and/or just remove really useful features. I also disconnect apps that get ruined by an update from the Play Store so they don't keep coming up when I check for updates.
Click to expand...
Click to collapse
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Jatin Verma x821 said:
I would advise you to read the posts again. They were asking about how to take backup of "personal apps" which twrp can't do, and if they are changing ROM then twrp backup won't be of any use to them. Therefore, whatever you're trying to tell here doesn't really help the discussion.
Click to expand...
Click to collapse
TWRP does backup personal apps and their settings. Once you restore a TWRP backup, you have everything back except media files - images, videos, documents, etc. The launcher icons, the apps, the system settings - everything is a perfect clone which you can restore on a new device (same model, of course).
I actually came across this thread searching to see if others had a problem where merely flashing TWRP caused Bluetooth to crash (and Atmos).
Use OrangeFox
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
s3rv said:
For me, the problem with BT and Joyose occurs only with TWRP v3.7.x. I went back to TWRP v3.6.1_9-0 but now backups are not working.
Click to expand...
Click to collapse
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
starkshadow said:
is there anyone use BT-fix-for-PE-20190618.zip to fix this problem ?
Click to expand...
Click to collapse
It looks like this guy didn't have any luck with it either. It may be divice specific
Dredead said:
I'm on an ROG Phone II with the same issue.
The "fix" is to wipe in TWRP and install Magisk BEFORE you leave for your first boot and NEVER come back to TWRP as the issue will return the second recovery is booted.
From what I can tell, this is correct. 3.6_XX-X allows me to come and go from TWRP as much as I please without incurring the bug, however, I haven't tested backup though I can't see a reason why they wouldn't work.
Are these existing backups that aren't working or the whole backup function in general?
It looks like this guy didn't have any luck with it either. It may be divice specific
Click to expand...
Click to collapse
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
starkshadow said:
amazing, I have do nothing, just reboot my device, and yesterday the bluetooth also has problem, but today I open bluetooth, it is no problem. I'm still confused about that.
Click to expand...
Click to collapse
It seems to be a twrp issue. What version do you have? And what version of magisk do you have?
I have recently flashed miui 12 (android 10) after bricking the phone using qtel. I noticed the Bluetooth problem last week and didn't find a fix. I have twrp 3.6.2 and magisk 25.1. I had twrp 3.7.1 but if failed to decrypt data using pattern so I rolled back to 3.6.2. And I thought that magisk had to do with the Bluetooth problem so I rolled back to 25.1 from 26.
I still can't use the Bluetooth, and I don't have time to reset the phone, I just finished restoring everything
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Olfason said:
I CAN CONFIRM
go back to the previous twrp 3.6.2 version + wipe factory reset or simply format data solve sucesfuly solve installation issue of Magisk 26.1 or Magisk Delta 25210
Click to expand...
Click to collapse
I can't afford resetting my phone right now , don't have enough time. I'll let it like that for some months.
Edit : I have miui 12.0.6 installed (android 10) and I'm not planning to upgrade since I have much better battery life (even better than every mod I tried). I wander if I flash miui rom from recovery can fix it?
Edit 2: flashing the rom from recovery didn't fix it