Hello everyone, I have a problem with the method: Downgrade / Unbrick Ville S4. To be noted that I bricked my One s involuntarily. Now if you follow the above method, when I give the code: $ lsusb watch-1 is seen the device correctly, but then when I press the power button for 10 seconds, the device disappears and I get this: Qualcomm, Inc. and continues back to scanning the device. Then do this code: $ ls / dev / sd * and of course the device is not connected. It 's like if I had a problem on the USB ports that do not maintain stable connection with the device, or my One s resets the time. I've used both Ubuntu and Mint13. Do you have any solution? Thank you. Sorry for my English.
pasquill75 said:
Hello everyone, I have a problem with the method: Downgrade / Unbrick Ville S4. To be noted that I bricked my One s involuntarily. Now if you follow the above method, when I give the code: $ lsusb watch-1 is seen the device correctly, but then when I press the power button for 10 seconds, the device disappears and I get this: Qualcomm, Inc. and continues back to scanning the device. Then do this code: $ ls / dev / sd * and of course the device is not connected. It 's like if I had a problem on the USB ports that do not maintain stable connection with the device, or my One s resets the time. I've used both Ubuntu and Mint13. Do you have any solution? Thank you. Sorry for my English.
Click to expand...
Click to collapse
Best off posting in the downgrade thread but if you think usb is the issue they try another pc.
You have to do the $ ls dev/sd* command multiple times by doing up enter up enter so that it will appear at least once. If you do the command once or twice, it won't work. You need to be really quick.
Darknites said:
Best off posting in the downgrade thread but if you think usb is the issue they try another pc.
Click to expand...
Click to collapse
I can not post in this thread because I do not have privileges. I've tried three PCs. Thank you.
pasquill75 said:
I can not post in this thread because I do not have privileges. I've tried three PCs. Thank you.
Click to expand...
Click to collapse
Oh ya dumb me sorry but what usaff22 said is right I had to do that 3 or 4 times.
usaff22 said:
You have to do the $ ls dev/sd* command multiple times by doing up enter up enter so that it will appear at least once. If you do the command once or twice, it won't work. You need to be really quick.
Click to expand...
Click to collapse
First of all, thank you. You think it's a speed problem? In fact sometimes comes too: Qualcomm. Inc. Gobi Wireless Modem (QDL mode), but then when I go to press the power button, the display disappears and this begins to look for the device Qualcomm, Inc. 001, 002, 003 etc.. I can not continue with the procedure because after telling me Connect device. One more thing: why when I enter the command $ tells me that is not valid? Which linux distro do you recommend?
pasquill75 said:
First of all, thank you. You think it's a speed problem? In fact sometimes comes too: Qualcomm. Inc. Gobi Wireless Modem (QDL mode), but then when I go to press the power button, the display disappears and this begins to look for the device Qualcomm, Inc. 001, 002, 003 etc.. I can not continue with the procedure because after telling me Connect device. One more thing: why when I enter the command $ tells me that is not valid? Which linux distro do you recommend?
Click to expand...
Click to collapse
I used Ubuntu 12.10 64-bit.
Darknites said:
I used Ubuntu 12.10 64-bit.
Click to expand...
Click to collapse
To you has the same problem?
I mean, why it makes me see the device and as soon as I press the power button to start the search again?
pasquill75 said:
To you has the same problem?
I mean, why it makes me see the device and as soon as I press the power button to start the search again?
Click to expand...
Click to collapse
I did the downgrade first try but like usaff22 says you need to spam $ ls dev/sd* when you reboot using the Up button and then hit enter in till it pops up.
pasquill75 said:
Then do this code: $ ls / dev / sd *
Click to expand...
Click to collapse
Disregard this if it's obvious, but the command you should use is:
ls /dev/sd*
(So you dont type the '$'-sign (that's your prompt) and there is only one space between 'ls' and '/dev/sd*' and no other spaces.)
usaff22 said:
..by doing up enter up enter... You need to be really quick.
Click to expand...
Click to collapse
You could do something like:
while [[ 1 ]] ; do ls /dev/sd* ; sleep 1 ; echo "Again..." ; done
-Jobo
touch of jobo said:
You could do something like:
while [[ 1 ]] ; do ls /dev/sd* ; sleep 1 ; echo "Again..." ; done
-Jobo
Click to expand...
Click to collapse
This is not I get it, you can be more basic? Thank you.
pasquill75 said:
This is not I get it, you can be more basic? Thank you.
Click to expand...
Click to collapse
Instead of the 'up .. enter .. up .. enter ..'-thing, this just runs it once per second in a loop.
It was in reply to usaff222 who explained that you have to run it multiple times. This is a lazy way to do it multiple times.
The first bit about the dollar sign and spaces was in reply to your original post.
Sorry for any confusion.
-Jobo
HI!
i'm new on the forum but i've found help in this site many times.
i'm in the same problema of pasquill75..when i do the command I have back everytime the same yellow line without sd*4 / 12..
I've tried many times and everytime faster but nothing changes
ps:I'm running ubuntu 12.10 fully installed on a hdd (not live cd or fully installed on my pc I mean)
can this be the problem? sorry for my bad english
Related
Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.
Forgive me for asking the obvious, but do you have USB Debugging enabled?
distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.
Fastboot devices gave me this output:
serial# fastboot
kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe
kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).
Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck
i ditched windows ages ago and i will never look back i am sick and tierd of waiting on moto uk to push ics. i use to have the dell streak and i rooted that but i was on windows then how do i root my xoom with linux mint is it possible and can any point me in the right direction please
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Thank you megabiteg Still learning linux but i Love it
megabiteg said:
Stand by, I will give you all the tools and options you need to do so, I could draft something tomorrow morning.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Cheers for the info just by any chance do you know the commands still learning Linux
llama-power said:
well, it isn't that hard since everything you really need on your computer ist fastboot and a way to push a file to an sdcard (fat formatted)...
Just go here, download and install the android sdk from there. Make sure the commands adb and fastboot are in your path. (test by issuing adb devices, shold return a list of attached android devices with usb debugging turned on)
After that, just follow these instructions. I am not sure if you need to run fastboot as root, but you'll see
Click to expand...
Click to collapse
elsworth1983 said:
Cheers for the info just by any chance do you know the commands still learning Linux
Click to expand...
Click to collapse
thought you ditched windows ages ago?
anyhow... don't have linux set up atm, so this will from memory and might contain some errors... Also, never tried mint, I always stuck to debian or debian-derivates...
anyhow, lets try this:
first, use your package management-system to install a jre (java runtime environment.
If that is set up, install the android sdk:
Code:
$ cd ~
$ wget http://dl.google.com/android/android-sdk_r17-linux.tgz
$ sudo su
[enter your su-password]
# cd /usr/local
# tar xfzv ~[yourusername]/android-sdk_r17-linux.tgz
# ./android-sdk-linux/tools/android
a window should open up and list some files available for download. Just select "Android SDK Platform-tools" and hit "Install 1 package...".
once that's finished (might take a while), close the Android SDK Manager and you should get back to your shell.
Code:
# ln -s /usr/local/android-sdk-linux/platform-tools/adb /usr/local/bin/adb
# ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot
# exit
$ rm android-sdk_r17-linux.tgz
now, connect your xoom to your computer and enable usb debugging in the settings of your xoom. If you issue adb devices, you should get something like
Code:
List of devices attached
043c12343456476547 device
if you receive something like bash: adb: command not found, something went wrong somewhere. Try the same using sudo: sudo adb devices if that doesn't fix it please write another post.
Also, if you encounter an error after entering any of the comments above, please do not continue until you resolved that error. (For example ask for a solution here)
And, since you are still learning to use linux: whenever instructions contain a $ or # at the beginning of a line, DO NOT ENTER THESE. They are just there to tell you to issue that command as normal user ($) or superuser (#)
/EDIT: btw: there may be an easier way to do this if you just want to use adb/fastboot this once: you could try to simply download the adb and fastboot- binaries and put these into the folder with your recovery.img-file. Might work, not sure about that, though. Also, since I don't have linux installed on my machine atm, I can't provide you with a link to these binaries.
cheers for all your help will give this a go "Dont want to back to windows
Android SDK manger log
Error Stopping ADB server failed (code-1)
Connected the xoom and did adb devices and it listed the xoom with no errors in the terminal Thank you again ? Were do i go from here now
glad to read it's working
just follow the instructions in this thread That will help you to install a custom recovery and root your xoom. It will not, however, install a custom rom. To do that, you'd also need to download a custom rom (usually comes in a flashable .zip-file), place that on an acutal sd-card which you're gonna put into your xoom, and install that file from within the custom recovery. Just make sure you grab a rom that works with your xoom (for example, you shouldn't put a us-4g-rom onto a wifi-only-xoom and vice versa)
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
elsworth1983 said:
have i done something wrong
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot oem unlock
fastboot: command not found
Click to expand...
Click to collapse
have you done the # ln -s /usr/local/android-sdk-linux/platform-tools/fastboot /usr/local/bin/fastboot? The error you're getting seems to suggest that it can't find the fastboot application? What happens if you type /usr/local/android-sdk-linux/platform-tools/fastboot oem unlock?
elsworth1983 said:
The problem i seem to be having is when the xoom is on i type <adb reboot bootloader> The xoom reboots to the fastboot screen after that no commands work and when i do ADB devices in the terminal the device list is empty ?
Click to expand...
Click to collapse
that is expected. adb is only available while android is booted up, fastboot is the protocol to use while in bootloader mode. As indicated before, I suspect that your computer can't find the fastboot application (on the computer).
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
elsworth1983 said:
Cheers for all the info i went back and started all from the top again only thing i am struggling with is Flashing the recovery now lol i get
god-WE174AA-ABU-s5306uk god # adb reboot bootloader
god-WE174AA-ABU-s5306uk god # fastboot flash recovery recovery-solarnz-100611-1150.img
error: cannot load 'recovery-solarnz-100611-1150.img'
I have it on a memory card which i checked which was working
Click to expand...
Click to collapse
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
all i can say is thank you for all the information every 1 is giving me my head is mashed lol so if i put recovery-Tiamat-R4c-100611-1150-cwm.img on the desktop what would the terminal code be
kofrad said:
The recovery image needs to be on your pc. It doesn't matter where on your pc as long as you can access it and know where it is.
Fastboot works by sending the image over the usb cable. Once you start flashing roms, those will need to be on your sd card within the xoom.
Click to expand...
Click to collapse
depends on where your desktop is If it is in ~/Desktop/, then the correct command should be
Code:
fastboot flash recovery ~/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
What am doing so wrong its lucky am not bold yet been trying this all day
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
if the graphical interface, where do you see the file located?
elsworth1983 said:
error: cannot load '/root/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img'
ARRRR i am really loosing the will to live ;-)
Click to expand...
Click to collapse
Sounds to me like you are running the commands as root. You likely have also downloaded the recovery image as a normal user. This means the '~' shortcut for the home directory is pointing you to someplace where the file is not.
Try using "fastboot flash /home/Your username/Desktop/recovery-Tiamat-R4c-100611-1150-cwm.img"
I have put the file on the desktop ? is that what u mean
Disclaimer: This is BETA. It works well, but may still set fire to your house if you anger it.
UPDATE 11/14/12 - Updated OP with SLS's device detection code fixes.
Update 2: Fixed bug in device detection loop causing freeze at "Waking Device"
JET - The Jewel/Evita Tool "kit."
This all started as a downgrade script for the Jewel. You can follow the original JET thread in the EVO 4G LTE forums. I'm creating this thread to track/support issues from Evita users.
JET performs several useful functions, including:
Downgrading your HBOOT to 1.09 for easier radio flashing.
SuperCID (For HTCDev unlocking)
Partition/IMEI backup.
Detection of eMMC partitions on a phone stuck in Qualcomm download mode
Possible unbricking of your device (depending on circumstances)
JET is and always will be 100% open source and with full support given here on XDA.
Changelog
11/9/12 - Name change to better reflect the direction of this project. Ported to Evita. Rewrote device detection code.
11/1/2012 - Added SuperCID capability
10/24/2012 - Modified emmc_recover to catch stalls at "Wait device /dev/sdXXX......" and try to recover.
10/21/2012 - Added --recover and --unbrick command line options
10/19/2012 - Beta posted
Click to expand...
Click to collapse
Credits:
Credit for the original EVO downgrading idea belongs to Mac_Gyver as seen in this post:
http://forum.xda-developers.com/showthread.php?t=1932914
This post refined that process and can still be referenced for manual downgrading:
http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Closeone for code submissions and a steady flow of awesome ideas.
SouL Shadow for some slick logging code
Initial Testers (AKA People willing to let a total stranger intentionally brick their phone for SCIENCE!)
AZ Fadeout
benny3
kjcmusic17
michael.stollaire
My lovely wife (distract with shiny object, snatch phone, cackle wildly, proceed to brick)
Some local folks not on XDA
absolutelygrimm and 18th.abn for consulting on the Evita side of things.
The XDA community for rallying behind this project and offering support to your fellow members
Click to expand...
Click to collapse
Requirements
Unlocked bootloader and a recent TWRP already flashed. (For most functions.)
A NATIVE Linux installation, or a LiveCD/Wubi install. Virtual Machines are NOT SUPPORTED.
[*]A 32 bit Linux installation/CD, or install ia32-libs or ia32-libs-multiarch
Linux Kernel v3.0 or higher (Ubuntu 12.04 LiveCDs meet this requirement)
USB Debugging turned on
Click to expand...
Click to collapse
FAQ
Q: Help! The tool keeps saying "Failed to flash HBoot" repeatedly. What do I do?
A: This is a timing issue. If the tool can't get a good lock on your phone, it will give and error and then try again. It will keep trying until it locks onto the phone and can flash. In addition, it is safe to unplug and replug the USB cable during this step, even to another USB port.
Q: This thing is taking forever!! Is it supposed to?
A: The process usually takes about 10 minutes but can take 15 or longer depending. Unfortunately the process for flashing the bootloader is rather painful, and has to be done in very small pieces. Thank HTC for that one. Ubuntu is also partially to blame.
Q: Is this a bootable CD? Can I use this from Windows?
A: This is NOT a bootable LiveCD. A LiveCD version (with further enhancements) is in the works.
Q: Is there/Will there be a Windows version?
A: No. Nor are there plans to make a Windows native version. There are some inherent issues with the way Windows deals with USB devices that prohibits us from accessing QDL. If you're not comfortable trying/using Linux, I suggest you wait for the LiveCD to be finished.
Click to expand...
Click to collapse
Instructions:
Boot Linux.
Download attached package.
Unzip to somewhere you have write access (/home/ubuntu for Ubuntu LiveCD users)
Open terminal.
cd to working directory.
$ chmod +x jet
$ sudo ./jet
Follow the onscreen instructions.
/happydance
Click to expand...
Click to collapse
Command Line Options
Code:
-b or --backup : Backup mode only (make bakp4 and fsp4, don't force QDL)
-c or --cidpreserve : Don't SuperCID the backup P4 file
-d or --detect : Find device (/dev/sd?)
-k or --kill : Soft brick the phone by corrupting P4 (be careful with this)
-r or --recover : Load HBOOT 1.09 and existing backup P4 (for people who stalled after QDL force)
-s or --supercid : SuperCID mod for nonbricked phones
-u or --unbrick : Load existing backup P4 file ONLY. (Quit QDL without downgrade)
Click to expand...
Click to collapse
To do:
P4 file generation from user entered MEID.
Merge both HW versions of JET and detect device at load.
LiveCD
All requests for features considered!
Click to expand...
Click to collapse
Source:
You can follow code revisions for the shell script here:
https://github.com/yarrimapirate/JET
LiveCD Development is underway. You can follow the code here:
https://github.com/closeone/JET
I use a modified version of Fuses emmc_recover. I have forked his source here:
https://github.com/yarrimapirate/emmc_recover
Click to expand...
Click to collapse
A big Thank You to all who've sent donations! Caffeine and beer help generate code, and a few extra bucks convinces the wife it's worth the time I spend glued to my PC/phone. Your donation money is also being used to buy devices to further test/develop with. :good:
Reserved.
This one too...
oh sweet, video coming right up!
Just one step closer to S-Off!
yarrimapirate said:
Since I'm not entirely familiar with the problem, I'll ask grim to expalin it to me so I can properly document it in the OP. Thanks for the heads up!
Click to expand...
Click to collapse
----
Hboot protects itself, I thought sbl3 verified hboot, then it protected itself but that's not the case. Sbl3 is controlling emmc mode from my understanding...
p9 (sbl3) sets emmc mode before p12(hboot) sets protection...........p1,2,3 will never be vulnerable to the same exploit as they have already set their protection well before emmc mode. They are the first 3 partitions so you cannot brick anything earlier in the chain. So, just say, hboot was p7, it would protect itself before emmc mode, and would never be vulnerable. -18th.abn
----
However, if for any reason you cannot flash Kernels/Radios.. Just run the 1.85 RUU and your issues will be solved.
----
To RUU downgrade, you will need to pull mmcblk0p23 from your phone and hex edit it. To do so, open terminal emulator on your phone..
Code:
$ su
# dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23
Open this in a hex editor of your choice.
at 0x0A0 you will see
ClearAutoImage..2.20.xxx.x...................... x being whatever number is listed..
change it to 1.00.000.0
Place back on your sdcard
open terminal emulator
Code:
$ su
# dd if=/sdcard/mmcblk0p23 of=/dev/block/mmcblk0p23
reboot to fastboot and lock your bootloader. Boot into your ROM and RUU downgrade
ugh i wish i had linux. i want old hboot back! . awesome job though, this is great to see.
Genetic517 said:
ugh i wish i had linux. i want old hboot back! . awesome job though, this is great to see.
Click to expand...
Click to collapse
Go boot up a liveCD and do it.
I have done it 3 or 4 times, but with the manual process. These tools work. I endorse them.
Genetic517 said:
ugh i wish i had linux. i want old hboot back! . awesome job though, this is great to see.
Click to expand...
Click to collapse
Just use the ubuntu live cd like suggested in the OP. Or dual boot it, ubuntu or other Linux distro is really great to have
EDIT: absolutelygrim beat me to it
Great job to all involved with this !. S-Off would be nice, but having Hboot 1.09 is pretty nice as well.
I'm using this now, a bit concerned that the device seems like it doesn't want to wake right now (stuck at Waking Device...) ANyone have any ideas? Would it be safe to unplug this USB cable and try a different one? I'm using one other than the one that came with the One X
absolutelygrim said:
Go boot up a liveCD and do it.
I have done it 3 or 4 times, but with the manual process. These tools work. I endorse them.
Click to expand...
Click to collapse
bpear96 said:
Just use the ubuntu live cd like suggested in the OP. Or dual boot it, ubuntu or other Linux distro is really great to have
EDIT: absolutelygrim beat me to it
Click to expand...
Click to collapse
i did read i could use livecd but i also read this in the FAQ. livecd looks to be unfinished? please correct me if im wrong. im 100% a windows guy, have never even used linux
Q: Is there/Will there be a Windows version?
A: No. Nor are there plans to make a Windows native version. There are some inherent issues with the way Windows deals with USB devices that prohibits us from accessing QDL. If you're not comfortable trying/using Linux, I suggest you wait for the LiveCD to be finished.
MyronJ906 said:
I'm using this now, a bit concerned that the device seems like it doesn't want to wake right now (stuck at Waking Device...) ANyone have any ideas? Would it be safe to unplug this USB cable and try a different one? I'm using one other than the one that came with the One X
Click to expand...
Click to collapse
Hold power down for 10 seconds
open another terminal window and type
Code:
watch -n.1 lsusb
let go of power when you see "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" disappear
Genetic517 said:
i did read i could use livecd but i also read this in the FAQ. livecd looks to be unfinished? please correct me if im wrong. im 100% a windows guy, have never even used linux
Q: Is there/Will there be a Windows version?
A: No. Nor are there plans to make a Windows native version. There are some inherent issues with the way Windows deals with USB devices that prohibits us from accessing QDL. If you're not comfortable trying/using Linux, I suggest you wait for the LiveCD to be finished.
Click to expand...
Click to collapse
He means a actual "jet" AIO live cd is what is a unfinished . Theres nothing stopping you from downloading the latest Ubuntu distro, burning it to a disc (or bootable usb) and running that on your computer. Ubuntu can be ran directly from the disc, no install needed (though it will be slower than install obviously ) Once your running the live cd/usb of ubuntu you can easily load up this toolkit.
absolutelygrim said:
Hold power down for 10 seconds
open another terminal window and type
Code:
watch -n.1 lsusb
let go of power when you see "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" disappear
Click to expand...
Click to collapse
It won't stay disappeared, it's pretty much appearing and then reappearing
MyronJ906 said:
It won't stay disappeared, it's pretty much appearing and then reappearing
Click to expand...
Click to collapse
did you brick by flashing ICJ or are you trying to downgrade?
edit: It should disappear and then say Qualcomm, Inc. for a few seconds
absolutelygrim said:
did you brick by flashing ICJ or are you trying to downgrade?
Click to expand...
Click to collapse
Downgrade. Haha just my luck for trying something I didn't need to do
If it's safe to actually unplug the USB and grab another cable, I'm definitely willing/able to do that
EDIT: and it does disappear and say Qualcom Inc for a few seconds, then nothing and then it flashes the full "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" for a split second and repeats the process
MyronJ906 said:
Downgrade. Haha just my luck for trying something I didn't need to do
If it's safe to actually unplug the USB and grab another cable, I'm definitely willing/able to do that
Click to expand...
Click to collapse
Yes, go get the cable that came with your phone and restart from the beginning
kickass!
absolutelygrim said:
Yes, go get the cable that came with your phone and restart from the beginning
Click to expand...
Click to collapse
Beginning as in from the very beginning of the script? Just ran home and grabbed the cable. Thanks for the help by the way
MyronJ906 said:
Beginning as in from the very beginning of the script? Just ran home and grabbed the cable. Thanks for the help by the way
Click to expand...
Click to collapse
Use the command line switch -r
sudo ./jet -r
Sent from my One X using xda app-developers app
Great work on this, to all involved!
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 everyone.. i have a htc one s ..
3 days ago it just went off with enough battery for no reason and it is not possible to switch it back on.. also power und volume buttons dont work and the screen always stays black .. i charged it for over a day and still completely dad..
when i connect it to the pc, i hear the sound of a new connection, but i think that it is just charging.. i see qhsusb_dload in the device manager the phone was never rooted or anything like that .. i just want to get my data back .. especially the photos on it.. would it also be possible to open the phone and get the sd card out or isn't there such a card? is there any chance to get the data out .. i already bought a new phone but i really would love to get all the photos back which havent been backed up for a year
thank you all in advance!
Try this http://unlimited.io/qhsusbdload.htm to relive your phone
Thank you for your fast reply.. but sorry, i have no idea how to install and boot to ubuntu
may someone please explain it to me step by step?
You can download from www.ubuntu.com and try to make a live usb with unetbootin. After that start up your pc from usb and run ubuntu. then download http://unlimited.io/qhsusbdload.htm and try
okay .. it is downloading and what to do next? just put the file on a usb stick? and how to boot from the stick?
sorry for being such a noob
Oh Men... Hahaha. Its very difficult explain here ... You can search how to make a ubuntu liveusb. And how to try ubuntu with out installed... Then when you Boot on ubuntu follow the instrucctions http://unlimited.io/qhsusbdload.htm
okay.. i created the usb stick and booted to ubuntu.. i downloaded the file and opened the terminal
then i connected the phone via usb and entered the commands.. still the phone stays black .. no matter how long i press the power button .. any ideas?
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip PblClear.zip
Archive: PblClear.zip
inflating: PblClear
[email protected]:~/Downloads$ chmod 755 PblClear
[email protected]:~/Downloads$ sudo modprobe qcserial
[email protected]:~/Downloads$ sudo ./PblClear
============= PblClear 0.1 =============
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Starting pblreset...
Press ENTER to start
QDL reset
Lisa1991 said:
okay.. i created the usb stick and booted to ubuntu.. i downloaded the file and opened the terminal
then i connected the phone via usb and entered the commands.. still the phone stays black .. no matter how long i press the power button .. any ideas?
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ unzip PblClear.zip
Archive: PblClear.zip
inflating: PblClear
[email protected]:~/Downloads$ chmod 755 PblClear
[email protected]:~/Downloads$ sudo modprobe qcserial
[email protected]:~/Downloads$ sudo ./PblClear
============= PblClear 0.1 =============
(c) Copyright 2012 Unlimited.IO
This program may not be redistributed in
nor included in other works works without
the express permission of team Unlimited.
Starting pblreset...
Press ENTER to start
QDL reset
Click to expand...
Click to collapse
that its just a idea... maybe work maybe not . you follow the instructions very carefully?
Yes. I did it just like the instructions and at the end it said qdl reset
but it is still not possible to bring the device back to life ..
is it somehow possible to save the data? i read about opening the HOS and unplug the battery.. would you think that this could help? or is there any other chance?
Lisa1991 said:
Yes. I did it just like the instructions and at the end it said qdl reset
but it is still not possible to bring the device back to life ..
is it somehow possible to save the data? i read about opening the HOS and unplug the battery.. would you think that this could help? or is there any other chance?
Click to expand...
Click to collapse
Really i dont know my friend . I dont think the one s have a sd internal.. so i dont know how to save data... The only way is turning on the phone
anyone else?
when i connect it to the pc it is shown in the device manager as "unknown device" .. so it really looks like it has left the qhsusb_dload mode.. but still no chance to get access to the data or to switch it back on
Lisa1991 said:
anyone else?
when i connect it to the pc it is shown in the device manager as "unknown device" .. so it really looks like it has left the qhsusb_dload mode.. but still no chance to get access to the data or to switch it back on
Click to expand...
Click to collapse
You have installed lasted HTC drivers?
yes ... deinstalled them and installed them again .. also the phone doesn#t start without using the pc
Lisa1991 said:
yes ... deinstalled them and installed them again .. also the phone doesn#t start without using the pc
Click to expand...
Click to collapse
Dont start without using pc? Did you mean with pc turn on?
that is what i did .. and it seems like the phone got out od the dload mode... but still i cant switch the phone on
and if i connect it to the pc, it only starts charging but i dont get access to the data, because it is still switched off...
Lisa1991 said:
that is what i did .. and it seems like the phone got out od the dload mode... but still i cant switch the phone on
and if i connect it to the pc, it only starts charging but i dont get access to the data, because it is still switched off...
Click to expand...
Click to collapse
Are you try connect to pc and press power+volDown for a Long time?
more than two minutes.. no result..
Moderator Information,
Thread cleaned. Keep posts on topic.