[Q]Oh dear God, what have I done?! - HTC Desire S

Well, I fear I may have completely buggered myself this time...
I unlocked using HTC Dev, and then followed: http://forum.xda-developers.com/showthread.php?p=26181347#post26181347 to root my device, which worked perfectly, big thanks to the guy for taking the time to sorting that out!
Now, Billy big balls here thought he was an expert because he'd done it once, and now thought he could install a custom rom, and, I can't load past my network providers screen. I think, with hindsight, I should have asked if it was compatible, my, HBOOT is 2.00(blah), which I fear may have been where I went wrong...
Now, I've got nothing on my memory card, I tried to clear the data, like some videos said we should do. But, it didn't work. So, I've took the memory card out, put it in another device, and put Fastboot and dll file, as well as the .Zip I used when I first rooted the device, and nothing. Still can't get passed the network providers screen.
I was wondering if you guys could help me out, but do it in very newbie and clear steps! (I am a bit slow)
Many thanks in advance guys!

Did you flash the boot.img separately?
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

Have you flashed the kernel?
fastboot flash boot <path to boot.img>/boot.img
Yeah - What he said :O

Can you still access the bootloader? Volume down + power

Firstly, thanks for the speedy responses.
Secondly, I have no idea what you guys are saying... What does all this mean?
But yeah, Dan-Fish, I can still access that menu, and I can still go into recovery mode!

OK
Now go to boot loader
Select fastboot using your volume keys
Hit power to get into fastboot mode
Connect to PC
Type
fastboot devices
Your phone should be listed here
Then extract the boot.img from the ROM's zip that you flashed
Fire the command
fastboot flash boot <path to boot.img>/boot.img
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

Because you unlocked with HTC DEV you need to make sure that you flash the correct kernel separately from the ROM. Have a look at this http://forum.xda-developers.com/showthread.php?p=19071114#post19071114

Right, I've finally managed to get that done, Suku_Patel, and thus far, it has loaded further than it has before, I am aware that it takes some time, for first boot especially, so, I'll give it a chance. As I speak, it's loaded up.
It's gone through set up, and it works! Many, many, many thanks for your help with this!

A afterthought, read the guides, can't count the number of times I have swyped the fastboot command.....
Sent from a Desire S waiting for Kernel 3. WAKE UP HTC!!!!

So, after the initial problems, and following the steps, it all worked perfectly, however...
I didn't like the ROM I was using, it kept cutting the volume in calls, and the camera didn't work, etc. Titanium back-up also did not register that it was rooted, so, I want to change the ROM.
I've got the ROM that I want, and I thought I'd done it right... Cleared all the data, etc. Again, I'm stuck on the loading screen. It gets past the vendor screen, but, fails to boot completely.
Is there any advice/help that you guys can offer me?
Many thanks in advance.

Repeat the steps for boot.img
Sent from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!

I'm pretty sure I have, I've:
Extracted the .img on the SD card, with the .Zip there,
Shut down the phone, started it in Fastboot, USB connected
Opened CMD prompt: Fastboot Flash Boot Boot.img
Done that, then restarted it with the ROM installed
Then it just gets stuck after my service provider, on the what would be 'HTC screen'. And fails to boot. I am a quite patient man, and I am aware that it may take a while, but, it's been on this for an age!

You need to extract boot.img to your PC, not to SD card. You're flashing from PC!
Why can't people follow the guides...

Related

