Hi Guys
My phone appears to have died... I was trying to run a few things at the same time. Podcast addict, google maps with directions, gps... and suddenly everything started throwing up error messages and resetting themselves repeatedly!
Suddenly the screen went blank and the phone kept on vibrating!
I tried restarting the phone... it didn't get any further than the Red M (of death).... and it was still vibrating continuously!
I did a soft reset (i think that is what it is called... Power + Vol down) and that finally stopped the vibrating, but it still wouldn't get any further than the Red M...
And that is pretty much all that I get no matter what I try.
I've tried Power + Vol up + Vol down. It just cycles to the Red M, then does the little cricket noise then blank screen, then back to Red M....
I've tried Power + Vol Down + Camera... turns it off... but then if I turn it back on, or plug in a power cable then it goes back into the Red M cycle...
In short my phone is fooked!
Do any of you have any super secret button combos/hacks/magic that can bring my phone back from the dead?
Cheers.
trevthedancer said:
Hi Guys
My phone appears to have died... I was trying to run a few things at the same time. Podcast addict, google maps with directions, gps... and suddenly everything started throwing up error messages and resetting themselves repeatedly!
Suddenly the screen went blank and the phone kept on vibrating!
I tried restarting the phone... it didn't get any further than the Red M (of death).... and it was still vibrating continuously!
I did a soft reset (i think that is what it is called... Power + Vol down) and that finally stopped the vibrating, but it still wouldn't get any further than the Red M...
And that is pretty much all that I get no matter what I try.
I've tried Power + Vol up + Vol down. It just cycles to the Red M, then does the little cricket noise then blank screen, then back to Red M....
I've tried Power + Vol Down + Camera... turns it off... but then if I turn it back on, or plug in a power cable then it goes back into the Red M cycle...
In short my phone is fooked!
Do any of you have any super secret button combos/hacks/magic that can bring my phone back from the dead?
Cheers.
Click to expand...
Click to collapse
Hold Power + Vol- permantly, when phone vibrates leave immediatly power and keep holding vol- until a menue appears. browse with vol- to recovery and select it with vol+
There you can make a factory reset (data-wipe)
ICuaI said:
Hold Power + Vol- permantly, when phone vibrates leave immediatly power and keep holding vol- until a menue appears. browse with vol- to recovery and select it with vol+
There you can make a factory reset (data-wipe)
Click to expand...
Click to collapse
Well... that half worked!
I got to the Boot mode selection menu, then selected Recovery Mode, and got this message...
"read from /dev/block/mmcblk0 failed: I/O error"
Any more hacks?
trevthedancer said:
Well... that half worked!
I got to the Boot mode selection menu, then selected Recovery Mode, and got this message...
"read from /dev/block/mmcblk0 failed: I/O error"
Any more hacks?
Click to expand...
Click to collapse
mmcblk0 is the raw name of sd-card partition. In this case the internal I think (but not sure, try to boot your phone without external sd-card; if that fails too, it is caused by internal)
So I think the solution for the problem is to format the sd-card partition. But your recovery can't access it, that why you have to try it per fastboot/adb or with flashing homemade fastboot.
Gesendet von meinem XT890 mit Tapatalk
cupioscire said:
mmcblk0 is the raw name of sd-card partition. In this case the internal I think (but not sure, try to boot your phone without external sd-card; if that fails too, it is caused by internal)
So I think the solution for the problem is to format the sd-card partition. But your recovery can't access it, that why you have to try it per fastboot/adb or with flashing homemade fastboot.
Gesendet von meinem XT890 mit Tapatalk
Click to expand...
Click to collapse
I think you're right. I've tried it with and without the SDcard and i get the same result.
Also...there is a previous error when the Boot Mode Selection Menu first starts that says
E:Can't read /dev/block/misc
(I/O error)
E:Failed to get BOS sync msg from MISC
Fastboot Reason:
fastboot: max download size: 100MB
Click to expand...
Click to collapse
So....tell me more about this fastboot business...
Your problem is pretty strange, but here you go:
First you need the correct firmware. Download it from this thread http://forum.xda-developers.com/showthread.php?t=2239706
Then you need drivers and the RDS lite software from this thread http://forum.xda-developers.com/showthread.php?t=1974568
There you find more information about the procedure.
Gesendet von meinem XT890 mit Tapatalk
cupioscire said:
Your problem is pretty strange, but here you go:
First you need the correct firmware. Download it from this thread http://forum.xda-developers.com/showthread.php?t=2239706
Then you need drivers and the RDS lite software from this thread http://forum.xda-developers.com/showthread.php?t=1974568
There you find more information about the procedure.
Gesendet von meinem XT890 mit Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try that when I get home. (Why do these things always happen while I'm on holidays?)
Seeing as how I'll be starting from scratch would it be possible for me to say install an alternative android version on there. One of the cyanogen mods for example? Would this require downloading a different firmware?
It isn't looking good...
My phone comes up with this error
E:Can't read /dev/block/misc
(I/O error)
E:Failed to get BOS sync msg from MISC
fastboot: max download size: 100MB
USB connected
Getvar max-download-size
Downloading ...
Flashing gpt ...
E:re-partition failed: Device or resource busy
Fastboot command failed
Click to expand...
Click to collapse
And RSDlite looks like the attached png...
Have I irreversably bricked my phone?
trevthedancer said:
It isn't looking good...
My phone comes up with this error
And RSDlite looks like the attached png...
Have I irreversably bricked my phone?
Click to expand...
Click to collapse
That's not good. I've already got this in mind before. Some part of your internal storage is heavily corrupted. It can't even flash the new partition table (gpt).
I can't say if it's a irreversibly brick, but I doesn't know a solution atm..
Gesendet von meinem XT890 mit Tapatalk
You can always give this a shot:
http://forum.xda-developers.com/showthread.php?t=2184877
I bricked my phone awhile ago trying to use RSDLite (which was a huge mistake), more than few times and that post saved me days of frustration.
Pretty much:
1. Unrar
2 . Install Drivers
3. Turn phone off (if able to)
4. Connect to pc
5. Hold the Camera button and power on until the green light comes on, it'll stay on longer than normal if you have a custom recovery installed.
6. Run the Unbrick.bat
You can try reading up on this, but I can tell you from first hand experience since I was not even able to access the custom recovery (save me an error, that this saved my phone from being nothing than a paperweight.
Bricked and then stuck on red M boot cycle.
Hope it helps.
l
Thanks for all your help guys... I gave in in the end. The phone is still on warrenty so I'm sending it back to Tesco. Hopefully they will send me a new one!
That is going to take about 2 weeks to get though... so in the meantime I think I'm going to get myself a Nexus 5! :victory:
majinfusion said:
You can always give this a shot:
http://forum.xda-developers.com/showthread.php?t=2184877
I bricked my phone awhile ago trying to use RSDLite (which was a huge mistake), more than few times and that post saved me days of frustration.
Pretty much:
1. Unrar
2 . Install Drivers
3. Turn phone off (if able to)
4. Connect to pc
5. Hold the Camera button and power on until the green light comes on, it'll stay on longer than normal if you have a custom recovery installed.
6. Run the Unbrick.bat
You can try reading up on this, but I can tell you from first hand experience since I was not even able to access the custom recovery (save me an error, that this saved my phone from being nothing than a paperweight.
Bricked and then stuck on red M boot cycle.
Hope it helps.
l
Click to expand...
Click to collapse
worked! my display is on thank u very much!!!!!
majinfusion said:
You can always give this a shot:
http://forum.xda-developers.com/showthread.php?t=2184877
I bricked my phone awhile ago trying to use RSDLite (which was a huge mistake), more than few times and that post saved me days of frustration.
Pretty much:
1. Unrar
2 . Install Drivers
3. Turn phone off (if able to)
4. Connect to pc
5. Hold the Camera button and power on until the green light comes on, it'll stay on longer than normal if you have a custom recovery installed.
6. Run the Unbrick.bat
You can try reading up on this, but I can tell you from first hand experience since I was not even able to access the custom recovery (save me an error, that this saved my phone from being nothing than a paperweight.
Bricked and then stuck on red M boot cycle.
Hope it helps.
l
Click to expand...
Click to collapse
Nothing works on my razr except the green led, it doent even vibrate.
i tried various combinations of these unbrick.bat, nothing solved my issue.
but there is still that windows connection sound when i link it up...
micash said:
Nothing works on my razr except the green led, it doent even vibrate.
i tried various combinations of these unbrick.bat, nothing solved my issue.
but there is still that windows connection sound when i link it up...
Click to expand...
Click to collapse
The green led and black screen indicates that you are in medfield flash mode (when using camera button to start). If after the windows sound u have something with 'medfield *' under device manager the drivers work.
And if then the unbrick.bat don't work u need to do it manually or there is another problem.
If u don't have the device in device manager, u will need to install the drivers correctly.
Hazou said:
The green led and black screen indicates that you are in medfield flash mode (when using camera button to start). If after the windows sound u have something with 'medfield *' under device manager the drivers work.
And if then the unbrick.bat don't work u need to do it manually or there is another problem.
If u don't have the device in device manager, u will need to install the drivers correctly.
Click to expand...
Click to collapse
How do you mean i have to do it manually? The medfield drivers seem to be installed properly i checked in device manager.
I guess my bootloader was totally destroyed after i tried to flash (apparently the wrong version of) TWRP over CWM.
I was on your kitkat 4.4.4. before
micash said:
How do you mean i have to do it manually? The medfield drivers seem to be installed properly i checked in device manager.
I guess my bootloader was totally destroyed after i tried to flash (apparently the wrong version of) TWRP over CWM.
I was on your kitkat 4.4.4. before
Click to expand...
Click to collapse
U could try to do the commands manually and see what kind of errors u get.
But how can the bootloader get corrupted while u are flashing the recovery. Weird error u got there.
Hazou said:
U could try to do the commands manually and see what kind of errors u get.
But how can the bootloader get corrupted while u are flashing the recovery. Weird error u got there.
Click to expand...
Click to collapse
While flashing it seem the process has stopped on the phone because i did wait about an hour so i forced a reboot and boom.
OK ill try with cmd later on and report my results. But i wont bet on success here...
Hazou said:
U could try to do the commands manually and see what kind of errors u get.
But how can the bootloader get corrupted while u are flashing the recovery. Weird error u got there.
Click to expand...
Click to collapse
I tried to run manually this line at first:
xfstk-dldr-solo.exe --fwdnx dnx
after 5 seconds it disconnects the medfield toolkit in device manager. Tried with this one:
xfstk-dldr-solo.exe --fwdnx dnx --fwimage ifwi --v
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Strange USB I/O Exception, though medfield stays connected the whole time.
micash said:
I tried to run manually this line at first:
xfstk-dldr-solo.exe --fwdnx dnx
after 5 seconds it disconnects the medfield toolkit in device manager. Tried with this one:
xfstk-dldr-solo.exe --fwdnx dnx --fwimage ifwi --v
Strange USB I/O Exception, though medfield stays connected the whole time.
Click to expand...
Click to collapse
That seems like an EMMC error. Something this device has sometimes. Some get it, most don't. You are probably one of the unlucky ones.
bad news..is it irreparable with that or any way to get a fix on it?
Related
Hello LG-2x owners !
I am in a big mess!
I just installled a new rom: http://forum.xda-developers.com/showthread.php?t=1699066
My Problem:
When I start my phone , it stucks in the boot. The bootlogo appears, it loads a few seconds and then it just reboots. Over and over again. No deal, I dealed allready with a thousands of bootlops but I cant enter the recovery menu in this case.
Why not? I push all the buttons like Power + Volume Up or Power + Volume down but it enters the boot.
I am so confused and out of plan.
How could I fix it?
Please help me XDA-Community!
Are you pressing the volume and power button past the first LG logo (white only) until you get to the second LG logo (with blue halo in background)?
Try releasing the keys only after you see the second logo.
Sent from my LG-SU660 using xda premium
Thanks for your reply, buddy
I really appriciate it.
The logo wih the colorfull background is not appearing. Thats the main problem, the entrance to the recovery is not there anymore. No colorfull lg logo, nothing.
Its like this: I push the requiered buttons at the very beginning, while pushing this buttons the phone starts. The LG Logo appears (without Background) and the bootlogo appears from this rom.
You might have to reflash your phone and start all over again. Check here for an emergency flash.
Assuming you have it backed up, you can also try this to hard reset:
http://www.knowyourmobile.com/lg/lg...3107/how_to_hard_reset_the_lg_optimus_2x.html
aragorn7 said:
Assuming you have it backed up, you can also try this to hard reset:
http://www.knowyourmobile.com/lg/lg...3107/how_to_hard_reset_the_lg_optimus_2x.html
Click to expand...
Click to collapse
This will ONLY work if you're able to boot your phone normally, and able to access the menus. And if he has CWM installed, holding the power button + vol down will enter CWM automatically. Correct me if I'm wrong!
korgndm said:
This will ONLY work if you're able to boot your phone normally, and able to access the menus. And if he has CWM installed, holding the power button + vol down will enter CWM automatically. Correct me if I'm wrong!
Click to expand...
Click to collapse
Hes right. I allready tried it. Not working.
Could you PLEASE make a detailed guide for me?
I just dont understand how to install ne nv flash drivers and stuff.
Please make a tutorial for me becuase I dont get the other one
Take a look here.
I saw this link allready but I dont understand the thing with installing the "ATX drivers".
I dont understand it because I got german windows and on top of that there are no photos or anything to know what he means so could you make something else to make it easier to understand?
Do you have take out the accu, take back in, and then hold power and vol-down till 2. boot logo appeared?
Gesendet von meinem HTC One S mit Tapatalk 2
it cant be more easy.
after you pull out the battery you press vol down vol up and connect with data cable to pc. nothing appears, but you go to control panel, then to system and there to device manager, you will se list of all devices and one of them will have some symbol. i think its question mark, you will click it with right mouse button and choose update driver, you will click find driver manually and find the directory with driver extracted from downloaded archive. click ok and driver is installed.
then you can navigate in windows terminal to folder with extracted archive and run the *.bat script with internal or external storage. you can download archive with whole rom on other threads or forums and by run the *.bat load new rom t phone
XXMrHyde said:
Do you have take out the accu, take back in, and then hold power and vol-down till 2. boot logo appeared?
Gesendet von meinem HTC One S mit Tapatalk 2
Click to expand...
Click to collapse
I did everything like described by the other links. It looks like this emergency flash is the last chance to get the game on.
Could you please explain me how I can install this apx driver ?
Zakkusu said:
I did everything like described by the other links. It looks like this emergency flash is the last chance to get the game on.
Could you please explain me how I can install this apx driver ?
Click to expand...
Click to collapse
The instructions on how to install the apx driver is here (see step #2):
http://forum.xda-developers.com/showthread.php?t=1327599
I did it !
Thank to the guide and to you guys, thanks a lot !!!
INSTALLING NVFLASH UTILITY (USING WINDOWS 7)
1. Download NVFlash Utility and Drivers here, and extract to a location of your choice (e.g.: Desktop);
2. Turn off your phone, remove the battery, SIM card and external SD;
3. Hold VolUp + VolDown buttons at the simultaneously and plug in your USB cable (if you use a desktop computer, I recommend using your rear USB ports). Your phone will show a black screen and you should see Windows trying to install a new device, but failing.
4. Right click on the notification showing a failed driver instalation (bottom right corner of your screen), and select 'Update device driver';
5. Select 'Browse computer...', and then select 'Let me pick...', followed by 'Have disk'.
6. Browse to directory you extracted the the zip you downloaded earilier, and point to 'usbpcdriver';
7. Accept any warnings, including the big red alert (you may need to disable UAC);
8. Now in Device Manager under 'USB Controllers' you should have an 'NVIDIA USB Boot-recovery driver for mobile devices';
If everything goes alright, you should now be prepared to flash your phone using NVFlash.
FLASHING YOUR DEVICE
This is the easy part.
Just go to the folder where you extracted the zip, and run 'flash'.
Wait until the utility works its magic and when complete, disconnect your phone from the USB cable, put the battery back in and SIM Card, and reboot to the stock LG ROM.
First boot might take a while, but it will eventually boot and that's all there is too it.
Hope this helped!
Credits to djmcnz @Modaco for the guide.
My screen stuck in "Unlocked Booloader.." and reset again and again, (this happended after i'm root it). I've tried many ways to fix it, include: http://forum.xda-developers.com/showthread.php?t=2218273. but have nothing..
The problem is that my computer doesn't reconigse my mobile. I can't go to "Recovery screen" by holding both "Power button and vol -" or ues file .bat. It still warning" device not found" and reset my phone despite of my drivers are fully installed
Sorry you guys because of my English, its not very well..
I'm very appreciated if any one find the way to fix it for me, i'm very confused now . Is it will be bricked forever ??. My moto xt890 is only 3 days old
Are you sure you booted it up correctly? Try holding down power and vol - until it vibrates. As soon as you feel it release power and hold vol - only. You have to be really quick though. Then you should be able to go to fastboot and reflash a new system image.
You can use this tutorial for more instructions: http://forum.xda-developers.com/showthread.php?t=2157162
Gesendet von meinem XT890 mit Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=2218273
Try asking the OP in this thread, he might be able to help
Hi there i have rooted my phone with doomlord's latest rootkit for c6603 UK devices (you can tell im a noob), when installng and the opening he chainfire 3 app it asked me to install some graphics drivers and i did, it then restarted and then the loop restarted (turns off after sony logo, doesn't even get to xperia logo, then turns back on). I have tried several fastboot and flash methods but the problems still persists, does anyone know of any recovery or factory reset methods wihtout having access to your xz?
Thanks
1. Hold on boot volum up and power for 12 seconds i think.
Or
2. Charge the phone and see what's happening
Gesendet von meinem C6603 mit Tapatalk
charging it goes into a reboot loop then after a few times it displays battery meter...
ive tried flashing with flashtool but it comes up with "For flashtool, Unknown Sources and Debugging must be checked in phone settings", no idea how i gonna do that though, anyway to flash without this on? maybe fastboot?
avi312singh said:
ive tried flashing with flashtool but it comes up with "For flashtool, Unknown Sources and Debugging must be checked in phone settings", no idea how i gonna do that though, anyway to flash without this on? maybe fastboot?
Click to expand...
Click to collapse
I assumed you installed chainfire 3D app.
So, if you want to flash with flashtool, you must set your phone in flash mode.
Hold vol - when plugging the usb cable in (with phone powered off).
If you got the loop, plug the USB cable pressing vol - at the moment the phone is off.
And it may warn you about usb debugging, etc but just ignore it and continue anyway. Ive got back from bootloops with this regardless of unknown sources or debugging. Usually even when bootlooping the hard shutdown will work, hold power and volume up untill the phone vibrates three times and turns off. You may feel it vibrate once, ignore and keep holding.
You do need the correct adb drivers installed to use flashtool, the downloaf here at xda i believe includes them you just have to open the drivers folder, open the exe and choose your phone from the list. If you get into flashboot mode (when you hold volume up and plug it into the computer the led should flash once to let younknow its in the right state. Sometimes flashtool will take a long time to prepare the files for flashing amf your phone will start up... Let flashtool finish prepping, then it will come up with a screen telling you to put the phone in flashmode (usually giving the wrong instructions to do so, ignore them) if so, now go ahead and unplug your phone, power it down via the hard shutdown function i mentioned, then hold volume up and plug it back in. If you get the led flash its working, and if it wont then install its because your drivers arent installed properly.
Also i may be wrong, but the chainfire 3d drivers are for older versions of android, dont try to install them again. I did this on another phone that I had upgraded to jellybean and ot softbricked it. Jellybean runs ope GL fine on this phone.
Ive installed official frmware on my phone (through flashing) and now im about to root it again.
Thanks
avi312singh said:
Ive installed official frmware on my phone (through flashing) and now im about to root it again.
Thanks
Click to expand...
Click to collapse
I have kind of the same problem here, can you please tell me how you solved it?
Hey guys,
A while back I tried to root my Xperia T and putting CWM on it. Something went wrong and I don't exactly know what. It went into a boot loop.
Every time it starts up, the LED turns purple for a couple of seconds and it reboots again. I waited for the battery to drain and honestly forgot about it.
Now i found it again and i want to get it out of the boot loop. The wierd thing is that I can get into ClockWorkMod recovery but nothing else. When in startup and I push VOL- it goes into CWM without a problem. It's like the normal firmware is missing and it can only get into CWM. Is this possible?
And i am trying to flash the stock firmware on it. But when i try to connect with my pc (drivers an flashtool in place and working) it doesn't really seem to connect. It worked 1 time out of the last 5 tries. But when i tried to flash, it said ERROR. The phone get's the blue LED when i connect it. but this only workes if my timing is exactly right in the boot loop. I will try to manage it again to get some screenshots.
I'll update when i have screenshots and everything (with the proper ERROR code)
In the meantime, does anyone have any clue of what is going on?
Thanks:good:,
Flip
flipster112 said:
Hey guys,
A while back I tried to root my Xperia T and putting CWM on it. Something went wrong and I don't exactly know what. It went into a boot loop.
Every time it starts up, the LED turns purple for a couple of seconds and it reboots again. I waited for the battery to drain and honestly forgot about it.
Now i found it again and i want to get it out of the boot loop. The wierd thing is that I can get into ClockWorkMod recovery but nothing else. When in startup and I push VOL- it goes into CWM without a problem. It's like the normal firmware is missing and it can only get into CWM. Is this possible?
And i am trying to flash the stock firmware on it. But when i try to connect with my pc (drivers an flashtool in place and working) it doesn't really seem to connect. It worked 1 time out of the last 5 tries. But when i tried to flash, it said ERROR. The phone get's the blue LED when i connect it. but this only workes if my timing is exactly right in the boot loop. I will try to manage it again to get some screenshots.
I'll update when i have screenshots and everything (with the proper ERROR code)
In the meantime, does anyone have any clue of what is going on?
Thanks:good:,
Flip
Click to expand...
Click to collapse
Blue LED means you're in Fastboot mode, you need to put it into Flashmode (green LED) for it to work. If Vol Down puts it into Fastboot mode, then Vol Up would put it in Flashmode (I assume). Considering you're talking about timing, then it seems you don't know how to put it into Fastboot/Flash mode properly.
1.- Turn off your phone.
2.- Connect the USB cable to your computer
3.- Open Flashtool
4.- Press down the corresponding volume button (keep it pressed), and connect USB cable to your phone
Alternatively, you could also connect your sdcard to your computer and copy a flashable ROM to it, then flash it in recovery. It seems your /system partition/folder is either incomplete or damaged.
Antiga Prime said:
Blue LED means you're in Fastboot mode, you need to put it into Flashmode (green LED) for it to work. If Vol Down puts it into Fastboot mode, then Vol Up would put it in Flashmode (I assume). Considering you're talking about timing, then it seems you don't know how to put it into Fastboot/Flash mode properly.
1.- Turn off your phone.
2.- Connect the USB cable to your computer
3.- Open Flashtool
4.- Press down the corresponding volume button (keep it pressed), and connect USB cable to your phone
Alternatively, you could also connect your sdcard to your computer and copy a flashable ROM to it, then flash it in recovery. It seems your /system partition/folder is either incomplete or damaged.
Click to expand...
Click to collapse
Hey,
thanks for the reply.
The problem is that i can't turn the phone off. The only way it stays off is when the battery is dead. Like it is now. I have just tried what you said. VOL- gives the green LED for flashmode. But even when it is in flashmode and connected with my pc(pc also said it's connected) it keeps rebooting. So the connection switches on and of every 30 seconds or so. I found out that there was a wrong file in the flashtool firmware folder. after trying to flash the standard firmware it tried to do something else. I've removed the file and set it up right.
When it was connected (green light and everything) I got this;
"09/025/2014 17:25:27 - ERROR - (Bundle.java:440) - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin"
"09/025/2014 17:25:39 - ERROR - (Bundle.java:440) - Cannot delete C:\Flashtool\.\firmwares\prepared\system.sin"
And that was all. I will try again in a few minutes, but maybe I missed something.
[EDIT]
Tried a few more times. VOL- to flashmode, connected with pc. Flashtool starts loading the green bar.
After a couple of minutes it stops and Flashtool says this:
09/021/2014 18:21:11 - ERROR - (X10flash.java:523) - Read error :31 : Een apparaat dat op het systeem is aangesloten, werkt niet.
09/021/2014 18:21:11 - ERROR - (X10flash.java:524) - Error flashing. Aborted
(Een apparaat dat op het systeem is aangesloten, werkt niet. -> English -> The device that is connected to the system, doesn't work.)
And the thing that irritates me most of all is the X10flash.java:52.. part. Why does it say X10flash when a Xperia T lt30p is connected en i'm trying to flash LT30_9.2.A.1.205_CH or LT30p_9.2.A.0.295_Generic IT.
I can't wrap my head around it.
I put some attachments in here so you can see what I see. Can someone see what I'm doing wrong or not doing at all?
I seriously do not know how or why. But i did it. Flashtool did not give a log or anything(with previous phones i saw a long list.) it looked like it did not do anything. but the phone is booting into android as we speak!
Thanks for the help Antiga Prime! not a lot, but enough!:laugh:
Now i need to find out how to delete all thisXD
Take the battery out and in, then leave it connected to the charger for one full day, don't do anything with it.
Xperia T doesn't let you take out the battery that easy. But it's fixed. I just need to know how to delete this thread
Sent from my C6903 using XDA Free mobile app
Hey, everybody!!
I seem to have incurred an issue while I was manually trying to install an OTA update in my Samsung Galaxy M31s through the ODIN Mode with the help of this video...
After I successfully followed all the steps in the video... after the last step when ODIN showed in pass in bright green colour. So it did in mine.
My phone rebooted as predicted in that video, only to get stuck in the endless Download/Odin Mode. Now, whatever I do, including pressing the Volume Down + Side key (for 7 seconds) while it's connected/disconnected to/from the PC... it keeps booting into the Download mode... I also tried pressing the Volume Up + Volume Down + Side Key(altogether), yet it keeps booting into the Download mode...!! Can you please suggest me a fix for this ASAP, 'cause I'm scared AF for my phone right now, and the data it stores. PLEASE HELP!! And...
Thank You(in advance)!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's some vbmeta issue...
Try going back to download mode or recovery and flashing null vbmeta.img... and then your patched firmware again...
-> For booting again to recovery mode:
▪︎ Press vol_up + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & power key and connect cable it will take you to recovery
mode.
-> For booting again to download mode:
▪︎ Press vol_down + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & down and connect cable it will take you to download mode(Note: Even after having experience sometimes this trick take me 2-3 tries, so don't get dishearted easily).
Correction...
That was vol_up(not down) for recovery mode (typo).
killerboychetan said:
It's some vbmeta issue...
Try going back to download mode or recovery and flashing null vbmeta.img... and then your patched firmware again...
-> For booting again to recovery mode:
▪︎ Press vol_down + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & power key and connect cable it will take you to recovery
mode.
-> For booting again to download mode:
▪︎ Press vol_down + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & down and connect cable it will take you to download mode(Note: Even after having experience sometimes this trick take me 2-3 tries, so don't get dishearted easily).
Click to expand...
Click to collapse
Hey, for some reason neither ODIN nor my computer can to recognize that my phone is linked to it. Even after installing the Samsung Mobile Drivers for Windows, I gave it a shot. However, I was out of luck there as well, and my phone continued to refuse to appear in ODIN or be recognized by my PC.
I also tried using your approach to start it in recovery mode, but it didn't work either; all it did was boot into Download mode after displaying the Samsung logo. I believe it may be that my PC isn't picking up my device by itself.
How should I proceed?
killerboychetan said:
It's some vbmeta issue...
Try going back to download mode or recovery and flashing null vbmeta.img... and then your patched firmware again...
-> For booting again to recovery mode:
▪︎ Press vol_down + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & power key and connect cable it will take you to recovery
mode.
-> For booting again to download mode:
▪︎ Press vol_down + power key [for few secs](it will force restart your phone)
▪︎ As soon as black screen appears, press vol_up & down and connect cable it will take you to download mode(Note: Even after having experience sometimes this trick take me 2-3 tries, so don't get dishearted easily).
Click to expand...
Click to collapse
Although my device does seem to show up when I connect it to another phone (same model in this case), but yet when I open in the settings, the USB transfer is controlled by my device which is currently stuck in Download mode, and I can't seem to switch it back to the functional device.
And one more thing, I know that my PC's USB is working since, before the flash ODIN, as well as my PC were able to detect my device... but after the Download mode boot loop, none of the attempts seem to be identifying my PHONE...
Thanks @killerboychetan your help is much appreciated!!
I hope we're able to fix this thing together
_HuH_x86 said:
Although my device does seem to show up when I connect it to another phone (same model in this case), but yet when I open in the settings, the USB transfer is controlled by my device which is currently stuck in Download mode, and I can't seem to switch it back to the functional device.
And one more thing, I know that my PC's USB is working since, before the flash ODIN, as well as my PC were able to detect my device... but after the Download mode boot loop, none of the attempts seem to be identifying my PHONE...
Thanks @killerboychetan your help is much appreciated!!
I hope we're able to fix this thing together
Click to expand...
Click to collapse
Ok, got you...
See bro, as like windows have secure boot Android also has AVB(Android Verified Boot). While flashing anything other than pure stock stuff, you need to disable AVB(if what you are flashing has not something to disable it) & to disable AVB, you have to flash null vbmeta.img to set AVB to zero.
[ Note: vbmeta is some sort of file which has verify boot metadata]
So, basically you are exactly not in flashing page of Download mode but rather in AVB warning page, to to get out of AVB warning you have to let phone battery die... [if it ain't]
& as far as i know restart drains battery a lot faster(i even tied my friend phone's vol_down & power button with something, when he get into a similar situation)
And when the battery completely died, pressed vol_up & down key together & connected the cable & then it went to real Download mode than i flashed stock on that case but in your case flashing null vbmeta will work.
killerboychetan said:
O
Ok, got you...
See bro, as like windows have secure boot Android also has AVB(Android Verified Boot). While flashing anything other than pure stock stuff, you need to disable AVB(if what you are flashing has not something to disable it) & to disable AVB, you have to flash null vbmeta.img to set AVB to zero.
[ Note: vbmeta is some sort of file which has verify boot metadata]
So, basically you are exactly not in flashing page of Download mode but rather in AVB warning page, to to get out of AVB warning you have to let phone battery die... [if it ain't]
& as far as i know restart drains battery a lot faster(i even tied my friend phone's vol_down & power button with something, when he get into a similar situation)
And when the battery completely died, pressed vol_up & down key together & connected the cable & then it went to real Download mode than i flashed stock on that case but in your case flashing null vbmeta will work.
Click to expand...
Click to collapse
Thank you so much for your response... Just two questions here:
If the battery is dead and then I connect it to the PC... wouldn't the phone just die out again... in between the flash since, my PC won't be able to charge the phone with the necessary power... so what do I do then?
And, would flashing this null vbmeta.img file factory reset my phone...!!? I mean yeah I get it that, it's better having the phone bricked... but I was just asking if it does/doesn't factory reset my phone... Honestly no problem, either ways!!
Thank You, so so so so so so so much... my friend!!
I owe you bro...!! FR... Thank You so much!!
killerboychetan said:
It's some vbmeta issue...
Try going back to download mode or recovery and flashing null vbmeta.img... and then your patched firmware again...
Click to expand...
Click to collapse
Hey, could you please elaborate on this... since I'm a bit of a noob... could you please explain me or redirect me to some thread explaining how to perform this with ODIN
_HuH_x86 said:
Thank you so much for your response... Just two questions here:
If the battery is dead and then I connect it to the PC... wouldn't the phone just die out again... in between the flash since, my PC won't be able to charge the phone with the necessary power... so what do I do then?
And, would flashing this null vbmeta.img file factory reset my phone...!!? I mean yeah I get it that, it's better having the phone bricked... but I was just asking if it does/doesn't factory reset my phone... Honestly no problem, either ways!!
Thank You, so so so so so so so much... my friend!!
I owe you bro...!! FR... Thank You so much!!
Click to expand...
Click to collapse
• After phone battery get dead, charge it till 3%(not more than that as if you get stuck, drain again will problematic)
Also, download mode don't require much battery & phone charge even in download mode.
• No way man... never... it's just a 4kb file carrying secure boot info. (It's just for some security purpose, which i feel some useless)
_HuH_x86 said:
Hey, could you please elaborate on this... since I'm a bit of a noob... could you please explain me or redirect me to some thread explaining how to perform this with ODIN
Click to expand...
Click to collapse
Oh! Sry, i forgot to tell you, how to flash vbmeta with ODIN.
So, first zip/archive vbmeta.img to .tar format by using 7zip or something...
Then flash that vbmeta.tar in AP in odin(Also, whenever you flash something with odin always remember to Turn-off auto-restart.
This issue has been already fixed...
It's requested to MODs, pls close this thread.
~Thanks
Hi brother i have same problem.. suddenly my m31s hang and switch off..then it's stuck in startup logo.. power by... I tried for hard reset but it's not coming..also tried Odin flash firmware but again its same problem, stuck in startup logo
Ankur2906 said:
Hi brother i have same problem.. suddenly my m31s hang and switch off..then it's stuck in startup logo.. power by... I tried for hard reset but it's not coming..also tried Odin flash firmware but again its same problem, stuck in startup logo
Click to expand...
Click to collapse
Pm me on tg...