My i9103 is just bricked
PC still recognizes it
I had done unbricking a few times in the past using the tool below
http://forum.xda-developers.com/showthread.php?t=1706572
but I failed to get into download mode this time
here are the final lines of the batch file:
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to createt the partition (code: 10) message: nverror: 0x5 (0x1000005) flags: 0
Can someone help??
try with different system, once had similar kind of issue then i tried in different system and it worked.
mj.vikram said:
try with different system, once had similar kind of issue then i tried in different system and it worked.
Click to expand...
Click to collapse
What do you mean by system?
OS of the PC?
leon090807 said:
What do you mean by system?
OS of the PC?
Click to expand...
Click to collapse
A different computer all together.
The-Droidster said:
A different computer all together.
Click to expand...
Click to collapse
my pc is running dual boot but both are on the same OS
Would trying it on the other OS make a difference?
leon090807 said:
my pc is running dual boot but both are on the same OS
Would trying it on the other OS make a difference?
Click to expand...
Click to collapse
May be you can try it once, i tried it on Win XP and it was giving some problems then i used the same process on my personal laptop running win 7 and it worked....
So i asked you to try it on different system..
mj.vikram said:
May be you can try it once, i tried it on Win XP and it was giving some problems then i used the same process on my personal laptop running win 7 and it worked....
So i asked you to try it on different system..
Click to expand...
Click to collapse
Thanks I'll try
but soft bricking can be saved in most of the cases, right?
AW: [Q] Unbricking my i9103
leon090807 said:
Thanks I'll try
but soft bricking can be saved in most of the cases, right?
Click to expand...
Click to collapse
Yes
Sent from my Galaxy Nexus using xda app-developers app
If doing the same steps with another system does not work
we can do nothing about it?
Does anybody know what does the error mean?
leon090807 said:
If doing the same steps with another system does not work
we can do nothing about it?
Does anybody know what does the error mean?
Click to expand...
Click to collapse
Can you have a look at this-> Click here
kataria.vikesh said:
Can you have a look at this-> Click here
Click to expand...
Click to collapse
I don't quite understand what is it about since I don't have much knowledge in nvflash and bootloader
Is this error of failing to create partition indicating that there is a problem with the partition table?
mj.vikram said:
try with different system, once had similar kind of issue then i tried in different system and it worked.
Click to expand...
Click to collapse
I've tried it on another notebook, but it still shows me the same lines and same errors
any solution?
leon090807 said:
I don't quite understand what is it about since I don't have much knowledge in nvflash and bootloader
Is this error of failing to create partition indicating that there is a problem with the partition table?
Click to expand...
Click to collapse
Its a problem of Partition buddy. Just read carefully the link I have given in previous post.
Related
Hi Guys,
So basically I have a P1000 in my hands. I was asked if I could upgrade it to gingerbread since it was running a slow froyo ROM from a Portuguese provider.
The thing is, since the beginning that I don't have access to ODIN. I can go into download mode but the tablet is not recognized in both windows ( USB Not Recognized - Unknown Device ) and linux ( device descriptor read/64, error -110 ).
Since I wasn't able to get in ODIN I used MobileODIN. I was able to flash gingerbread and I was able to boot but something went wrong because on boot and recovery I had colored lines. This was probably a bootloader issue since MobileOdin doesn't flash it.
After it I made the biggest error, I flashed thru MobileOdin the Overcome Kernel. The flash it self went fine and it was booting after but the big problem for me was that it changed RFS to EXT4, changing the partitions it self leaving me locked to that ROM since MobileOdin doesn't partition.
I didn't realized the impact of the kernel at the time and I basically killed the TAB when I tried to go back to froyo using again MobileOdin. It flashed the kernel but then it wasn't able to boot into recovery and the Tab was freezed in "Galaxy Tab" screen.
The thing is, I JUST NEED DOWNLOAD MODE!!! I'm able to get into it but I can't get a way to get recognized by the PC.
The cable it self is working since it worked with ADB,etc in the ROM.
I tried many drivers, with and without kies, and 5 different PCs (Win7x64,x32, XPx32) and no luck.
Was able to try other cable to but I have the same issue.
Basically I think I'm screwed! I don't think any of the bricked guides apply to me since I can go into Download Mode! I just need to get it detected by some OS.
Any ideas? Thanks!
Use linux with heimdall.
Your descriptor issue is probably irrelevant, maybe linux trying to mount the SD card.
Sent from my GT-N7100 using xda app-developers app
priyana said:
Use linux with heimdall.
Your descriptor issue is probably irrelevant, maybe linux trying to mount the SD card.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Hi!
I already tried heimdall, but the device doesn't show in lsusb.
When using heimdall command line it just says that it doesn't find any device in Download Mode :\
Next thing I was thinking was to take out the battery because I'm really out of options really :|
Not sure if this matters, but I always have this in my machine. (Ubuntu)
create a file /etc/udev/rules.d/51-android.rules
within, add these lines
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
save the file, then do a /etc/init.d/udev restart
that should make the device hot pluggable, detected, in ubuntu.
@edition
Priyana told me about your problem... There was another friend on this community had something like yours...
And these are the private messages between me and him... I hope it will help for you...
salahmed said:
PiracyX said:
salahmed said:
This a zip for USB drivers .... I had also had hard times till I get my tab back... I hope it will work for you...
https://dl.dropboxusercontent.com/u/57742286/P1000 USB Drivers.zip
Click to expand...
Click to collapse
HI there. Thanks for the link. I can't seem to install thse drivers at all. My win7 laptop is x86 and give me a error message about making sure its the right package. On my Win8 systems i execute it but it starts to load then nothing on both Laptop and PC.
Heimdall i can see the unknown device but refused to install drivers from the drivers folder.
Should i create an xp install?
Click to expand...
Click to collapse
You have to install the drivers on windows 8 according to:
1- right click on the setup.exe then select
2- troubleshoot compatibility.
3- run through the wizard selecting that your application was running fine on earlier version of windows ...
Good luck
Regards
Sent while I am driving on the traffic jam ... Lol
Click to expand...
Click to collapse
Regards...
Sent from my Galaxy Nexus using Tapatalk 2
priyana said:
Not sure if this matters, but I always have this in my machine. (Ubuntu)
create a file /etc/udev/rules.d/51-android.rules
within, add these lines
#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
save the file, then do a /etc/init.d/udev restart
that should make the device hot pluggable, detected, in ubuntu.
Click to expand...
Click to collapse
Hi!
I already have that line, the behavior is the same :\
salahmed said:
@edition
Priyana told me about your problem... There was another friend on this community had something like yours...
And these are the private messages between me and him... I hope it will help for you...
Regards...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi!
Thanks for the help but are those x64? Was trying to run in XP x32 but it says is not a valid win32 app. I saw they are 1.3.450.0, are they changed? I think I already tried that version without luck :|
Regards.
These drivers I was using on windows 7 without any issues... But after I used windows 8 I couldn't install them...
It is supposed that they are not changed and am using them for the last two years... I tried Odin 3.07 and it also work great for the tab..
Sent from my Galaxy Nexus using Tapatalk 2
salahmed said:
These drivers I was using on windows 7 without any issues... But after I used windows 8 I couldn't install them...
It is supposed that they are not changed and am using them for the last two years... I tried Odin 3.07 and it also work great for the tab..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi!
Tried the drivers without any luck :\
Tried removing the battery for some minutes too and still have the same problem.
Do you guys think JTAG could help in this situation?
Thanks
Does a device need to be seen by lsusb?
If you do a heimdall flash, does it give error?
Sent from my GT-N7100 using xda app-developers app
priyana said:
Does a device need to be seen by lsusb?
If you do a heimdall flash, does it give error?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
When in Download Mode it doesn't show in lsusb.
Heimdall just says it didn't found a device in Download Mode.
In dmesg the error is " device descriptor read/64, error -110 "
Going for JTAG.
I will let you guys know if it works out.
Thanks for the help
wehere did u get the jtag?
help
please help me my gt-p1000 is hard bricked i can't acces to the download mode or to other else mode i need help because my father gave me that dfirst it was soft bricked i tried to repair it with odin but i accidently auto reboot f.reset time and re-partition but it is only re-partition that needed to be active so i close odin and since it is hard bricked i live in ouagadougou burkina faso so it did that i can have a good reparator it why i came to xda please help me
It is because of your battery. Reinsert it. Even I had the same problem!!
Sent from my HTC Desire 526G dual sim using XDA Free mobile app
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 honor 3c (h30u10). Unlocked its bootloader, Rooted the set, installed miui through TWRP. Working flawlessly.
Handed over the set to one of my friends. He returned it in bootloop. What i tried to recover was:
- Tried to install miui again with TWRP but it failed.
- Tried to format internal partitions but also failed
- All the partitions showing 0 MB size.
TWRP shows E: Unable to mount '/cache'
E: Unable to mount '/data'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount internal storage
and Internal Storage 0MB
- Tried to falsh stock (ROM_H30-U10_V100R001C900B108_SIGNED) rom to re-lock the bootloader.
- The flashing process starts but failed at 100 percent with following error message:
BROM ERROR: S_SECURITY _AC_REGION_NOT_FOUND_IN_SECROIMG (6128), MSP ERROR CODE: 0X00
- It is worth mentioning that when i flashed "H30-U10 V100R001C900B127" with SPFT it flashed 100% Successfully with green circle. But when i switched on the phone it vibrates only.
--Screenshot is attached for reference.
Here are the guies which i tired to follow with no sucess
> http://www.carbontesla.com/2014/08/...-u10-b108-stock-jb-firmware-v100r001c900b108/
Please help......
i dont know if this will help but i had updated from b127 to b320 and unlocked+rooted it and after that while flashing a software called magisk it got softbricked and was not going past the honor logo... i tried to flash the stock b108 rom using 'format and upgrade' option in spf tools and now the phone did not even turn on just vibrated every 15 20 seconds... after hours of searching saw a guy using the download option to flash the stock rom... i tried it and it worked... got my phone back to life... phew...
So as for u , may be the download option works instead of all format
gopinaidu77 said:
So as for u , may be the download option works instead of all format
Click to expand...
Click to collapse
already tried bro but no luck.
I have visited many technicians in the market. According to them it can only be resolved by J-TAG but no body knows how to do that. Anybody here at XDA if knows about J-TAG or something like that please help.
zaheer_rose said:
already tried bro but no luck.
I have visited many technicians in the market. According to them it can only be resolved by J-TAG but no body knows how to do that. Anybody here at XDA if knows about J-TAG or something like that please help.
Click to expand...
Click to collapse
Currently do you have access to TWRP ? or just black screen?
zaheer_rose said:
already tried bro but no luck.
I have visited many technicians in the market. According to them it can only be resolved by J-TAG but no body knows how to do that. Anybody here at XDA if knows about J-TAG or something like that please help.
Click to expand...
Click to collapse
JTAG is a bit expensive. It's a piece of electronic device that will pair with the phone to fix any critical problem.
miststudent2011 said:
Currently do you have access to TWRP ? or just black screen?
Click to expand...
Click to collapse
Currently the set vibrates only when connected with pc during flashing
gopinaidu77 said:
JTAG is a bit expensive. It's a piece of electronic device that will pair with the phone to fix any critical problem.
Click to expand...
Click to collapse
How much expensive bro?
zaheer_rose said:
Currently the set vibrates only when connected with pc during flashing
Click to expand...
Click to collapse
so that means your device is still recognised by PC?
zaheer_rose said:
How much expensive bro?
Click to expand...
Click to collapse
Around $30-50 depends on phone model.
miststudent2011 said:
so that means your device is still recognised by PC?
Click to expand...
Click to collapse
It vibrates only bro. I will post latest results within three days after my exam.
zaheer_rose said:
It vibrates only bro. I will post latest results within three days after my exam.
Click to expand...
Click to collapse
Carry on with your exams ping me once you finish your examinations.
All the best. :good:
zaheer_rose said:
It vibrates only bro. I will post latest results within three days after my exam.
Click to expand...
Click to collapse
But when are back ,please make a new thread with ur issue as title .
Did you solve your issue??
hassanjavaid8181 said:
Did you solve your issue??
Click to expand...
Click to collapse
no bro. its still the same issue.
zaheer_rose said:
no bro. its still the same issue.
Click to expand...
Click to collapse
is it recognizing by pc?
I know its an old thread
I am having the same issue
If I download files of stock rom with DA DL with Checksum I get checksum failed error and if I do it with it I get 6028 secro ac region error
Please help
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
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!