Related
hi everyone, add me to the list of idiots that shouldn't be doing things like this...
i bought an xtc2clip and should have stopped there, without using it. i had trouble writing files to the chip through their software (latest 1.18). but while poking around, i got s-off. so far so good. when i tried to copy the files over to unlock the bootloader, it kept giving me an error, so i gave up on the xtc2clip (yes, i changed the ribbon cable many times...).
so just after getting s-off, i was able to install TWRP through fastboot. keep in mind, my phone was still s-off, but bootloader locked. i booted TWRP several times just to check things out... all seemed OK.
i then installed SuperSU, using TWRP. i downloaded the 2.46 zip, placed it on my SD card and installed from within TWRP.
i rebooted, and the phone hung on the red verizon screen... i left it like that for at least ten minutes. i was able to reboot through adb, but it never progressed beyond the red verizon screen.
i did some reading, and found other users in a similar state flashed a new ROM to get around that. i then flashed adnybones' Stock Deodexed *Official* -- 3.10.605.7 i found here on XDA.
now - my phone had updated to the latest firmware - so per andybones' instructions, i flashed the 3.10.605.7 linked from his howto.
the flash went OK. i installed the ROM, that seemed to go OK. i rebooted and observed different boot animation - that was a good sign. then the phone hung for over 10 minutes again, never loading the OS.
now, i can reboot to fastboot or download, but cannot boot the OS. the phone goes immediately to fastboot, and will not boot to recovery. it will boot to download, but not recovery...
so i can't get into TWRP and i can't get into the OS.
help?!?!??!?
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
c5satellite2 said:
I have actually used the clip to s-off a VZW M9. It wasn't able to unlock the bootloader at the time, but I was able to flash TWRP and install SU on the stock OS. I then used the shell command to unlock the bootloader.
You stated that your bootloader was never unlocked, and you flashed a custom rom. If that is the case then you need to unlock the bootloader and reflash your custom rom. You will probably need to flash the same VZW stock rom you had prior to flashing a custom rom.
Click to expand...
Click to collapse
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
c5satellite2 said:
Here is the link to unlocking the bootloader if you are s-off:
http://forum.xda-developers.com/showthread.php?t=3092036
[how to] lock/unlock your bootloader without htcdev(s-off required)
Click to expand...
Click to collapse
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
c5satellite2 said:
Doesn't the clip now support unlocking VZW M9? Update the xtc software and try again maybe?
If not you will need to flash a stock rom, install SU, and follow the instructions from the link above for unlocking. Once you are unlocked you can start flashing roms.
Click to expand...
Click to collapse
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
c5satellite2 said:
This is all based on the assumption that your bootloader is locked.
If I misunderstood or you are actually unlocked and forgot to mention it, please disregard everything above.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
pwhitt said:
the xtc2clip has two methods to unlock the bootloader. neither will work for me... the "bootloader unlock" tab throws an error when i try to copy the files over the the sd card (i've tried multiple cables and repeated many, many times - something isn't right with this hardware). the newer method, in the "special unlock" tab appears to work, but my phone did nothing after booting with the card installed. and yes, i've seen the other discussions, videos and pics of how to install the sd card. i was able to verify the phone sees the card in the OS, and i'm using the sdcard cradle that came with the phone.
the bootloader status consistently read *** LOCKED *** - so there is no doubt about it.
yes - the problem is that i need root in order to follow those... the problem started after flashing SuperSU. i cannot follow that guide unless i have SU working and an adb shell open to the phone. installing SuperSU is what landed my in fastboot-only land.
xtc2clip says it does, and i'm certain people can use it to do so... but i've only gotten errors when it tries to write to the sd card. i have manually copied files to the sdcard in the xtc2clip - that's how i got s-off and supercid. i've had nothing but problems trying to use the xtc2clip, and now with s-off, i'm hoping there is a simpler way to do this through adb / fastboot shell. is there?
yeah - that's all correct. bootloader is locked, s-off, will boot only to fastboot.
where is the original ROM that came with this phone?? i'll try reflashing that...
Click to expand...
Click to collapse
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Mr Troop said:
Follow this
:http://forum.xda-developers.com/verizon-one-m9/general/ruu-vzw-3-10-605-7-0pjaimg-signed-t3277629
Click to expand...
Click to collapse
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
pwhitt said:
well... i did everything to the letter, and the phone doesn't install the image. in download mode, the phone displays a message at the bottom that the sd card isn't mounted. i tried to check the sd card from within download mode, and it displayed something about smart sd card not found, or something similar.
the sd card is formatted exFat, so maybe i need to format it fat32? it's a 128gb card, i can try again with an 8gb fat32, but i thought exFat was supported...
for the record, i did everything to the letter - even copied the file name from the site to avoid typoing the name... it's a zero, not an O, that sort of thing.
i'll post more information when i have time.
any other help??
Click to expand...
Click to collapse
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
OH! well then, i'll give it another go when i get back to it.
Thanks a lot!
Mr Troop said:
Yes format to Fat 32 and it is a zero,also make sure its the only file on the sd card and no bigger than 32gb card
Click to expand...
Click to collapse
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
pwhitt said:
Mr Troop, you're a life saver - thank you very much.
Now if I may be a pest, how do i unlock the bootloader? I keep finding this howto:
http://forum.xda-developers.com/one-m9/general/how-to-lock-unlock-bootloader-htcdevs-t3092036
which is what c5satellite2 pointed me too as well, but this won't work for me since i don't have working SU.
it seems like i need root to unlock the bootloader, but i need to unlock the bootloader (apparently) to get SU...
i have read about 50 different threads spanning the last year+, and I'm not having a lot of luck...
your help is greatly appreciated!
Click to expand...
Click to collapse
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Mr Troop said:
Well done :good:
Yes i have used this or theirs htcdev
dont forget to change title to solved
https://www.htcdev.com/
Click to expand...
Click to collapse
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Mr Troop said:
Just looked and i dont think you can unlock the bootloader by htcdev
will keep looking
Click to expand...
Click to collapse
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
pwhitt said:
right! that's the whole problem. verizon has locked the bootloader, and HTC isn't unlocking verizon phones...
this is killing me. i pay hundreds of dollars for a product, and it's loaded with their bloatware and i can't run an adblocker???
it's insulting.
Click to expand...
Click to collapse
HTC does not allow devices with a Verizon CID to be unlocked.
Your S-Off, You would need a way to switch to superCID (or any other nonVerizon CID) in order to oem unlock.
but not 100% sure so i would leave it and do some research check back tomorrow :good:
I was able to write the super cid, but I can't get the device string ........ Adb barfs, because oem unlocking can't be enabled.
Edit: n/m, saw you tried this already.
I know there's a way to do this, but you'll have better luck asking in the Verizon M9 forums. Many, many people have unlocked their bootloaders, HTC and Verizon notwithstanding.
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
From what I can recall, I did exactly that. Installed twrp, and had it install su. Then I unlocked boot loader. It doesn't make sense, but it worked.
Sent from my HTC One_M8 using XDA Free mobile app
pwhitt said:
OK - will do, however, how do i unlock the bootloader???
i'm hesitant to flash TWRP recovery and try installing SuperSU - since that's what borked it last time... any pointers?
Click to expand...
Click to collapse
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Htcdev to unlock bootloader but you need oem unlocking ticked in the rom.
If adb doesn't work its because you dont have usb debugging enabled in the rom. You only have fastboot access for now. But thats ok because thats all you need to flash twrp 2.9.0.1 and supersu 2.65.
Sent from my HTC One M9 using Tapatalk
shivadow said:
Twrp 2.9.0.1 and supersu 2.65. Only that combo seems to work. That is how mine and many others are set up.
Click to expand...
Click to collapse
I have been using 3.0.0.0 and 2.65 since upgrading to MM and have had zero problems.
Please don't ask why (the answer will be: "because I'm stupid"), but I relocked my bootloader and now my Swift 2 Plus won't boot anymore. When turning it on, it vibrates and the Wileyfox logo flashes for less than a second. After that the screen stays black and nothing happens. Same thing when I try to boot into recovery. I can only boot into the bootloader but I can't flash any images or unlock it again ("FAILED (remote: oem unlock is not allowed)").
Is there any way I can revive my phone or is it lost?
I think your only way is to flash twrp again with fastboot install method :
//twrp.me/devices/wileyfoxswift2.html
And then flash the stock rom :
//cyngn.com/support
hope it will helps you!
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
Sorry, I'm a new user so I can't post link, you've just have to ad "https" at the beginning of the line.
Thanks for answering, but I can't do that, because the bootloader is locked and protected from unlocking. I guess the only thing I can do is ask the support if they can provide the mbn and xml files that are needed for unbricking with QFIL (I can boot into edl mode as I recently found out). They probably won't but it's worth a shot.
If you use the signed zip ( not the fastboot image) the default recovery should be able to install it.
It doesn't boot to recovery. Only fastboot and edl mode work.
You could try flashing fastboot image from http://cyngn.com/support
Sent from my Swift 2 using XDA-Developers mobile app
Thanks, but that doesn't work with a locked bootloader (already tried).
It seems like the only way to revive it is with QFIL, but for doing that it needs the matching mbn and xml files that aren't included in the factory images. Wileyfox support wasn't helpful, either.
xrmnx said:
Thanks, but that doesn't work with a locked bootloader (already tried).
Click to expand...
Click to collapse
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
I'm actually not sure, if I still have root privileges. It could be that I turned it off inside the SuperSU app.
I tried to flash the stock rom and that didn't work, though. Do I have to do something different than usually to flash with root privileges?
boa05 said:
Can't we put the dirty cow bug to a use now? It should work on the phone unless it has the latest security patches, right? And with root privileges you should be able to flash a new recovery or reset the phone.:fingers-crossed:
Click to expand...
Click to collapse
I read a little about dirty cow, now (didn't know much about it before), but if I understand it right, I need adb to upload files onto the phone, right? Sadly, adb doesn't work. Only fastboot :/
Hmmm, there is a similar thread for the Nexus 5X. You might want to check it out if you haven't already ( http://forum.xda-developers.com/nexus-5x/help/nexus-5x-permanently-bricked-locked-t3232105/page2 ).
A few of the suggestions were to try with:
Code:
fastboot flashing unlock
or
Code:
fastboot format userdata
fastboot format cache
I don't know if it will be of any help but it is worth a shot.
You could try to flash individual portions of the stock image like the recovery or the userdata but I doubt that it will be successful.
PS: From the thread above, for some reason removing the SIM card allowed them to enter recovery.
Thanks, but none of these solutions works. Already tried all of them a couple of times....
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
Code:
fastboot update <path/to/zip>
or this one to try to wipe the device? (dunno if the command is still in use, though)
Code:
fastboot -w
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Pak0St said:
Hmmm, how about you try to trick it then?
Grab the official signed firmware, place it on SD Card and try with:
or this one to try to wipe the device? (dunno if the command is still in use, though)
If this doesn't work as well, I guess it will be a waiting game for QFIL files.
Click to expand...
Click to collapse
I tried to flash/update every official rom (with and without -w) there is, but I never put it on an SD-card. Does that make a difference? If so, this might be one ofhe stupidest mistakes I ever made :/
I'll try in a few days. Not much time, at the moment...
Yes... Waiting for QFIL files is what I'm prepared for...
The idea with the SDCard is just a random thought. There is a slight chance to trigger the allowed update policies.
Usually you place the update.zip through adb (not possible in this situation) but placing it on the sdcard is possible.
Still, QFIL is the safest bet once someone uploads the files.
Pak0St said:
Still, QFIL is the safest bet once someone uploads the files.
Click to expand...
Click to collapse
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
xrmnx said:
That's what I thought. Since I couldn't find any (yet), is there a way to extract the QFIL files from a working phone (I bought another one since I needed a phone)? I don't think so, but I hope I'm wrong...
Click to expand...
Click to collapse
I'm in the same boat here, same phone and same issue. Did you find a way to fix it? already searched all internet for a fix. Thanks a lot
Sorry, but for some reason I never saw your answer... I never found a solution either, though
how to unlock bootloader
Use fast boot to unlock the bootloader again.
connect your Swift 2 to your PC and in a command prompt type the following "fastboot oem unlock"
When you press enter, check the phone and using the volume keys you need to select yes and then press power to execute.
Your bootloader should then be unlocked again. Good Luck.
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img ,
{{{ bootloader "NO NEED" This Work Before Just Because v48 and v56 have the same bootloader version }}} , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
EDIT HELLO
Things Have Changed Dont Try To Downgrade Bootloader or The Phone Will Get Hard Bricked , Why well bootloader versions on new firmwares have been upgraded please check all the information on the Bootloader/Fastboot
MODE Of The Phone Which Version You Have , Now For Example If You Are On Version NCQS26.69-64-5 you will need SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml full package then extract and now you will need SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml extract it too , Now Just Move The 2 Oems Images And 4 System Images And Boot Image To SPERRY_SPRINT_NCQS26.69-64-5_cid50_XT1766-SS_7.1.1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml Folder Next Look for RSD_Lite_Motorola_XML_To_Batch_Script on Google Download it And Watch The Video Of Rootjunky on how to use it. Very Simple Wish All Of You Luck And im Not Responsible Of Any Damage Of Your Phone Use This Guide On Your Own Terms.
ozmage said:
You Need From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which Is Not For The XT1766 if You Flash This You Will Loose The Baseband And SoftBrick The Phone .
And From firmware.center / firmware / Motorola / Moto%20E4 / Stock / XT1766 /
XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip This One Have The Ratio And Modem And FsG images Of Your Phone Thats Why We Need It .
Lets Begin , if You Have This Phone You Had Noticed That After Upgrade To The Last Version The Ability To Add Apn And Modify Them And The Hotspot Wont Work Any More This Is Because The Locked Everything Up For No Reason Well Money Is the Reason , We need to Extract XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip in a folder and SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
in other folder , you must know your way to flash servicefile.xml on linux or windows no details here and bootloader unlocked , well that is easy , now we have to put the files : the 2 OEM files , the 4 System Files , boot.img , bootloader , recovey.img from SPERRY_SPRINT_NCQ26.69-48_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip inside the folder that have the XT1766_SPERRY_SPRINT_7.1.1_NCQ26.69-56_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip firmware and replace those files , optional for rooting you can replace recovery.img with the Squid2 TWRP recovery.img file and The boot.img Patched Fixed F2FS kernel which is based in the stock firmware kernel sources that we are going to flash here and then flash supersu inside twrp , Well Thats It after Flashing This Downgrade Custom stock you will have back the ability to ADD apn's Again And Use The Hotspot included in the Stock Firmware , Cheers , Thanks To All The People Involved in the development for Perry Moto E4 Thanks Everybody i hope this help somebody with the XT1766. :laugh:
Click to expand...
Click to collapse
I flashed the Sprint firmware and had data working on my XT1766 after it got it's carrier update, the Sprint firmware does not soft brick the phone as I flashed it and can confirm it doesn't soft brick it, so you are incorrect in saying that.
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
dlinderaz said:
I'm not sure if I did something wrong but after trying this, my phone kept saying, "phone stopped working". I had backed up my phone so I restored it. Any ideas on what might have happened?
Click to expand...
Click to collapse
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
madbat99 said:
Yeah, don't try to restore system apps. Phone app has some quirks, it's in oem. There are oem hide xml files and so on. Why try to restore phone?
Click to expand...
Click to collapse
I restored the entire thing after flashed the indicated files causing the error message.
dlinderaz said:
I restored the entire thing after flashed the indicated files causing the error message.
Click to expand...
Click to collapse
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
madbat99 said:
Oh, I never tried this method. I used rsd lite to flash the firmware (the one op says will brick you, it didn't by the way). After flashing new firmware I restored only data, nothing system or boot related, and have had no issues.
Click to expand...
Click to collapse
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
dlinderaz said:
Thank you so much for the info. I'll give that a try tomorrow. I appreciate your time and help.
Click to expand...
Click to collapse
Keep in mind I have the virgin mobile version (sprint xt1766). Don't know which one you have. Some have had trouble with rsdlite on Windows 10, it worked fine for me though.
I used rsdlite from here
The newest one, 6.2.4 I think
Apn Xt1766
I just want to add apn and want to use hot spot again
As the phone is updated on latest build ..
I don't want the root access..
What's should I try then from previous build , can anyone
Guide me easy steps plz.
Xt1766 how to get working apn
Will anyone confirm
danishamini.saifi said:
Will anyone confirm
Click to expand...
Click to collapse
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
madbat99 said:
The steps are there. Just don't use the root part if you don't want root. Once you switch the files, flash the service file.xml with rsdlite.
Click to expand...
Click to collapse
Thanks, ill try and share the result.
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
danishamini.saifi said:
I've tested it.. It worked for me but there is an issue
With this method occurred as well..
While Turing on the phone " BAD KEY" msg pops up on
Black display for 4-5 seconds and then mobile shows Motorola logo...
Now what is suppose to be done to get rid off BAD KEY msg.
Click to expand...
Click to collapse
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
madbat99 said:
That's normal if you unlock the bootloader. Flash the no verity opt encrypt, or magisk, and it will change from bad key to n/a. But there will always be a message if you unlock the bootloader.
I know you said you don't need root, so that bad key message is there to stay.
Click to expand...
Click to collapse
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
danishamini.saifi said:
oh... i got it, thanks...
just one thing more please, if i go towards rooting the phone as well, will this be removed or N/A or something will be there?
Click to expand...
Click to collapse
N/A will be there. But you can flash a new boot logo to kinda hide it. Instead of a black screen, any logo you want, maybe with a white strip at the top to hide it. I'll get you a link.
Here are some good ones. https://forum.xda-developers.com/mo...om-boot-logos-converted-t3759320/post75787882
And here is the guide to make your own
https://forum.xda-developers.com/moto-e4/how-to/replace-n-boot-image-t3687212/post74118155
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
danishamini.saifi said:
@madbat99
Everything you shared was perfect I made my own logo to hide bad key apn working ..
Now I want to have thebroot access in my phone XT1766..
TWRP IS ALREADY ISTALLED ON THE PHONE AS I AM FLASHING LOGOS..
WHAT SHOULD I INSTALLED TO GET ROOT ACCESS ..
SUPER USER ETC.. PLZ SHARE WITH ME..
and the main reason to have the root access is, I want to block or disable OTA update ..
Plz confirm, how will it be possible ..as I downgraded to get working APN But phone updated again now.
I want the phone to be stopped from being updated..
Plz help me out fixing this..
Thanks
Click to expand...
Click to collapse
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
madbat99 said:
Just don't accept the update. You can root by flashing magisk. You will still receive update notification. You'll need to disable the moto update app. I forget which one exactly. But your phone shouldn't be able to do ota updates once you are rooted with twrp installed. The update will fail.
here is the root thread.
Click to expand...
Click to collapse
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
dlinderaz said:
Thank you. I wish I had known this. I had to flash the stock recovery, etc for the updates to work. A little bit of an unnecessary hastle.
Click to expand...
Click to collapse
Ota updates will likely always fail if you have twrp, or have modified the system in any way. The ota performs many checks (assert props) to see if the system is clean. If any asserts fail, the ota will fail. Even restoring the stock recovery doesn't guarantee the ota will work.
Update: The guys at Razer are just about as clueless as a retail phone carrier. They told me to do the exact same thing, the factory reset and all that, but they don't know what they're doing.
So FYI: IF YOU'RE BOOTLOADER IS LOCKED AND YOUR OS WON'T START, YOU'RE SCREWED.
Okay so I rooted the phone on Oreo, the second to last update, and tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again.
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it.
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader.
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
---------- Post added at 02:07 PM ---------- Previous post was at 02:03 PM ----------
Dashaquavius said:
Okay so I rooted the phone on Oreo, the second to last update, sand tried to update it to the May update, and the update kept failing inside the system update app. So, I tried installing it by flashing it from a computer. Unsuccessfully. So, I booted into TWRP and installed every image manually through TWRP. Bootlooped it. Soooooo I tried to flash the latest stock image from the computer, and it goes through, but the phone refuses to turn on. And I can't even unlock the the bootloader because in the command prompt it says it's not allowed. So I'm stuck with a paperweight that won't unlock any bootloaders and won't even boot into the OS. I think I royally screwed it up and I desperately just wanna use the phone again..
I've tried everything. My drivers are correct, and It just won't cooperate with me no matter what I do to it. It'll either keep booting into download mode or get stuck on the splash screen forever.
I'm literally desperate at this point. I can't do anything with this thing!!! I can't flash anything because it's locked and the phone won't boot into the OS for me to even unlock it..
Click to expand...
Click to collapse
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Roxas598 said:
How did you get twrp with a locked bootloader? :S is that a thing now?
You cant flash the factory images without an unlocked bootloader. So if you didn't check the OEM unlock allowed setting you won't be able to unlock it so won't be able to flash the firmware.
Honestly i think you're out of luck if you can't unlock your bootloader
Click to expand...
Click to collapse
iliais347 said:
Wait how did your bootloader relock itaelf? Because that can happen only with the lock/lock_critical command.
Did you say the factory images fully flash with no errors? Both "fastboot flashing unlock/unlock_critical" don't work?
Click to expand...
Click to collapse
waiflih said:
You should try the flash_all.bat or flash_all.sh script from the latest images. If you want to keep your data just comment or erase the line with the "fastboot erase userdata" in the flash_all.
Be sure to have fastboot in your path
Click to expand...
Click to collapse
1. I didn't flash TWRP with the bootloader in the locked state, it was while it was unlocked.
2. Out of desperation, after flashing the stock images multiple times (while it says errors and maximum download reached and stuff) I re-locked the bootloader with the command thinking it would finally at least boot into the OS, to no avail.
3. Factory images didn't flash without some kind of error.
4. I'm unable to run any kind of commands, it says it's not allowed.
5. I've flashed multiple times, flashed the previous updates and the latest updates, and there's always some kind of error or it's not allowed.
I'm just gonna contact Razer. Apparently, I can't flash anything if the bootloader is locked? And the phone won't even boot into the OS to let me tick the option? I think I'm screwed.
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
waiflih said:
For what you are telling you may have an outdated fastboot version. Can you try flash_all and post the error messages? kinda difficult to help without that
Click to expand...
Click to collapse
It says flashing is not allowed for everything.
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
waiflih said:
Ok that is indeed strange. Take a look at this https://insider.razer.com/index.php...afe-method-warning-rebuilds-partitions.23532/
its for the robin but since you already tried everything else you can give it a shot
Click to expand...
Click to collapse
I just got off with Razer support, they're just gonna send me a new one.
And apparently, absolutely NO OTG support!
Let this thread serve as a warning..
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
parky169 said:
how did you manage to get razer to agree a replacement??.i had a speaker issue and had to send a video of my problem then a week later they finally agreed to replace it.you have done really well for them to accept phone back for replacemnet..as for relocking bootloader as far as i read the other day once you do this phone is bricked
Click to expand...
Click to collapse
Interesting. I sent 2 phones with speaker issues and they offered a replacement for both and gave me shipping labela.
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone
rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?
Well not really. But I follow many instrucciones from differents post and nothing
rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:
I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.
Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/
Ok., I will let you guys know thank you
Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.
You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.
@rectangularspace Link to the standalone platform tools HERE. This is all you need.
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.
rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.
I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.
rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good: