Related
BIG NEWS, methods to get zune nodo. http://forum.xda-developers.com/showthread.php?t=1012189 !!!!
Download usaip.eu/en/USAIP.pbk open it and connect to EUROIP PPTP Hungary withUSERNAME: demo
PASSWORD: demo
Connect your phone to the PC
Disable WLAN in your phone but be sure to have FLIGHT MODE off, turn on the data connection in ur cellular setting
OPEN the Use cellular data connection to check for updates IN phones setting and remain in this setting
Start Zune and keep it running all the time
Manually search for an update within Zune
After a few seconds (about 21 seconds for me) disable data transfer on the already opened settings tab on your phone -->wait and The update shows up!
I MANAGED TO GET UPDATE BY USING THIS METHOD!!!
Update OK.
thank you
RUU_Mozart_HTC_Europe_1.28.401.04_5.52.09.16_22.33 a.50_RELEASE => Update Feb (7008) => !!! Update Mar (7390)
Updated
Sorry, this confirmed working, just remember to turn on the data connection in ur cellular setting.
Works perfect for me... Thanks!!!!
Can't get it to work on my Focus. Do you need 7008?
EDIT: Installed 7008 by unbranding and tried again, still no update found.
Great! Thank you, it's worked on my HD7
rmcgraw said:
Can't get it to work on my Focus. Do you need 7008?
EDIT: Installed 7008 by unbranding and tried again, still no update found.
Click to expand...
Click to collapse
turn on the data connection in ur cellular setting,
and waiting 21 seconds in the 5th step
keeps saying can't check for updates right now error . make sure your pc is connected to the internet?
dememted1 said:
keeps saying can't check for updates right now error . make sure your pc is connected to the internet?
Click to expand...
Click to collapse
same problem here.
Original Thread here:
http://forum.xda-developers.com/showthread.php?t=1012189
updating at the moment
Took some messing around, had to reconnect to the VPN and untick the check box after 5 seconds of update searching.
But then it found the update
Downloading goes slow over the VPn but hey!, i'm getting the update
Using a Samsung Omnia 7
Bonebreaker said:
Original Thread here:
http://forum.xda-developers.com/showthread.php?t=1012189
Click to expand...
Click to collapse
I sorry, I don't know there have been already a original thread.
got nodo on my att focus
dev unlock, unbrand from att to 000-88
get pre 7008
get nodo (painfully slow with backup)
still unlocked and still sideloading apps
no .pbk needed
^^^^^^^^^^^^^^^^^^^^^
How did you do this can you give me steps I also have an at&T focus.. I would like to get nodo and not lose any of my sideloaded apps.
It took me over 50 tries.
I was getting the "Phone up to date message" at 28 seconds. I turned off data at 10 seconds and got the update
Focus, ATT, USA
jotato said:
It took me over 50 tries.
I was getting the "Phone up to date message" at 28 seconds. I turned off data at 10 seconds and got the update
Focus, ATT, USA
Click to expand...
Click to collapse
So you followed the steps in the OP and now you have nodo and it's unlocked? I assume you did chevron unlock and install the samsungtools to keep it from relocking.. did you do anything else?
This is great news, but is this version of NoDo optimized for U.S. handsets?
Oscardog777 said:
This is great news, but is this version of NoDo optimized for U.S. handsets?
Click to expand...
Click to collapse
NoDo is NoDo. The update is specifically tailored for Foruses (or is it Foci), so it shouldn't matter. Realistically, they all should run equivocally. The question that remains is, did it really work, or is this guy pulling our leg such that we try and recreate what he did over and over again with no success. Being the overzealous techie I am, I will try this out...
thealanshow said:
NoDo is NoDo. The update is specifically tailored for Foruses (or is it Foci), so it shouldn't matter. Realistically, they all should run equivocally. The question that remains is, did it really work, or is this guy pulling our leg such that we try and recreate what he did over and over again with no success. Being the overzealous techie I am, I will try this out...
Click to expand...
Click to collapse
I can confirm it works, I was just prompted for the update, I'm just hesitant to pull the trigger on it because I don't want it to update to a (I'm assuming) european radio firmware that kills by battery/gives me ****ty reception.
IVIadness said:
So you followed the steps in the OP and now you have nodo and it's unlocked? I assume you did chevron unlock and install the samsungtools to keep it from relocking.. did you do anything else?
Click to expand...
Click to collapse
Forget the op instructions. Just follow the chev unlock, Samsung tools, and Samsung registry to brand your phone from att-us to 000-88. Zune will prompt you to update to release 7008. After that it will frompt you for nodo. I did nothing in the op. After I updated I rebranded to att and all is well.
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
JRSouth said:
I have an ATT ZenFone 2E that I rooted successfully with this guide (http://forum.xda-developers.com/showthread.php?t=3116531). Due to an error on my part(fat finger) I accidentally started the OTA update. Now when I try to boot the phone all I get is the AT&T logo/splash screen. I can get it to go into recovery mode and it also will connect via ADB. I have tried flashing the UL-ASUS_Z00D-WW-12.16.5.30-user.zip firmware via ADB fastboot but I get an error saying firmware is wrong carrier ATT (WW). Am I using the wrong firmware for AT&T? I have searched all over and cannot find any ZenFone 2 firmware other than WW, TW, and CN. Any help or suggestions much appreciated.
Click to expand...
Click to collapse
i have the exact problem since saturday, you have to use the ATT firmware but i couldnt find it anywhere
also
please pm me if u fixed yours
Lactaid said:
please pm me if u fixed yours
Click to expand...
Click to collapse
Still no luck. I'm sure if we could find the AT&T firmware we would be able to recover. Unfortunately it appears it is not available on ASUS support and AT&T doesn't even provide firmware. Our only hope may be from a backup of another device that isn't bricked.
Does anybody know if we could possibly use the temporary CWM recovery used in the root method to flash to another ROM that is compatible with this device? Any input would be greatly appreciated.
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
JRSouth said:
Are there any details I can provide that would be helpful in finding a solution to recover this device? I've seen a few other people are having the same issue as I am and I would like to help them as well if I can get mine fixed. Thanks
Click to expand...
Click to collapse
ive literally tried everything, my device has been bricked for like 3 weeks now
Lactaid said:
ive literally tried everything, my device has been bricked for like 3 weeks now
Click to expand...
Click to collapse
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
JRSouth said:
Just out of curiosity have you tried running the xoa_unroot.bat while your device is in recovery/fastboot mode? Im not sure if it will help but I've found in other threads that to avoid soft bricking your device you must run the unroot prior to applying the OTA update. I'm sure it's probably too late but maybe worth a shot. I'm going to try it when I get home from work today.
Click to expand...
Click to collapse
i havent tried it yet, do you have a tutorial of it?
The truth hurts, your screwd. This is a budget phone. At&t will not support it. Throw away device my their standards.
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
http://forum.xda-developers.com/showpost.php?p=63323103&postcount=118
^^^This worked for me successfully!
Make sure to only restore system and disable MD5 Checksum Verification.
I have the same problem, what do I do with that file? How do I apply it through the SD, so I can apply update from SD? I forgot pin code to phone so i need to restore
need help
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
how do I flash this?
Hola, alguien lo consiguió hacer..???
Lactaid said:
http://forum.xda-developers.com/attachment.php?attachmentid=3505774&d=1444776691 here the system image for the file maybe try to flash it to see if it helps
Click to expand...
Click to collapse
Im getting an error that day footer is wrong :/
m1chb3ltr3 said:
Im getting an error that day footer is wrong :/
Click to expand...
Click to collapse
Wait, are you bricked and tried using that as the fix? I cant post links but Check out Asus, They have Firmware, Kernel (havent checked but read it earlier today), and Boot Unlock that you can get right from (assuming you have an account) My Products.
Also... Has anyone used that method recently?
Cathaterfish said:
Sorry I will give credit to DavePmer for his guide in minute, but qouting him for some reason wouldnt let me post, even when I removed the links? anyways I'll edit and give credit I promise
So my phone is stuck on the Asus Logo, I downloaded all of this and followed the instructions all the way up to:
11) now the fun part. open your microsd card and check the folder TWRP\BACKUPS see if it has a folder named
01234567890123456789 if it does great if not, not a problem just copy all the system files from the folder
you extracted TWRP-zf2e-ATT_12.16.10.7 to your microsd card TWRP\BACKUP\01234567890123456789\ whatever folder you have next\ in other words, replace your system.ext4.win000 files with my system.ext4.win000 file.
Replace your system.ext4.win001 with mine, and replace system.ext4.win00.md5 with mine as well as system.ext4.win001.md5 when done safely dismount the microsd card.
It then occurred to me that i should be more careful this time around... This was from October and although I ran across links saying for the most part that this was a good shot for fixing my ZE500CL, Z00D or whatever. But things have changed since then and I was wondering if this is still the best/easiest/safe route. I learned pretty quick that over looking things like OTA/Root or in my case Making assumptions is a fast path to really doing a number on your phone. (Honestly I just started even giving thought to rooting my phone, just considered them back ups I kept in a box). I now have the itch to do this right so hoping to fix this and go about this the right way.
Thanks for any input.
Currently DLing RussaiNBeaR, went and bought a card reader/writer. I was going to Download the firmware, kernel and boot unlock tool but currently staying at a place where im getting 160kbs on my DL's. So if I can get away with davepmer's guide that would be great, or something other or smaller than downloading 4gbs on this Internet Connection.
EDIT: Forgot to add that I haven't completed this step yet because the wording kind of tripped me up. And I want to do this right. When he says "in other words replace your system.ext4.win000 files with my system.ext4.win000 file." and then goes on and 3 more to the list. Does that mean only copy and replace those 4? or does that include all system.(whatever).(extension) files? Im sure it sounds really dumb or noobish but the fact that the next step is using twrp to restore using system only makes me afraid to do this part wrong.
Click to expand...
Click to collapse
ayuda
ATT ZE500CL/Z00D rom
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
levibuko said:
Hey guys,
so i got my 5x a few days ago and set up root etc. A few laters i wanted to listen to music and realized that my jack is not working ( cant put my earphones all the way in, no contact).
So i wanted to send it back and get another one, Using the awesome nexus 5x toolkit i went back to stock and locked the bootloader, but now everytime it boots up i get that ugly message that my device is corrupt and i dont want to have any troubles because of it. any help? (flashed the mhc19j, it came with an older version).
Thanks!
Click to expand...
Click to collapse
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
so there is no official way to dismiss the warning? only replacing it with the tool?
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
levibuko said:
so there is no official way to dismiss the warning? only replacing it with the tool?
Click to expand...
Click to collapse
No. In fact someone put up a bounty to get ride of it.
Hinesight 20/20 said:
Just fixed my 5x yesterday! Rooted it etc right out of the box and, presto, that warning. I'm having trouble with the link though. Here goes...
Or not. There's a thread with a flashable zip in here. I just Googled "corruption bootloader warning" sans the quotes and there it was.
Click to expand...
Click to collapse
clcdev said:
nope. That warning will appear on devices with an unlocked bootloader. The only way around it is to re-lock the bootloader or cover it up with a bootloader skin like the material design one available on this site
Click to expand...
Click to collapse
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
levibuko said:
Well. i didt lock my bootloader and it is till there.
i am not talking about ""Your device software can't be checked for corruption. Please lock the bootloader." (Orange)"
but about this one:" Your device is corrupt. It can't be trusted and may not work properly." (Red)"
Click to expand...
Click to collapse
Ah. Sorry, I misunderstood the error you were getting. I believe that second one is due to a mismatch between the particular rom you are running and the vendor version. If you flashed back to stock using the latest stock images, I'm not sure why you are getting it as the vendor version should match (unless something else went wrong during the flash).
just finished unlocking my T-Mobile HTC 10 bootloader thorugh HTCdev.com! Got the token, copied and pasted, got the email and flashed the .bin file! Awesome!!
seniorstew said:
just finished unlocking my T-Mobile HTC 10 bootloader thorugh HTCdev.com! Got the token, copied and pasted, got the email and flashed the .bin file! Awesome!!
Click to expand...
Click to collapse
Sweet! Thanks will do the same tonight. Are you on the latest update?
Good to know, now I might trade in my T-Mobile Note 5 for the 10 with JoD
seniorstew said:
just finished unlocking my T-Mobile HTC 10 bootloader thorugh HTCdev.com! Got the token, copied and pasted, got the email and flashed the .bin file! Awesome!!
Click to expand...
Click to collapse
First thing I did this afternoon! Will the current version of TWRP work on this model?
Sent from my HTC 10 using XDA-Developers mobile app
Is anyone having issues with the HTCDEV site? When I click the "Begin Unlock Bootloader" button, I get an SSL error in Firefox, and it will never load in IE. The SSL Error keeps popping up even after the exception.
TheHeffNerr said:
Is anyone having issues with the HTCDEV site? When I click the "Begin Unlock Bootloader" button, I get an SSL error in Firefox, and it will never load in IE. The SSL Error keeps popping up even after the exception.
Click to expand...
Click to collapse
Sorry, can't say that I have.
I'm looking to flash TWRP and root this phone but I want to be able to fully restore the phone in case something goes wrong. Are there any RUU files I can use to restore the phone?
Sent from my HTC 10 using XDA-Developers mobile app
TheHeffNerr said:
Is anyone having issues with the HTCDEV site? When I click the "Begin Unlock Bootloader" button, I get an SSL error in Firefox, and it will never load in IE. The SSL Error keeps popping up even after the exception.
Click to expand...
Click to collapse
Multiple people have had issues in Firefox and IE with the generated bin file not working, and using Chrome fixing that...maybe try doing the prices in Chrome and see goes that goes
dems86 said:
Multiple people have had issues in Firefox and IE with the generated bin file not working, and using Chrome fixing that...maybe try doing the prices in Chrome and see goes that goes
Click to expand...
Click to collapse
I just tried Chrome before I saw your post, and it's doing the same thing as Firefox :/.
Guess, I'll try rebooting? sure why not that solves everything on windows.
*edit*
Yea... no rebooting didn't help.... who woulda thunk it.
*edit EDIT*
Seems like it might be working on my linux box...
*edit edit edit*
Works find on my linux box... I guess you can just get a bootable version of linux and do it.
pbaldw10 said:
. Are there any RUU files I can use to restore the phone?
Click to expand...
Click to collapse
Not yet, official ruu will not be posted until T-Mobile pushes an update and no T-Mobile users have posted system image backup yet.
What you should do is produce your own system backup before modifying your device following the instructions in the twrp thread. Then you can even share that backup with the community so that others may benefit.
Behold_this said:
Not yet, official ruu will not be posted until T-Mobile pushes an update and no T-Mobile users have posted system image backup yet.
What you should do is produce your own system backup before modifying your device following the instructions in the twrp thread. Then you can even share that backup with the community so that others may benefit.
Click to expand...
Click to collapse
I'll work on this tomorrow in my free time, got a newborn to look after so free time is limited these days.
Sent from my HTC 10 using XDA-Developers mobile app
I tried unlocking like 6 times. I keep getting unlocked failed message token wrong size. Starting to really piss me off. Don't know what to do. Any help would be appreciated.
cwalker0906 said:
I tried unlocking like 6 times. I keep getting unlocked failed message token wrong size. Starting to really piss me off. Don't know what to do. Any help would be appreciated.
Click to expand...
Click to collapse
Try submitting your token in different browsers. Many users are reporting issues when using IE or Firefox.
cwalker0906 said:
I tried unlocking like 6 times. I keep getting unlocked failed message token wrong size. Starting to really piss me off. Don't know what to do. Any help would be appreciated.
Click to expand...
Click to collapse
What Browser are you using ? Some people have had to switch browsers for whatever reason
Sent from my HTC 10 using Tapatalk
I got mine on the latest HTC US RUU (no more tmobile crap) after S-offing it and unlocking the bootloader. Now I have xposed, twrp and root and it is working flawlessly. Bye bye Nexus 6.
Behold_this said:
Try submitting your token in different browsers. Many users are reporting issues when using IE or Firefox.
Click to expand...
Click to collapse
Was using ie will try chrome tomorrow. Got pissed and went to sleep before I ended up throwing the computer lol
Behold_this said:
Try submitting your token in different browsers. Many users are reporting issues when using IE or Firefox.
Click to expand...
Click to collapse
dems86 said:
What Browser are you using ? Some people have had to switch browsers for whatever reason
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
I think the issue is with windows in general. Well, the versions of browsers they are pushing out to windows. I got it to work on my Linux box.
TheHeffNerr said:
I think the issue is with windows in general. Well, the versions of browsers they are pushing out to windows. I got it to work on my Linux box.
Click to expand...
Click to collapse
FWIW, Windows 10 + chrome browser, no issue
nvm
Behold_this said:
FWIW, Windows 10 + chrome browser, no issue
Click to expand...
Click to collapse
Interesting... What version of Chrome? SSL has been getting patched left and right and it's been stupid.
The first time I did it didn't work with the unlock.bin they gave me. After I couldn't login to the website for the longest time. Decided to clear browser cache and reboot the computer and then I could log in. The unlock worked the second time. All in all probably took me about an hour to hour and a half to get it sorted out
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...