More B63M users here?

Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
B63M... thats my phone
Henkdrenth said:
Hi all, I just ordered a Chinese B63M phone at cect-shop.
Nice phone with great specs.
I alreadu know how to root it, but are there already custom Roms available?
Could'nt find a lot of info, just a Russion version.
Click to expand...
Click to collapse
Now that makes us 2 people who owns a B63M and got it from cect-shop.
What I find out about their phones is that it may not easily allow you to perform some insider operations, for instance, maybe its me but I could not find any custom recovery installed and this led to my first issue after I rooted, and installed the ROM manager, I saw the 'fix permission' and clicked it hoping to resolve my force close issues and it asked me to reboot after performing the process but it never got out of the boot, the loop continued, trying to boot into recovery become impossible but somehow a combination got me into a mode where I was able to clear flash and this took me back to a pre factory flash good thing I backed up titanium so I cld restore my apps and upgrade.
Right now I have tried to flash and the screen has gone blank yet the phone is responding to touch as I can hear sounds when the screen is clicked, indicating that its not bricked I just cant see anything going on (this is my current situation and seriously looking for help).
Lastly, I am trying to find out the htc equivalent to this b63m, it looks htc but I cant be sure which of the htc has been more or less cloned... this is going to help with a lot of things if known.
Cheers
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Cect is German
Henkdrenth said:
Hi there,
If you are looking for a custom recovery, try this forum, altough you have to translate it because it is in German.
Lots of people there with our phone end they know how to get a custom recovery on it.
Click to expand...
Click to collapse
Yeah thanks, I have also stumbled on the site forum before but I cld not get something out of it, maybe I have not taken time enough to search, I am back on it now and hope I get a solution to the blacked out screen problems I have after flashing.
You know cect-shop is German, they are a German company in China... I am talking to them on skype and hoping they can help me out but they seem pretty busy or cant be bothered because their response is so much delayed or even not at all.
Well technoforum has a special B63M section with all tools required.
They also have nice custom roms like a Cyanogen fork.
I also don't speak Italian, but with the help of Google translate I'm getting pretty far.
But I do let Google translate from Italian to English, that gives me the best result.
Good luck!!
Do you also get no working screen after a reboot with both volume + and power button?
That should get you to the recovery screen without any ROM drivers.
Very correct, no screen even in recovery
When I do the button combination, I believe that it may have responded to my combination for recovery mode but I just cant see anything on the screen, it just remains the same way it was... maybe it graphics issue, as in is the graphics is messed up for some reason or resolution issue, you wont see anything being displayed.
I am just guessing here but all I did was to simply flash an update.zip from sd card.
That is very strange, since flashing a rom does not affect the screen of the recovery boot.
The rom video driver gets only active during the boot process of the rom.
In the past I had some boot problems with my Wildfire start-up that I solved by removing the SIM card and SD card, removed the battery for some minutes and them booted completely resetted.
You could try that, if that does not solve the problem, the only way to wipe the phone back to factory-reset is doing it blind.
After I get my phone I could make a step-by-step guide so you could get to the reset menu...
Another possibility is to re-flash a fresh recovery img to the phone. Since I don't know what was in your update.zip, you could messed up the recovery menue, or even the bootloader.
Re-flashing those could also help and you don. t need the display from the phone, since you use the PC for that.
Here it is
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Waiting on you... I hope my blank screen gets sorted.
balamu96m said:
I too have a B63M...!!! Spice Mi-350n...........
If you need a moded recovery, i can port it for you........but you need to follow some instructions...i'll give them tomorrow!!
Click to expand...
Click to collapse
Ahh thanks man... Ii will wait to hear from you tomorrow, I aim in UK and depending on what time zones you are in but I hope to find you online to connect again.
I hope you have understood my particular issue here tho, the screen if blank even tho the fone seem to be alive and it follows the boot sequence, I can even find it using 'adb devices' command, it just the screen gone blank.
Someone suggested it may be the boot.img but I dont know about that.
Cheers
I'm from India - Local time here is GMT+5:30......!!
So, here you go !!
B63M= MTK6573 + 650mhz + Android 2.3
So, one modded recovery.img can't be used for every B63M.......this is because a different B63M phone will have a different recovery.img..........(hope u understand)
Backing up everything:
1) ROOT is necessary. It is recommended to put the phone in 'Airplane mode' so that it won't disturb the process and make sure you have ~500 mb space in SD card.
2) Download 'BackUpTools.rar' from HERE and extract it to your SD Card. You'll have 2 folders - 'gscript' and 'Install'.
3) Install 'GScriptLite.apk' from gscript folder.
3) After installation, open the 'GScriptLite' application -> Menu -> Add Script.
4) Tick 'Needs SU ?'
5) Click 'Load File' and select 'Back23.sh' and then select 'save'
6) Now Click on 'Back 23' and Super User will ask for Permission and allow it. Nothing more to touch. Wait for few minutes. After few mins, it will say 'Auto Close is Cancelled'. Now its safe to close.
7) Your Back-Up will be in 'backup_' folder located in your SD card's root.
It will have files named ' firmware.info, preloader.img, nvram.img, seccnfg.img, uboot.img, boot.img, recovery.img, secstatic. img, misc.img, logo.img, expdb.img, cache.img, system.img, data.img' in that folder. Copy it to your computer and keep it at a safe place. More Over if you are posting in the forums or sharing it online, don't include ' data.img, cache.img and nvram.img' as they contain your personal information.
Here i need two files.One is recovery.img and the other is firmware.info.
If you give both, i can port one for your phone !! Also mention your phone's model name/number because, without that it is not possible.
xdadeem said:
Here is the update.zip I flashed. http://chinamobiles.org/downloads.php?do=file&id=618&langid=4
HTML:
I am a bit surprised myself that the screen is blanked out but the phone seem to be working still.
I have removed both SIMS and SD card plus battery several times etc. nothing changed.
You said ''After I get my phone I could make a step-by-step guide so you could get to the reset menu...'', I hope you get your phone soon tho, and i can see the step-by-step guide you made.
I have actually flashed recovery into it using flash tool, ODIN dont seem to see the phone (at least the yellow box saying COm4 or 5 is not showing), I can see the phone using adb but when I say adb reboot download or recovery, something happens but I cant see what it is.
Click to expand...
Click to collapse
That was the problem, you flashed only the update, not a complete Rom.
I suggest you make a complete re-flash vorm scratch, so refash a fresh recovery.img and re-flash als a new Rom.
You can vind one at technoforum' as earlier mentioned
I thot you shd read my latest.
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Great to hear that you have visual again!
You still have root yes?
The golight rom from technoforum is a good one.
I expect mine any moment now so I can customize mine too.
Good luck!
xdadeem said:
Ok guys I appreciate this a lot.
Here at this point I think you shd hear my developments before taking any further actions or suggestions.
aha thanks, I did just that and it worked although it is still blank at the beginning of boot but later something shows up on screen and completes boots.
Remember I mentioned that someone suggested it might be a boot.img problem... well, I used flashtool to flash a boot image and I can say it worked, I now have the visuals, even tho the screen is still blank at boot start but soon after it picks up and its working, now I have the phone again.
so @balamu96m, my issue was basically the screen, without seeing anything I cannot follow the back up suggestion you gave me here, but now I can see it again.
A couple of additional issues tho...
1- I checked the kernel and it has changed from 2.3.5 into 2.3.4 and >In the current ROM flash I have lost a couple of capabilities like Flashlight, camera etc
2- I followed this link http://www.technoforum.it/forum/viewtopic.php?f=73&t=3351 to flash recovery and it says Successful with the green Circle -OK-... but I still cant get boot into recovery either when I use the keys combi or when I try to boot into recovery in mobileuncle tools, it just goes blank and stays like so until I have to remove the battery and restart boot normally.
3- From the same link above they have the Golight ROM in part 2 after recovery in part 1, I am assuming this a good ROM to flash and the things I lost will get back, but I still cant boot into recovery.
Coming back to the response from balamu96m... Should I still go ahead with what yu suggested and provide you the files details you want? both recovery.img and firmware.info... I am asking because I no longer have the original ROM that came with the phone and like I said I cant even get into Recovery after I tried flashing a new recovery.img, this one from the same link above (see the recovery.img inside the 'Recovery Moddata' file from the 'UPDATEB63MRecovery2012' download file.)
Click to expand...
Click to collapse
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
It was always so
balamu96m said:
You flashed a recovery, but that is not working ah?? Oh God!!
Why did you do that bro??
Do you have any backup of the stock one??
If you dont have, then i have 2 ideas....one idea is to flash something else such that your fone won't boot....now you can send your phone back to the manufacturer and ask them to reflash everything!!!
The other idea, i'll tell you after sometime!!
Click to expand...
Click to collapse
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
xdadeem said:
The reason i flashed recovery initially was that my phone went into a boot loop and I was unable to get into recovery, after a while somehow i figure it out and cleared flash and then restored my phone apps and co and got on fine.
But if I could not get into recovery it means that there was not stock recovery on my phone or it got missing somehow. This I have to ask Henkdrenth since he is getting the same phone from the same shop too, but there was no recovery in my B63m, I already heard there is a recovery problem with the phone anyway, and thats why I flashed recovery and it worked but then I flashed ROM and the screen went blank, which is what got me to this forum.
I did not just go and flash recovery, it because there was none on the phone in my opinion.
Click to expand...
Click to collapse
Now, is the recovery working??
Does the phone boot properly??
Wrong section. Moving to general.
YES and NO
balamu96m said:
Now, is the recovery working??
Does the phone boot properly??
Click to expand...
Click to collapse
After many troubles, I found a mod for w690 which is the build version of my phone, I could not boot to recovery so used flashtool and when I load the scatter text of the one I found, it automatically load in every item on the list including recovery and boot img , etc, so I flashed these to my phone... and for the first time I was back in how the phone came to me,
Gingerbread has now returned to 2.3.5.
One thing I have noticed is that the phone freezes on me and then reboots?
I still cannot boot into recovery, I tried this again using mobileuncle tools...
It seem that I have flashed my phone which is good, but I was unable to wipe cache because I could not boot into recovery to do this which may be the source of the current freeze and reboot.
Can I solve this using the mobileuncle or what can I do to wipe cache, if that is the problem
Well, received mine, rooted it an flashed a new recovery from technoforum using myuncletools.
All went well, so I suggest you do also a fres re-flash with a proper recovery.
Hope that should solve your problem.
Edit: moved from my tablet to my PC to look for the link of a correct recoveryfile for you.
First, load this recovery.
Unpack it and put the content to the root of your SD card.
Use myuncletools to flash this recovery.
Now you should have a usable custom recovery that allows you to factory-reset and wipe your phone
Install a fresh rom
How to? Look here

