Related
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
simms22 said:
no working recovery with a locked bootloader, sorry. if the bootloader is locked, you cant flash anything. its locked. to flash things, you need an unlocked bootloader. its like locking a door, but expecting it to open magically when you walk up to it.
Click to expand...
Click to collapse
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
briman0094 said:
I forgot to mention that I re-unlocked the bootloader. I can also boot the OS so I'd be able to enable OEM unlock again if needed.
Click to expand...
Click to collapse
important thing to forget to mention
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
simms22 said:
important thing to forget to mention
Click to expand...
Click to collapse
I guess I assumed that when I said "continues to boot normally" people would assume I could re-enable "OEM Unlock" if needed
scryan said:
So what happened when you reflashed the lasted version of twrp for your device after verifying the downloads md5?
Click to expand...
Click to collapse
All the console output indicates success, and it boots to the initial "TEAMWIN" logo for a few seconds and reboots.
No Recovery Similiar issue
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it. Nobody mentioned anything about it completely wiping the phone, including the internal SD card. I set most of the stuff back up again but realized that it was suffering from the bug on the old radio version that causes it to lose LTE randomly.
I went and rebooted into TWRP to try and flash it, and TWRP showed a completely empty sdcard partition and said it could not mount '/data'. I enabled "require pattern to boot," thinking it may not have known to decrypt the partition without that, and now I can't get into TWRP at all. I tried disabling the "require pattern to boot" option again but no luck. It shows the "Google" logo for about 5 seconds, then the blue "TEAMWIN" logo for about 3 seconds, then reboots to the "Google" logo and proceeds to boot normally. I should note that I have CM12.1 installed, and the latest TWRP. I've tried reflashing TWRP and that didn't help; I also did "fastboot format cache" and then "fastboot flash cache cache.img" using the stock factory cache.img. I got the radio flashed using fastboot, but I'd really like to have a working recovery.
Click to expand...
Click to collapse
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
ray6279 said:
Briman, I seem to have a similar issue on my and wife's Google Nexus 6s. I unlocked and rooted using Wug Tool Kit I used in years past with seamless success. To confirm root CM 12.1 I can get into bootloader, Teamwin. From there I am to flash the Superuser, Busybox and TWRP zips under SD\iReady to Flash\Rootfiles..... Only I am not given an option on the menu? I am struggling with using the command prompt and proper paths from SDK Tools so that is not an option at this moment. I see a File Manager that shows this path but am hesitant to use it as I have READ this could cause damage ( brick) to the system. Watching your thread for answers or possibilities. I know the senior members as Simm22 dislike tool kits and so do I. I am simply trying to grow and learn.
Click to expand...
Click to collapse
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
briman0094 said:
I was trying to fix an issue with my phone the other day, and saw that re-locking the bootloader might fix it.
Click to expand...
Click to collapse
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
nhizzat said:
Saw that bit of advice where? I can't think of a single thing re-locking the bootloader would fix.
Click to expand...
Click to collapse
A screenshot of an e-mail from a Google employee regarding Android Pay and SafetyNet.
50% JOY No Fastboot?
simms22 said:
na, toolkits work fine. sure, they occasionally do mess up, but its not very ofver. i generally like ut when noobies do the rooting the correct way the first time, that way they can learn some basic things about how everything works. then, they can yse toolkits all they
btw, teamwin isnt your bootloader, its your recovery. team win = twrp. now all you need to do is download the latest supersu and flash it via your recovery, and the you can install a busybox app from tbe play store, and use it to unstall .
Click to expand...
Click to collapse
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
ray6279 said:
I followed your directions while working on my Nexus6 phone. Was able to access bootloader then install iReady files. Worked perfectly and phone loaded SUPERUSER, BUSYBOX & PERM RECOVERY. Not so much on wife's Nexus 6. I get thru UNLOCK & ROOT w/custom recovery on the Wug Fresh Tool Kit. At RECOVERY menu pulls up SD - Up one level. No option is allowed to continue on and load the three mentioned packages. I then able to reboot to system. Does it appear I am bootloading but not fastbooting? Will try and insert images.
Click to expand...
Click to collapse
one question.. what is perm recovery?? the only recovery that works on the n6 is twrp recovery.
and when you are in her recovery, is it showing you the right location where the files should be? if nit, you csn change the lication.
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
ray6279 said:
Simm & Others. Thank you for your good words and suggestions. It would be easier for me to list what I did not attempt rather than what I did try. . I tried nearly most functions in the Wug Fresh ( by Harold) v2.0.5 after failing to find the correct command prompt to use ADB. What happened is an odditity. Mind you, I've been on these two Nexus 6 phones for 4-6hours a day for about ten days! Day later, Happened to be waiting for wife in parking lot and picked up phone and pressed SuperUser. Viola! It went into TWRP and gave me an RECOVERY option. On impluse, I flashed TWRP and Superuser zips. It took and processed. however, the best part of this is the hands on learning experience of booting, flashing, wiping, language, terms, SDK, Android and more. Once I figure out my path problem on my windows based PC to loading ABD commands I am continuing my self study of Android and App development. How do I get the packages out of the SDK Tool Kit to folders in PC? Thanks all.
Click to expand...
Click to collapse
your welcome, but you are still off in one bit of fact. you use fastboot, not adb, to flash a recovery(and system.img)
edit.. you can use apps like flashify to flash recovery, if you have root already.
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
ray6279 said:
So BOOTLOADER is the USB connection between the device and PC. FASTBOOT is the process via we make changes in the device via the PC. ADB is the device language via which we communicate. So do I still need to flash a system recovery image? Flashify App? I already went thru install>iready to flash> superuser (version)>busybox>flash>reboot>system. I'm going cross eyed from reading. The wiping part worries me as I fear formatting or deleting essential data.
Click to expand...
Click to collapse
ok, when wiping, dont do the first option wipe, itll wipe your whole phone clean. you need to select the advanced options and pick what you want wiped. fastboot is the way to unlock your bootloader, or flash a recovery. also, you use it to flash a system.img or any part of it.
adb is a general linux that can be used with android, anywhere but in the bootloader(only fastboot in the bootloader).
bootloader isnt the usb connection between the device and the pc, its part of the phone that boots it and decides if the rom is safe to run. thats why we unlock it. so we can flash roms eithout googles key.
fastboot is the tool that you use to do whatever needs to be fone in the bootloader, adb everywhere else.
a recovery you need if you want to flash custom roms, kernels, supersu, or other mods. you can also wipe different partitions with the recovery, or make a "nandroid' backup. thats a bavkup of everything. its like a complete snapshot of everything during the time you made it. if you ever mess up your phone, you can restore it, and you will be at the exact same place when you made the backup.
anything else?
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Bricked is right !
quyvinh said:
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
My recovery is still untouched, so does bootloader. That is why I said mine os softbrick. It means if I have the stock ROM, then I am ready to go back alive again. I cannot imagine how could you erase the stock recovery? Unless you failed the custom recovery, then it probadly hard bricked. If I can find how to fix it then I will post here. I am currently working around with MTK Droid tool and SP Flash tool, but they are working partially only. Cannot write out the scatter file. Man, this phone is tough.
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(merge 3 files system.ext4.winxxx into 1 with extension .win)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
grampyog said:
I am that guy. Got the phone from Best Buy. Did the OEM unlock and USB debugging from developer options. Next I booted into Fastboot and issued the "fastboot oem unlock". It proceeded to erase the phone including the boot image. Now there doesn't seem to be anyway to get back to the bootloader to flash a recovery image. Strangely there doesn't seem to be anyway back into the bootloader if you can't boot into recovery. I have tried every key combination that I can think of but it seems that without a recovery you are not getting back into the bootloader.
Any suggestions would certainly be appreciated. It's 250 miles round trip to BB for me. I live fairly remote in Idaho.
Thanks
Click to expand...
Click to collapse
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
min1968 said:
I merged two win.000 and win.001 files into one .win, now I got 2 final files: boot.emmc.win and system.ext4.win,
Using tWRP recovery to restore, but cannot boot to android, always go to recovery...
Click to expand...
Click to collapse
Did you do this?
emowing said:
13. select wipe, format data, type in yes (this fixes the boot looping issue -- credit @acotto)
Click to expand...
Click to collapse
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
This is because first these phones are MTK67xx phone, and 2nd they are running on new android 5.1. So the way they are rooted different with the old ways.
grampyog said:
I have at least 15 devices rooted. Always you could fastboot. This is a first for me.
Click to expand...
Click to collapse
eksasol said:
It would be really nice if someone can upload the back up of the logo partition. I have the Gionee logo on this, not a big deal.
Click to expand...
Click to collapse
Here you go. this is a twrp backup.
quyvinh said:
[Updated] please go to this thread for SAFETY root with CWM recovery
http://forum.xda-developers.com/vivo-xl/development/root-confirmed-blu-vivo-xl-unlock-t3314010
======================================================================================
Hi all,
When you are reading my thread, I bet you want to root your new BLU Vivo XL. However, please be careful what you are going to do. I assume you know how to unlock bootloader for now.
Not like its brother, BLU Life one X 2016, the processing of unlock bootloader through adb will cause your phone become soft brick (bootloop). Instead of colorful logo. you are now seeing white "Android" on the black screen, and it keep going and going ...
I am not an expert, but I have been playing with a lot of phones, including recently rooted/unlock_bootloader Life X 16 which is very good phone. For right now, there is no safeway to unlock bootloader and root. All one click root are not working.
I know most of you get this phone from Bestbuy, so you sill have time to return or exchange.
*** If you brick your phone, do not too worry. Assume you have USB debug checked and you unlocked bootloader ( that is why you brick it), go ahead and flash TWRP in fastboot, then download firmware and restore it in TWRP
TWRP file (thanks jemmini): http://forum.xda-developers.com/vivo-xl/development/recovery-t3311601
ROM (thanks John Hale from BLU): https://drive.google.com/folderview?id=0B0g-ojj_rL70czVOZERhY3AxeHc#
(DO NOT merge these files, leave them alone like it is.)
Last word: I will keep my eye on this phone. Please share all of your experiences so others can learn. Thanks.
Click to expand...
Click to collapse
how do i restore the rom im kinda a newb i rooted my phone than restored and now im stuck a startup and it wont go it. just gets stuck on "checking connection" i have the vivo XL and i am in need of help so how do i get this rom back to original because i dont know what to do:fingers-crossed:
Bam-Great
Followed all of the instructions and many tries later I have a phone that boots and works just fine. What I'm not finding is an image of the original rom anywhere. Pretty sure I've looked closely but if anyone has a link take me to your leader. My thanks to the awesome person that put this tutorial together. If anyone has bricked their phone trying to root follow these instructions.
Note: The stock MS drivers did not work make sure to load the VCOM drivers.
Many thanks again,
Ken
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
xdadev_user11 said:
Download the Gionee S Plus folder: https://docs.google.com/uc?id=0B31-_QP1UrPsOGpIT0pDQUlqd0k
download the vcom drivers and follow the guide from this link: https://forum.hovatek.com/thread-440.html
use sp flash tool by following this guide: https://forum.hovatek.com/thread-159-post-228.html#pid228
install recovery and root by following this guide: http://forum.xda-developers.com/vivo-xl/how-to/root-tutorial-t3313120
restore to the Blu Vivo XL backup stock rom with TWRP: https://drive.google.com/folder/d/0B0g-ojj_rL70czVOZERhY3AxeHc/edit
Did you do this?
Click to expand...
Click to collapse
Any ideas if this restore method with Bypass the Factory reset protection?
Just as a quick update. Simply formatting with the flash tool. And installing the gionee firmware was enough to bypass the Google factory reset prevention. Hope this helps anyone else that forget there Gmail address they used.
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
cas8180 said:
Whats the method/tehnique for doing the restore of the TWRP backup of the factory OS? I tried throwing the extracted folder on there and zipping it up and throwing it onto the phones internal memory and TWRP didnt seem to recognize wither when I went into the restore menu. What am I missing?
Click to expand...
Click to collapse
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
xdadev_user11 said:
Mine is setup as "/sdcard0/TWRP/BACKUPS/BLU_VIVO_XL/2016-02-12--04-36-53_S_plus". I put the extracted files in the "2016-02-12--04-36-53_S_plus" folder.
Click to expand...
Click to collapse
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
cas8180 said:
So that worked for the restore. I was able to get back into what appears to be the factory installed ROM. However I lost all of my SIM card functionality now my phone will not recognize my SIM no matter which slot I stick it into. I tried doing a complete wipe and restoring again but nothing appears to be working. I am thinking I am going to have to go back to the GIONEE based firmware.....
Click to expand...
Click to collapse
That's strange. grampyog had the same problem. But the backup rom worked for me and eksasol. Very strange.
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
xdadev_user11 said:
cas8180, I uploaded a twrp backup containing nvram and secro. Can you download it, try it, and see if it works?
Click to expand...
Click to collapse
That did it my good man! I have a complete bundle now with boot logo and the nvram secro files you included I feel compelled to mirror so let me work on that. Thanks a bunch thanks to you I am back in business!
Here is the link for the complete TWRP backup that should be able to restore any device back to stock. https://www.dropbox.com/s/x4lgfv27jtgirkh/Blu_VivoXL_backup-2016-03-05.zip?dl=0
Hello.
Last night I decided I wanted to root my LG G4 running marshmallow (so we're talking about H81120i). I was able to unlock my bootloader, restart the phone and use it, etc. I was able to boot into TWRP (but not anymore for some reason) and restart the phone and use it as well, however, when I installed SuperSu using TWRP and cleared my cache my phone gets stuck at the second white t mobile screen.
I am able to get into download mode, factory reset mode, etc, just not access android. When I plug my phone into my the drivers suggest that it is a COM6 port. The LG support software recognizes my phone while in download mode though. What are my options here? Will it be safe to flash H81110n using the lg flash tool 2014 version or will that break the phone more? I thought I'd ask here first because I've always found any and all information I need for this sort of thing here.
If you need any more information to safely answer this question I will provide anything you need.
Thanks.
toxicturn said:
Hello.
Last night I decided I wanted to root my LG G4 running marshmallow (so we're talking about H81120i). I was able to unlock my bootloader, restart the phone and use it, etc. I was able to boot into TWRP (but not anymore for some reason) and restart the phone and use it as well, however, when I installed SuperSu using TWRP and cleared my cache my phone gets stuck at the second white t mobile screen.
I am able to get into download mode, factory reset mode, etc, just not access android. When I plug my phone into my the drivers suggest that it is a COM6 port. The LG support software recognizes my phone while in download mode though. What are my options here? Will it be safe to flash H81110n using the lg flash tool 2014 version or will that break the phone more? I thought I'd ask here first because I've always found any and all information I need for this sort of thing here.
If you need any more information to safely answer this question I will provide anything you need.
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
Make sure you carefully follow the guide.
Did you perhaps only boot into twrp but not install it?
I would try to flash the kdz again through either LGBridge or LGUp again as you still have download mode.
Hi Guys,
Figured I will ask the experts here. My mate dropped his S5 Mini a few days ago, since then the touch screen does not work so he can't put in a pattern to unlock the phone. New screen prices in South Africa is ridiculous, especially for a 3 year old phone. I want to help him get his photo's off the phone but the we can't do the pattern unlock and S5 mini does not support OTG cables, so we can't use a PC mouse etc. Also can't enable USB debugging obviously.
I'm thinking of trying via the Recovery loader or whatever you all it. The stock recovery does not seem to allow mounting of the various partitions via ADB from what I have read, so will I need to flash a custom Recovery like TWRP 3.0.0? Also see you need to have an unlocked bootloader in order to flash a custom recovery. I presume rooting the device with CF-Auto-Root will unlock the boot loader? I can then load the custom recovery after doing the root?
Rough process would be.
1. Boot Download mode -> Flash CF-auto-root -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
2. Boot Download mode -> Flash custom recovery -> Reboot | From what I have read this is safe and does not trash any data as its a separate partition?
3. Boot Recovery Mode
Any help would be appreciated as I really dont want to trash his data.
Cheers
Jacques
Hello,
I am not going to lie to you and tell you my goal.
My father committed suicide and the police "succeeded" in taking my father's data but he refuses to tell us its content, not even to my mother. I am of age and therefore "old enough" to understand the risks etc.. But I would like to have answers and be able to access the memory of my father's phone or bypass the android code.
I have started to learn how an Android works (ADB, ROM, Nethunter with HID for brute force) I am motivated by my approach but I don't have enough knowledge to reach my goal and I need you. Could you help me?
It is a samsung Galaxy A71 without active ADB.
Thanks !
Im sorry to that you can install twrp and acces the devices memory. After you install twrp enter twrp mode press mount and mount data and cache after that connect the phone to your pc and you should see the phones internal storage if this dosent work you can use twrp adb and use adb on your pc and pull all the phone contents using "adb pull storage/emulated/0" please be carefull if you dont install twrp properly you could lose all the phones contents. If i helped you make sure to leave a like
Thank you for your answer! it makes me believe a little more in the chances of success. I will try to install twrp on a samsung A40 which is currently used as a test. But I can't do it. Do you have any links or tutorials to help me understand how it works or how to install twrp without ADB or oem unlock ?
Many thanks
mypomme said:
Thank you for your answer! it makes me believe a little more in the chances of success. I will try to install twrp on a samsung A40 which is currently used as a test. But I can't do it. Do you have any links or tutorials to help me understand how it works or how to install twrp without ADB or oem unlock ?
Many thanks
Click to expand...
Click to collapse
You can't install twrp with adb the only way is using odin here is a video that should help you understand better
and here is the link for twrp for a40 https://twrp.me/samsung/samsunggalaxya40.html
Sloobot said:
You can't install twrp with adb the only way is using odin here is a video that should help you understand better
and here is the link for twrp for a40 https://twrp.me/samsung/samsunggalaxya40.html
Click to expand...
Click to collapse
Thanks,
I intentionally left the oem block on and did not activate the develloper mode to put myself in the same situation as my father's phone. And ODIN tells me FAIL.
So I think that if we have no access to the phone with the code to access the developer options we can not do anything.
mypomme said:
Thanks,
I intentionally left the oem block on and did not activate the develloper mode to put myself in the same situation as my father's phone. And ODIN tells me FAIL.
So I think that if we have no access to the phone with the code to access the developer options we can not do anything.
Click to expand...
Click to collapse
Did you flash the vbmeta disabler before hand? https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
This is my problem I don't know how to do with Odin :/
Sloobot said:
Did you flash the vbmeta disabler before hand? https://forum.xda-developers.com/t/recovery-official-twrp-for-galaxy-a40-a405fn.4025587/
Click to expand...
Click to collapse
mypomme said:
This is my problem I don't know how to do with Odin :/
Click to expand...
Click to collapse
Try this
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Try this without oem unlock and formating data in twrp