Team Win Recovery Project v3.0.0.0 for D605
{
"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"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible
Related
i have a Karbonn A30 with 5'9" screen.i want to create a CWM recovery for the device.
i have tried many ways but its not working.the original recovery is attached below.
michael.the.don said:
i have a Karbonn A30 with 5'9" screen.i want to create a CWM recovery for the device.
i have tried many ways but its not working.the original recovery is attached below.
Click to expand...
Click to collapse
Have you tried running it through the official Clockworkmod Recovery builder? Or have you taken a look at the guides Porting ClockworkMod Recovery to a New Device and [GUIDE] Compile CWM Recovery?
i have tried porting it. i dont knw if its working or not.because its a MT6577 device and i cannot get it to flash the recovery partiton. even AIO flasher hangs when i try to flash recovery.can u tell me if the below given build is a successfull port.i used the online builder for this.
how did u extract recovery.img??
rakesh1988 said:
how did u extract recovery.img??
Click to expand...
Click to collapse
First you have to figure out which block is the recovery partition this can be found by either typing in terminal emulator or ADB shell "mount" or running a command similar to "cd dev/block/platform/{SoC Name Here for example mmci-omap-hs.0}/by-name" then once in that directory "ls -l" noting the block name of the recovery partition. After you have done that then you can dump the recovery partition to your phone by running the command "dd if={path to recovery partition you obtained earlier from one of the above mentioned commands} of={path to SD Card or output destination}/recovery.img".
michael.the.don said:
i have tried porting it. i dont knw if its working or not.because its a MT6577 device and i cannot get it to flash the recovery partiton. even AIO flasher hangs when i try to flash recovery.can u tell me if the below given build is a successfull port.i used the online builder for this.
Click to expand...
Click to collapse
Try flashing it through MobileUncle Tools, worked on MMX A110, another MT6577 device.
MobileUncle Tools doesnot flash.anyway bricked my device using sp flash tools.it will be back tomm from servicing.
michael.the.don said:
MobileUncle Tools doesnot flash.anyway bricked my device using sp flash tools.it will be back tomm from servicing.
Click to expand...
Click to collapse
is there no stock rom for a30 which can be used to flash the phone using sp flash tool??
i tried to get recovery img dump on sd card
i was at cd dev/block/platform/abcd(soomething was der)/by-num
after that i get list of mmcblk0p1 to mmcblk0p6
how to confirm that which is a recovery ?
arkerio said:
i tried to get recovery img dump on sd card
i was at cd dev/block/platform/abcd(soomething was der)/by-num
after that i get list of mmcblk0p1 to mmcblk0p6
how to confirm that which is a recovery ?
Click to expand...
Click to collapse
The directory should be by-name not by-num. After you are in the correct directory type "ls -l" the recovery partition should be the partition with the "SOS" name listed. If you only have by-num directory you can try running (Make sure to be running the shell as superuser by typing "su" in terminal emulator or ADB shell first) "cat /proc/mtd" and if that doesn't work try (Also with superuser permissions) cat /proc/emmc both of this commands if they return a value the recovery partition will be named "recovery". Let me know if you still have questions .
here is s gscript that lets u dump all the partitions.a ful rom backup.
i have a full dump.only the PRELOADER and DSP_bl is corrupted.
i cant get them to load in sp flash tools
see the attached gscript.for complete backup use the "back_mt6575_a4_v2c" script.
i have attacher the scatter file if some one needs it.my device is still in servicing.so i cant go foreward.
{credits for the "back_mt6575_a4_v2c" script to original developer.i fount it not mine.i dont knw whos it is.}
M very noob in all this things and i dnt know how to use above scripts
but from the reply above -1
i got it how to backup recovery img
cat /proc/emmc this command works
learning learning learning will ask question if i stuck
preparing ubuntu pc
here is the turorial how to use the gscript.http://forum.xda-developers.com/showthread.php?t=1825722
see the section where it says rombackup.
but instead of using the script mentioned in the tutorial.use the one i have given above.u dont need any commands here.it will backup automatically/.
Hi
m getting error while unpacking recovery.img
"Error: the input file does not appear to be a valid file. at ./unpack-mt65xx.pl
line 45."
but the recovery.img which is attched to firsth post is getiing unpack perfectly
what m doing wrong
i got recovery by following commands
one is - cat /dev/block/mmcblk0p2 > /mnt/sdcard/recovery.img
&
second is if=/dev/block/mmcblk0p2 of=/mnt/sdcard/recovery.img
using both the command i get recovery.img but it is of 5MB
and the recovery which is attached at 1st post is of 6MB
EDIT:
michael.the.don i have used ur given script and m able to get all img as backup
and i have also created cwm as per guide given by you
let me know how you bricked ur device ?
what you were trying ?
How did you get that scatter file ?
my recovery is attached but yet no tried it
cherry mobile titan CWR,TWRP and Stock Recovery
High Guys here is the different recoveries from our rebranded Karbon a30 to Cherry Mobile Titan TV
Clockworkmod - CWMR - 6.0.1.5
https://mega.co.nz/#!YUgEkSKC!JjokMRNW9dmpk5XbVVSBKz4LAi9fjcAWkzuChCDuE4s
TWRP Lewa Recovery - 1.0
https://mega.co.nz/#!oVoS2ABB!TGXNFF0dL6V5J2enBS0juGYWXKRhwOpPddJV0GC_q_g
TWRP Lewa Recovery - 2.3
https://mega.co.nz/#!9d5FxIpT!XqBoqyiDJg914Tfajwp4i3xioMAjo9ZVI2zf5LqjRbc
Stock Recovery
https://mega.co.nz/#!dAZSDCba!CP49czZxvdpbKBG3gWzPMzSv3bxdFRi8AQKvEI2-5z4
Enjoy
rnovino
Junior Member
Join Date: Nov 2012
Posts: 16
cherry mobile titan CWR,TWRP and Stock Recovery
High Guys here is the different recoveries from our rebranded Karbon a30 to Cherry Mobile Titan TV
Clockworkmod - CWMR - 6.0.1.5
https://mega.co.nz/#!YUgEkSKC!JjokMR...cAWkzuChCDuE4s
TWRP Lewa Recovery - 1.0
https://mega.co.nz/#!oVoS2ABB!TGXNFF...OpPddJV0GC_q_g
TWRP Lewa Recovery - 2.3
https://mega.co.nz/#!9d5FxIpT!XqBoqy...9ZVI2zf5LqjRbc
Stock Recovery
https://mega.co.nz/#!dAZSDCba!CP49cz...Ri8AQKvEI2-5z4
Enjoy
Click to expand...
Click to collapse
These are .img files and need to be flashed using Mobile Uncle from Play Store
Once you have downloaded any of the recovery file you need to download the MOBILE UNCLE MTK TOOL on google play store for you to port the recovery update on your 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"
}
and then copy the RECOVERY.IMG from the recovery image you have downloaded either the CWMR and TWRP on the root of your sd card or internal storage
now open the MOBILE UNCLE MTK TOOL and click the RECOVERY UPDATE and you will see the RECOVERY.IMG at the top that you have copy on the root of your storage.
NOTE: be sure to check the spelling that it is spelled as “recovery.img” without the quotes or else it will not be detected on the folder
now just click ok then ok again and it will reboot to recovery, after rebooting it will now be on the recovery mode that you have chosen , in this example i used the TWRP v2.3.2.3.
and now you can select backup and check all the things you want to backup and swipe the handle on the bottom part and wait for it to finish
to check if you have backup successfully you can click the restore mode and you will see the backup you have made, and from there you can choose on what backup you want to restore.
ALL THE BEST GUYS!!!!!
SOURCE:http://pinoyscreencast.net/cherry-mobile-titan-tv-and-karbon-a30-stock-cwmr-v6-0-1-5-and-twrp-v2-3-2-3-recovery/
If You find my post helpful, Hit Thanks!
Thank you. Flashed CWMR successfully on Karbonn A30
ApplePriest said:
Thank you. Flashed CWMR successfully on Karbonn A30
Click to expand...
Click to collapse
AWESOME!!!!!
Twrp (karbonn a30) link is asking for decryption password, please share the same
Sent from my Micromax A110 using Tapatalk 4 Beta
Hoe to download recovery. Img from above link
Sent from my Karbonn A30 using XDA Premium 4 mobile app
Hey....bought a refurbished bootloader unlocked Ultra 6806 on latest software, ...and my old tried and tru efforts at getting TWRP fail apparently because I lack the recovery partition.
Can anyone direct me to a kernel/.img link that would do that for me.
Am I asking the right question?!
Thanks
I think you mean c6806
If bootloader is unlocked. Cool
Just flash kitkat ftf with flashtool. And do dual recovery.
Or just try philz recovery try flashing it with rashr
Flash 4.4 correct? Still couldn't install TWRP on rooted kitkat. 'lack of recovery partition'.
Trying to implement this (http://forum.xda-developers.com/xpe...de-root-z-ultra-stock-lollipop-5-0-2-t3094094).
Kingo fails every time on Lollipop).
RealityFails said:
I think you mean c6806
If bootloader is unlocked. Cool
Just flash kitkat ftf with flashtool. And do dual recovery.
Or just try philz recovery try flashing it with rashr
Click to expand...
Click to collapse
Which one is the best to install for sm-910t?
rockky said:
Flash 4.4 correct? Still couldn't install TWRP on rooted kitkat. 'lack of recovery partition'.
Trying to implement this (http://forum.xda-developers.com/xpe...de-root-z-ultra-stock-lollipop-5-0-2-t3094094).
Kingo fails every time on Lollipop).
Click to expand...
Click to collapse
As stated if your bootloader is already unlocked. Use flash tool and flash a kitkat ftf. Once on kitkat root it, and install nuts dual recovery.
Or you could just root and flash .IMG with recovery which will do all the work.
---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------
When on kitkat and rooted use rashr and flash this
https://drive.google.com/file/d/0BxU1aYWczltnYV9FSUpoT1lwMkU/view?usp=docslist_api
Its 100% safe but I'm not responsible if you mess up.
RealityFails said:
As stated if your bootloader is already unlocked. Use flash tool and flash a kitkat ftf. Once on kitkat root it, and install nuts dual recovery.
Or you could just root and flash .IMG with recovery which will do all the work.
---------- Post added at 07:06 PM ---------- Previous post was at 07:02 PM ----------
When on kitkat and rooted use rashr and flash this
https://drive.google.com/file/d/0BxU1aYWczltnYV9FSUpoT1lwMkU/view?usp=docslist_api
Its 100% safe but I'm not responsible if you mess up.
Click to expand...
Click to collapse
Why are you sending him back to KK? If his bootloader is unlocked, he can just go ahead and flash TWRP/CWM/Philz through fastboot/flashtool/QuickIMG/installer. That's the whole point of having an unlocked bootloader.
If you are on the latest software, then the recovery partition should already be there.
The problem that you are probably experiencing is in finding a recovery that is compatible with the partition, the TWRP images over at TWRP.ME are not.
Saatvik Shukla has posted a build of TWRP 2.8.7.0 which can be installed into the partition using the FASTBOOT FLASH RECOVERY [filename] method and can be found at the link below.
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082
Thanks all
Gonna get at it
Thanks...all went well.root 5.1.1 plus TWRP.
only problem is no write privileges on files.
QUOTE=pTeronaut;63520115]If you are on the latest software, then the recovery partition should already be there.
The problem that you are probably experiencing is in finding a recovery that is compatible with the partition, the TWRP images over at TWRP.ME are not.
Saatvik Shukla has posted a build of TWRP 2.8.7.0 which can be installed into the partition using the FASTBOOT FLASH RECOVERY [filename] method and can be found at the link below.
http://forum.xda-developers.com/xperia-z-ultra/development/twrp-togari-t3197082[/QUOTE]
Re-flash supersu.zip
can any one help i am still unable to get loaded the recovery on my xperia , i tried almost every method can any one please tell me step by step to install recovery , i have tried ,
1, dual recovery batch file ( i got error adb server out dated)
2, rashr is flashing but when i rebooted to recovery nothing... just phone restart normally ... ( i used the above file .img to flash via rashr)
3, when tried twrp manager ( its giving me error that no recovery partition )
4, tried through via adb ( the adb giving error that server is out dated)
i am on ****ing windows 10 where cannot access the fast boot .....
can any one please help me , my phone is on FTF .108 --> properly Rooted .. --> fully stock rooted ( kitkat ) unlocked boot loader....
what am i doing wrong or i am out of luck.... ( i have rooted my htc magic perfected spl via gold card method whcih was crazingly hard back in 2009 but xperia z is beating the **** out of me in 2016 )
isnt there any way for me to install recovery so that i an flash rooted marshmallow on my xperia z ultra...
pintspin said:
can any one help i am still unable to get loaded the recovery on my xperia , i tried almost every method can any one please tell me step by step to install recovery , i have tried ,
1, dual recovery batch file ( i got error adb server out dated)
2, rashr is flashing but when i rebooted to recovery nothing... just phone restart normally ... ( i used the above file .img to flash via rashr)
3, when tried twrp manager ( its giving me error that no recovery partition )
4, tried through via adb ( the adb giving error that server is out dated)
i am on ****ing windows 10 where cannot access the fast boot .....
can any one please help me , my phone is on FTF .108 --> properly Rooted .. --> fully stock rooted ( kitkat ) unlocked boot loader....
what am i doing wrong or i am out of luck.... ( i have rooted my htc magic perfected spl via gold card method whcih was crazingly hard back in 2009 but xperia z is beating the **** out of me in 2016 )
isnt there any way for me to install recovery so that i an flash rooted marshmallow on my xperia z ultra...
Click to expand...
Click to collapse
Type these commands in cmd. Run CMD as Administrator:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Then "Disable driver signature enforcement" on boot:
Press windows key + R
Type: shutdown -o -r -t 0
Press enter
You will now be here:
{
"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"
}
Select "Troubleshoot"
Select “Advanced options” and “Startup Settings”.
Click "Restart":
When computer reboots and you see this screen: Press F7
Install systemwide ADB
http://forum.xda-developers.com/showthread.php?p=48915118
Direct link: www14.zippyshare.com/d/ufYG71o0/4863743/adb-setup-1.4.3.exe
Download Flashtool driver pack:
http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS41LTIwMTQwMzE4
Run the file
Scroll down the list until you se Xperia Z ultra C68xx whatever your model is.
Install the drivers
Done
On your desktop: Hold "shift" and right click. Choose Open Command Window here
In the CMD type: Fastboot.
IF you see a list of text describing what fastboot is. You are fine.
Boot the phone to fastboot: Power off, Hold Volume up and plugin the usb cable and blue LED should be constant on.
I only needed to turn testsigning off, then reboot on my W10 pro computer. YMMV.
pTeronaut said:
I only needed to turn testsigning off, then reboot on my W10 pro computer. YMMV.
Click to expand...
Click to collapse
Rebooting again resets testsigning to on. The driver will continue to work as long as the system don't touch the driver.
If windows trying to update the drivers from microsoft driver catalogue. It might happen that this driver will be forced off because the lack of a signature.
A trigger for this would be if you plugin in a new hardware such as a brand new usb stick or hard disk or whatever you might want to use.
SÜPERUSER said:
Type these commands in cmd. Run CMD as Administrator:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Then "Disable driver signature enforcement" on boot:
Press windows key + R
Type: shutdown -o -r -t 0
Press enter
You will now be here:
Select "Troubleshoot"
Select “Advanced options” and “Startup Settings”.
Click "Restart":
When computer reboots and you see this screen: Press F7
Install systemwide ADB
http://forum.xda-developers.com/showthread.php?p=48915118
Direct link: www14.zippyshare.com/d/ufYG71o0/4863743/adb-setup-1.4.3.exe
Download Flashtool driver pack:
http://doomlord.xperia-files.com/download.php?dlid=Rmxhc2h0b29sLWRyaXZlcnMtMS41LTIwMTQwMzE4
Run the file
Scroll down the list until you se Xperia Z ultra C68xx whatever your model is.
Install the drivers
Done
On your desktop: Hold "shift" and right click. Choose Open Command Window here
In the CMD type: Fastboot.
IF you see a list of text describing what fastboot is. You are fine.
Boot the phone to fastboot: Power off, Hold Volume up and plugin the usb cable and blue LED should be constant on.
Click to expand...
Click to collapse
thank you so much SU, finally i got the access of fastboot to my xzu on win 10 i am back in business ... and finally got the recovery loaded as well...
amazing guide...!! you are like AMON_RA ... to me... .
regadrs
pint
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"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"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone. Downgrade from OOS 12 works now.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://sourceforge.net/projects/op8t-9r-fastboot-roms/files/OnePlus_9R/
Nice
Hi OP, I changed the tag from Development to How To Guide, because we only use Development for original work like you build the ROM from kernel/device tree etc... Thanks.
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
* !!! IMPORTANT !!!
Before flashing make sure you know about which type of ram your device supports i.e LPDDR4X/LPDDR5 as flashing wrong xbl config will hardbrick your device.
Here’s how you can check what type of ram your device has:-
Now, as to exactly find out which variant that you have, turn on USB debugging and enter this command:-
Code:
adb shell getprop ro.boot.ddr_type
If the value is 0, that means you have LPDDR4X. If the value is 1, that means you have LPDDR5.
This command is more reliable than the Devcheck and other apps.
DOWNLOAD:- https://drive.google.com/file/d/1LTknGhfR2JTtXhN0rGMCS4OwmUdqt3PF/view?usp=sharing
Click to expand...
Click to collapse
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
theincognito said:
You will most likely need to visit the service center and get your phone repaired.
Are you sure that your device had DDR5?
Click to expand...
Click to collapse
Actually，I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
zwk22160 said:
Actually，I checked my DDR type via devcheck instead of the adb command. Seems that the dev check is no so reliable. Anyway, I have already sent my phone to the service center to repair, I have a OnePlus 7 pro as the backup phone, so it doesn't affect me too much.
Click to expand...
Click to collapse
Yeah. The apps aren't reliable at this. Always use the adb command. 100% reliable. And since it's harbricked for you, I am pretty sure that you have a DDR4X variant.
zwk22160 said:
Errr sorry I can make sure that I have the DDR5,but it seems that when I complete the flash using the DDR5 profile config,my phone hard bricked, so how can I get it back? Now it can not even enter 9008 mode
Click to expand...
Click to collapse
It’s clearly written to not trust devcheck and other apps that prop is the only trusted source of finding which type of ram ur device has. It has also come to my attention that DDR5 devices can boot to EDL if we flash wrong xbl configs on them but the DDR4 ones can’t boot to EDL if wrong xbl config is flashed. (Means ddr4 users would have to get phone repaired by service center if wrong xbl config is flashed on their device)
PetiaWarzel said:
Created a Tutorial based on your firmware/instructions. Hoping you will like it.
https://androidmtk.com/install-firmware-oneplus-9r
Click to expand...
Click to collapse
Appreciate it a lot! Thanks
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
hmm for me the
Code:
adb shell getprop ro.boot.ddr_type
returns empty.
I guess that infers I'm using LPDDR4X?
Edit:
Code:
adb shell getprop
This would return a complete list of all the properties you can query with this command. For me, this list doesn't seem to have any field called "ro.boot.ddr_type"
{
"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"
}
I'm using the Chinese variant of OP9R, not so sure if it matters.
Also, DevCheck would not report RAM variants under the hardware tab as well.
Leohearts said:
I faced the same problem
Service center says they can't flash it back
They ended up replaced a new motherboard for me
Click to expand...
Click to collapse
I checked it again and
OnePlus9R:/ $ getprop | grep ddr
[ro.boot.ddr_type]: [1]
[vendor.boot.ddr_type]: [1]
OnePlus9R:/ $
I'm sure flashed the ddr5 version, but it hard-bricked and even cant boot into 9008
*UPDATED*
* Added OxygenOS 11.2.6.6 Fastboot ROM
* Removed xbl configs so that now no more hardbricks happen
* Reduced partition sizes for inactive slot so that ROMs can be flashed properly through fastboot
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Mkkt Bkkt said:
will this work on Chinese variant 12gb/256gb ddr4 ? LE2100 bl is already unlocked
Click to expand...
Click to collapse
If ur using oxygenos then yes
HELLBOY017 said:
If ur using oxygenos then yes
Click to expand...
Click to collapse
yes , for some reason it came with oxygenos preinstalled
HELLBOY017 said:
Ever wanted to unbrick your device or switch to stock ROM from a custom ROM without using MSM Unbrick tool and keeping your bootloader unlocked after that well fastboot ROMs are here to help you . I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
1). Download the zip
2). Unpack the zip in a folder
3). Reboot the OnePlus 9R in fastboot-bootloader mode (Power and volume + and volume-)
4). Connect the OnePlus 9R to PC
5). Run flash-all.bat flasher
6). Wait until the process end
7). Voila! your OnePlus 9R will now boot into OxygenOS
POINTS TO REMEMBER
* "Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
* These ROMs can't be used to update or downgrade your phone but just to restore your phone.
* This can’t be used to switch from ColorOS to OxygenOS you can use MSM unbrick tool to do that.
DOWNLOAD:-
https://mega.nz/folder/ePIETB4D#sU8cJ54l4UI7JCXGwc7Nog
Click to expand...
Click to collapse
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
logeshwywan said:
Download link in Mega can't download with standard account, requires premium. could you please upload in other hosting website if possible? Thanks!
Click to expand...
Click to collapse
Will do
Link updated.
*Apologies for updating it late as I had fever so didn't have time for mirror it somewhere else
Hi Guys!
I bought Lenovo Tab m8 TB-8505X a few months ago and i see it's lagging and still on Android 10. I want to install custom rom but there is no TWRP for this device. Can anybody develop TWRP or help me finding TWRP. Thanks in advance
https://forum.xda-developers.com/t/lenovo-tab-m8.4049539/post-84209395
https://forum.xda-developers.com/t/lenovo-tab-m8.4049539/post-84320503
aIecxs said:
https://forum.xda-developers.com/t/lenovo-tab-m8.4049539/post-84209395
https://forum.xda-developers.com/t/lenovo-tab-m8.4049539/post-84320503
Click to expand...
Click to collapse
It's for TB-8505F (WIFI ONLY), mine is TB-8505X (WIFI+LTE). Will it still work?
you tell us
I am looking for a twrp recovery for the Lenovo tab m8 tb-8506f. CANT FIND ANY
aIecxs said:
you tell us
Click to expand...
Click to collapse
Flashed successfully but there is a problem. I don't see SYSTEM under wipe and can't install any image properly. Is there any fix?
copy-paste the adb output with mouse + enter key, put in [code]tags[/code] here.
while in TWRP
Code:
adb shell
# cat /etc/fstab
# ls -l $(find /dev/block -name by-name)/*
# cat /proc/mounts
_allaie_ said:
Flashed successfully but there is a problem. I don't see SYSTEM under wipe and can't install any image properly. Is there any fix?
Click to expand...
Click to collapse
Hello, I also have Lenovo Tab M8 8505X and i also want to install twrp in it but i need confirm a few things first
As you said, u have successfully flashed the twrp please answer me a few questions;
Have you also flashed VM.beta and Preserve force encryption in it? or just twrp?
What stock rom was your tablet running before you installed twrp in it?
Also please tell the android version it was runing
and the kernel version too
long story short,
please send the screen shot of the 'About Tablet' section of your tablet.
make sure the screenshot is of full that it also sover the hardware specs because there are so many varients and generation of Lenovo Tab M8.
So i just want to match wether my Tablet is similar to yours before trying to flash.
aIecxs said:
copy-paste the adb output with mouse + enter key, put in [code]tags[/code] here.
while in TWRP
Code:
adb shell
# cat /etc/fstab
# ls -l $(find /dev/block -name by-name)/*
# cat /proc/mounts
Click to expand...
Click to collapse
Hello, i did not understood what you meant by 'put in [code]tags[/code]'
pls explain me
Code:
[C0DE]
put your terminal output here
[/C0DE]
{
"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"
}
aIecxs said:
Code:
[C0DE]
put your terminal output here
[/C0DE]
View attachment 5826927
Click to expand...
Click to collapse
Code:
GOT IT, THANKS
Invinciblity said:
Hello, I also have Lenovo Tab M8 8505X and i also want to install twrp in it but i need confirm a few things first
As you said, u have successfully flashed the twrp please answer me a few questions;
Have you also flashed VM.beta and Preserve force encryption in it? or just twrp?
What stock rom was your tablet running before you installed twrp in it?
Also please tell the android version it was runing
and the kernel version too
long story short,
please send the screen shot of the 'About Tablet' section of your tablet.
make sure the screenshot is of full that it also sover the hardware specs because there are so many varients and generation of Lenovo Tab M8.
So i just want to match wether my Tablet is similar to yours before trying to flash.
Click to expand...
Click to collapse
I flashed twrp first, then the vbmeta via fastboot (not with twrp) and then reboot to recovery by holding power, vol+ and vol-, then releasing power key. That's how I booted successfully into that (TWRP).
And I don't require twrp now, I just reset my tab with smart and rescue assistant. I wanted to flash every treble Android 13 GSI.
My tab is on latest Android 10
Click to expand...
Click to collapse
a
_allaie_ said:
I flashed twrp first, then the vbmeta via fastboot (not with twrp) and then reboot to recovery by holding power, vol+ and vol-, then releasing power key. That's how I booted successfully into that (TWRP).
And I don't require twrp now, I just reset my tab with smart and rescue assistant. I wanted to flash every treble Android 13 GSI?
Click to expand...
Click to collapse
_allaie_ said:
I flashed twrp first, then the vbmeta via fastboot (not with twrp) and then reboot to recovery by holding power, vol+ and vol-, then releasing power key. That's how I booted successfully into that (TWRP).
And I don't require twrp now, I just reset my tab with smart and rescue assistant. I wanted to flash every treble Android 13 GSI.
Click to expand...
Click to collapse
But please send your device's About section page's screenshot
so that i can make sure it will work on my device too or not
Sure if you want to.
Here you go
If it still doesn't help, i would suggest resetting device with LENOVO SMART AND RESCUE ASSISTANT but keep in mind it will delete all your data, so proceed after doing backup.
Invinciblity said:
But please send your device's About section page's screenshot
so that i can make sure it will work on my device too or not
Click to expand...
Click to collapse
_allaie_ said:
If it still doesn't help, i would suggest resetting device with LENOVO SMART AND RESCUE ASSISTANT but keep in mind it will delete all your data, so proceed after doing backup.
Click to expand...
Click to collapse
Thanks a lot for this help
I have matched with mine
and found that only the stock rom is diffrent
your's is the updated one
but i wasn't able to update bcz i have unlocked my device
Else everything is same-to-same
So i'm gonna flash it
Again thanks a lot
@_allaie_ System is working now in TWRP? or do you still want me to fix? waiting for the partitions info...
aIecxs said:
@_allaie_ System is working now in TWRP? or do you still want me to fix? waiting for the partitions info...
Click to expand...
Click to collapse
Thanks for your help. But I've replaced twrp with stock one. As I said, i just wanted to flash GSI but now with fastboot it works fine.
Thanks Again
Invinciblity said:
Thanks a lot for this help
I have matched with mine
and found that only the stock rom is diffrent
your's is the updated one
but i wasn't able to update bcz i have unlocked my device
Else everything is same-to-same
So i'm gonna flash it
Again thanks a lot
Click to expand...
Click to collapse
You need Smart and Rescue Assistant on PC and it can update your tab even with unlocked bootloader. After successful rescue, bootloader will get locked again. Hope it helps
_allaie_ said:
You need Smart and Rescue Assistant on PC and it can update your tab even with unlocked bootloader. After successful rescue, bootloader will get locked again. Hope it helps
Click to expand...
Click to collapse
Thanks for informing about this tool, it made things easier!