Officially desperate. Please help. Will pay in form of just about anything.

Hi all,
Here is my sad saga.
Today, I decided I wanted to move up to ICS. I had 2.3.4 on a Koodoo phone that I decided was ready for the brave new world of ICS (bought it off Kijiji, now running it on Rogers which means I have no option of bringing it into a shop).
Ran into some issues but some good folks saved my butt in a number of tough spots. However, my grave seems to have been dug deeper by the minute. Essentially, I have managed to upgrade to 4.0.3. but am stuck with no 3G connection, hence no phone signal. This is a HUGE issue since I require my phone for work (foolish move #1 of the night).
Here are things I have tried and the challenges I have faced thus far:
1) CWM. Have not been able to access it or install it successfully. However have somehow managed to root the device. I did it through a one-click root/CWM tool I found online but have never been able to access CWM from the recovery screen, only stock recovery.
2) Changing the radio baseband version. Fail, since I have no CWM. Or Root Explorer because...
3) I can't access the google Market as I have no data connection. And did I mention no wireless? I live out in a rural area (sad story #1). It's ethernet only, sadly
4) Also, I have very limited access to a PC. I do have one at work, but I have my own macbook. Although I could use the PC at work to try some stuff out, I can't be spending my entire day Googling for help. Seems like employers would frown greatly on it. I've already spent a solid 4 hours on the forums and Internet tonight trying to find something that works. Absolutely no dice.
5) Attempted to get back to 2.3.6. No joy. Phone won't budge from 4.0.3. and I think it has to do a huge part with no CWM.
6) Factory reset a number of times. Still stuck on 4.0.3. with no 3G connection.
7) Reset APNs to default. Still no luck. Perhaps it isn't the radio baseband after all?
8) Also tried entering and leaving airplane mode a number of times. Zero luck.
9) I have a pretty low comfort level with PCs to be honest. I am open to all instructions, as long as they are detailed and written For Dummies.
Please help. I really, truly do not know what else to do or where else to turn but the forums. I've tried everything I could think of and I'm afraid this will impact my job since I need to be in constant phone contact for work. I'm exhausted from stress and worry. I swear this will be the last time I experiment with my phone (I know I've said it before, but this time I MEAN it!)
Thank you all you kind-hearted folk out there for anything you can do to help.
first cell phone model you have and that you had changed baseband before all ... You can also try a new version of CMW in case, can also be kernel problem that uses TO in the mobile ...
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
You have to relax first lol. When you're panicky nothing gets done so calm down. Do what the guy above says. Install cwm with fast boot. First install the android sdk then get the drivers. Get fast boot file down as well. Remember that the command fastboot flash whatever varies from operating systems.
With cwm installed, do a test. Backup your efs folder , which is essentially extremely important. You would better do a nandroud backup. Then, try various radios. See if that's your issue. If not change to trying out new roms . Worse case scenario go back to your 2.3.6 rom by flashing with cwm or install cyanogen mod 7.
Best of luck
Sent from my Nexus S using Tapatalk 2
dreamsforgotten said:
So you have a nexus with barely PC access running ics minus a recovery. Good news is your in luck. You need proper tools to do the job. Easiest method is either on that Mac or at work, install the phones drivers. search Google for the fastboot binary for the operating system your using. Once the drivers are installed boot to fast boot not recovery but the screen where you choose recovery. Open a terminal on the PC and type fastboot devices. No period. Should return a serial number on the screen. Your good to go. When you download the fastboot program, put it in a folder on the PC. Also put cwm for your phone in a .img format not a .zip. That should give you a name like cwm-2.5.5.0.img. When you open the terminal, navigate to the folder with both files. After typing fastboot devices and seeing the number type fastboot flash recovery cwm-and-whatever.img
That should give you cwm.
Also you got root have you tried downloading rommanager apk from the net putting it on the sd then installing. Once it installs try to flash recovery from the app
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Follow dreamsforgotten's instructions should get you out of the problem.
And yeah, relax.
You flashed the wrong ROM. the i9020a never got 4.0.3, it went straight from 2.3.6 to 4.0.4. you flashed a ROM for the i9020/i9023. This means that you have a US modem, a problem with those in the gingerbread days is that if you toggled 3G off, you lost it.
Now, I'm not 100% sure this will fix your issue, it *will* bring you back to proper stock image for your phone. Also, keep in mind, that you are responsible for anything you do to your phone, I in no way take any responsibility.
Instructions are for windows
Start by downloading the factory image:
Factory image for your phone
(ref) https://developers.google.com/android/nexus/images
Uncompress this file, you will need the following files:
Image-sojua-imm76d.zip
bootloader-crespo-i9020xxkl1.img
radio-crespo-i9020uckj1.img
Put these all in a folder, you'll need them shortly
Now you need to connect your phone to the computer. follow this guide, part 1 ONLY:
http://forum.xda-developers.com/showthread.php?t=1007782
You should still be in the bootloader when you do the following steps, (turn phone off, press and hold the volume down, power up the phone)
Grab a copy of fastboot.exe and put it in the folder with the IMG files (PM me if you can't find one)
Now, test to make sure your phone is seen by fastboot:
Open a cmd prompt and go to the folder where the img files and fastboot are stored.
Type: fastboot devices
you should get a response like this:
C:\temp\nexus image files>fastboot devices
xxxxxxxxxxxxxxxx fastboot
(x's will be alphanumeric)
This means that fastboot can now see your device. if you get nothing, something went wrong above.. troubleshoot that.
If everything is good, start flashing:
fastboot flash bootloader bootloader-crespo-i9020xxkl1.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020uckj1.img
fastboot reboot-bootloader
fastboot -w update image-sojua-imm76d.zip
Reboot your phone and be *Very* patient with the first boot.
You should now be good.
Thanks all so very much for all the help! It was extremely helpful and really helped to get my head around things.
What I ended up doing was (for those who might be stuck in the same situation as me):
1) Wipe everything. EVERYTHING. Used fastboot into CWM to help me do that.
2) Put in Kustom Kream found here:
http://forum.xda-developers.com/showthread.php?t=1399956
3) CM9 from here:
http://download.cyanogenmod.com/?type=nightly&device=crespo
* Not super stable to be honest; I've had at least three times where my entire phone randomly shut down and went into the CM9 boot screen and was stuck there until I did a battery pull. Reinstalled each time through CWM. Hope this gets fixed soon!
I found that Kustom Kream put CWM AND rooted my phone AND had everything working in terms of radio bands, sending SMS, etc. I originally had major issues with radios but now I have KB3 although the signal is kind of weak. Maybe because I live in a relatively far out suburban area?
But this solved my problems. Good luck to anyone out there stuck where I am, I feel your pain!
I would recommend that you at least flash a radio that is designed to work with your model - ucjk. That way you won't have any issues if you toggle to 2G.
Sent from my Galaxy Nexus

