SM-N915R 6.01 firmware.
I have attempted every CF-Auto-Root venture out there without success. It simply fails, most often resulting in my having to re-flash stock firmware to get it going again. Here are 2 pics of what I get. See anything that I'm overlooking? I've tried to just flash TWRP but could only find .img files which, of course, Odin doesn't do. I read somewhere that I needed version 3.XX for Marshmellow. I tried TWRP ver 2.XXX as a .tar file but it failed as well.
I'm at the point where I'm getting ready to purchase a "One Click Root" solution for $40. Save me from the indignity.
RT
btw.....attempted to move this post to "general" but was not knowledgeable enuf to do it. Maybe moderator might intervene if need be. Thx.
{
"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"
}
View attachment 3858959
Use odin to flash recovery, untick the AUTOREBOOT option. When done, after pass appear, just remove the phone from cable and remove battery. Put it back to phone and reboot recovery then use twrp to flash supersu.
twrp > http://forum.xda-developers.com/note-edge/development/twrp-915fy-915tmo-moment-t3129459
supersu > https://download.chainfire.eu/962/SuperSU/RC-SuperSU-v2.73-20160517124156.zip
I'm having the same issue.
I believe it is related to the bootloader. It seems that the Marshmallow update locked my bootloader and I haven't been able to find a way to unlock that works or doesn't seem sketchy and involves doing a survey to download the magic tool that unlocks the bootloader.
I'd love to get root back on this device.
Hey you both,
Try with the latest version of TWRP [v3.0.2.0] in this forum (courtesy of Micky387) in tar format if you use Odin because it's multilanguage and it supports the latest Chainfire's root method without asking all the time about SuperSu : http://forum.xda-developers.com/misc.php?do=showattachments&t=3129459
and the latest stable version of SuperSu v.2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip.
To install Xposed try always the "alt" version, the latest I checked is v85.1-alt-sdk23
https://www.androidfilehost.com/?w=files&flid=64212 (but wanam has alredy post v.86-alt-sdk23: https://www.androidfilehost.com/?w=files&flid=78075).
Good luck
colgao said:
Hey you both,
Try with the latest version of TWRP [v3.0.2.0] in this forum (courtesy of Micky387) in tar format if you use Odin because it's multilanguage and it supports the latest Chainfire's root method without asking all the time about SuperSu : http://forum.xda-developers.com/misc.php?do=showattachments&t=3129459
and the latest stable version of SuperSu v.2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip.
To install Xposed try always the "alt" version, the latest I checked is v85.1-alt-sdk23
https://www.androidfilehost.com/?w=files&flid=64212 (but wanam has alredy post v.86-alt-sdk23: https://www.androidfilehost.com/?w=files&flid=78075).
Good luck
Click to expand...
Click to collapse
Well, that was slick and went well. Previous attempts at flashing TWRP via Odin meet with failure, but this one worked perfectly. Copied SU over, installed via TWRP, ran it, and now I'm rooted again.
Thanks for your willingness to help.
Out
RT
Please delete my post
Sent from my SM-N915L using XDA-Developers mobile app
colgao said:
Hey you both,
Try with the latest version of TWRP [v3.0.2.0] in this forum (courtesy of Micky387) in tar format if you use Odin because it's multilanguage and it supports the latest Chainfire's root method without asking all the time about SuperSu : http://forum.xda-developers.com/misc.php?do=showattachments&t=3129459
and the latest stable version of SuperSu v.2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip.
To install Xposed try always the "alt" version, the latest I checked is v85.1-alt-sdk23
https://www.androidfilehost.com/?w=files&flid=64212 (but wanam has alredy post v.86-alt-sdk23: https://www.androidfilehost.com/?w=files&flid=78075).
Good luck
Click to expand...
Click to collapse
can anyone share the step by step root ? is this cf-root on stock rom method ? by the way mine model is sm-n915g on MM
Aimara said:
can anyone share the step by step root ? is this cf-root on stock rom method ? by the way mine model is sm-n915g on MM
Click to expand...
Click to collapse
Getting rooted by this method is quite simple and vanilla. Should work for most phones I'd think
Really, it's simply a matter of following the steps outlined in colgao's post. It does require some knowledge using Odin.
Here's what I did:
So, use the links provided in colgao's post to download TWRP and SuperSu. TWRP comes as a TAR file, install-able using Odin, and SuperSu as a ZIP file, install-able using TWRP
Use Odin to install TWRP. All my other attempts at installing TWRP failed, and I couldn't find a TAR file version until colgao's post. It's apparently important to not allow the first reboot back into the operating system for fear of it overwriting the newly installed TWRP recovery back into stock. Disrupt the reboot so as to first go into recovery and let TWRP automatically do a fix.
You need to get the SuperSu zip file onto your phone or at least some sort of accessible media that TWRP can use. I used ES File Explorer from Play Store, but I'll guess any file explorer program would work.
After installing TWRP via Odin, reboot into recovery mode and using TWRP install the SuperSu ZIP file you put on your phone, reboot, run SuperSu and Bob's your uncle, you're rooted.
Good luck
RT
what i notice in the other thread is seem like many people had problems rooting even i see the steps are simple, the twrp for sm-n915g is the first tar file ?
twrp_3.0.0-2-915F-915FY-915G-915V.tar 16.50 MB 114
twrp_3.0-SM-N915tmo_SM-N915can.zip 13.74 MB 1996
twrp_3.0-SM-N915P_SM-N915R4.zip 13.71 MB 1416
twrp_3.0-915T_915CAN.tar 16.41 MB 982
twrp_3.0-915F-915FY-915G-915V.zip 13.78 MB 7356
twrp_3.0-915F-915FY-915G-915V.tar 16.46 MB 5736
twrp-3.0.2.0_tbelteskt.zip 13.22 MB 172
twrp-3.0.2.0_SM-N915P,SM-N915R4.zip 13.59 MB 178
twrp-3.0.2.0_915tmo-915can.zip 13.61 MB 440
twrp-3.0.2.0_915F_915FY_915G_915VZW.zip 13.66 MB 1756
twrp-3.0-915P_915R4.tar 16.38 MB 946
twrp-2.8.7.0-915S-K-L.tar 11.63 MB 20
twrp-2.8.7.0-915S-K-L.tar 11.63 MB 122
tempFileForShare_2015-07-16-07-43-27.jpg 241.7 KB 114
recovery.log 20.5 KB 10
Kernel_V2.1_F2FS_by_Micky387.zip 11.12 MB 52
20160306_024231.jpg 237.1 KB 160
2015-07-25 08.47.27.jpg 256.6 KB 648
1466889288906.jpg 38.8 KB 156
1437292564610.jpg
Aimara said:
what i notice in the other thread is seem like many people had problems rooting even i see the steps are simple, the twrp for sm-n915g is the first tar file ?
twrp_3.0.0-2-915F-915FY-915G-915V.tar 16.50 MB 114
twrp_3.0-SM-N915tmo_SM-N915can.zip 13.74 MB 1996
twrp_3.0-SM-N915P_SM-N915R4.zip 13.71 MB 1416
twrp_3.0-915T_915CAN.tar 16.41 MB 982
twrp_3.0-915F-915FY-915G-915V.zip 13.78 MB 7356
twrp_3.0-915F-915FY-915G-915V.tar 16.46 MB 5736
twrp-3.0.2.0_tbelteskt.zip 13.22 MB 172
twrp-3.0.2.0_SM-N915P,SM-N915R4.zip 13.59 MB 178
twrp-3.0.2.0_915tmo-915can.zip 13.61 MB 440
twrp-3.0.2.0_915F_915FY_915G_915VZW.zip 13.66 MB 1756
twrp-3.0-915P_915R4.tar 16.38 MB 946
twrp-2.8.7.0-915S-K-L.tar 11.63 MB 20
twrp-2.8.7.0-915S-K-L.tar 11.63 MB 122
tempFileForShare_2015-07-16-07-43-27.jpg 241.7 KB 114
recovery.log 20.5 KB 10
Kernel_V2.1_F2FS_by_Micky387.zip 11.12 MB 52
20160306_024231.jpg 237.1 KB 160
2015-07-25 08.47.27.jpg 256.6 KB 648
1466889288906.jpg 38.8 KB 156
1437292564610.jpg
Click to expand...
Click to collapse
Yes, I believe that file will work.
All the other exploits I tried, using Odin with various cf-root files, failed. The only thing that "worked" for me was installing TWRP, then flashing Superus using TWRP.
Worth a try I think.
Devildoc99 said:
Getting rooted by this method is quite simple and vanilla. Should work for most phones I'd think
Really, it's simply a matter of following the steps outlined in colgao's post. It does require some knowledge using Odin.
Here's what I did:
So, use the links provided in colgao's post to download TWRP and SuperSu. TWRP comes as a TAR file, install-able using Odin, and SuperSu as a ZIP file, install-able using TWRP
Use Odin to install TWRP. All my other attempts at installing TWRP failed, and I couldn't find a TAR file version until colgao's post. It's apparently important to not allow the first reboot back into the operating system for fear of it overwriting the newly installed TWRP recovery back into stock. Disrupt the reboot so as to first go into recovery and let TWRP automatically do a fix.
You need to get the SuperSu zip file onto your phone or at least some sort of accessible media that TWRP can use. I used ES File Explorer from Play Store, but I'll guess any file explorer program would work.
After installing TWRP via Odin, reboot into recovery mode and using TWRP install the SuperSu ZIP file you put on your phone, reboot, run SuperSu and Bob's your uncle, you're rooted.
Good luck
RT
Click to expand...
Click to collapse
do i still have to unlock the bootloader of my phone before proceeding?
johnkernelle2 said:
do i still have to unlock the bootloader of my phone before proceeding?
Click to expand...
Click to collapse
You know, I'm not certain, but I believe you do, as well as enabling USB Debugging and checking off allowing insecure apps.
There are a multitude of articles on how to do all this.
Good Luck
Devildoc99 said:
SM-N915R 6.01 firmware.
I have attempted every CF-Auto-Root venture out there without success. It simply fails, most often resulting in my having to re-flash stock firmware to get it going again. Here are 2 pics of what I get. See anything that I'm overlooking? I've tried to just flash TWRP but could only find .img files which, of course, Odin doesn't do. I read somewhere that I needed version 3.XX for Marshmellow. I tried TWRP ver 2.XXX as a .tar file but it failed as well.
I'm at the point where I'm getting ready to purchase a "One Click Root" solution for $40. Save me from the indignity.
RT
btw.....attempted to move this post to "general" but was not knowledgeable enuf to do it. Maybe moderator might intervene if need be. Thx.
View attachment 3858958
View attachment 3858959
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...axy-note-edge-sm-n915fy-android-6-01-t3379797
Devildoc99 said:
You know, I'm not certain, but I believe you do, as well as enabling USB Debugging and checking off allowing insecure apps.
There are a multitude of articles on how to do all this.
Good Luck
Click to expand...
Click to collapse
Can you Please give me a link on how to unlock the bootloader for my phone? (SM-N915G Android 6.0.1, build number MMB29M.N915GXXU1DPG6) there are many articles on the web but i am afraid to try them out, i do not know if it will work for the version of my phone. Thanks
colgao said:
Hey you both,
Try with the latest version of TWRP [v3.0.2.0] in this forum (courtesy of Micky387) in tar format if you use Odin because it's multilanguage and it supports the latest Chainfire's root method without asking all the time about SuperSu : http://forum.xda-developers.com/misc.php?do=showattachments&t=3129459
and the latest stable version of SuperSu v.2.76: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip.
To install Xposed try always the "alt" version, the latest I checked is v85.1-alt-sdk23
https://www.androidfilehost.com/?w=files&flid=64212 (but wanam has alredy post v.86-alt-sdk23: https://www.androidfilehost.com/?w=files&flid=78075).
Good luck
Click to expand...
Click to collapse
I have SM-N915F on 6.0.1. Everything is stock.
Are these steps; flashing TWRP with Odin and SuperSU with TWRP are enough to root my phone??????
OR, do I need to flash the BOOTLOADER as well? If yes, please share the link for the 6.0.1 bootloader. I tried to find the most heard about bootloader from @micky387 but couldn't find one for 6.0.1.
Related
Any procedures on how I can root this new version?
I just got the OTA notification and updated through Pc companion but I lost root jn the process.
I have a locked bootloader BTW.
Thanx n advance.
BragaisG said:
Any procedures on how I can root this new version?
I just got the OTA notification and updated through Pc companion but I lost root jn the process.
I have a locked bootloader BTW.
Thanx n advance.
Click to expand...
Click to collapse
This is wrong thread for Q&A, but I can enlight you its not possibe today with locked bootloader. Have a good day!
Root is possible with locked bootloader.
Did it a few minutes ago.
Flashed 4.4.4 via Flashtool
Rooted via Easytool
Dualrecovery via .bat with Point 3 in the menue
Then flashed a 5.0.2 Zip I made with PRFCreator including Root (SuperSu 2.4.6) and Dualrecovery
Everything is working fine!
You can more accurately describe these operations how to do it ??
spoxxx said:
You can more accurately describe these operations how to do it ??
Click to expand...
Click to collapse
1. Download the firmware for your device with "XperiFirm"
2. Make a ftf of the firmware you just downloaded with "Flashtool".
3. Download "dual recovery" and latest "SuperSU" package.
4. Make sure you have a custom recovery already on your phone.
5. Read how to use this tool and make a zip for your phone to flash with it
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
6. Flash the zip through recovery. Wipe cache, data and dalvik before ideally. Done. You will be pre-rooted with SuperSU.
PS: Don't try to install Xposed yet, it causes bootloops after first reboot so I am back on Kitkat until that's sorted.
Here is the tutorial for PRFCreator:
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Then flash the zip from sdcard1 via Philz Recovery
1st boot takes a long time
When already on 5.0.2, then flash a Kitkat FTF via Flashtool
Then root the 4.4.X with Easyroot
After that you have to use Dualrecovery installer, there you choose point 3
ZU will restart, pushing Vol Up will start Philz Recovery
In Philz Recovery Wipe Data, Cache, Dalvik, Factory reset
Then install Zip
didnt work for me
Thi method didnt work for me. My mobile is C6802. It went into a loop
The steps I followed were like this:
Flash kitkat with flashtool
Root with philz dual recovery
go into philz recovery
flash the zip file made with the link given above.
for recovery i downloaded philz dual recovery flashable
Try to make your own Zip with PRFCreator with a FTF for the C6802
Excuse me, does it work with locked bootloader? I'm coming from rooted 4.4 with locked bootloader but after I've followed your steps now I am in a bootloop
zot71 said:
Excuse me, does it work with locked bootloader? I'm coming from rooted 4.4 with locked bootloader but after I've followed your steps now I am in a bootloop
Click to expand...
Click to collapse
Followed again all the steps but checking more options in PRFCreator.... Lollipopo 5.02 with root is actually running on my Z Ultra
Thanks for your instructions!!
Actually there's a way to root 5.0.2 on UB without recompiling the .ftf and reflashing 4.4.4 back and forth. Just did that yesterday after having a bootloop with that pre-rooted .ftf.
So here's the idea (assuming you have an unlocked bootloader):
You will need the 5.0.2 .ftf, flashtool, fastboot, boot.img file from doomkernel v.22, XZDualrecovery zip and latest SuperSU zip from koushik's webpage (the one with 7 or 8 folders in it).
1) Clean flash any Lollipop .ftf with Flashtool.
2) Use fastboot to flash the boot.img from DoomKernel, thus you get a working recovery.
3) Restart the phone straight into recovery without letting it boot.
4) Flash SuperSU and XZDualRecovery, do the wipes (cache+dalvik) and power off the phone.
5) With Flashtool flash only the kernel of the Lollipop rom.
6) Reboot and enjoy! Now you have a fresh stock Lollipop ROM with full root access and a working recovery.
I suppose you could lock the bootloader back after that if you need it, though I don't see any reason to do that.
P.S. I will try to update this post with all links later when I get to my PC, posting with my XZU now.
zot71 said:
Followed again all the steps but checking more options in PRFCreator.... Lollipopo 5.02 with root is actually running on my Z Ultra
Thanks for your instructions!!
Click to expand...
Click to collapse
What options did you tick?
how to get lollipop kernel file
leeleewye said:
how to get lollipop kernel file
Click to expand...
Click to collapse
If you're asking about my previous post, then you don't actually have to "get" it. You should load the very same .ftf into Flashtool and then uncheck every tick except "KERNEL". That's the way to flash only one part of the rom.
Xa6a said:
Actually there's a way to root 5.0.2 on UB without recompiling the .ftf and reflashing 4.4.4 back and forth. Just did that yesterday after having a bootloop with that pre-rooted .ftf.
So here's the idea (assuming you have an unlocked bootloader):
You will need the 5.0.2 .ftf, flashtool, fastboot, boot.img file from doomkernel v.22, XZDualrecovery zip and latest SuperSU zip from koushik's webpage (the one with 7 or 8 folders in it).
1) Clean flash any Lollipop .ftf with Flashtool.
2) Use fastboot to flash the boot.img from DoomKernel, thus you get a working recovery.
3) Restart the phone straight into recovery without letting it boot.
4) Flash SuperSU and XZDualRecovery, do the wipes (cache+dalvik) and power off the phone.
5) With Flashtool flash only the kernel of the Lollipop rom.
6) Reboot and enjoy! Now you have a fresh stock Lollipop ROM with full root access and a working recovery.
I suppose you could lock the bootloader back after that if you need it, though I don't see any reason to do that.
P.S. I will try to update this post with all links later when I get to my PC, posting with my XZU now.
Click to expand...
Click to collapse
Successful with this guide. Thanks man.
Looking forward with the guide with links.
Thanx!
Sent from my C6833 using XDA Free mobile app
seking said:
What options did you tick?
Click to expand...
Click to collapse
I don't know if it is correct but I checked all the options in the upper right and everything worked.
Actually I am using my rooted lollipop without wiping everything except cache and dalvikcache and its running perfectly.
Thanks for the guide!!!
Xa6a said:
Actually there's a way to root 5.0.2 on UB without recompiling the .ftf and reflashing 4.4.4 back and forth. Just did that yesterday after having a bootloop with that pre-rooted .ftf.
So here's the idea (assuming you have an unlocked bootloader):
You will need the 5.0.2 .ftf, flashtool, fastboot, boot.img file from doomkernel v.22, XZDualrecovery zip and latest SuperSU zip from koushik's webpage (the one with 7 or 8 folders in it).
2) Use fastboot to flash the boot.img from DoomKernel, thus you get a working recovery.
.
Click to expand...
Click to collapse
Please give me file boot.img with many thanks.
I remember that, the boot.img file from doomkernel v.22 from kitkat 4.4.4, what is a trouble happend ?
Mucho79 said:
Here is the tutorial for PRFCreator:
http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
Then flash the zip from sdcard1 via Philz Recovery
1st boot takes a long time
When already on 5.0.2, then flash a Kitkat FTF via Flashtool
Then root the 4.4.X with Easyroot
After that you have to use Dualrecovery installer, there you choose point 3
ZU will restart, pushing Vol Up will start Philz Recovery
In Philz Recovery Wipe Data, Cache, Dalvik, Factory reset
Then install Zip
Click to expand...
Click to collapse
Is this process ok ? please show me before I flashing to my phone.
{
"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"
}
on C6833 I create flashable Zip stock 5.0.2 with SuperSU and dualrecovery. you must flash android 4.4.4 and root + dualrecovery then build pre rooted zip rom and flash it from Philz recovery
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
reednoel4u said:
Is this process ok ? please show me before I flashing to my phone.
Click to expand...
Click to collapse
You must check all option's
How to have right root on Speed 7 & Speed 7 Plus (Zp951/952) Mtk 6753
{
"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"
}
In this thread we will discuss how to receive right root in the new Phone Zopo Speed 7 & plus
Everybody are Welcome!
MANY THANKS TO OUR MODERATORS TO OPEN THIS SECTION !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
Software section
Drivers
http://www.4shared.com/rar/THPrHzDxce/USB_VCOM_Driver.html
https://www.dropbox.com/s/125r5twipmdt1wn/MT6589 drivers.zip
http://www.4shared.com/zip/Y_F6KBCe/...sb_driver.html
http://www.4shared.com/rar/5wokI0ev/...NDROID__B.html
http://www.4shared.com/zip/dSb69w17/Copy_of_Driver.html
http://www.4shared.com/rar/qM8hDW5u/zopo_usb_drivers.html
https://copy.com/eUvMdQBAqiJmLLzp
http://ge.tt/2yL21VT/v/2
Firmware
http://global.zopomobile.com/?p=1
Recovery Modded
Cwm Base no touch
https://copy.com/Of0epSHxRkpwoJkX
Flashtool V.5.1520
Flashtool V.5.1444
Version ONLY for Mtk 67xx
http://www.4shared.com/rar/AU4kSVORce/SP_Flash_Tool_exe_Windows_v514.html
Flashtool V.5.1520
Version ONLY for Mtk 67xx
http://www.4shared.com/zip/UNGyZqy2ba/SP_Flash_Tool_exe_Windows_v515.html
Utility section
Drivers Installation :
Procedure :
To install the USB drivers VCOM the phone must be turned off and connected to the PC with or without a battery depending on the type of device,
get a screen like this in the device manager of the computer
Once you have installed the terminal will be shown in this way (the COM port may be different)
For those who have problems with the installation of these drivers and have had in the past a terminal mtk
they may have a driver conflict, or even if you just do the confusion and installed it different,
to solve, you can try to use the program
usbdeview:
http://www.nirsoft.net/utils/trans/usbdeview_italian.zip
select all items in that report as VCOM USB Preloader in the Mediatek figure right click Unistall and restart the PC.
Installation of the Firmware:
PROCEDURE
1) Setup new Firmware
To download the new firmware.
Unzip the compressed file and insert into the firmware folder:
a) recovery modded (is necessary for receive right root)
Phone off without usb cable and possibly removed the battery and put back for a perfect reset .....
and hold mode 'of off without usb cable connected!
Run Flashtool version octa-core ..... select the file, and then scatter firmware upgrade ...... NOW ONLY CONNECT USB CABLE not before!
Wait for the end of the installation procedure of the firmware and eventually restart the phone!
This' whole simplified procedure for installing the original firmware.
Installation only the Recovery modded:
PROCEDURE
1) Download the new Recovery modded.
Unzip if the file is compressed and copy and replace into the firmware folder:
(remember that in the Firmware's folder must be only one recovery file example Recovery.img)
The recovery modded (is necessary for receive right root)
2) Phone off without usb cable and possibly removed the battery and put back for a perfect reset .....
and hold mode 'of off without usb cable connected!
3) Run Flashtool version octa-core ..... select scatter loading
View attachment 3460476
4) select the folder where is the firmware and select the scatter .img
View attachment 3460477
5) "Download only "must be present in the box .....
Run the button in the top of flashtool program with the green arrow download ...... NOW ONLY CONNECT USB CABLE not before!
Wait for the end of the installation procedure of the firmware
remove the usb cable and eventually restart the phone!
ROOT Section
PROCEDURE (SuperSu)
1) Download the SuperSu App from the Xda Web SIte
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Copy it to your SD card .
2) Go into recovery modded
(REMEMBER THE WAY TO ENTER IN RECOVERY MODDED)
(you must use power menu button +=(in the same time) level volume ( +) in the same time and wait for start the phone.....do not remove the fingers on the buttons)
run the menu up to install zip from ext card .....and select the Select SuperSu v.xx .zip and install
Reboot into android S.O.
You should see the app installed Super Su.
3) Install Busybox (from files or from GooglePlay store)
open the app and give the right Su power and wait for it's scan
4) Install the binary from the Busybox menu' "normal install"
After correctly installed the binary ...Reboot the phone
And you will have your rights as a Root
Many Thanks to:
Jessica Tang, Feng, Xiaoyi Tang, Jaynes,Lee,Tao, Charles
To The Author of Super Su: Chainfire.
All My Friends here and from others web sites and forums that help me "always" in the time:
Carliv,Yuweng, Codelover,Bigrammy,SevenMax, Marsapa, PaoloTHL, Command0, M3N3chm0,Biobio,ICEMAN,Mrjavum, Hypo Turtle,Stahl.
I apologize in advance if not list them all!
Others Programs and Applications that run in these two phones to have right root
@Everybody,
This thread like the others Zopo's threads opened from me will not receive from me any others posts cause problems connected to the Zopo heads.
I apologize to all my followers...
ghost45 said:
@Everybody,
This thread like the others Zopo's threads opened from me will not receive from me any others posts cause problems connected to the Zopo heads.
I apologize to all my followers...
Click to expand...
Click to collapse
What happened? Could you explain it to us, please?
Where is the scatter file? I have download all software but there isn't any txt scatter file.
To have scatter file download an original ROM on zopomobile.com website. In ROM's zip file there is also the scatter.
Hi!
thank U!
But...where do I have to put the scatter file?
into the complete Su...erSU-v2.46.zip file ?
it didn't work for me! ...... error "installation aborted"
what could be wrong?
eristes said:
Hi!
thank U!
But...where do I have to put the scatter file?
into the complete Su...erSU-v2.46.zip file ?
it didn't work for me! ...... error "installation aborted"
what could be wrong?
Click to expand...
Click to collapse
Is impossible that not run!
Have you installed the recovery modded?
Sent from my Zp 953 using XDA Free mobile app
Cannot install firmware patch on rooted device
My zopo speed 7 has received new update that solve some device problem but when reboot the device cannot enter in recovery mode correctly to upgrade firmware (it show only "fix root" yes or no) and when boot second time it ask me to download and install the update another time.
What can i do to enable device patch installation?
Thank you
drastik73 said:
My zopo speed 7 has received new update that solve some device problem but when reboot the device cannot enter in recovery mode correctly to upgrade firmware (it show only "fix root" yes or no) and when boot second time it ask me to download and install the update another time.
What can i do to enable device patch installation?
Thank you
Click to expand...
Click to collapse
As you said, you can not install an OTA update if you have rooted the phone and/or you have made changes in system files, you need to restore the system (not a factory reset) to its original stated. You need stock recovery too.
You can use Flash Tool to flash the original ROM from Zopo, but be sure you uncheck the USERDATA mark if you don't want to loose your files/programs/configuration...... Once you have the original system back, you have to apply all the OTA's until you reach the last 20151016.
Once you are in the last version make sure to backup boot.img and system before you root the phone again, so next time you can only restore using that backup instead of flash the original Rom, so you only will need apply the last OTA.
If you want to use it, I made a bakcup from the last 20151016 system and boot using Flash Tool > Read Back optión, so if you flash this backup you will have your system updated directly.
https://mega.nz/#!xVpglLIL!uo6Bik6LO5aHiFuPxG5HH0fxGytXUhiPDuXofxDul2Q
Just unzip the files and use Flash Tool to flash the needed files (boot.img, system.img and trustzone.bin) using the scatter file included to make it less confusing. (Speed 7, not for Speed 7 Plus).
Regards.
Thank you elperroderoke, i have used your backup with no problem, the strange thing though is that the update had to solve "third part launcher is not setted after restart" but i've the same problem after every phone restart i lost about half number of icon on launcher.
New update
Hi elperroderoke, there is another update, can you give me your updated backup as last time?
Thank you
elperroderoke said:
As you said, you can not install an OTA update if you have rooted the phone and/or you have made changes in system files, you need to restore the system (not a factory reset) to its original stated. You need stock recovery too.
You can use Flash Tool to flash the original ROM from Zopo, but be sure you uncheck the USERDATA mark if you don't want to loose your files/programs/configuration...... Once you have the original system back, you have to apply all the OTA's until you reach the last 20151016.
Once you are in the last version make sure to backup boot.img and system before you root the phone again, so next time you can only restore using that backup instead of flash the original Rom, so you only will need apply the last OTA.
If you want to use it, I made a bakcup from the last 20151016 system and boot using Flash Tool > Read Back optión, so if you flash this backup you will have your system updated directly.
Just unzip the files and use Flash Tool to flash the needed files (boot.img, system.img and trustzone.bin) using the scatter file included to make it less confusing. (Speed 7, not for Speed 7 Plus).
Regards.
Click to expand...
Click to collapse
drastik73 said:
Hi elperroderoke, there is another update, can you give me your updated backup as last time?
Thank you
Click to expand...
Click to collapse
Sorry, but I don't have this phone anymore. Now testing Meyzu M1 Note .
Regards.
Enviado desde mi m1 note mediante Tapatalk
This phone can be very simply rooted with NewKingrootV4.52_C127_B227_xda_release_2015_09_28_105243.apk
After doing that you would like to remove kinguser and related files, and replace it with the well known SuperSU.
Run the script given here: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
How can I root Zopo Speed 7 with official Android 6.0 ROM?
I cannot download recovery from link in this thread:
Code:
Recovery Modded
Cwm Base no touch
CLICK TO HIDE CONTENT
https://copy.com/Of0epSHxRkpwoJkX
Kingroot and framaroot doesn't work.
how can i root new update 6 MM on speed 7? any method ?
I do not own the device anymore. So I can't support the thread anymore, if anyone wants to carry on just pm me. But as far as I know there are newer threads about this topic. Thank you
Hey there,
I decided to write a how-to on gaining root for the g531f Galaxy grand prime ve.
This should work for all grand prime devices based on marvel soc.
About this method:
Knox counter was not tripped for my device using this method.
The main steps, flashing latest stock and twrp, are perfomed by Odin. To gain root chainfire's supersu is flashed with twrp. If you are unsure about any step there are enough guides found on xda refering odin, twrp and supersu.
So let's get started.
I`M NOT RESPONSIBLE FOR ANY DAMAGE OR WARANTY LOST ON YOUR PHONE.
1. Make sure your device drivers is installed properly
2. Get Odin v3.09 for example here:
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
3. Get your latest firmware and extract it once
http://www.sammobile.com/firmwares/database/SM-G531F/
4. Get twrp
https://dl.twrp.me/grandprimevelte/twrp-2.8.7.1-grandprimevelte.img.tar.html
5. Get supersu by chainfire
Latest beta
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or confirmed working version 5.52 beta, if the latest doesn't work thanks to @XelSam:
https://download.chainfire.eu/743/Su...erSU-v2.52.zip
6. Backup all things you need and copy supersu to external sd card
7. Boot to stock recovery and perform a factory reset and wipe internal memory.
(power off device and keep holding volume up, home and power button)
8. Reboot to download Mode, then start odin and connect your device
(holding volume down, home and power button to get into download Mode)
9. Flash your firmware with Odin by using the AP button and hit start. Make sure repartition is NOT selected and untick auto reboot. This step takes some time
10. Boot to download Mode again. And flash twrp as mentioned above. Using AP and the same selection.
--if twrp doesn't boot you have to use another firmware (step 9) post #20-- thanks to @bluepower
11. Boot into twrp recovery. Hit install and select the supersu zip file then clean cache and dalvic.
(holding volume up, home and power button)
12. Reboot your phone and see if everything is working.
13. Go to dev settings and tick "manufacturer unlock" to prevent fap lock.
(unlock dev settings: Settings - about phone - tap build number 7 times). If that doesn't work check post #4 and #6 and say thx to @hck5
14. Make a nandroid in twrp recovery to have a clean rooted rom to return to if anything gets messed up with further modding (eg. xposed framework etc.)
10.1 100%Working firmware
If you can't find a version that allows to flash twrp (carrier lock) use this unbranded one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
Check gps. If it doesn't lock install this app and configure your region.
https://play.google.com/store/apps/details?id=by.zatta.agps
CREDITS and CUDOS
chainfire
Twrp team
Odin team
Samsung
If you are interested in xposed check wanams xposed thread.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
The x86 version is working fine for me
For audio enhancement I'm using dolby atmos cause Viper didn't do the trick for me.
http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
So have fun with your unchained device and hit thanks button.
Great job!
Hey there i have the same model and i'm happy that last night i've found your post
i used the pre-rooted firmware and i had the system ui rebooting problem after i uninstalled any of the apps
also i've seen guys who had that security tab problem from settings (didn't happened to me)
I am extracting the stock rom now i prepared everything
i also wanted so badly the viper fx cause the sound is pretty low
i searched for alternative but here you are with dolby atmos
i greatly thank you for the effort for posting this tuto
i will be back after i do the job!
Thanks!!!
---------- Post added at 12:46 PM ---------- Previous post was at 12:25 PM ----------
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
hck5 said:
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
Click to expand...
Click to collapse
Thx for your feedback and confirmation that it is working.
So have fun with your device.
BTW don't forget to make a nandroid backup before you mess around with xposed modules to get back to your rooted rom. I destroyed my system twice with xposed.... And I had to go through this procedure again (thanks touchwiz).
okay
ok. thanks for the advice i was just messing with the modules and i have no backup xD
there is a pic with all i have so far
{
"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"
}
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
and this is the ultimate fix
"i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable" thanks to bhavstech xda member
hck5 said:
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
Click to expand...
Click to collapse
Try to unlock via dev settings. Manufacturer unlock.
http://forum.xda-developers.com/attachment.php?attachmentid=3495074&d=1443947143
If that doesn't work you have to delete your Google account as far as I know.
For me it is working with Google account, but I can't remember if I ticked the dev setting option before or after adding my Google account.
for me has been this one
klausel said:
5. Get supersu by chainfire
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
eau4x6 said:
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
Click to expand...
Click to collapse
I don't know exactly what you mean with sideloading app.
But as far as I know root is needed to install supersu via Google play store. Of course you can sideload the app via adb shell when booted to twrp. But I wanted to keep the tutorial simple without setting up adb etc.
Hope your question is answered.
Thank's for recovery
I thing a new nice rom will coming soon for 531F
klausel said:
Of course you can sideload the app via adb shell when booted to twrp.
Click to expand...
Click to collapse
Transfering APK to internal storage/sd card and installing from there (by opening it in file manager) is what I had in mind.
I don't think is that easy.. You must set system read and write and I guess twrp helps it installing supers in a better way than your file manager does
---------- Post added at 12:49 PM ---------- Previous post was at 12:45 PM ----------
We just need a hell of a rom
finally thank you very much! ?
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
bluepower said:
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
Click to expand...
Click to collapse
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
klausel said:
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
Click to expand...
Click to collapse
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
bluepower said:
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
Click to expand...
Click to collapse
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
bluepower said:
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
Click to expand...
Click to collapse
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
klausel said:
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
Click to expand...
Click to collapse
I'm back. Thanks. I'm going to try now.
Edit: Ok, done.
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
bluepower said:
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
Click to expand...
Click to collapse
Glad to know you got it and thanks for your feedback.
To rule out all misunderstandings and help other people with the same problem.
1. You flashed a rom from another carrier for your region and 2. updated it to the latest version via ota.
3. You installed twrp and 4. supersu
Is that the way you proceeded.?
Did the line for fap lock appear in dl mode?
Thanks in advance
Since TWRP is still not ported to V10, so i decided to make a prerooted-boot.img.
Download Link
You can flash this boot.img to root your Honor V10 AL20C00 (6GB+128GB China Edition) on stock firmware (B132)
Usage:
0. Unlock bootloader and close find my phone.
1. Power off your phone
2. Plug your phone to computer
3. Hold power and volume down until boot into fastboot mode
4. flash this boot.img by adb ( fastboot flash ramdisk boot-root-b122.img), please download adb by yourself
5. reboot (fastboot reboot)
Your phone may reboot twice, and you'll get root access.
Declaim:
I only test this on my own phone (BKL-AL20C00), Use this on your own risk. I'm not responsible for your phone's damage.
using this tool means you accept this.
Thanks:
HRT-Lin
@mankindtw for his Mate-10 root boot.img
cofface for his bootimg.exe to unpack and repack boot.img
@worstenbrood for his Huawei Update Extractor
Does this root work on stock BKL-AL20 8.0.0.132 update?
Same question. I got BKL-L09 8.0.0.120
No bootloader unlock needed? And i also hope, someone can confirm this on BKL-09 - 120 .
They didn't lock bootloader? Already preorder international unit
Hi,
Can you be a little more specific? Did you unlock your Bootloader first? When you say stock firmware B132, do you mean version 8.0.0.132 ? Thank you in advance for your reply!
Custom Recovery for V10
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
I'm hesitant to try this without more information
harshshah17 said:
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
Click to expand...
Click to collapse
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
piphol said:
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
Click to expand...
Click to collapse
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
harshshah17 said:
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
Click to expand...
Click to collapse
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Only thing I've seen that doesn't work with root is face unlock. Also how can I flash magisk since there isn't a recovery yet. Can I use flashify?
Yut kill
dawnc said:
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Click to expand...
Click to collapse
Where can you find the full OTA?
whymista said:
Where can you find the full OTA?
Click to expand...
Click to collapse
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. ?
piphol said:
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. [emoji25]
Click to expand...
Click to collapse
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
whymista said:
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
Click to expand...
Click to collapse
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
piphol said:
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
Click to expand...
Click to collapse
I have the bkl-l09. I'd appreciate it if you could. I'll try this version since it can't hurt though.
Sent from my ONEPLUS A5000 using Tapatalk
So I tried to flash it through adb and it didn't work this is what I got.
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I'm trying to use the recovery tool they have that says I need 5 different files but I've no idea where to find them like the system img etc.
Sent from my ONEPLUS A5000 using Tapatalk
This is what it's saying I need to unbrick
{
"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"
}
Sent from my ONEPLUS A5000 using Tapatalk
whymista said:
This is what it's saying I need to unbrick View attachment 4405892
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It should be "fastboot flash ramdisk <boot image name>".
Second, if it doesn't help, the next step is to enter e-recovery mode. Press Volume Up + Power for 15 seconds. Follow the prompts and it should download the full OTA for you. I think you need your Huawei ID in the process (and a good Wifi signal).
Lastly, I think this is a sure bet but will cost you, google "funkyhuawei honor v10 rebranding guide". You will find a reddit link. They are the only team who "holds" BKL-L09 Full OTA roms that I know of. You need to buy "credits" to download OTAs and unbrick your phone. Unfortunately, team MT (team behind Firmware Finder) hasn't got a hold of a full OTA of BKL-L09.
From my experience, the first suggested solution should already work. I hope you don't get to the third solution.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"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"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !