Hello,
I got my Xperia 10 into a bootloop. I'm still able to enter recovery, but I've never been able to get out of the bootloop, no matter what I tried.
I started trying to flash software onto it with Sony Mobile Flasher. I'm using version 0.9.28.0. Every time I try flashing, the process gets stuck on the same line:
Sending getvar:max-download-size
Does anyone know what exactly this means or how I can fix this?
Any help is greatly appreciated. :good:
Did you find a solution, I am facing the same problem.
gluzm said:
Did you find a solution, I am facing the same problem.
Click to expand...
Click to collapse
The problem stopped occurring.
However, I began having problems with the missing flash script. I fixed that and was able to flash firmware from XperiFirm.
Do you have a missing script file as well or is it just me?
Update
Here's an update.
The problem with getting stuck on getvar:max-download-size only occurs if it's the second time flashing the device after initial connection (and any attempt after that I guess).
This means, connect the phone, try flashing. If for some reason you try another flash without disconnecting the phone, it will get stuck.
This has always helped me, not sure if it's a universal solution.
Flash using Newflasher
Chronic2k13 said:
Flash using Newflasher
Click to expand...
Click to collapse
I tried that too, but it consistently reports the same errors as FlashTool concerning this problem.
Kestnix said:
I tried that too, but it consistently reports the same errors as FlashTool concerning this problem.
Click to expand...
Click to collapse
Are you deleting all the TA files before you flash?
Chronic2k13 said:
Are you deleting all the TA files before you flash?
Click to expand...
Click to collapse
Yes, I am. I don't remember whether I deleted all of them or just the ones I didn't want.
Should've I kept some in particular?
Kestnix said:
Yes, I am. I don't remember whether I deleted all of them or just the ones I didn't want.
Should've I kept some in particular?
Click to expand...
Click to collapse
Delete all of them! The one in the partition folder too! Then drag the rest of the folder into the Newflasher folder and then follow the instructions on the Newflasher page
Chronic2k13 said:
Delete all of them! The one in the partition folder too! Then drag the rest of the folder into the Newflasher folder and then follow the instructions on the Newflasher page
Click to expand...
Click to collapse
I see. Thanks! Just curious, that applies to all Xperia phones and all ROMs or is it different for older ones?
Also, is a flash script needed for NewFlasher. I don't think one is, but I haven't looked into NewFlasher as much as I should have.
Kestnix said:
I see. Thanks! Just curious, that applies to all Xperia phones and all ROMs or is it different for older ones?
Also, is a flash script needed for NewFlasher. I don't think one is, but I haven't looked into NewFlasher as much as I should have.
Click to expand...
Click to collapse
I think it's for all Xperias after 2019! No flash script needed. You just have to have fastboot drivers and the drivers for your phone! No need to have your bootloader unlocked either.
Kestnix said:
Hello,
I got my Xperia 10 into a bootloop. I'm still able to enter recovery, but I've never been able to get out of the bootloop, no matter what I tried.
I started trying to flash software onto it with Sony Mobile Flasher. I'm using version 0.9.28.0. Every time I try flashing, the process gets stuck on the same line:
Sending getvar:max-download-size
Does anyone know what exactly this means or how I can fix this?
Any help is greatly appreciated. :good:
Click to expand...
Click to collapse
You can use newflasher(https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426 to flash the firmware
Tried via newflasher, deleted all .ta files, even in boot folder, but i got again and again getvar:max-download-size error. Any solution, please?
Edit: Solved. Forgot to tap on usb debugging option and then allow to computer
Solutions:
1. Tap many times build number to open developer options
2. Turn on usb debugging
3. Connect phone via cable while it is turned on and press Allow when computer asks in it
4. Then try to flash android 10. Write n n n to commands, no need any gordon driver or etc
Maybe need restart phone and pc one time, when you turn on usb debugging and then Allow it
Also i installed android driver, after connect via cable, it was yellow ? <= that sign (in computer > manage > device manager)
Kestnix said:
Update
Here's an update.
The problem with getting stuck on getvar:max-download-size only occurs if it's the second time flashing the device after initial connection (and any attempt after that I guess).
This means, connect the phone, try flashing. If for some reason you try another flash without disconnecting the phone, it will get stuck.
This has always helped me, not sure if it's a universal solution.
Click to expand...
Click to collapse
im facing the same problem, how can i flash again after it got stuck?
imkofficial said:
im facing the same problem, how can i flash again after it got stuck?
Click to expand...
Click to collapse
Try closing the program and opening it again.
Make sure it's always the first flash after opening the program.
That's what solved it for me. Though honestly, this was more than a year ago , new versions of FlashTool might not have this problem anymore? I honestly don't know, haven't tried in a while.
Kestnix said:
Try closing the program and opening it again.
Make sure it's always the first flash after opening the program.
That's what solved it for me. Though honestly, this was more than a year ago , new versions of FlashTool might not have this problem anymore? I honestly don't know, haven't tried in a while.
Click to expand...
Click to collapse
ive tried that and it didnt work
imkofficial said:
ive tried that and it didnt work
Click to expand...
Click to collapse
Also the part with reconnecting the phone for each flash? If none of this works, I don't currently have a solution... Sorry
Related
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
have made a backup? to open recovery?
Shoib said:
My milestone(Telus; BL 90.74) is pretty much bricked. I tried to do this, but like with everything else I do modding wise I failed horribly. It got to the point to where whenever I tried turning on my phone, it would stay frozen on the M logo. I've wasted my entire day searching from blogs to forums to videos trying to fix this but nothing worked. And now my phone won't even turn on unless I access the bootloader menu.
I know I have to reflash the sbf file, but the thing is my computer no longer detects my phone since the disaster. I'm really frustrated and stressed because of this. I thought doing a factory reset would do something but now all of my data on the phone is gone for nothing.
Can anyone please help? I know there's like 7 threads on this, but none of them help even if I follow the instructions step by step.
Click to expand...
Click to collapse
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
maybe try a diffrent computer first or try the official motorola update software?
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
max_avatar said:
have made a backup? to open recovery?
Click to expand...
Click to collapse
No, I haven't made a backup yet. I haven't accessed openrecovery either, the guide gave me a headache.
sileshn said:
Do you get any error shown while going into bootloader mode?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
It says "Battery Ok
Ok to program
connect USB
Data Cable"
smokeymacweed said:
maybe try a diffrent computer first or try the official motorola update software?
Click to expand...
Click to collapse
I could try that by putting an official update.zip so the boot loader will accept. Problem is there isn't any updates further to what I have and froyo womn't come anytime soon unless you were referring to something else.
DummyPLUG said:
press "up" on keyboard when power on, can it be detect by rsd now?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Let me try this. I'm going to bed for now, Ill post results tomorrow.
You can try installing your usb drivers again and try.Since you did not get any error in the bootloader mode, it could be problems with your usb drivers.
Uninstall the usb drivers and reinstall them again. Then try.
BTW, which version of rsdlite are you using?
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
xdazoli said:
Helo
Maybe tray this:
- Download an RSD Lite (I use 4.7)
- Download an GOT firmware from: and-developers.com / sbf:milestone (bottom of site)
- Set the phone to bootloader mode
- Start RSD Lite with Administrator permissions
- Connect the phone
- Select the downloaded sbf file
- When U see phone connected click Start
Sorry for my english
Click to expand...
Click to collapse
Ok, I did everything you said and flashed it with A853_Telus_Firmware_SHOLS_U2_03.10.0__USASHLSMR2TLSB1B2B505F.0R_1FF.sbf. But now it still gets stuck at the moto sign
Edit: I think I might have a solution as I flashed the phone with vulnerable_recovery_only_RAMDLD90_78.sbf which will let me use an update.zip. The only problem is I can't access my memory card and I don't have anything that could at home.
Edit: Ok, I fixed my phone and now it has 2.2.1. Thanks guys, I appreciate the help.
hi. I read somewhere here about rooting using doomlord's method (http://forum.xda-developers.com/showthread.php?t=2440375). my questions are:
1. will this method work for stock Xperia SP? Literally just out of the box, everything stock. running JB 4.1.2 v.254.
2. what are the chances of bricking my phone? i really want to root mine because i want custom ROMs on it but im really nervous because its my only phone, and this will be the first time ill do it.
thanks in advance. appreciate all your replies
1.-Yes, thats the method for .254: You need to flash .257 kernel first.
2.-Sony phones can't get "bricked"...99% of the times they only get a boot loop, which means your SP wont get past the Sony-Xperia logo. In this scenario you need to repair via Flashtool or Update Service. Flashtool is more effective for "bricked" phones.
cachanilla86 said:
1.-Yes, thats the method for .254: You need to flash .257 kernel first.
2.-Sony phones can't get "bricked"...99% of the times they only get a boot loop, which means your SP wont get past the Sony-Xperia logo. In this scenario you need to repair via Flashtool or Update Service. Flashtool is more effective for "bricked" phones.
Click to expand...
Click to collapse
thanks. incase of bootloop, is it easy to repair?
papawil01 said:
thanks. incase of bootloop, is it easy to repair?
Click to expand...
Click to collapse
Yes, just do a lil' research about flashtool and how to turn off the phone.
cachanilla86 said:
Yes, just do a lil' research about flashtool and how to turn off the phone.
Click to expand...
Click to collapse
alright. lastly, what are the chances that ill get my phone to bootloop? is it high, or not likely if i follow the steps thoroughly?
Still nervous about rooting my phone. (sigh)
Sent from my C5303
papawil01 said:
Still nervous about rooting my phone. (sigh)
Sent from my C5303
Click to expand...
Click to collapse
I have done it 8 times, with no problems at all. At first one I have only offline charging bug, but when I repair software with PC Companion, than make root with this method again that solve the problem with offline charging.
But only root? When U first read than do - its unable to brick your phone.
smogf said:
I have done it 8 times, with no problems at all. At first one I have only offline charging bug, but when I repair software with PC Companion, than make root with this method again that solve the problem with offline charging.
But only root? When U first read than do - its unable to brick your phone.
Click to expand...
Click to collapse
i tried rooting my phone two times. but i cant. whenever i run doomlords runme_win file, it says "error: cannot find device" or "error: device disconnected". any ideas? ive mustered enough courage to root my phone and it seems easy, but i dont know why it keeps getting this error. TIA
papawil01 said:
i tried rooting my phone two times. but i cant. whenever i run doomlords runme_win file, it says "error: cannot find device" or "error: device disconnected". any ideas? ive mustered enough courage to root my phone and it seems easy, but i dont know why it keeps getting this error. TIA
Click to expand...
Click to collapse
First of all connect your phone in flashtool, select Devices -> Chek Drivers and check if you have ABD driver installed.
Have you enable USB Debugging? Phone have to be also connected in MSC mode.
And at last. Have you turn off Flashtool before running script??
So on. More questions ask better in "ROOTing" thread. Or at first read this thread from start to the end before aksing quiestions. Theres a lot of answers.
smogf said:
First of all connect your phone in flashtool, select Devices -> Chek Drivers and check if you have ABD driver installed.
Have you enable USB Debugging? Phone have to be also connected in MSC mode.
And at last. Have you turn off Flashtool before running script??
So on. More questions ask better in "ROOTing" thread. Or at first read this thread from start to the end before aksing quiestions. Theres a lot of answers.
Click to expand...
Click to collapse
i think adb drivers are not installed. do you know how? it says: "list of adb devices: none" sorry but i get too flooded with all the info here so i try to ask on this thread. thanks
i have xperia zr cc5502 with 5.1.1 stock installed on it
i have tried to follow CM tutorial on thier site wiki.cyanogenmod.org/w/Install_CM_for_yuga
but when im trying to do fastboot im getting waiting for device's and i do have fastboot installed via android studio
and i managed to get my phone into fastboot mode(blue notification light)
thanks
Did you install the relevant drivers for the ZR? Easiest way to do this would be by installing Flashtool (by Androxyde), which includes a GUI for flashing images via fastboot.
SirVer said:
Did you install the relevant drivers for the ZR? Easiest way to do this would be by installing Flashtool (by Androxyde), which includes a GUI for flashing images via fastboot.
Click to expand...
Click to collapse
i have downloaded the program
i looked online to how to get scatter-loading file
and when i followed the instruction
its says i dont have mtd file or emmc
also i tired to follow the guide here developer.sonymobile.com/unlockbootloader/imei-verification/79e3de6c1cdcb72796f5497654fe1c6769602ea35174b9a25be5cab6f6d90919f8448ef693675ac8fd8b9aa0a0520820d90f6e15c7efd5b0934255d1b7f3ec95
but when i type fastboot devices
i get nothing i return (although i can see the blue light )
That's because you don't have the drivers installed. And I didn't mean SP Flashtool - that's for MediaTek devices. We use Flashtool by Androxyde (Google it) for Xperia devices, and it's a lot less difficult to use (no scatter files, for example). There are several guides on XDA for Flashtool, look for one. In those guides, you'll see how to install the drivers. Also, Flashtool can unlock your bootloader without wiping the internal data or anything, so it's preferable to the normal way.
SirVer said:
That's because you don't have the drivers installed. And I didn't mean SP Flashtool - that's for MediaTek devices. We use Flashtool by Androxyde (Google it) for Xperia devices, and it's a lot less difficult to use (no scatter files, for example). There are several guides on XDA for Flashtool, look for one. In those guides, you'll see how to install the drivers. Also, Flashtool can unlock your bootloader without wiping the internal data or anything, so it's preferable to the normal way.
Click to expand...
Click to collapse
okay i followed the instructions and it said everything went successfully
but from some reason the light switched from blue to red and then no light and now i cant enter any mode(fastboot or recovery)
i used the the instructions here orum.xda-developers.com/showthread.php?t=2658952
edit: if i pull out the battery and then turn it back in and then press the power button it vibrates for a second
edit 2: the phone began to heat up,now it's very hot and it's connected to anything
That's odd... Please state exactly what you did, what you flashed (if you did flash something), and if possible, the Flashtool output for the operations.
SirVer said:
That's odd... Please state exactly what you did, what you flashed (if you did flash something), and if possible, the Flashtool output for the operations.
Click to expand...
Click to collapse
i just gave it to some phone lab and they fixed it
styxxer said:
i just gave it to some phone lab and they fixed it
Click to expand...
Click to collapse
Nice. ?
Did they tell you what the problem was? How much did it cost you?
SirVer said:
Nice.
Did they tell you what the problem was? How much did it cost you?
Click to expand...
Click to collapse
it coast 51.12$ and they said there was a problem with the fastboot:angel:
Woah, $50?! The only way I can think of that justifies $50 for that repair would be if the motherboard was f**ked up and they had to replace it. If that's what happened, then congratulations; most phones don't recover from motherboard damage. ?
SirVer said:
Woah, $50?! The only way I can think of that justifies $50 for that repair would be if the motherboard was f**ked up and they had to replace it. If that's what happened, then congratulations; most phones don't recover from motherboard damage.
Click to expand...
Click to collapse
i dont know what they did,but im glad it's working
also i see when the phone starts up the Entel logo(which is Chilean telecommunications company), can you tell why?
Sounds like your phone magically became carrier customized, which probably means the motherboard was replaced, or a new bootloader/ROM specific to that carrier was flashed.
Thanks for help
Sent from my Lenovo K50a40
Hello,
One week ago, I was using my phone as usual when suddenly froze and I pulled the battery, then I was stuck in boot loop so I decided to go into download mode and reflash it, but I accidentally flashed H811N instead of H811H , now my phone is hard bricked !! " No charging / No download mode / Nothing at all " , is there any way to fix it ?
Thanks
There's a fix a couple posts down. Have you tried that yet?
mjoecarroll said:
There's a fix a couple posts down. Have you tried that yet?
Click to expand...
Click to collapse
Yes I tried but I got some errors ! I don't know why, I think it might be because of I did not find a stock dump (img) of H81110H ?
What errors did you get? Which build did you use?
Also, try this. It doesn't look like he has the system.img available, but you could always try to pull it out of the kdz. There's some directions online.
mjoecarroll said:
What errors did you get? Which build did you use?
Also, try this. It doesn't look like he has the system.img available, but you could always try to pull it out of the kdz. There's some directions online.
Click to expand...
Click to collapse
Thanks a lot for your answer, what it really happened that I manged to make it boot to bootloader for the first time, then I tried to flash the KDZ file, but it stuck on 9% giving me an error, then I tried to go to download mode again but now it gives me blank screen !! ..
mo5br said:
Thanks a lot for your answer, what it really happened that I manged to make it boot to bootloader for the first time, then I tried to flash the KDZ file, but it stuck on 9% giving me an error, then I tried to go to download mode again but now it gives me blank screen !! ..
Click to expand...
Click to collapse
Were you able to try the files I gave you there?
And do you know which error it gave you? You might want to try to fastboot a recovery (put a recovery in the same folder as your adb and fastboot, name it recovery.img, run command "fastboot boot recovery.img", then installing a rom from the recovery), although I haven't tried his method yet so I am not sure if that is even possible.
mjoecarroll said:
Were you able to try the files I gave you there?
And do you know which error it gave you? You might want to try to fastboot a recovery (put a recovery in the same folder as your adb and fastboot, name it recovery.img, run command "fastboot boot recovery.img", then installing a rom from the recovery), although I haven't tried his method yet so I am not sure if that is even possible.
Click to expand...
Click to collapse
I actually the error was about flashing a different version then I tried for another time gave an error of different size of firmware.
When I try to connect the phone to my computer, it appeares as "qhsusb_bulk" and doesn't recognize the phone.
Now I can't turn it on or charge it, or even getting to download mode ! ??
Try using the Google Android adb drivers. Keep trying different USB ports until it works.
mjoecarroll said:
Try using the Google Android adb drivers. Keep trying different USB ports until it works.
Click to expand...
Click to collapse
I tried but still not recognizable, I tried all ports in my computer but still not working .. any other ideas ?
mo5br said:
I tried but still not recognizable, I tried all ports in my computer but still not working .. any other ideas ?
Click to expand...
Click to collapse
Something similar happened on my G2 at one point, so everything I'm saying is going off that.
Firstly, what was the situation of your phone prior to this? Was it rooted? Did it tend to overheat? What are the first three numbers on your serial number?
mjoecarroll said:
Something similar happened on my G2 at one point, so everything I'm saying is going off that.
Firstly, what was the situation of your phone prior to this? Was it rooted? Did it tend to overheat? What are the first three numbers on your serial number?
Click to expand...
Click to collapse
Well I did a really strange thing, in which I put my phone in the freezer, and I got into the download mode again. When I start to flash the KDZ file, I got an error " Erro Code = 0x2000, TOT antirollback version is smaller than device version. " , any ideas how can I solve it ?
mo5br said:
Well I did a really strange thing, in which I put my phone in the freezer, and I got into the download mode again. When I start to flash the KDZ file, I got an error " Erro Code = 0x2000, TOT antirollback version is smaller than device version. " , any ideas how can I solve it ?
Click to expand...
Click to collapse
That usually means you were on marshmallow and tried to downgrade to lollipop. You sure you had lollipop?
mjoecarroll said:
That usually means you were on marshmallow and tried to downgrade to lollipop. You sure you had lollipop?
Click to expand...
Click to collapse
I am actually not sure which version I had !! any ideas ?
Did your notifications show up on your lockscreen?
mjoecarroll said:
Did your notifications show up on your lockscreen?
Click to expand...
Click to collapse
I think I was on Lollipop (5.0) , since i did a quick research and I found out that ..
mo5br said:
I think I was on Lollipop (5.0) , since i did a quick research and I found out that ..
Click to expand...
Click to collapse
What build versions did you use to try to fix your phone?
mjoecarroll said:
What build versions did you use to try to fix your phone?
Click to expand...
Click to collapse
Unfortunately, I don't know I am so sorry...
mo5br said:
Unfortunately, I don't know I am so sorry...
Click to expand...
Click to collapse
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
mjoecarroll said:
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
Click to expand...
Click to collapse
I'll try and let you know what would happen, thanks a lot
mjoecarroll said:
At this point, I'd recommend trying the method with every version on opensource.lge.com newer than the version you tried that gave you the previous error.
Click to expand...
Click to collapse
Unfortunately, nothing worked with me ? what's the next step now ? :crying:
I have an xperia xz3 that was updated to android 10 and then started bootlooping and it wont go out of it. Ive tried to use flashtool and other programs to reflash the software but sadly it isnt recognized with windows on any of my machines (yes i have the drivers installed) It shows up in emma and reveals the imei but im unsure if thats the actual IMEI. I can get the phone into flash and fastboot mode. But it simply comes up as Android with a warning sign telling me my drivers for it arent installed correctly (which they are to my knowledge). I am very aware that many people are having this issue and im curious as to see if its hardware or software related. My phone is in flawless shape besides a few minor scratches. I can provide any more info if needed please help me thanks!
Varied Gamer said:
I have an xperia xz3 that was updated to android 10 and then started bootlooping and it wont go out of it. Ive tried to use flashtool and other programs to reflash the software but sadly it isnt recognized with windows on any of my machines (yes i have the drivers installed) It shows up in emma and reveals the imei but im unsure if thats the actual IMEI. I can get the phone into flash and fastboot mode. But it simply comes up as Android with a warning sign telling me my drivers for it arent installed correctly (which they are to my knowledge). I am very aware that many people are having this issue and im curious as to see if its hardware or software related. My phone is in flawless shape besides a few minor scratches. I can provide any more info if needed please help me thanks!
Click to expand...
Click to collapse
And no it isnt waterdamaged nor does it seem to overheat when being powered on.
Varied Gamer said:
And no it isnt waterdamaged nor does it seem to overheat when being powered on.
Click to expand...
Click to collapse
Try Linux
Maybe your windows has a driver problem
MartinX3 said:
Try Linux
Maybe your windows has a driver problem
Click to expand...
Click to collapse
So you're saying I should make a virtual machine and see if its detected on there?
Varied Gamer said:
So you're saying I should make a virtual machine and see if its detected on there?
Click to expand...
Click to collapse
Yes
Or Boot linux from an USB stick
MartinX3 said:
Yes
Or Boot linux from an USB stick
Click to expand...
Click to collapse
I just booted to linux but how am I supposed to install the device drivers? And also how do I see what's connected linux is confusing lol
Varied Gamer said:
I just booted to linux but how am I supposed to install the device drivers? And also how do I see what's connected linux is confusing lol
Click to expand...
Click to collapse
Just install the android platform tools there for adb and fastboot
The drivers are already integrated in Linux [emoji14]
MartinX3 said:
Just install the android platform tools there for adb and fastboot
The drivers are already integrated in Linux [emoji14]
Click to expand...
Click to collapse
I've got as fastboot installed now. I put the phone in fastboot mode and I typed in fastboot devices and it's showing
"???????? fastboot"
Idk what to do from here I'm not sure if it's recognizing the phone or not
Varied Gamer said:
I've got as fastboot installed now. I put the phone in fastboot mode and I typed in fastboot devices and it's showing
"???????? fastboot"
Idk what to do from here I'm not sure if it's recognizing the phone or not
Click to expand...
Click to collapse
Did you replace your number by ???? ?
Or doesn't really show ???? In the terminal?
I mean your phone is now recognized and you can flash which stock you want with newflasher and xperifirm from XDA.
MartinX3 said:
Did you replace your number by ???? ?
Or doesn't really show ???? In the terminal?
I mean your phone is now recognized and you can flash which stock you want with newflasher and xperifirm from XDA.
Click to expand...
Click to collapse
It appears as a bunch of question marks as stated above. Also when I type the usual things such as fastboot reboot recovery it says unknown reboot target recovery. And when I try to do as reboot recovery it says error no devices or emulators found. But I'll try and install new flasher to see if it detects it
Start newflasher with sudo
OR with the udev package you may install before
MartinX3 said:
Did you replace your number by ???? ?
Or doesn't really show ???? In the terminal?
I mean your phone is now recognized and you can flash which stock you want with newflasher and xperifirm from XDA.
Click to expand...
Click to collapse
I can't seem to figure out how to get new flasher to run on linux. I downloaded it then extracted it but when I click on the .exe file it just brings me to another sub folder with a bunch of data that's confusing. I don't know how to open it or get it to work at all
Use the Linux version
MartinX3 said:
Use the Linux version
Click to expand...
Click to collapse
Can you give me link on where i get that? I couldn't figure it out
Varied Gamer said:
Can you give me link on where i get that? I couldn't figure it out
Click to expand...
Click to collapse
It's in the newflasher XDA thread
The *.x64 file
MartinX3 said:
It's in the newflasher XDA thread
The *.x64 file
Click to expand...
Click to collapse
GOOD NEWS!!
I was actually able to get it to work on windows with newflasher. Turns out that it turns on fine now. But there's a big issue. Whenever I shut it off or restart the phone it goes back into the bootloops until I reflash the software again. Then it will turn on fine and work indefinitely until it's shut off. Do you know what might be causing this issue or how I could fix it?
good news is I'm making progress lol
Varied Gamer said:
GOOD NEWS!!
I was actually able to get it to work on windows with newflasher. Turns out that it turns on fine now. But there's a big issue. Whenever I shut it off or restart the phone it goes back into the bootloops until I reflash the software again. Then it will turn on fine and work indefinitely until it's shut off. Do you know what might be causing this issue or how I could fix it?
good news is I'm making progress lol
Click to expand...
Click to collapse
Nice!
You could try to do a fullwipe with fastboot -w
MartinX3 said:
It's in the newflasher XDA thread
The *.x64 file
Click to expand...
Click to collapse
MartinX3 said:
Nice!
You could try to do a fullwipe with fastboot -w
Click to expand...
Click to collapse
Ok so basically it had a Google lock so I bypassed that and after the bypass it appears to be working normally? I shut it down a few times and turned it back on and it booted up in under 15 seconds! Hopefully it stays that way and I didn't jynx it but all I can do is hope! But for now it is fixed!!! I'm very happy right now as I got this phone for only $33
Varied Gamer said:
Ok so basically it had a Google lock so I bypassed that and after the bypass it appears to be working normally? I shut it down a few times and turned it back on and it booted up in under 15 seconds! Hopefully it stays that way and I didn't jynx it but all I can do is hope! But for now it is fixed!!! I'm very happy right now as I got this phone for only $33
Click to expand...
Click to collapse
Nice to hear
But sadly it sounds like you bought a stolen phone
MartinX3 said:
Nice to hear
But sadly it sounds like you bought a stolen phone
Click to expand...
Click to collapse
Oh no it's not stolen. The person who had it before updated it and got the issue so they sold it off. The imei is clear with no signs of it being stolen. Hope this clears some things up!