[Q] One S Brick? HELP!

Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2

HELP PLEASE. iM EXPECTING AND EXTREMELY IMPORTANT WORK CALL!!!!!!!!!

edit
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). The Switched to the Galaxy note & S3 for a while NOw Im using the HTC one S. I normally never have these problems or ever post on the forums. But Im desperate for fast help. I know how to do everything on both the htc evo 4g and design.
but The Ville is diff. without the removable battery
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
ultimul said:
why would you flash something made for HTC ONE S if you have HTC EVO
especially when you're just starting to learn about
sorry, but I would guess that you're chance is to find somewhere a ruu for your model
Click to expand...
Click to collapse
I have the HTC One S Ville
I was stating how I use to have the evo
gisaac2157 said:
I had the hTC EVO Design 4G as pretty much my first Smart Android. (Im not including the LG optimus M). There is no development forum for that devices in XDA so I used SDX-DEV I actually started learning how to kang my own roms.
im blabbering....
let me try to STEPbySTEP explain my steps up to my not working Device.
!. I tried to Flash the Energy_9.07.2012.OneS.zip rom through TWRP at first. (thats was the suggesttion in the thread. So that the recovery would Flash the correct Kernel. But upon reboot. I discovered that contrary to the devs suggestion the WiFi still didnt work. So I flashed CWM through ROM manager. reboot into recovery flash wiped cache/ factory reset. But I dont think I wiped system, data, or anything not in the main Menu, Energy_9.07.2012.OneS.zip and I reboot. Upon reboot the HTC screen had the warning for use in htc do not distribute...then the bootanimation popped up and finally the booted up fine. Wifi was working this time. But now my network wasnt right. I didnt give the rom time to settle in though. I panic and open CMD and ran adb reboot fastboot.
Waited waited
now the boot loader was up. I had to unplug my deviice for the screen to show fastboot usb.
then this is where I think I ****ed up my phone
(I extracted the boot.img from the Energy_9.07.2012.OneS.zip and placed it in my android folder on C I also adb pulled my twrp recovery to
C:\android and renamed to recovery,img I wanted TWRP back I hate how CWM automaticaly boots when you plug it in tp charge from dead)
Now I had in my C:\Android\boot.img and \recovery.img.
I ran the command (im not sure if I ran boot or recovery first)Also my phone was anywhere near a full battery cloase to dead but my CMD window showed complete.
C:\Windows\system32>fastboot flash boot C:\android\boot.img
C:\Windows\system32>fastboot flash recovery C:\android\recovery.img
Now my phone is plugged into my Lenovo Thinkpad t410 with Win7 Pro OEM The red light to the top right isnt blinking like the battery to low to power on notification. Its steady. but when I hold down to turn on either the lights for the capacitie buttons flash untill I let go of the button or I do a combo of plugging in and out the usb and holding the power and volume bottons not sure Which order. PLEASE HELP! iM EXPECTING A PHONE CALL ABOUT A JOB INTERVIEW RESULTS.
In my time in CMD this error did pop up a few times. But I open HTC sync let it load. and then it would work.
C:\Windows\system32>adb reboot device
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
Would A ruu fix this????? Although I haven't once successively used one.
COMMENT, PM, IM, ME I DON'T CARE JUST PLEASE HELP ME AN MY POOR [PHONE] GUARANTEED THANKS BUTTON!!!!!!! USAGE AS FOR HELPING.
Click to expand...
Click to collapse
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See http://www.4shared.com/folder/jKN2qjTl/HTC_Ville_RUU_Collection.html for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
gisaac2157 said:
I have the HTC One S Ville
I was stating how I use to have the evo
Click to expand...
Click to collapse
can you reboot into recovery/fastboot? press the power button for 5-7 seconds until the keys start blinking;
the phone should reset after it
some RUU, you can find here:
http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Thanks so much.
AKToronto said:
If you hold down the power button long enough the leds should stop flashing. You should try that and then once it goes off, hold down the volume down and the power button.
That should get you back into bootloader. From there you may want to try flashing a custom kernel (the SENSE version of Fusion, for example).
An RUU could help, but you would need to relock your bootloader in order to flash it. You would need to be able to get to your bootloader screen. RUUs are EXE files and are pretty self explanatory when you run them and have your phone connected. See <font color="red"> as a new member cant post links</font> for RUUs. There is also a thread on RUUs in the development thread. Read that too.
But first things first, you need to be able to access your bootloader! Keep fiddling with your power button and volume down button.
AKToronto
Click to expand...
Click to collapse
I feel really stupid for not knowing THAT. Now whats up with the energy rom? the thread says stable. How am I suppose to flash it?

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.
matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2
UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.
matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app
matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!
befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....
Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.
You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app
You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

Categories

Resources