hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
jac10000 said:
Try to unplug and replug the USB cable. I have the same problem and after unplug and replug usb cable that work. Maybe you must hold power down on your phone for about 10 seconds after replug
If that does not work, restart the computer
Click to expand...
Click to collapse
I've tried to unplug and replug and also to restart my pc,but I recive everytime the same line without what I need ..
I'm running ubuntu 12.10 fully installed on an external hdd..can this be a problem?
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
jac10000 said:
Have you really brick your phone with killp4 ?
You should talk about your problem in this thread beacause you would have more answers: http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
I've not bricked the phone with the guide,but after I flashed an RUU and tried to update OTA to JB..then,during the automatic process ,the phone stopped band gone bricked . so I can 't follow the guide from the start and the files that I need ha ve been passed to me by some people on another site.
PS.I can't write on that thread because I ve not 10 posts yet
UMBYDD said:
hi everyone i've found another thread about this problem but no one answered to me so i decided to start a new thread.
I'm trying to unbrick my one s but I'm blocked at the second command of the tutorial when I've to enter the command ls dev/sd* etc..
I'm trying in the right way: when 'qualcomm inc. ecc ' disappear I do the command in the second window of the terminal (I alredy tried faster and faster) but I always had back the same yellow line without sd*4 and 12 that i need...
can you help me??? sorry for my bad english!
Click to expand...
Click to collapse
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
bluebenno said:
Notes:
I did this procedure yesterday - I cry once or twice! - but it will 100% work. Relax!
It can be very,very hard the 'working time' is only seconds - I was not quick enough to do a ls in the other window. I suspect this is your problem.
On my TMobile HTC One S, I had to hold the power button for 15 seconds then release ( not ten nor thirty ). I suspect this could be your problem too.
On some linux distro's the kernel module qcserial will block the emmc_recover program ( not your problem )
On some linux distro's udev will be too slow and the procedure cannot work => Debian based distro's seem to work better. ubuntu should be fine
On some linux distro's /dev/ttyUSB0 is taken by other devices - this is hard coded in emmc_recover. Often this is used by USB to serial devices or internal modems in laptops ( also not your problem )
The 'new' drive letter is always one more. i.e. One a two disk rig ( sda & sdb ) the phone will be sdc
=> My suggestion to all is: Recover mmcblk0p4 ( bakp4 ) first as it's only one write - this is step 12. If this works and the phone is okay (and you are okay!), brick it again then do the full procedure.
This may give you better visual:
1) Run a shell script or enter in a linux shell:
while true
do
ls -al /dev/sd*
echo =========
sleep 0.2
done
2) While above running, connect the phone and do the 15 second power button push then release. Remember to verify with the suggested command ( watch -n 1 lsusb )
With reference and much thanks to the software and forum authors for http://forum.xda-developers.com/showthread.php?t=1990043. I cannot post their either as I am new user too.
Hope this helps, good luck
Click to expand...
Click to collapse
well..first of all this is not a problem of speed.. I'm really really quick! then the 10 seconds procedure works well for me..after 10 sec the qualcomm. inc. etc disappear.
I have the bakp4 because I take it from another friend on the forum.
now I've not comprise so well your procedure ..can you explain me better the 2 steps? thank you!
ps.I've tried to do the step 12 but it tells me COMMAND NOT FOUND
Hello All!
Don't know if this is the right place.
I have a Medion LifeTab S10346 which is really a Lenovo LifeTab S1034x. Its an Intel Atom Z3735F tablet with Android 4.4
It has an USB-OTG port and I try to boot Linux:
- I have connected an powered USB-Hub to the USB-OTG port
- I have connected a keyboard and a USB-Stick to the hub
- on the stick is Ubuntu 14.04 64bit live (GPT partition with fat32)
Now I can turn the tablet on while pressing Vol+ and Power so it boots in the efi shell. Here I can:
Code:
map -r //find the stick
fs1: //change to the stick
cd EFI
cd BOOT
grubx64.efi //start grub
Now I'm in grub and can use it the usual way and can start booting ubuntu but as soon as I start booting the LEDs on my hub goes out. The linux kernel starts an I see the typically messages on the screen but it can not load the root filesystem and my keyboard is dead so it stays in a minimal shell.
So my question is:
It is generally possible to boot a live linux this way or is it a big mistake I'm trying for?
Thanks!
Are there any news on this?
I've tried the same with Fedore 21 & 22 Beta, but they all show the same behavior: As soon as the kernel boots, the USB turns off and that's it
No. I have returned the tab.
Cherubim said:
Are there any news on this?
I've tried the same with Fedore 21 & 22 Beta, but they all show the same behavior: As soon as the kernel boots, the USB turns off and that's it
Click to expand...
Click to collapse
Hi. What about installing to emmc?
I tried to install android 7.1 86x firstly for BIOS(legacy) mode because i like to keep the second OS hidden then I can boot directly to Windows 8.1 on EFI, then I selected to install grub however my stock bootloader was still starting and nothing of grub and therefore I cannot boot into android. Then I decided to install for EFI because I was a whole day trying to work that out and couldn't find any answer on Internet, however seems like the stock bootloader starts instead of grub after I restart the pc.
Extra information:
My pc has an E1-2000 AMD processor, it is 64 bits (and yes, i downloaded the right iso file).
Windows boots from EFI, and I had Kali Linux previously installed with grub and worked fine.After I removed kali I also removed grub with "bootrec /fixmbr" and "/fixboot" on command prompt.
Windows is working fine.
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
LilAnt530 said:
Try downloading the easyUEFI tool (check google) and on windows set a partition for Grub + setting it as the default over MBR
Click to expand...
Click to collapse
What if I don't have windows there anymore? Is there a similar solution, inside a command line maybe?
I think I'm in a similar situation where I can install and run Androidx86 from my USB, but if I restart the laptop it won't find any boot option.
Hello ... !!
I installed the Linux system on my Lg g4 phone without a routine and then with the new userland program. Then I loaded the required files for windows 10 arm and installed qemu and installed the xfce4 interface and gave the commands to run windows 10 ARM in the terminal through the qemu program. Freeze on the prompt to press any button to take off from the CD or DVD and does not complete and then I did the same steps on my laptop system work but show me the blue death screen immediately after the takeoff
Note: The system needs to GPT and I own the MBR on the laptop Is that why the system Take off by UEFI which requires a GPT Do anyone help me
----------***** :good::good: *****----------
Hello ... !!
I installed the Linux system on my Lg g4 phone without a routine and then with the new userland program. Then I loaded the required files for windows 10 arm and installed qemu and installed the xfce4 interface and gave the commands to run windows 10 ARM in the terminal through the qemu program. Freeze on the prompt to press any button to take off from the CD or DVD and does not complete and then I did the same steps on my laptop system work but show me the blue death screen immediately after the takeoff
Note: The system needs to GPT and I own the MBR on the laptop Is that why the system Take off by UEFI which requires a GPT Do anyone help me . . !!! :angel:
:good::good::good::good::good::good::good::good::good::good: