Hello Everyone, it's just sad that my first post on this forum had to be a frustrating one. First of all I would like to start off with a few general points that you guys should know before (commenting or raging at me):
1. My HTC legend was only purchased 3 months ago.
2. I HAVE looked around the forum for answers but I cannot seem to find a suitable solution.
3. My phone has already been rooted.
4. This problem has not occurred before.
5. I am in desperate need of help...
Anyway, I've recently rooted my HTC Legend (like 3 days ago) using this method http://forum.xda-developers.com/showthread.php?t=1223950&page=3 . Everything worked well and I was impressed with how smooth everything was going (flashed cyanogen mod 7 and OC'ed). However only just recently (like 3 hours ago) I connected my phone via the USB cord (provided by the phone itself) and the usual connection status where we can choose (Charge only, disk drive, sync etc) was not coming up. I pulled down the notification bar and nothing was there. Only the USB DEBUGGING sign was there. I tried rebooting my PC and my phone a couple of times but the connection status is still not coming up . I have also tried turning off and on USB debugging mode, re installing/updating SDK and HTC sync (but I doubt that's the problem because I could view the connection status before I downloaded SDK). For some reason there is no "Connection PC" thing that I was pretty sure the stock HTC legend had but I don't know if Cyanogen mod 7 removed that or something.
I went across this forum and tried many of the threads that displayed a similar problem (most were unanswered..). I hope that my USB is not bricked because I don't want to go through the tedious process of unrooting my phone and waiting for my phone from repairs. PLEASE CAN ANYONE HELP ME?!
If it would help: my pc can detect the phone but I cannot change to hard drive mode because the status isn't showing..... Damn this is annoying
Sent from my Legend using xda premium
Anyone?
Sent from my Legend using xda premium
With CM7, or any Android phone using a stock ROM, you have to select disk drive from the notification bar. With that said, in the case that that won't appear, have you tried changing ROMs?
There's also a way to nudge disk drive into working without changing ROMs, and I doubt it'll work, but it's always worth trying.
Reboot into CWM and mount the SD from there. That'll hopefully get 'er going.
Before I say anything, thanks for replying
Okay so what you're suggesting is what most people have been saying about this issue. The problem is that I don't know how to flash a different rom without using the computer
So of you wouldn't mind can you explain in clear (to the best of your abilities lol) how to go about that step? Sorry, but this is my first smartphone and I'm a noob this clockwork recovery thingy. Sigh, the weird thing is cm 7 worked perfectly for a few days (till I oced it).
Cheers
And how do you reboot to CMW? Is that recovery mode, cause if it is I can't do anything once it goes to that red triangle with exclamation mark thingy.
PS: And just in case I have resolve to flashing a new rom, which one do you recommend?
1st of all google that red triangle with exlamation mark thingie. Use these exact words... you'll see, it's amazing...
Sent from my HTC Legend
Don't mind it when people don't reply to your thread. It's a problem with the Legend not being as highly regarded this far into a smartphone's life.
When you get to the screen with the Android device and red triangular exclamatory point, you've reached the first step into booting into recovery. From rooting, an update.zip file should've remained on your SD card. If not, use it from ROM Manager. From that screen, simply press VOLUP + Power to reach HTC's recovery. From there, apply the update.zip from the root of your SD (it'll do it automatically), and you'll be booted into CWM.
Another method, and useful if you already don't have a different ROM loaded onto your external storage, would be to use ROM Manager: https://market.android.com/details?id=com.koushikdutta.rommanager&feature=search_result
From your phone, download a different ROM like you would on your computer, it's a smartphone after all! Leave the rest to the app. It will not only keep ClockworkMod Recovery up to date, but also provides a more simple interface to access basic recovery functions.
First of all I already have rom manager installed because it came with the CM 7 rom after I flashed it. What I don't understand is what update.zip you are talking about because I have one already on the root of my sd card (are you talking about that one). And do I need to do a nandroid back up before doing this procedure? And how do I mount the sd card from CMW lol.. soz FOR the noob questions.
EDIT: I just went to CM Recovery and mounted it onto my PC and pressed one of the options that says "mounts and storage" but when I do, all that happens is that the screen turns into the weird Hat logo with a dark background screen and nothing happens (I can't access the mass storage still). I pressed home which brought me back to my original CMW recovery page and I pretty much tried all of the options and it does the same thing WUT THE HECK! I don't know if its the version of my CMW (v5.0.2.0) or if its something that I'm doing wrong......
EDIT2: OMFG I was freaken pressing the power button to choose my options when I should have been pressing the scrolls button LOL *awkies*. Anyways, USB storage now shows up but what do I do now lol? Do I just reboot and the Mass Storage works again or do I have to reflash it (is it the same steps as flashing a new rom or are the steps different now?). Either way I'm glad that the USB storage still works thanks man I would have given you like a thousand likes or something but can only do it once lol.
Well problem fixed, just reflashed my Cm 7 rom and the USB storage is up and running again Thanks Asovse!
PS: MERRY CHRISTMAS TO EVERYONE READING THIS POST
Sent from my Legend using xda premium
Glad I could help!
Happy holidays, mate!
Related
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
GreenLanternBatman said:
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
Click to expand...
Click to collapse
It sounds like you don't have Amon's recovery flashed yet.
This is probably the easiest thing you can do.
http://forum.xda-developers.com/wiki/index.php?title=How_to_flash_Recovery_Image
or this
http://forum.xda-developers.com/showthread.php?t=742228
In either case, you need to read, and educate yourself.
Precursor - If you run a back up program like Titanium Back Up or MyBackUp Pro, now would be a good time to do that.
I think your main problem is that to get into Recovery mode, you need to hit Volume Up + Power (End). Once there, I'd suggest going to Back Up/Restore and doing a Nandroid Back Up. This will save the entire state of your phone just as it is before you went into Recovery. Exactly as is. Next, go to Wipe, and select options 1 - Factory/Data Reset and 2 - Dalvik Cache. If you don't already have the KaosFroyo-v34.zip file on the root (meaning NOT in a folder) of your card, you can go back to the main Recovery screen and select 2 - USB MS Toggle which will mount your SD card to the computer and you can drag and drop the file from there. Once you've followed these steps, now you are ready to choose option Flash Zip from SD card. Select the zip you need and let it do its thing. You didn't mention if you had apps2sd set up not. If you don't, ignore this next part, if you do, pay attention. IF and only IF you were using apps2sd then you will need to reformat your card to work with Froyo roms. Froyo already has the benefit baked into it but it utlilizes it in a different way. To reformat, you will want to copy everything from your SD card to your computer, then in Recovery, go to Partition card. For Ext and Swap sizes select "0" and then hit ok for partition the rest of the card in FAT32 format. Done. You can add back on contents from the SD card in Recovery through the USB Toggle mode or after you boot everything up, it does not matter (the only difference being that your computer will ask if you want to copy and merge folders if you do it after you boot because it will remake some of the folders for you on booting) . With that being said, now it's time to try out KaosFroyo! The first boot WILL take awhile and the phone will be very slow once it does boot as it has to Sync all of your info and applications back from the Market. Once that gets finished, then you can restore your data if you saved it through Titanium or MyBackUp. I usually like to give it a reboot after all this fun stuff, just to give it a chance to gather itself, if you will. After that, you should be good to go with learning the ins and outs of Froyo Hope this helps!
Did you make a amon backup before you first rooted you phone? I had that same problem when I flashed Kaosfroyo v34. I would boot up in recovery (Vol up+end) and I would have the android with the ! above him. I started freaking out. What I did was restore my nand backup back to 2.1. Then I re-rooted back to KaosFroyo v34. Then went into recovery and everything was good. My advice, unroot then root again. Maybe its not the best/easiest way, but it did the trick for me. And as always, search the forums, there is a post for almost anything. Hope that helps.
Hi all, I hope somone can help me, I have a TMobile UK Samsung GS2, I have it unlocked and rooted for some time now and have been happily flashing custom ROM's with no problems but a couple of days ago after flashing and update to my current ICS ROM, I am no longer able to connect it to a PC I get an error message saying the device is unrecognised, I have tried 3 different PC's and 3 different cables, I even tired a MAC! I have rolled back to a previous ICS version via nandroid backup and that does not work, I even rolled back to a GB version of a nandroid backup and still no joy, I have tried pretty much every wipe option available and installed from new, it still does not connect, if I boot into download mode odin does not pick it up, Kies does not pick it up, I have an hdmi adapter to plug into my TV that does not work anymore as well as an adapter to connect a flash drive and although the power light on the flash drive shows up the device does not show on the phone, I can charge the phone however. I have posted on the ROM forum on XDA and the guys there have tried to help mainly by different wipe options but nothing has so far worked.
I noticed while experimenting with different kernels that the back around the camera would get very hot, I wonder if something has burnt out, if I am going to try and send it back to TMobile under warranty I guess I need to flash a stock ROM and would have done this through Odin but that is not an option
Does any of you genii out there know how I can fix this?? I am not such a newb and work in IT so have a gut feeling it is a hardware problem that is not easy to fix however one of you may know what to do.
Thanks in advance.
You could use mobile odin to flash the stock rom back, it sounds like your micro usb connector has gone faulty, its a common fault with the Galaxy S2.
I already answered you in your other post.
Please don't double post. (forum rule #5)
ctomgee said:
I already answered you in your other post.
Please don't double post. (forum rule #5)
Click to expand...
Click to collapse
Sorry about that I originally posted here then saw that it was probably the wrong forum, so I reposted, can I remove this one??
Ok guys after hours of wiping a flashing I have got to the bottom of my problem, I tired cleaning the usb port on the phone as suggested in the general forum and tried installing some mobile dev tools from microsoft, neither of which seemed to work, although I did manage to blow quite a bit of dust out with the compressed air!! Then I read a post where one guy was doing all his flashing without the sim and sd card installed, so I took both of them out and would you believe it I plugged my phone into my PC in download mode and odin picked it up! to I booted the phone plugged it back into the PC and voila it picked up the phone without errors as a mass storage device!! , I put the sim back in and tired again, picked up mass storage device again!! , so I figure my sandisk 64gb micro sd card has become corrupt, I have backed it up and formatted it in CWM and now that is picked up too!!! will transfer the data back over to it to be sure it is fine.
I wanted to say a big thanks to all who have offeed advie and help, especially nickmax1, cooza, ger5, daclaus and of course indie for his great rom, I lost the faith for a while there but have it back now thanks to you guys, it is a pleasure to be part of this great community.
Cheers all
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
GOT IT!!!!!!!!!!!!!!!!!!
plymouthrock99 said:
I have a BLU Quattro 4.5 android device and when I try to connect via USB Debug mode and run ADB Device it will not find my phone. I have searched high and low in order to locate the driver with no luck. The generic USB driver from google won't even work. I have even run emulator from the phone and when I type: pm set-install-location 2, it comes back with Killed and then back to command prompt. When I type: pm get-install-location it comes back as 0[auto]. My phones main memory is 1 gb and 1.5 internal usb memory. With all of the main system apps updated on the main drive, the phone cannot handle ANY other apps, even when I put apps on the usb memory it is very sluggish. I need help in trying to install and run all of the apps from the external sd card and just have the system apps running on the main disk. I would also like any help in finding the driver needed to access the phone in ADB.
BLU Quattro 4.5"
4 GB Internal Memory( Broken up to 1 GB Main, 1.5 GB USB Storage, and not sure where the other .5 GB went.)
1 GB Ram
NVIDIA Tegra 1.5 GHZ Quad Core
16 GB Class 10 Micro SD Card
Android 4.0.4 ICS
Unlocked Running Straight Talk/T-Mobile Sim
Click to expand...
Click to collapse
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee! pdanet.co
plymouthrock99 said:
found generic driver from PDANET that finally allowed me to access my phone from ADB and I was able to make the necessary changes. Yippeee!
Click to expand...
Click to collapse
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
I have one as well and was able to root it with the latest bin4ry tool! Hopefully Blu will enhance their customer support as they gain more popularity and release some source code or dev tools for the phone. Or at least, since it's rooted, the device can eventually gain support from any devs.
Kah,
Can you post root instructions for us, please?
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Any Information posted in this thread is Great!
I don't mind taking this off track of what the original thread. I like it that it is progressing the way it is, helps me out with other questions and anyone else that starts off with my problem probably wants additional information on what else could be done with these phones.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Average
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
londonflu said:
Good news! I just bought the same phone, and I'm waiting on delivery as we speak. From the reviews I've read so far this phone delivers the most bang for the buck. I just hope that we'll be able too root it soon. How do you like it so far?
Click to expand...
Click to collapse
plymouthrock99 said:
I am still having issues with ram and touchscreen when main storage location gets full. It becomes very unresponsive and the touchscreen becomes very sluggish. Some things I cannot move to the external sd card and all the installed apps still get installed on primary drive even after changing default install location. I need to figure out how to install and run everything, including the android os.
Click to expand...
Click to collapse
Try using Mounts2SD..
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
j21blackjack said:
I doubt I'll get much help on this, but I'll give it a shot. I just got my Quattro 4.5 today, and tried to root it with Bin4ry. It never did the first reboot, it just turned the phone off. After a few minutes I turned it back on still connected to USB, Bin4ry tried to finish, but gave a permission denied error on the superuser apk. Now my phone is in continuous boot loop, it gets to the lock screen, but says Go Laucher and system UI has stopped, then reboots. Is this thing bricked? Holding volume down and power just goes to a modem download screen, but no USB connection or anything. :crying:
Click to expand...
Click to collapse
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
kah1593 said:
I'm sorry to hear than man. Which version of Bin4ry did you use? You could try quickly using adb to boot into recovery mode while the phone is still in the process of booting. You'd have to keep sending
Code:
adb reboot recovery
until adb recognizes the device. Hopefully, it'll restart into recovery before it crashes. Not sure if it'll work, but it's an idea.
Click to expand...
Click to collapse
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
j21blackjack said:
Everything is fixed! I figured out how to get into recovery. I was able to do a factory reset from there and everything came back, actually maybe better. Then I found an old version of Bin4ry, v15, and tried again. This time it worked perfectly. This phone is pretty awesome, I just wish there was developer support for it.
Click to expand...
Click to collapse
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
kah1593 said:
Great! How'd you manage to get into recovery mode despite the boot loop? In case anyone else runs into the same issue.
Click to expand...
Click to collapse
Hold volume up and power until it turns on. As soon as the screen changes to green, I let go of the power button and keep holding the volume up button until it's in recovery mode. It seems the power button release has to be timed right or else it just sits on the green screen, or powers off again. It takes a couple of tries for me. I probably did 10 factory resets last night before finally getting it rooted, lol. The built in recovery has an option to flash from external storage, kind of makes me wonder how easy this phone would be to get CWM working. Of course, the real problem is getting developers to write the custom ROMs for it. The only thing this $230 phone is missing from its $600 cousins is 4G LTE, but on Tmobile it doesn't even matter right now. It's still blazing fast even on stock with no overclock, I can't imagine how much more awesome it would be with a custom rom.
kah1593 said:
Sorry, I would've posted before but I wasn't sure if that would move the thread off track. It was very easy actually:
Make sure adb recognizes the device (mine said 123ABCDEF... or something like that for some reason. It doesn't matter apparently).
- Also I'm using windows 7 and after allowing the few default drivers to install, it worked instantly. ( I believe. I do remember messing around with some other software, but I think that was in hopes of finding a root tool. If you have any issues, I can post the names of other software I tried. The OP's method could possibly work too)
I downloaded Root_with_Restore_by_Bin4ry_v23.
- there's a new version out now, but I would expect it to work as well
I choose the normal mode and followed the directions.
- If I remember correctly, it gives you the option to install superuser or super su. I chose superuser, and it worked. But after using it for a bit, it gave me lots of issues with root privileges, so I installed super su from the market and I haven't had an issue since.
Click to expand...
Click to collapse
Can anyone post a link of where I'll find the proper drivers? It just shows BLU with an exclamation in my Device Manager. The PDANET trick did not work as it won't detect the device. - and if I can get this working, I'll post an actual tutorial for it.
If anyone could post an update.zip of the original rom that would be fantastic. - and clockwork 6 will run on our devices with some work. but right now, mine is a brick, it still has recovery but the stock rom is effed.
I'm in the same situation. I deleted my contacts.apk in hopes of replacing it with a stock version, now it's stuck in a boot loop, and factory reset doesn't help.
Alright guys, I hit the jackpot. I have CM 10.1 working on my Quattro 4.5. It all began when I read somewhere on the xda forums that the Quattro 4.5 and k-touch v9 are essential the same phone. I said before, my phone was bricked so I figured I do some more research and see what I could do. Turns out that person as right. I found a website ( http://www.needrom.com/phone-roms/k-touch/k-touch-v9/ ) that has 3 roms for the v9, CM 10.1, MIUI 3.4.5, and CM 10, and instructions to install them. I decided to take a leap of faith and follow the directions given for CM 10.1. The installation directions for custom recovery CWM 6.0.1.1 worked perfectly - only problem is after you've installed the recovery, the menus are in Chinese.
Once again, My phone was bricked and essentially completely erased. If your phone isn't bricked, it should be fine as long as you do a factory reset before. I would suggest doing this before installing the CWM recovery because I have no clue how to do the reset using the Chinese menu.
I downloaded the CM 10.1 rom from the website above and gapps for 4.2.2 as well (you can find this with google). If you're using one of the other roms, obviously make sure you're using the proper gapps version.
ADB works while in recovery so use this to push the zips to the phone. I say this because I've discovered the sd card directory changes depending if your phone is bricked or not (i.e. /emmc vs /sdcard).
Flash the rom zip, then gapps - select the 2nd option in the main menu then in the following menu, the 4th option. This should lead you to the directory containing your zip files. Choose the appropriate one, and let the CWM work its magic. ( also from messing around I can also tell you the first option in the main menu is to reboot)
Once you've reboot, everything should work perfectly - WIFI, bluetooth, brightness, camera, video recording, audio, microphone, not a single problem except the volume being much louder than before. It's amazing. I have straighttalk's $30 plan, so I'm still stuck with a dumbphone until I bump up to the unlimited everything at the end of the cycle, so I can't test the phone radio, but I would expect it to work considering everything else does as well. Let me know if I left something out. I would test the other roms, but I'm so happy and content with my phone working again, I don't want to go through the effort just yet.
I found a way to create an English recovery that works from the Chinese version. Just replace the recovery.img provided with this one. Here's the link: https://www.dropbox.com/s/5y6r9gvspvouhbo/recovery.img I don't think this should cause any issues because it hasn't for me, but remember you are using this at your own risk. Though if an issue does arise, I'll try my best to help.
Install with English Recovery?
Did you install with the English recovery, because I am stuck at CM10.1 boot screen installing with the English recovery.
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Hopper8's 'Odin troubleshooting' thread stickied in the General section; in particular flashing the 3 part firmware (this will wipe your phone). Also try everything in that thread for as long as you have the patience for it. These cases tend to be fixed by perseverance, or not at all. There's no easy fix. It's either a hardware issue(s), NAND corruption, or something really obvious being missed here. If it's the latter, hopefully the stuff in Hopper's thread helps you fix it. If it's either of the other two, I'd be cutting my losses.
Ansell2k12 said:
Good evening all, my apologies in advance if i am asking a stupid or already answered question,
i have looked through this forum and many others along side through google and i am unable to find a solution or solved post in regards to fixing this phone.
I recently purchased a second hand s2 from ebay, not the best move but it was cheap, and i was in need of a phone.
the phone came with damaged screen, so i ordered a replacement and thought no more.
after receiving the screen i replaced it fitted it and was in the belief that the phone would be up and running, no no no this is not the case...
upon fitting the screen i found that the phone would lag as such, as if two fingers were placed on the screen, with motions being very sticky also requiring a large amount of force to respond when trying to use it. normal androids will switch between home screens effortlessly and relatively fluid.
Seeing this issue i thought a simple firmware upgrade would suffice and id have a usable phone. upon upgrading via kies i was unable to install the MTP drivers and so switched to the program odin for the update.
i downloaded what i believe to be uk firmware from samsung-updates,
firmware I9100XWMS2_I9100BULS3_I9100VODLSF_HOME
which has also caused the phone to boot in what looks to be spanish. although e3 and cwm show in english.
after the update the phone seems to be in a soft bricked state, the phone will repsond to input from soft keys, go into recovery and download mode accept all firmwares i have tried 9 times out of 10. but when reaching the android home screen is completely frozen, no response from touch or soft keys, except only for volume up and power to reset the device.
thinking the recently purchased LCD was the culprit i have sent it back and had a replacement, still the issue is present.
I have tried many different roms/kernels in the hope to solve this problem and i am at my wits end!
any help in bringing this thing back to life would be of great help as i am without a phone, or enough money to replace it again...
thanks for any response
cheers Ansell2k12
Click to expand...
Click to collapse
lcd may be the culprit but also the firmware is crashed flash it again properly after a factory reset from e3
Progress...but not as id hoped...
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Ansell2k12 said:
first off thanks to you mistahbungle & bhavstech,
unfortunately im only little further forward.
After the flash using 3 part file firmware the phone is now running in English language on an updated firmware, but still appears to be frozen/ crashed.
updates on appearance, maybe its still salvageable?
Clock now updates after reboot
English language
charge icon does not change when unplugging/replugging charger/data cable but is recognized by the PC - MTP is now installing, but requires reboot, after reboot of the PC, MTP installs again and request reboot again... and continues to do so.
clock doesn't update at home screen, again appears to be frozen/crashed
still no response to touch, touch buttons or soft keys - only phone rest volume up and power.
when phone is at samsung splash screen i get notification of voice mails/texts on the phone.
Thanks again Ansell2k12
Click to expand...
Click to collapse
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
king_below_my_lord said:
Your issue of a semi frozen state is very familiar to me but the reasons can be many and one of those are the /sdcard partition not mounting properly and likewise it could also be a failure of the other major partitions but if the device booted and made it to the lockscreen then you may have some hope, first if you have a external card plugged try booting without it, if the issues repeat try swapping the ext card with the internal /sdcard by flashing a modified vold.fstab file for your firmware which swaps the partitions effectively making the device mount the ext card as the /sdcard partition. I am expecting you have gone through the default troubleshooting methods like a clean flash etc.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Ansell2k12 said:
Yes i have done multiple flashes, tried another sd card as the original was unreadable by the phone but picked up the second faultlessly, although flashing a custom firmware failed when trying to load in cwm.
as for a modified vold.fstab file,this is new to me. Could i ask how its modified or where i would get the file? im guessing id use odin to flash it to the device?
thanks for the response
Ansell2k12
Click to expand...
Click to collapse
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
??
king_below_my_lord said:
There are some threads in which I myself detailed about swapping memory its done via a custom recovery and not using Odin.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
any chance you could point n the right direction?
i have had a look at the stuff to edit vold, and it seems i am unable to do so as my phone isnt usable once booted
cheers Ansell2k12
Phone has gone in the bin cheers guys, thanks for the help
....
You could easily flash a edited vold.fstab file by generating a flashable zip file. That's why I said via recovery or if you are clever enough you can easily use recovery flashable Aroma file manager to overwrite the file.
Sent from my GT-I9100 using Tapatalk