Related
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
prdog1 said:
Can't flash the OTA in TWRP. Have to be completely stock. It is picking up the TWRP recovery build that does not match stock recovery. TWRP is built from AOSP source and dees_troy is one of the devs.
Click to expand...
Click to collapse
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash either, right? It certainly seems like an exploit worthy of my time to patch, but I was trying to avoid the data loss :/
rvrzl said:
Oh, I thought you could flash it as long as you downloaded and flashed it manually via recovery, instead of letting the OTA do it's thing automatically. Bummer!
There's no way to remove the recovery without doing a full re-flash, right? It certainly seems like an exploit worth of my time to patch, but I was trying to avoid the data loss :/
Click to expand...
Click to collapse
You can fastboot flash the corresponding factory images. Skip the userdata data image and will will not wipe data. OTA's are worthless if gonna run root and recovery. Someone may make a TWRP flashable. Would have to search for it.
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
rvrzl said:
Awesome, I'll dig around and figure out how to skip certain images while flashing and give that a try (I've never had to do that before). I'm pretty comfortable in the terminal though, so I'm not too worried. Thanks for your help, @prdog1
Click to expand...
Click to collapse
If you're running root, fastboot flash the system.img only. If you don't run a custom kernel, you probably should also fastboot flash the boot.img too.
Keep supersu on your sdcard and after flashing system DO NOT boot the rom. Boot straight into TWRP and flash supersu
If you boot rom install-recovery.sh will install stock recovery on first boot. .flashing super su amended this script so that won't happen.
You can also flash the radio.img. Your choice.
rvrzl said:
I have an unlocked & rooted Nexus 6 (T-Mo, I My build number is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP,
Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Click to expand...
Click to collapse
For OTA's the device needs to be unrooted and complete stock. Including 'recovery'. So flashing with TWRP-recovery will not work.
An alternative is to flash only the new system.img with fastboot.
FWIW, recovery flashable updates are here:
http://forum.xda-developers.com/showthread.php?t=3066052
rvrzl said:
Hey guys,
I have an unlocked & rooted Nexus 6 (T-Mo, I believe) that I'm using for Google Fi. I'm currently on the 5.1.1 update that I got pre-root, when Project Fi pushed it to me. My build number (in About phone) is LYZ28E .
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
Again, my ROM is the stock OTA that Google pushed me. I'm not running anything custom aside from TWRP. Any clue why the installer is showing my device as 5.0/LRX21M, when it's actually 5.1.1/LYZ28E?
Thanks in advance!
Click to expand...
Click to collapse
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
snatale1 said:
I'm having the exact same issue, but theirs gotta be a way around it, not sure how it does it but if I use the sideload option in NRT then it somehow boots STOCK recovery to flash the OTA, problem then for me is I loose connectivity when that happens. I retain sideload ADB connectivity when I try in Linux, but can't get the phone into stock recovery that way. If I can't get it in by the weekend guess I gotta fully return the phone to stock to get that update in. Hopefully somebody figures it out.
Click to expand...
Click to collapse
You can flash the OTA all day anyway you want but if you are not stock it won't take. Only other way is one of the flashable TWRP versions that were linked to. And right now looks like that thread is down for update.
danarama said:
Booting to a stock recovery is easy.
"fastboot boot recovery.img"
Then you can adb sideload, as long as your rom is entirely stock and never rooted.
That said, fastboot flashing the system.img would probably be quicker.
Click to expand...
Click to collapse
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
rvrzl said:
Today I was attempting to flash the official Stagefright update via TWRP, however it keeps failing with the following message:
Code:
Package expects build fingerprint of google/shamu/shamu:5.1.1/LYZ28E/1914015 : user/release-keys;
This device has Android/aosp_shamu/shamu: 5.0/LRX21M/dees_troy11191312 : userdebug/test-keys
!
Click to expand...
Click to collapse
Because of this, I did the update twice; different methods, to see of there are possible differences.
Differences between official OTA and flashing the new system.img only.
Update 1: Flashing only the new system image (1,7 Gb) with fastboot.
Update 2: Return to stock LMY47Z and install official OTA (24,2 Mb)
Both updates have the same results. Data and apps were kept but there were changes:
a. Changes in build.prop gone (DPI, Wifi interval);
b. Standard icons because the DPI value 384 was changed to 560;
c. BGN-launcher replaced. Google Now launcher became white again;
d. Root gone (SuperSu and Busybox);
(Update 2. Of course returning to stock, replaces the custom kernel).
After rerooting the N6 the following actions were needed after both update methods:
- edit the file: system/build.prop to change the dpi and wifi interval;
- reflash/reinstall: BGN-Launcher, SuperSU and Busybox;
- uninstall updates of the Google app to get BGN-launcher working;
- replacing icons from drawer to start screen.
So when you have made changes to the system, like DPI settings, an update will leave your data alone, but not the settings.
Clawz114 said:
If I am running everything stock apart from the recovery (using TWRP), with an unlocked bootloader and the device is not rooted, can I simply flash the stock recovery.img without losing any of my data? Is it really that simple? Do I have to use a particular recovery.img?
All I want to do is restore the stock recovery so I can OTA the stagefright update. TWRP is preventing me from doing so at the moment, but I don't want to lose all my data.
Click to expand...
Click to collapse
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
efrant said:
Yes, that is all you have to do: flash the stock recovery corresponding to the Android build you are currently using. You will not lose any data. Remember, data is stored on the userdata partition, so as long as you don't flash that image, all your data will be left intact.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
That said, the only reason not to flash the rightbversiin is if the download link.is down or you have a local copy of a different version anyway.
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
How are you trying to flash the OTA?
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Clawz114 said:
Thanks, I flashed the LYZ28E recovery and all seemed well. However, I then went to install the OTA, and it ended up giving me the error, with the Android on it's back and the exclamation mark. Rebooted the phone and apparently "Your system is up to date".
Click to expand...
Click to collapse
What is the error?
danarama said:
[snip]
The OTA doesn't check the recovery version, since it replaces recovery on first boot anyway. Only matters that its stock.
Click to expand...
Click to collapse
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
danarama said:
The exclamation mark isn't an error. That's the stock recovery splash screen. You have to press vol up + power at that screen to get to the menu
Click to expand...
Click to collapse
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
danarama said:
How are you trying to flash the OTA?
Click to expand...
Click to collapse
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
danarama said:
By unrooted, lets be clear. The rom must never have been rooted. Unrooting a rom won't work
Click to expand...
Click to collapse
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
efrant said:
What is the error?
Click to expand...
Click to collapse
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
efrant said:
What is the error?
You are right, the OTA doesn't check the version of the recovery. However, I can tell you for a fact that on older Nexus devices, using a recovery from a different version of Android would not allow an update to flash. (It is possible this has changed since then though.) I remember very clearly, helping many users troubleshoot (particularly given that the only available toolkit at the time would flash only one generic stock recovery, and not a specific version), and it was confirmed that the errors users were having were due to using a wrong version of the stock recovery, so the recovery version did indeed matter (at least on the Galaxy Nexus it did).
Click to expand...
Click to collapse
I believe it changed for lollipop OTA's. I don't think it had changed for kitKat.
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
Clawz114 said:
I press install update now, let the phone reboot and I get the installation screen with the progress bar. It sits at about 10% filled for about 10 seconds then I get the picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
The only thing I flashed was a stock recovery.img, to replace TWRP. I am trying to get the latest update the normal way, by getting the notification I have an update available, and pressing install update now.
I have never rooted the phone. I updated the phone manually a while back and long story short, I flashed TWRP recovery instead of the stock recovery as I intended to. I just want to revert everything back to stock (which it should be now that I have replaced TWRP with stock recovery)
As above, it's picture of the android laying on it's back with a red triangle and an exclamation mark. Underneath that it just says "Error!".
Click to expand...
Click to collapse
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
danarama said:
If you're.familiar with fastboot already, why not just download the full factory image and flash system, boot, bootloader, radio and recovery images?
Click to expand...
Click to collapse
I'm going to have to do just that by the looks of it.
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
yosmokinman said:
Sounds like it will work, but why mess with the ota? More work and risk honestly.
Since you're already using fastboot just flash the newest boot and system.img. Then flash/boot twrp and flash su like you'd need to do anyway. Done. You don't lose anything flashing system.
Click to expand...
Click to collapse
That is true, kind of just wondering/gathering information. It just seemed like with the new root method, OTA would be possible and less risky than before.
Sent from my MotoG3 using Tapatalk
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Srandista said:
@quakeaz there is one step missing on your guide. After boot.img you also have to flash stock recovery.img. From Lollipop, Google is also checking installed recovery, and for successful OTA, it has to be stock as well.
Otherwise, your guide should work, I've done same thing with my Nexus 5 and 7 for like last 3 months.
Click to expand...
Click to collapse
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
quakeaz said:
Thanks for your reply, but I intentionally left that step out, due to step 2 in my list. By only booting TWRP, instead of flashing, I assume stock recovery will remain after rooting.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Sounds good!
Sent from my MotoG3 using Tapatalk
quakeaz said:
I am looking for an easy way to be able to receive OTA updates after rooting with the 'systemless' root method, the steps I mention below assume that the system partition remains untouched after rooting. I have searched and not found a clear answer on this.
Would I be correct in assuming that this procedure should work to receive an OTA update and keep stock recovery after rooting?
Start with completely stock Android 6.0
fastboot boot twrp-recovery.img (boot TWRP, NOT flash, to maintain stock recovery after rooting)
Flash systemless root with TWRP
OTA arrives (Android 6.0.1 for example)
fastboot flash boot boot.img (with stock 6.0 kernel, root lost)
Accept & install OTA update
Success?
So unless I am missing something, this method would leave the system in a stock, unrooted state after the OTA is installed, and could be repeated for future updates. Anybody have any experience with this yet?
Click to expand...
Click to collapse
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Thanks for the info. So I take it while using systemless root, installing ota without unrooting is a big nono? The January ota just downloaded and is asking me to install, should I do it manually?
Chainfire said:
Instead of fastboot flashing boot.img, you can use "Settings --> Full Unroot" in SuperSU. During SuperSU systemless flash, your old boot image is backed up. Among other things, the full unroot option will restore the backup, assuming it hasn't been lost due to a factory reset and whatnot.
On many firmwares, this procedure also restores stock recovery. This requires that both the firmware supports recreating the recovery from the boot image plus a patch file (most do), and that TWRP did not remove said patch file (which some versions do).
That being said, if you're using fastboot anyway, flashing boot, recovery, system and vendor manually is always the safest thing before an OTA.
Click to expand...
Click to collapse
Thank you for this thread and the procedure. I tried myself to avoid as much as possible to use a computer for super easy OTA update. But there is always one obligatory step: to root the phone.
Phone systemless rooted (2.66) - TWRP installed - OTA arrives.
In SuperSu app : Fully unroot
Install OTA - success
Fastboot boot (or install) TWRP
Flash superSu 2.66.zip
And that's it!
My question is the following: Does it exist a possibility to load on step 3. something that could flash superSu.zip from within the phone, no computer required?
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Judim said:
Maybe FlashFire? I guess not, for it needs root and the point is to flash a rooting zip... You see the loop there...
Would it be theoreticaly possible at all?
Click to expand...
Click to collapse
Yes, this is one of the use-cases of FlashFire. I just haven't finished updating it to 6.0 yet.
Oh nice!
I didn't know it cause I never had the chance to try out FlashFire.
Thanks so much for everything you do for the Android community!
Cheers!
Srandista said:
Ah, sorry, I overlooked that.
Since I have flashed TWRP instead of stock recovery, I'm going by same process as you write, just reflash stock recovery. And can confirm, that the process is indeed working (no need to install system.img, as with previous system-based SuperSU).
Click to expand...
Click to collapse
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
ShanxRoux said:
mine fail here. i previously got systemless root 2.62, blu spark kernel and twrp. fastboot flash stock boot and recovery. reboot to update and it fail. any idea why?
Click to expand...
Click to collapse
Did you modify system?
Try flashing system, boot, and recovery.
Then try again.
Hi, I have a Oneplus One and today has been released an OTA, so I tried the method. I have COS13 JK (latest full rom) firmware, with systemless 2.84beta supersu and twrp.
The only apps that have root access are AdAway and Greenify (without mods to system apps). No Busybox installed.
I reverted via fastboot to original JK boot.img and recovery.img, and restored, via Adaway, the original hosts file, then I applied the OTA via stock Cyano Recovery, but update failed ("system partition has unexpected contents" error).
Why?
Thanks.
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
caldent said:
you have to unroot first from the app.Revert to original boot. and then flash
Sent from my ASUS_Z00LD using Tapatalk
Click to expand...
Click to collapse
I tried: no way to install OTA, I had to wait for the full rom, and dirty flashed it via TWRP without a problem.
Then I rerooted.
Bye!
ok i seem to be getting the run around on where i need to be to ask my question(s)
i am very interested in systemless root....
that being said i am clueless and all info i am findingis just super confusing me.
if someone could humor a noob to systemless rooting that would be greatly appreciated!!
i recently bought 2 new phone for my household, both are the lg tribute hd (also called lg x style)
one click root and pc method of kingoroot etc dont work... i cant locate a twrp or a cwm for this model easily by searching so i am assuming there isnt one (maybe someone could located or help to build one?)- or maybe im not tech smart enough and i can use any?(i dont think so)
model is lg ls675,android 6.0.1, kernel version 3.10.49, build # MXB48T, software is ls676zv3
main reason at the moment for trying to get root is to remove bloatware and to be able to wifi tether without limitations buy the provider, on ther phone that i have obtained root on i used an app called WIFI Tether Router which works beautifully but requires root...
please help as this is how we use our computer with internet and its beneficial all the way around especially to get rid of bloatware and keep device running smoothly...
thanks again for any help. greatly appreciated.
if im not in the right thread please kindly direct me to the correct one. thanks
Hey there everyone.
I have CyanogenMod flashed in my H811. It was working just fine when in Marshmallo i.e. Cm13. but a few days ago it upgraded to cm14, nougat. there were a lot of issues and i wanted to revert but cm13 was nowhere to be found. the nougat version was working just fine when yesterday it notified me of an update. i downloaded that update and tried to install it. phone rebooted into recovery but it didn't automatically flash the update ( which it usually does whenever a new update is set to install) so i just located the file and flashed it and then rebooted it afterwards. that's when i saw that it rebooted into TWRP again instead of system. i've tried almost everything since yesterday. Flashed other roms, tried to restore backups but no success. even reset my phone completely and then tried to, but to no success. i cannot even access download mode which if i could, i would've had flashed the stock kdz. Everytime i try to reboot it into system or download mode, it just reboots back into TWRP. Please help.
Edit: I was using the wrong method for entering the download mode. i was pressing the volume down button instead of volume up while plugging into my pc. If you encounter the same problem, make a backup ( to restore apps later) in TWRP and move it to your pc, also backup your internal data (music, pictures etc). Also download gapps, check arm64 and android 7.1. Now Using the lgup tool, flash the stock rom kdz, the latest one is 20o. Your phone will be back to stock. Then flash twrp again using adb and use adb to boot into twrp. once booted, copy the cm update from your pc to phone, ( this is the update which caused the problem, back it up too. it'll be in sdcard/cmupdate/ ) and also the twrp backup that you had made earlier. Then on your phone, flash the cm rom and Gapps, and then restore the twrp backup when when restoring, go to advanced restore and select data only. and restore that. after it completes, turn on your phone, connect it to pc and move the internal data (pics and music) back to your phone.
I am in the same trouble except I am using CM recovery
Screen prompts below error message when flashing any ROM:
Patching system image unconditionally....
E: unknown command [log]
Somtimes I can see a broken (heart) android Robot
Then phone goes back to recovery home page
Anyone can help us? Should I flash TWRP recovery to overwrite CM recovery? Is phone hard/soft bricked?
Same exact issue. I have TWRP. Did the December second CM update and have no clue what to do.
TechGuruGJ said:
Same exact issue. I have TWRP. Did the December second CM update and have no clue what to do.
Click to expand...
Click to collapse
eruisi said:
I am in the same trouble except I am using CM recovery
Screen prompts below error message when flashing any ROM:
Patching system image unconditionally....
E: unknown command [log]
Somtimes I can see a broken (heart) android Robot
Then phone goes back to recovery home page
Anyone can help us? Should I flash TWRP recovery to overwrite CM recovery? Is phone hard/soft bricked?
Click to expand...
Click to collapse
i found the solution. i was using the wrong method to enter download mode. it was pressing Volume up button while plugging into my pc. i recommend you both to make a backup and move that to your pc, enter download mode and flash the stock rom, then flash twrp again and the current cm rom and restore the 'data' from the backup made. it'll restore the phone to back where it was.
Armaghan Bashir said:
Edit: I was using the wrong method for entering the download mode. i was pressing the volume down button instead of volume up while plugging into my pc. If you encounter the same problem, make a backup ( to restore apps later) in TWRP and move it to your pc, also backup your internal data (music, pictures etc). Also download gapps, check arm64 and android 7.1. Now Using the lgup tool, flash the stock rom kdz, the latest one is 20o. Your phone will be back to stock. Then flash twrp again using adb and use adb to boot into twrp. once booted, copy the cm update from your pc to phone, ( this is the update which caused the problem, back it up too. it'll be in sdcard/cmupdate/ ) and also the twrp backup that you had made earlier. Then on your phone, flash the cm rom and Gapps, and then restore the twrp backup when when restoring, go to advanced restore and select data only. and restore that. after it completes, turn on your phone, connect it to pc and move the internal data (pics and music) back to your phone.
Click to expand...
Click to collapse
Hi , I have the same problem, just wanted to get some clarification on how to sort this out as I've not used LGUP before or flashed stock rom:
from here: http://forum.xda-developers.com/tmo...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
which file do i need? is it the KDZ version? once that's downloaded do i follow these instructions from LGUP page?
"TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient "
thanks.
charmander21 said:
Hi , I have the same problem, just wanted to get some clarification on how to sort this out as I've not used LGUP before or flashed stock rom:
from here: http://forum.xda-developers.com/tmo...om-mm-lg-g4-h811-20o-stock-debloated-t3412394
which file do i need? is it the KDZ version? once that's downloaded do i follow these instructions from LGUP page?
"TO GO BACK TO LP FROM MM - Open LGUP on your computer, click on FILE PATH and point it towards your LP KDZ. Close LGUP and re-open LGUP. Make sure you select REFURBISH this will do a full wipe, tick BIN file. Press Start. Make cup of tea and be patient "
thanks.
Click to expand...
Click to collapse
Hey, The flash rom of LG G4 is in the format .kdz. also, i used the .kdz which i already had from almost 3 months ago when i had to flash my phone to stock. so I don't remember from where did i get it but here is a link that i extracted from IDM.
https://www.androidfilehost.com/?fid=24572369242688134
Download this file, then on the lg flash tool, select ''Upgrade'', select your .kdz file by clicking the rectangular bar next to 'bin file' and then flash it. That's all.
Armaghan Bashir said:
Hey, The flash rom of LG G4 is in the format .kdz. also, i used the .kdz which i already had from almost 3 months ago when i had to flash my phone to stock. so I don't remember from where did i get it but here is a link that i extracted from IDM.
https://www.androidfilehost.com/?fid=24572369242688134
Download this file, then on the lg flash tool, select ''Upgrade'', select your .kdz file by clicking the rectangular bar next to 'bin file' and then flash it. That's all.
Click to expand...
Click to collapse
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
---------- Post added at 02:44 PM ---------- Previous post was at 02:15 PM ----------
charmander21 said:
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
Click to expand...
Click to collapse
Ah no worries, in download mode now.
Glad to know
charmander21 said:
Thanks - you mean using LGUP tool? what mode do I have to put my phone into to run LGUP? LGUP is not seeing my phone, even though it shows up fine in windows.
---------- Post added at 02:44 PM ---------- Previous post was at 02:15 PM ----------
Ah no worries, in download mode now.
Click to expand...
Click to collapse
Hey, i had to contact you again. Just wanted to ask if you by any chance had a cm13 backup or rom zip? I want to revert back.
Hey, sorry I don't, I wiped it I reverted to stock and the flashed cm 14.1 - its working well, but no xposed available yet.
Incidentally I think the whole problem was to do with updating from cm with xposed, to cm nougat (as yet no xposed) without disabling/uninstalling xposed first.
charmander21 said:
Hey, sorry I don't, I wiped it I reverted to stock and the flashed cm 14.1 - its working well, but no xposed available yet.
Incidentally I think the whole problem was to do with updating from cm with xposed, to cm nougat (as yet no xposed) without disabling/uninstalling xposed first.
Click to expand...
Click to collapse
Tell me this, when you had cm13, could you record 4k videos with any third party camera app? Or play 2k videos on youtube or a media player? Because i couldn't until i recieved a cm13 update which enabled those features. Now i actually have a cm13 backup which is dated 31st of august. And it doesn't let me record in 4k or play jn 2k. So I'm searching for someone who has a backup after that. And the reason i want to revert is actually theming option in cm 13. 14 doesnt have it yet. Hope it gets soon and also Xposed.
https://support.t-mobile.com/docs/DOC-28979
Pushed out December 5th, H81120x, just over 79MB, described as "Google monthly security enhancements".
I've forgotten where OTA update files are downloaded too. Can anyone refresh my memory?
Thanks!
This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.
pizzaboy192 said:
This is good to know. Any idea if I need to be worried about the phone being rooted\xposed? This is my first Android device in many years and can't remember how to handle OTAs.
Click to expand...
Click to collapse
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.
raptorddd said:
some roms get ota some dont you must be on stock rom i guess. or wait till they release KDZ.
Click to expand...
Click to collapse
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.
pizzaboy192 said:
I'm running rooted stock because I need band12 and volte where I live and only stock has that working.
Click to expand...
Click to collapse
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.
raptorddd said:
yeah well i have never recive one since am not in the USA. i always used KDZ. so either flash latest 20v or wait but not sure what rom seems all MM have not been updated.
Click to expand...
Click to collapse
I just checked and no updates yet. Maybe Xposed and magisk are messing with it.
Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.
thejaredhuang said:
Is there a way to install it with TWRP installed? I got it and the phone rebooted but only to TWRP.
Click to expand...
Click to collapse
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
is there a KDZ available yet? maybe you need to do a refurbished flash of KDZ. 20x
pizzaboy192 said:
I think since the H811 has an unlocked bootloader the easiest way is going to be flashing the stock recovery through TWRP, reboot, install the OTA, and then fastboot back into TWRP and reinstall it. (Unless it keeps root through Magisk or something and then you can just use the TWRP app rooted to reinstall)
Click to expand...
Click to collapse
I'm not rooted so no worries. Its there a stock recovery image somewhere or do i need to extract one from the 20v kdz
So is there a directory where the OTA is downloaded to? I have the KDZ for 20v but I can't get a valid cab file to extract the DZ when I use LGExtractor (this is when I'm trying to extract the stock recovery.img).
Update file
Here is the update file for 20x, i extracted it from the /cache directory. I tried to flash it via TWRP but there is some ID checker that errors out and fails to install on TWRP
https://1drv.ms/u/s!AvCSuR2bvtpdg9tZBW-m9yVP6gYGng
For help about root
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x
Somnathdey said:
How to root and install twrp... Plzz help me... Given procedure not working stuck to send command port no.. Position.. Plzzz any one give some help or other way to get root and install twrp. My version is lg g4 h811 20x
Click to expand...
Click to collapse
THIS MIGHT FACTORY RESET YOUR PHONE. BE SURE YOU ARE OKAY WITH THAT.
1: make sure you've enabled Developer Options in settings (go to About Phone, tap the Build Number a bunch until it pops up saying you've enabled developer options.
2: Make sure you've enabled bootloader unlock in Developer options
3: make sure your device's ADB drivers are installed. The phone comes with the resource CD built in, so you can always use that to make sure it is set up
4: run ADB on your computer, type adb reboot fastboot to get into fastboot mode. The phone should reboot. If it does not, recheck steps 1, 2, and 3.
5: type "fastboot oem unlock". This it should report it as OK or Success. If so, type fastboot reboot. It may or may not factory reset your phone at this point. It didn't with mine but YMMV.
6: once Android has booted, follow the steps to install TWRP. Same steps as above but you'll be booting a TWRP image instead and then flashing it.
For help about root
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb
Somnathdey said:
Have tried this mathod bt still not working my phn stuck in fast boot mode.. In command after typing fastboot oem unlock not working.... Plzz send me some working * platform tools for root in which i can start the command and adb
Click to expand...
Click to collapse
Sure thing. You'll get more help though posting a new thread instead of on one unrelated.
gregoriusaryanto said:
few days after updated, software version changed into H81120x, my camera suddenly and always crashed and getting hot not like usual. please help me fixing this problem
Click to expand...
Click to collapse
No problem here, try to reset the phone or at least clear the cache of camera.
So my phone finally presented me with the OTA, but it fails to install because of TWRP (expected). I grabbed the update.zip and did the basic modification to allow me to flash it via TWRP but it still fails. LG Bridge doesn't get past checking software version. I am running stock, rooted with Magisk, RCTD removed and some minor root-free debloat (The "uninstall apps for user 0" trick)
What LG OEM apps are required to get LG Bridge to work?
Edit: Could I dirty flash a full stock ROM over it (including stock recovery) to get the OTA to work and then just debloat again?)
Does the KDZ file only come from LG? I wonder if I can update and then somehow extract KDZ to share with everyone...
EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.
S7 G930T Flat Odin Factory FIrmware Downloads
G930TUVU4CRI2_8.0_4File_USA (T-Mobile).rar
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I had to look this up so thought I'd share This is for Tmobile Versions
Example: G930TUVS8CRJ1 (5th # from right is 8, BL version - this is found in Settings>About Phone>Software Information>Baseband Version)
Which Oreo versions are safe (ver 4):
G930TUVU4CRI2 Oct 1, 2018
G930TUVU4CRF1 June 28, 2018
Not safe (ver 8):
G930TUVS8CRJ1 Oct 26, 2018 release date
---------- Post added at 02:55 AM ---------- Previous post was at 02:49 AM ----------
BTW nice work as always Jr! Oh, & almost forgot ...your last comment saved my @zz!!! I wasn't aware of the ver 8 issue, and the fact that u can't downgrade!! DAMN Samsung!!!!! I was seriously about to try this latest update just to try & figure out RCS not working on CRF1 & randomly came across this! THANKS! (BTW if you know anything about RCS on s7 or services/apks needed for functionality on CRF1 please pm me!)
On another note, let's have a contest to see who can hold on to the S7 the longest as their primary phone
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
FranMLG said:
It works perfectly , I had no problem installing it. But I have a question:
Could I replace the SuperSu with the Magisk?
I am also in the Rom Project L S7 of Lanc-City: 3
Click to expand...
Click to collapse
No magisk requires custom boot.img
Sent using some kind of device I modified
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Thanks for the effort and providing root for T-Mobile. Perhaps I am an unlucky person. By the time I discovered this thread, my phone was already updated to G930TUVS8CRJ1 version. I am wondering if there is any hope for V8 bootloader to root their phone in near future. Here is my humble request if you could provide root for V8 update. TIA.
jrkruse said:
No magisk requires custom boot.img
Sent using some kind of device I modified
Click to expand...
Click to collapse
can we do full backup after setting up the phone and then restore it without any bugs and issues?
zfk110 said:
can we do full backup after setting up the phone and then restore it without any bugs and issues?
Click to expand...
Click to collapse
Do a system.img backup
Sent using some kind of device I modified
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
boofbatch said:
Thank you. It worked fine on my nougat s7 flat with v4 bootloader. Now I have nougat root. I have a question if I may, Can I use tmp twrp to flash Oreo or one of your, or other roms? Or would I need to upgrade the kernel or something because I can flash Oreo being that I'm on Nougat. Thanks.
Click to expand...
Click to collapse
You have to update bootloaders and firmware as well so its better to update to oreo first
Sent using some kind of device I modified
working fine.
update: gonna have to switch back to u firmware because even when i unroot the phone, certain games wont work or connect to server. i cant install magisk to bypass safetynet or hide magisk after installing so root isnt even seeming worth it on this device. might as well stick to the u firmware and disable the apps I dont need and disable ota update so that i dont get the v8 bootloader update. It was fun while it lasted.
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
That's exactly what happened to me, I did not know
FranMLG said:
Man, will you update the Recovery for the new security patch (CRJ1) ?, I've run out of Root , and I can no longer go back in the version.
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
That's exactly what happened to me, I did not know
Click to expand...
Click to collapse
yikes sorry to hear that
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
zfk110 said:
I bought a phone which is already to g930tuvs8crj1 I tried to down grade but it wont let me, what are my options? Thanks
Click to expand...
Click to collapse
Enjoy Stock
Sent using some kind of device I modified
jrkruse said:
Enjoy Stock
Sent using some kind of device I modified
Click to expand...
Click to collapse
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
zfk110 said:
After looking around for 4 days I was finally able to find G930T U8 ENG ROOT Modem.bin file, but when I'm trying to flash it using odin it wont pass file Analyzing
I hope you can look more into it. if we can flash this then we can able to root U8 bootloaders too
https://drive.google.com/open?id=1dhHeYAPsCqKQ_eFfuzPaYbgFv0y1BSLr
These guys also selling Eng boot for $60
https://support.halabtech.com/index.php?a=downloads&b=file&id=90428
Click to expand...
Click to collapse
Im just waiting on them to email me the passwords
Sent using some kind of device I modified
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
marvelv94 said:
Alright guys i really need your help...i just bought a used samsung. galaxy s7 G930T...the problem is it doesnt get any network...thr signal says searching and theres is nl network bar...the issue is i cant tell if it is unlocked or not..because it reads my sim...it displays the right access point....shoes sim tools...but just doesn't get network..i ve tried all sim cards...i tried using the tmobile unlock tool that came with the device butbit says unlock failed reboot device repeatedly....ive tried factory reset....i love this phone and would really like to use it...Pls any suggestions or help...the software version is 8.0. baseband version is G930TUVS8CRL1
Click to expand...
Click to collapse
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
jrkruse said:
Sounds like you bought yourself a blacklisted phone
Sent using some kind of device I modified
Click to expand...
Click to collapse
It is not blacklisted ...i already checked...any help?