So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Somebodyz said:
So i kinda ****ed up on trying to install a custom rom, dint make a backup and had wrong bootloader for the rom i had planned. After trying different things to fix it. it went from bad to worse ( i think) and now im stuck in the fastboot menu. TWRP cannot boot up, it has error messages but it go's away fast so i cant see them.
Can i still recover my phone?
Click to expand...
Click to collapse
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
KrisM22 said:
So do you have a backup of stock or anything?
If not, RSD lite latest 7.1.1 stock
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
Click to expand...
Click to collapse
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Somebodyz said:
Did not make a backup no, RSD doesnt see my phone though. how would i go about fixing it? Windows does see my phone as fastboost addison s
Click to expand...
Click to collapse
What version of RSD do you have - it's on the top bar when you stat RSD.
KrisM22 said:
What version of RSD do you have - it's on the top bar when you stat RSD.
Click to expand...
Click to collapse
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Somebodyz said:
the version is : RSD Lite v6.2.4 multi-flash / multiflex tool. is that the correct one?
Click to expand...
Click to collapse
yes, now try a number of different cables. Make sure your phone is in fastboot mode.
That work?
KrisM22 said:
That work?
Click to expand...
Click to collapse
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Somebodyz said:
Tried to find, and failed in, finding other cables since this is the only phone with usb-c. are there other possibilites or should i buy a new cable?
Click to expand...
Click to collapse
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
KrisM22 said:
Only reason I suggested that was because of second post on this thread
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
I did one a couple days ago with an old A to micro cable and a cheap ($3 for 5) Micro female to C male adapter that I got on ebay. Worked fine. Other than that I have no ideas. Sorry. I understand there may be some need to have cables with 56K ohm resisters if used for charging, but I don't have any of those yet - still using old stuff.
Click to expand...
Click to collapse
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Try to reflash the latest TWRP
mijing said:
Try to reflash the latest TWRP
Click to expand...
Click to collapse
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Somebodyz said:
if it try to boot it from cmd or if i try to reflash it, it says: cannot mount /data and unable to find crypto footer. on the top line. RSD Lite sees my phone now though, so do i need to reflash twrp?
Click to expand...
Click to collapse
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it ?
mijing said:
Did you unlock your bootloader before flashing the TWRP?
Twrp reflash is will not be damage our phone you can try it
Click to expand...
Click to collapse
as i said i did try to reflash it and it gave me that message. and yea i did unlock the bootloader first.
Somebodyz said:
So i managed to get it to connect with a different cable (yeay), but i was wondering how much the stock rom version affects stuff? since there seem to be of stock roms to choose from. after ****ing it up i dont want to do that again.
moto z play
product/variant: addison xt1635-02 32gb p7
bootloader: c0.14 (sha-9325e5f, 2016-07-11)
Would anyone be able to give any pointers to what specific one i need?
Click to expand...
Click to collapse
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
KrisM22 said:
Yay!!! cable!!! Who would have guessed!! Thanks @okaban !!!
Which one you choose depends mostly on which country or area you are in because flashing one from another country will mess things up (wrong radio frequencies). Then choose the latest one - never one earlier than where you were at. So what country/area are you in? and I'll try to help you choose.
Click to expand...
Click to collapse
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Somebodyz said:
yea had to wait till today for the cables to arive, hence the delay.
But im from the netherlands (europe). and im guessing the one i was at is from 2016-07-11, atleast thats the date at the BL: message
Click to expand...
Click to collapse
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
KrisM22 said:
Lots of questions for you to answer in here so read till end before start!
Okay. We need an expert (someone in Netherlands who has done it!!!)
I was thinking you were reteu and this post would agree
https://forum.xda-developers.com/showpost.php?p=72013707&postcount=126
though not totally certain.
The only rom I see for reteu is 24-104-25 which if you d/l and expand it (which I did) is 6.0.1 .
- - - - -
I didn't ask - are you able to boot to stock now?
- - - - - - -
Back to first post, you say you got error messages from twrp when you tried to flash a custom ROM. This would be typical if you were still on 6.x bootloader. and trying to flash a custom 8.x ROM.
So:
1) Had you ever updated stock (ota) to nougat?
2) did you go to motorola and unlock bootloader?
if no to update and yes to unlock, let's take @mijing 's idea and reflash TWRP, though I am going to suggest you go back in time a bit and flash this one:
https://androidfilehost.com/?fid=745425885120744582
That one will work for flashing 7.x custom ROMs and is the one I am using at the moment. It will not deal with 8.x custom ROMs but we can easily deal with that later.
To flash TWRP:
boot to fastboot on phone
connect via (good ) cable
On PC in terminal
To temporarily boot this recovery: (substitute actual name of TWRP you downloaded)
Code:
fastboot boot twrp.img
Don't reboot:
use vol up/dn to step to recovery and press power and see if it in fact boots to TWRP.
If it does, then boot back to bootloader and
To permanently flash it: again substitute correct name of img
Code:
fastboot flash recovery twrp.img
If that works that should get you going for flashing 7.x custom ROMs,
though if you want stock you would have to take a CHANCE and RSD that one above. If that works you would still have to flash TWRP. It would NOT affect your bootloader-unlock status.
Click to expand...
Click to collapse
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Somebodyz said:
i dint make a backup at the start so i lost all OS. i dont think i updated the stock the nougat, and i dint know what it meant so i ignored it (basicly where this mess started)
and i did manage to flash the twrp you sent me.
and i dint really want stock i thought it would be better to go back to it.
i want this rom: https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
it says i need a nougat bootloader, do i have that now or do i still need to do stuff to get this rom?
(also a massive thanks for all of your help so far)
Click to expand...
Click to collapse
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
KrisM22 said:
This has all been re-written:
You're welcome! and thanks to @mijing !!!!!!
Wow - we got much further than I thought! Good work!!!
No, I believe you have a MM B/L,
The problem with the 7.x bootloader mod is that once you apply it I believe you can never RSD lite back to 6.0.1 or you will brick your phone and need to send it to Moto for blankflash. Course you may decide that's a moot point.
I don't know if LinOS 14 (7.x) needs a 7.x bootloader - I think I was wrong - I think it may indeed. LinOS 14 should be a good one for you to play with and should flash fine with that TWRP. I also highly recommend
https://forum.xda-developers.com/moto-z-play/development/rom-aospextended-rom-v4-6-amulyax-t3735010
which I flashed yesterday and love.
Both those should flash fine with the Deh TWRP you have on.
Keep us posted.
---------- Post added at 03:14 PM ---------- Previous post was at 03:05 PM ----------
@somebodyz I just redid the above post - a lot was wrong.
Click to expand...
Click to collapse
So adb devices doesnt let me see my device. but adb sideload works. only problem is, is: This package supports bootloaders: 0xc105, 0xC106, 0xC107, 0xC112, 0xC113 and this device has bootloader 0xc014. do i need an older version then or what should i do?
i just found this https://forum.xda-developers.com/showpost.php?p=74069195&postcount=91, is that a good thing for me to do?
Related
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.
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
jayreed1 said:
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
Click to expand...
Click to collapse
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
tabp0le said:
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
Click to expand...
Click to collapse
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
jayreed1 said:
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
Click to expand...
Click to collapse
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
andybones said:
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
Click to expand...
Click to collapse
I read the entire post as you recommended, and I believe I now know how to proceed.
Unfortunately, I've ran myself clear out of free time.
I'll give this a go and report back as soon as I get a few free hours again--probably Friday or so.
Thanks a million!
You guys are very welcome.
Please proceed at your own risk (as with any flashing).
I've tried to make the guide I used as clear as possible and will certainly help if anything is unclear, but keep in mind nougat wasn't out at the time it was created. I don't foresee any issues as really the main thing that is making it boot was anyone that had flashed the us unlocked firmware at any point in time, and I believe people are still converting, The guide is really flashing the us unlocked firmware then back to your (Sprint) RUU.
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
jayreed1 said:
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
Click to expand...
Click to collapse
Nice! Great to finally see some feedback from a sprint user. Wanted to try this myself before I upgrade to nougat firmware. Only thing I'm confused about is you having to erase modem 1&2. What does that mean?
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
jayreed1 said:
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
Click to expand...
Click to collapse
Awesome thanks! Sprint released Nougat OTA yesterday and OMJ extracted firmware that we can flash. Sprint Nougat RUU isn't out yet though waiting for it on HTC's site. Check it out on Sprint HTC 10 XDA dev page. If you flash the firmware and everything still works fine please let me know. Should be trying this if I have time tonight. Have a lot of homework :silly:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
andybones said:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
Click to expand...
Click to collapse
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
Click to expand...
Click to collapse
Very welcome, least I can do.
Nice work on finding the difference. Will certainly save alot of trouble for many!
guys right now what i have to do?
* i updated my htc 10 sprint till the last MM ota, i didn´t make nougat update
* i unlocked my bootloader and install unoficial twrp that i found here
* i have last viper rom
what should i do so i can install other custom roms because right now i can´t pass the boot logo
i´m s off
---------- Post added at 05:27 AM ---------- Previous post was at 05:19 AM ----------
i just need to flash this?
Attached Files
File Type: zip rfg_3.imgs.zip - [Click for QR Code] (1.91 MB, 12 views)
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Click to expand...
Click to collapse
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
beastlymonkey said:
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
Click to expand...
Click to collapse
Are you flashing it while in Download mode or bootloader?
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Are you flashing it while in Download mode or bootloader?
Click to expand...
Click to collapse
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
beastlymonkey said:
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
Click to expand...
Click to collapse
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Click to expand...
Click to collapse
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
beastlymonkey said:
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
Click to expand...
Click to collapse
Yeah I know TWRP is flashed from Download mode, but some stuff apparently still use the bootloader.
Sent from my Sprint HTC 10 using Tapatalk
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Mcandrew2809 said:
Hello,
can somebody upload exactly this FW for this phone?
For 2 SIM cards? Yes
Software channel: reteu
Baseband version: M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST
Kernel: original (stock): 3.18.31....
Android security level: 1 August 2017
Android version: 7.0
Build number: NPPS25.137-72-4
I can't find this ROM anywhere, but reallly need it. Thx in advance.
Click to expand...
Click to collapse
I managed to break my XT1676 also, couldn't find the NPPS25.137-15-11 image either.
I ended up flashing NPP25.137-33 using RSDLite but modifying the flashing script to not flash the partition layout or the bootloader as they are older versions and got it back up and running. If you had that image on the phone previously and you have an unlocked bootloader you can do the same.
Let me know if you need more instructions.
Cheers.
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Mcandrew2809 said:
Thank you for replying, raiamino.
I'd like to ask if is there any other option especially for phones with locked bootloader? I'd like to reflash my phone because it became unbelievably slow and laggy after some time. Factory reset didn't help much.
I flashed a lot of phones in the past (for example Sony Ericsson Xperia X8, Lenovo S60...) but this phone really surprises me about flashing. I found a lot of custom ROMs here on xda and I was thinking about flashing some also, but I'm a little bit scared of it - I don't know, which one is compatible and which isn't (nowhere is written if is custom ROM built for 2/16, 3/16, SingleSIM, DualSIM... variant). I need Moto Gestures feature (really useful thing for me) also, but don't know, if any custom ROM supports it. Do you know about any which will not cause brick (or hard brick) if I will flash it? Thx in advance.
Btw, sorry for bad English, but it's not my native language. Greetings from little big country - Slovakia.
Click to expand...
Click to collapse
you can do the following - warning it will erase everything on internal storage including photos music downloads documents etc - backup to sd card or laptop first if you want to keep these things
put phone into fastboot mode and connect to laptop
In a terminal/command prompt window assuming you have fastboot installed type the following
Code:
fastboot erase userdata
When you restart your phone it will be like the first time you switched it on (albeit with upgraded firmware version)
LineageOS supports moto gestures - For me they all work except shake to open camera app but you can set it to open with a double press of the power button
Flashing a custom rom designed for your phone will not hard brick it as it will never touch the bootloader so you will always be able to enter fastboot mode
Of course you can soft brick which means it either bootloops or you cant access recovery if you don't follow the correct process but you can solve that just by repeating the process correctly
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Mcandrew2809 said:
All right, I will give it a try at evening (not enough time right now). So If I will do the fastboot command...
Code:
fastboot erase userdata
...what will happen? Is it the same procedure as factory reset + wipe cache?
Click to expand...
Click to collapse
yes but it also wipes everything on internal storage data partition
A reset + wipe cache will format data but not user data (things that are stored on internal storage such as pictures music documents downloads)
It does not format system or anything else
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Mcandrew2809 said:
Thank you, it helped a lot! :highfive:
EDIT: what's difference between erase and format in fastboot? Would something bad happen if i do format command instead of erase?
Click to expand...
Click to collapse
Iv no idea - it will either give an error unknown command or do something
erase userdata is the correct use
Hello,
I have the same phone and like to download the stock rom first before flashing a custom one (RR e.g.). I can't find anywhere a download for this version's custom rom yet. Is there any way to save the stock rom out of the still unmodified phone?
Thanks for your help!
Bro.. check this.. npps is for xt 1676 ( Europe, Turkey ) and npp is for xt 1677 ( India) . Both are dual sim 3gb version phones.. just may be customization difference. Hopefully all modem bands may work.
Npps or xt 1676 unfortunately dont have version above 25.137-15 ( which is an older firmware from what u have ) , so never flash it.
But npp have higher version 72/76/82.
Just in case u are not confident enough avoid gpt, and bootloader flashing.
Btw.. if you have messed up ur bootloader ( cant boot into fastboot) .. i think give these files a try.. btw.. you have nothing to loose since u have messed up pretty bad with bootloader.
This is the only last try till Oreo upadate ( if moto ever release it for g5)
Btw.. if u get successful.. please share.
https://www.clangsm.com/forum/index.php?showtopic=482933
---------- Post added at 02:34 PM ---------- Previous post was at 02:16 PM ----------
And if u are worried about modem ( which may cause wifi /signal issue) avoid flashing modem or try flashing old modem from npps25.137-15 ( the file is available in same directory) you can use the modem file only for flashing )
I mean.. first flash the complete npp25.137-76 ( i choose that file because its non branded ) .. after successful boot, check wifi and sim.
If everything is ok.. use the same..
If you have problems with wifi or sim..
Use modem file from npps 25.137-15 and flash modem partion only.
Or completely avoid all trial and error methods. And just flash npp25-137-76 with out flashing modem , bootloader, gpt, - its just like flashing a new kernel and system.. everything except system and kernel will remanin the same.
The method works only if u have a working bootloader. If its not there.. there is no way to trial and error things.. till u courageously flash the bootloader and gpt from npp version..
Hope you will get something.
---------- Post added at 02:51 PM ---------- Previous post was at 02:34 PM ----------
Currently.. my xt1676 is working with August security update ( npps - 25.137-72-4 ) rooted, unlocked.. i am trying hard to mess it up.. unfortunately twrp backup helps me to unbrick few times!! But soon or later i will manage to mess it up!!!???
Only then i will give these files a try... ( Or atlest till pixel 2 comes to retailer near by) . For now this is my backup phone after selling s7 edge.
This is just 2 weeks old.. and i manage to mess its os 5-6 times till now.. so i think i will be joining your club soon
Just the same phone as yours..2 weeks old.. but its alive till now.
showlyshah said:
Just the same phone as yours..2 weeks old.. but its alive till now.
Click to expand...
Click to collapse
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
Take a twrp backup .. a clean one..
tys0n said:
Hi. Sorry for bumping an old thread but I thought it was better then to make a new one.
I bought this phone a few days ago and it had NPPS25.137-72-4 when delivered. Been trying to read up a bit on this device but since I'm used to samsung, it all takes a while to figure things out
Got it unlocked/rooted fine, but I want to make sure I have something to fall back on in case of trouble.
I've been searching for this fw without any luck. Any chance some one got it and can share it?
NPPS25.137-72-4
Or if anyone can suggest a different one that could work. ( I don't really understand the fw names yet)
Thanks in advance.
Click to expand...
Click to collapse
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
showlyshah said:
Take a twrp backup .. a clean one..
Click to expand...
Click to collapse
Smonic said:
There's no flash able zips of stock ROMs here unfortunately. Weird for me too since I was Samsung through and through. Take a back up of your own ROM via TWRP or you can use the debloated stock ROM by Fedray on the ROM forum.
Click to expand...
Click to collapse
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
tys0n said:
Thanks for your answers.Thats actualy first thing I did after flashing twrp to have a clean backup of system and boot.
I also made a few partition backups in terminal, like persist, oem, modem and a few others so hopefully I'm fine.
Do you guys know if I can take stock recovery from lower version fw in case I would ever need it again?
I highly doubt I ever will, but just in case
Edit: If anyone needs a system/boot backup of this fw, just let me know and I'll upload it.
Click to expand...
Click to collapse
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
showlyshah said:
Infact i need a full twrp backup of the exact same firmware.. if u can uplaod.. please do that.. btw.. if u need recovery image i can extract it from ota.. and send to you.
Click to expand...
Click to collapse
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
tys0n said:
Yes please. If you could do that, that would be great
I'll zip the backup and upload it in a few hours when I get to my computer.
Click to expand...
Click to collapse
Me too.. i will do it tomorrow itself.
Ok, here we go. Stock TWRP backup from XT1676.
NPPS25.137-72-4
CEDRIC_XT1676-NPPS25.137-72-4_TWRP.zip
Unzip, put in your twrp backup folder and restore.
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=13304
I got this too..
Hello,
So i wanna go back from 8.1 aosp to stock rom, but i saw these different firmware versions people are talking about on this site like v10f,k,h or something and i don't get what they mean. If i install the firmware from here: https://forum.xda-developers.com/lg-g7-thinq/how-to/guide-how-to-flash-stock-firmware-lock-t3820888 , will it work? And is it the proper one? I had it installed once but only to get back from a bootloop, so I didn't really use it. Also, I checked on this website: https://www.mylgphones.com/lg-phones-software-update-hungary-download-lg-stock-kdz-firmware , i found the exact variant using my imei but there is no download link.
Clickau said:
Hello,
So i wanna go back from 8.1 aosp to stock rom, but i saw these different firmware versions people are talking about on this site like v10f,k,h or something and i don't get what they mean. If i install the firmware from here: https://forum.xda-developers.com/lg-g7-thinq/how-to/guide-how-to-flash-stock-firmware-lock-t3820888 , will it work? And is it the proper one? I had it installed once but only to get back from a bootloop, so I didn't really use it. Also, I checked on this website: https://www.mylgphones.com/lg-phones-software-update-hungary-download-lg-stock-kdz-firmware , i found the exact variant using my imei but there is no download link.
Click to expand...
Click to collapse
Hmmm...i would say don't rush unless you are sure.Maybe someone can help you.But in the past when i had sony (all sony categorie ) device u can flash any customized firmware version of countries of stock firmware as long you have UNLOCKED device.Not sure for lg.Please wait until someone guide you.Also please check link in this thread maybe it has what you need.(under kdz folder).
V10 b,f,k etc are system versions. Like program versions 1.2, 1.3, etc. There are 2 ways of going back to stock. You can use LG bridge to reinstall stock. Just reboot to download mode (reboot, USB , vol+). LG bridge should automatically detect the phone and allow you to update/go back to stock
LameMonster82 said:
V10 b,f,k etc are system versions. Like program versions 1.2, 1.3, etc. There are 2 ways of going back to stock. You can use LG bridge to reinstall stock. Just reboot to download mode (reboot, USB , vol+). LG bridge should automatically detect the phone and allow you to update/go back to stock
Click to expand...
Click to collapse
dev neo said:
Hmmm...i would say don't rush unless you are sure.Maybe someone can help you.But in the past when i had sony (all sony categorie ) device u can flash any customized firmware version of countries of stock firmware as long you have UNLOCKED device.Not sure for lg.Please wait until someone guide you.Also please check link in this thread maybe it has what you need.(under kdz folder).
Click to expand...
Click to collapse
Ok thank you, but i would like to make a full rom backup of the aosp i currently have installed. I don't think i can use twrp cause last time i flashed it, it bootlooped (even with the persistent version) and i had to reflash the boot img etc. I read about making a nandroid backup ( https://forum.xda-developers.com/showthread.php?t=1818321 ) with adb and dd but i would have to backup the entire memory and restore it and i would like not to mess with protected bootloader partitions for example. And i don't know exactly which partitions i want to backup with the method described above bcs there are partitions like recovery-persist and recovery-refresh and i don't know which are the right ones. Is there a way to do it?
Clickau said:
Hello,
So i wanna go back from 8.1 aosp to stock rom, but i saw these different firmware versions people are talking about on this site like v10f,k,h or something and i don't get what they mean. If i install the firmware from here: https://forum.xda-developers.com/lg-g7-thinq/how-to/guide-how-to-flash-stock-firmware-lock-t3820888 , will it work? And is it the proper one? I had it installed once but only to get back from a bootloop, so I didn't really use it. Also, I checked on this website: https://www.mylgphones.com/lg-phones-software-update-hungary-download-lg-stock-kdz-firmware , i found the exact variant using my imei but there is no download link.
Click to expand...
Click to collapse
use https://lg-firmware-rom.com/ to download the latest firmware for your phone with IMEI
---------- Post added at 01:39 AM ---------- Previous post was at 01:30 AM ----------
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Hugask said:
Weird screen behavior, it seem to me that it isn't a hardware fault, cause when plugging in a charger the phone is able to show the MI logo, but not the charging icon
The phone is able to boot and i can hear the phone locking and unlocking, can see that the screen is on because of the backlight, but there is no image, SO FRUSTRATING!!
If you have any idea of what's going on and can give me a tip, i would thank you so much, the phone has been on this state for a long time
Don't know how to upload videos, if you think that can help diagnose it i can upload it and share a link or something
Click to expand...
Click to collapse
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
SubwayChamp said:
What did you do before?
Did you flash something?
Is it device unlocked?
This happen also in fastboot/recovery mode?
Click to expand...
Click to collapse
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Hugask said:
I hadnt updated my Rom, Pixel experience, in a while, so i took the opportunity and flashed an (at the time) beta Pixel Experience Android 10, i reverted and everything was fine for about one day i think, then some artifacting wich would come and go until the display gived up completly (about an hour between the two)
Yes, it is unlocked, and when in fastboot/recovery the screen is lighted up but not showing anything
My guess is that i have a low level firmware issue, as i had problem with those before (was running a custom ROM from day 1, so i had to manually update firware to use newer versions of PE (still pie version) and almost bricked my device
Click to expand...
Click to collapse
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
SubwayChamp said:
Then try the next:
- Flash a different vendor.
- Flash a different kernel.
- Revert to stock ROM, no need to lock or nothing, just flash first the recovery ROM but if it doesn't result then flash the fastboot ROM through EDL, so that you know you can boot to EDL mode without need to open the back cover, this will restore all the original images.
Click to expand...
Click to collapse
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Hugask said:
Ok, so... i think i have all the files, but i'm really lost, how am i supposed to flash the vendor, firmware and stock ROM via fastboot?
Also, i put the device in fastboot, so... thats a win i guess (screen working surprisingtly)
I'm just not finding how to do this, it's been a while that i havent messed with this side of android, if you could help me it would mean the world for me
Click to expand...
Click to collapse
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
SubwayChamp said:
You can flash some images invoking the right partition, I mean, you can flash vendor image onto the vendor partition using
Code:
fastboot flash vendor vendor.img
, and in case you need to flash all the ROM you should use MiFlash tool
Click to expand...
Click to collapse
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Hugask said:
Ok, so... i am NOT keeping up with what i need to do, i found a vendor update in a site but it is not an image, i am so confused, i don't how was i able to mess around with this i am basically a noob, i feel so dumb, this should have been so easy and here i am having trouble
If you could make a step by step instruction or send a link where i can get a vendor .img it would be perfect thanks in advance
Click to expand...
Click to collapse
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
SubwayChamp said:
Ok, update what is the current status of your device, you said screen now displaying, Did you refer only to fastboot mode? Could you see the bunny in fastboot? But booted up on system screen is displaying nothing?
Click to expand...
Click to collapse
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Hugask said:
Yes, that is correct, i can see the fastboot screen 100%, no artifacts, just plain working, still no recovery (if i remember right i have orange fox) or ROM screen
Click to expand...
Click to collapse
And what do you want to do now? Did you unlock bootloader?
SubwayChamp said:
And what do you want to do now? Did you unlock bootloader?
Click to expand...
Click to collapse
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Hugask said:
I actually want to check that, i took the phone to a tecnitician and he may have locked the bootloader
I think the next step would be flashing the vendor, firmwares and stock rom again, right?
Click to expand...
Click to collapse
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
SubwayChamp said:
if your bootloader is locked, you can't flash through fastboot mode either vendor or stock ROM, you should need to use EDL method or you can re-unlock bootloader and this way will work. Anyway i don't understand what actually your issue is.
Click to expand...
Click to collapse
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Hugask said:
The issue is the display not working, and it's gotta be a firmware issue as it's on my desk right now showing a bunny, also i am not used to fastboot flash anything, i just was used to recoveries and what not
Just runned some code and it's locked, this is getting better and better oh boy
How am i gonna unlock this if i can't even unlock the phone? last time with screen working it was already a nightmare, having to wait for miui account, do i have any method of doing this without using EDL?
Click to expand...
Click to collapse
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
SubwayChamp said:
Well, this make sense although it's not clear if you did unlock it previously and after that at some time you did lock it again.
If you didn't unlock it previously you would need to bind your Mi account to the device and enable USB debugging and OEM unlock options but if you didn't before without a screen working you have a more difficult way, confirm me if that is the case.
Anyway I got happily surprised when I bought this device some months ago at the first attempt I could unlock it without have to wait time, try it and see what happen.
Click to expand...
Click to collapse
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Hugask said:
It was unloked and i locked again, don't know if this helps my case or if i am royally screwed up
And yeah, Xioami does make difficult to do the process of unlocking but only to recently released devices, aparently to stop re-sellers to buy the cheaper chinese rom and put the global version on them, i think that when a device doenst get made anymore makes sense that they would make it more easy (i bought the device 2 weeks after launch)
Click to expand...
Click to collapse
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
SubwayChamp said:
Ok, of course this makes a huge difference, if you did unlock it previously then you couldn't receive any wait time, I wonder why you didn't try it if you didn 't. Check if MiUnlock tool unlock your device instantly.
Click to expand...
Click to collapse
OMG THIS WORKED
It's been sucessfully unlocked
Hugask said:
OMG THIS WORKED
It's been sucessfully unlocked
Click to expand...
Click to collapse
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
SubwayChamp said:
Hmm, OK, now you have your way sorted out, you can try with a custom ROM (all of them contain a vendor) or in case a custom ROM doesn't solve it you have to try a stock ROM through Mi Flash tool.
Click to expand...
Click to collapse
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Hugask said:
Ok, but how am i gonna flash a rom with fastboot? Is that a thing?
Also, i don't think the vendor is gonna be my only problem, but also the firmware, is there a way to flash firmware without the recovery and trough fastboot?
Click to expand...
Click to collapse
You can't be sure of that, sometimes the vendor correct the issue, sometimes the firmware.
Firmware it is in the stock ROM that can be flashed either through fastboot or EDL mode (be careful to not relock bootloader or you couldn't enable this time OEM unlock option). Now that you have the way more clear just do a search "how to flash stock ROM on Xiaomi devices either through fastboot or EDL mode", just keep in mind that you don't need to open the back cover of the device, usually from a device off (only on unlocked ones) you could send it to EDL by pressing both volume buttons at same time that it is connected to PC, I gave you the main tips, for the rest you will find a lot of tutorials.