Right, I'm sure there is similar here, but I had loads of difficulty finding it, so I thought I'd create my own version.
I'm a complete noob at this, so I'll make it easier on you, and put it as plainly as possible. EVERY step is listed as if you're in the same [or similar] situation.
I only recently tried to get CM10 onto my phone, and on first try, I soft-bricked it. I unlocked the Bootloader, Rooted, Installed TWRP and a version of CWM when it didn't work, and CM10 seemed to work fine, but upon booting for the first time, and leaving it for about 15 minutes, I realised something went wrong. Tried going back to the most recent RUU [the EU OTA version], and that didn't work [after relocking the bootloader, yes]. Started freaking out a small bit, as it stopped letting me mount the storage in Recovery, even though ADB could still see the phone.
Asked a friend to help, and we found this over on the One X sub-forum.
BEING AWARE THIS IS RELATIVE TO hasoon2000's All-In-One Toolkit
[nice work btw! Might wanna look into this btw - it may be a small bug with your software. No offense ]
Turned out it was the boot.img that installed incorrectly, so making sure the .zip MD5 is correct is first step.
If that's not the issue, the 2nd step is to just open the .zip and take the boot.img out of the root of the container, and pushing that to the phone using ADB [the one that come's with the AIO is perfect]. If you're not sure how to get into ADB, and get it to stay open, here's what you do:
1. Copy the directory of "adb.exe" within your AIO's "data" folder [for example, mine is D:\Administrator.Sheol\HTC\All-In-One\Data\]
Click to expand...
Click to collapse
2. Open Command Prompt [in Vista onwards, type "cmd" into the Start menu Search Bar, in XP, open the "run" dialog in type cmd. Alternatively, find it in Start > Accessories, in all recent versions of Windows]
Click to expand...
Click to collapse
3. Type the following into Command Prompt:
cd D:\Administrator.Sheol\HTC\All-In-One\Data\
{
"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"
}
Remembering your directory WILL be different, so adjust accordingly!
Click to expand...
Click to collapse
4. It'll list all ADB's command's. Don't worry, it's meant to. If you want to, skim through them to familiarise yourself with it. At this point you may want to maximise the window, to fill the screen height [makes every thing much easier]
Click to expand...
Click to collapse
5. Follow this thread to the tee > [Tutorial] How to flash a new boot.img via Fastboot
Click to expand...
Click to collapse
Doing exactly this, worked a charm, and now I have a flawless CM10 HTC One S! After the GApps install of course [which can be done in your Recovery after downloading it/pushing it to your phone, by using the "Install from .zip" option]
Related
Hi All,
I've been reading this forum for a good few days now as I am trying to get my Kyros functioning the way I need it to. However, I've run into a few problems and am not 100% sure as to what to do. Before I go on, I'm not very techy, so I would be very greatful if replies could be as straight forward as possible, without much jargon as that really loses me
First off, we've just managed to install the windows and ADB drives. I'm following all the instructions from here: http://forum.xda-developers.com/showthread.php?t=858952. That took some hacks our side, but is now working.
I'm pretty stuck on the clockwork reboot though. Again, followed the instructions from the link above. When it initially rebooted, it went straight into the Android System Recovery mode (the robot with the triangle opening screen.) I've tried it over and over, following the directions exactly as explained in the link, but all I'm getting is the generic Androis system recov.
The Recovery zip file is on my SD card. Do I need to unzip it to get the recovery.img to show? Is that something that I'm doing wrong? I also updated the OS (I guess) from the coby site before I started working on these other changes.
So basically, this is the issue right now. Trying to get the clockwork to run and all I'm getting is the android system...and that's when it doesn't just reboot back to the home screen directly.
Any advice would be great. Thanks
And out of the blue, after an hour of angry TV watching, it's now worked. I can't tell you what I did differently as I followed all the same steps as before. Must just have been lucky I guess.
I am having the same issue, and i tried to unzip the update.zip but i boot back to the recovery mode, can someone assist me with this, i have a galaxy s (Vibrant).
thanks
Try going to your sd folder and delete the clockwork recovery folder then uninstall rom manager and redownload it from the market after it installs open up rom manager and click on flash clockworkmod recovery and let it download the update.zip file and your done
Sent from my SGH-T959 using XDA App
Oh yeah after all those steps and you still get back into the stock recovery system click on reinstall package and it should boot into cwm I hope that helps
Sent from my SGH-T959 using XDA App
ASR
baalcat said:
Trying to get the clockwork to run and all I'm getting is the android system
Click to expand...
Click to collapse
like this ?
{
"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"
}
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Bertrum said:
Hi guys,
Just got my SNS and have been lurking on here trying to figure out how to ROOT it. There are plenty of guides, and I was using this one
http://forum.xda-developers.com/showthread.php?t=895545
For some reason, and at risk of sounding like an idiiot, SDK doesnt have fastboot (or I cant find it) and I cant even use Command Prompt to execute any commands such as "ADB Devices". It also wont let me change the driver to Android Bootloader Interface in Device Manager.
I basically need to start from scratch and Im tearing my hair out trying to figure it out. Sorry about the FRAT
Cheers
Click to expand...
Click to collapse
http://jaxov.com/2011/02/how-to-root-android-2-3-3-gingerbread-on-nexus-s/
I liked this guide. First time rooting.
On command prompt, you have to go to the Android\android-sdk\tools folder then execute those fastboot command.
Your command prompt probably says C:\Users\Your User Name.. [I have Windows 7]
Type 'cd..' (without ' ') until your line says C:\>
Then type the following cd Program Files\Android\android-sdk\tools
It could be Program Files (x86) not Program Files.. depends which bit you have. You can type those fastboot command from there.
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Bertrum said:
Thanks for that info. Worked a treat right upto the part where I have to put the clockwork image on. command prompt keeps saying it cannot load it. Any ideas?
Click to expand...
Click to collapse
Did you download ClockWorkMod img and paste it into android-sdk\tools folder? You can do that my opening My Computer folder -> C:\ -> Program Files -> Android -> android-sdk -> tools folder.
Then open command prompt and type like that. I just did the first line for you.
{
"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"
}
Yours could be Program Files, not Program Files (x86) though. I downloaded 32-bit version accidentally and I didn't wanted to do it over.
After that you use your Nexus S to boot into bootloader [which the instruction says] and continue on.
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Bertrum said:
thanks all sorted now. now to reinstall all my data as i didnt root straight away. ha!
Thanks for all your help.
Click to expand...
Click to collapse
I'm glad I helped. I had hard time rooting yesterday but it's all good now
I finished everything last night. All unlocked and rooted. Also running CM7 rc2 with the n14 kernel.
Its soo fast compared to my old blackberry and my friends galaxy.
Many thanks to the people who worked on the roms and kernels. Your knowledge astounds me.
Sent from my Nexus S using XDA Premium App
Hi, i got this Samsung G S 4g. I was supposed to fix the rom (somewhat unstable thing). I will try to write all the things i have done until now. I got the "phone to pc" icon. I cannot boot or use download mode (the triangule thing)
General Info
Device is rooted. T-mobile branded, carrier-locked.
Froyo rom. (i think is stock but rooted).
Somewhat old device.
Had stock recovery (Android recovery e3 o something like that)
SGH-T959V (KB5)
Things i did
1. Pull some files from device, to sim-unlock. (using ADB) DID not modify anything else
2. SIM-Unlock using code (worked)
Then, device worked ok some weeks... then stopped working, contacts and phone apps crashed suddenly, everytime i open them
4. Use lastest Heimdall and this guide to get CWM on the phone. The idea was to flash the kernel. did not work. Check the part called "How To Flash a Kernel with Heimdall".
I did that. NOTE: used this kernel insted of the "old" one that the guide says.
Then it output this error: "libusb error: -12". So Heimdall didn't detect the device so i used zadig.exe after reinstalling the samsung drivers to avoid this issue. Then, it started working, and output something like this: "failed sending file part packet heimdall"
And now i have this:
{
"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"
}
What you have is an alternate form of DL mode that occurs after a failed flash. Read this to get back up and running.
Lumins Guide
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Major kudos to diego930 for such a nicely detailed description of his problem!
Yes... my computer didn't feel like showing the tiny disturbing phone this morning, else I could have skipped the suggestion to reboot.
That just means that the safeties are off and your phone is ready and waiting to get flashed. You're close... and probably got fixed, based on the thanks provided.
Theraze said:
Or just reboot the phone, it should go to a disturbing looking tiny-phone mode. Then just resend your heimdall command and it should happily work.
Click to expand...
Click to collapse
How i do reboot ? I just get the phone to pc icon everytime lol
jeffsf said:
Major kudos to diego930 for such a nicely detailed description of his problem!
Click to expand...
Click to collapse
Thanks I like making myself very clear (and i know how annoying is the lack of info)
I haven't touch the device since i broke it so i'm going to try that guide and post any news. Thanks all!
When you get that phone to pc icon, just use Heimdall to flash again.
The reboot-step is from official-download mode where it has the big yellow caution taking you to panic-download mode where it has the tiny phone you posted in #1. Once you have panic-download mode, your phone is ready to accept anything. Even whatever failed before.
Summary: Repeat OP Step 4.
ok, done. Fix using heimdall 1 click! I just reflash GB with kernels and bootloaders, now it works flawless.
Thanks Theraze.
Bit confused how to unlock the bootloader on my moto G..
I am following this guide: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
But I'm stuck on the part "
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
I'm currently installing the following in the screenshot I've taken, but I don't know where the SDK tools are installing to? there is no folder in program files etc...
Many thanks 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"
}
Rightclick on this computer and choose properties, then select advanced settings then surroundings variabels, then in system variables choose path (starts with C and choose modifty and add \android-sdk\platform-tools ( this is where the sdk is located on my pc) at the end of the string.
Also copy AdbWinUsbApi.dll and AdbWinApi.dll (both are in the platform-tools folder) to the windows\system32\ folder.
ps: you only need the top 2 items from the android sdk manager and the Google Drivers.
Thanks but I don't quite understand? I'm on Windows 8.1..
Also AdbWinUsbApi.dll is not even located on my PC ? :-/
junglebungle said:
Thanks but I don't quite understand? I'm on Windows 8.1..
Click to expand...
Click to collapse
Me too Go to system variables and look for path, click edit and add the location of your android-sdk at the end of the string.
Also AdbWinUsbApi.dll is not even located on my PC ? I really am lost I must be losing brain cells.
junglebungle said:
Also AdbWinUsbApi.dll is not even located on my PC ? I really am lost I must be losing brain cells.
Click to expand...
Click to collapse
Both dll`s are in the \android-sdk\platform-tools\ folder, copy them to C:\windows\system32\.
Here is a full guide http://www.google.nl/url?sa=t&rct=j...OWoMssTikMpokJ6TtwEND5A&bvm=bv.59026428,d.d2k for installing adb
That folder isn't anywhere on my PC though that's the problem?!
never mind I've done it, I've pasted the key into the motorola site "3A45890085034220#5441383833304358553100585431303332000000#64ED856A41ADE4D962B9AF1039E9690B98543710#6B94ED010F0000000000000000000000"
And clicked "can my device be unlocked?" and it doesn't do anything, then I request unlock key at the bottom of the page and it just goes to a white blank page? :/
Done it finally! phew lol
junglebungle said:
never mind I've done it, I've pasted the key into the motorola site "3A45890085034220#5441383833304358553100585431303332000000#64ED856A41ADE4D962B9AF1039E9690B98543710#6B94ED010F0000000000000000000000"
And clicked "can my device be unlocked?" and it doesn't do anything, then I request unlock key at the bottom of the page and it just goes to a white blank page? :/
Click to expand...
Click to collapse
I haven`t unlocked my MG so can`t help you there. Maybe someone can help you with this
-Edit- All right bro
What was the fox for the problem?
Sent from my XT1032 using Tapatalk
Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
{
"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"
}
anyone have any idea what the problem might be?
ingovals said:
Because of the incredibly slow and laggy tablet I have I decided to try to do something about it.
So going from some thread here I decided to try to Root it using Motochopper, it seemed to go well but then the SuperSU app did not run, giving me a error No SU binary. I found out the supposedly Motochopper doesn't work with the 10.6.1.14.10 build. Anyways I later read that rooting wasn's necessary when adding custom roms so I unlocked with official app and then tried installing via fastboot a custom recovery TWRP 2.7.0.0
After running the command it just seemed to be stuck, nothing happened. I allowed it to go on but in the end I think the table was out of battery power and this was left on my command prompt.
anyone have any idea what the problem might be?
Click to expand...
Click to collapse
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
LetMeKnow said:
You may want to put the twrp.blob in the adb directory/folder and try again, good luck.....:fingers-crossed:
Click to expand...
Click to collapse
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
ingovals said:
Haha, no I did not forget to do that. Perhaps it was because the trwp.blob was blocked or something, but tried again and it worked instantly now.
thank you.
Click to expand...
Click to collapse
It is good to hear that it worked out for you...:good: I recommended that because I did not see the twrp.blob from your screen shot when you were executing the fastboot command. In your adb directory, you have only four files, two .exe for adb/fastboot and two libraries or dll supporting adb/fastboot....
Congratulations by the way!!! :highfive: