Related
I updated the Radio on my 32a then I went to Fastboot mode to load the hboot image and discovered that i get a (failed : remote not allowed) message everytime I try to flash anything. So I guess I need a goldcard the only problem is I can't boot up to reformat the SD and make a goldcard...
Any idea's??
I'm lost!!
Can someone make a Goldcard for me, on another phone? I don't know what to do,
Thanks in advance...
anyone???
I'll pay for a goldcard if someone sends me one, assuming I can use one made on another phone in my phone. I need a way to get past my Fastboot mode and I can't boot to recovery or get anywhere else... to make a Goldcard
HELP?!?!
i used my memory card that came with my phone to create a gold card and it worked perfectly well just make sure you follow the guide to the letter.
you cant use one from another phone as you have to get the CID from your phone which is unique from phone to phone.
i believe what you should of done was flash the image first then update the radio but just search the forums theres bound to be someone with the same problem or even a google search might help
icow said:
i used my memory card that came with my phone to create a gold card and it worked perfectly well just make sure you follow the guide to the letter.
you cant use one from another phone as you have to get the CID from your phone which is unique from phone to phone.
i believe what you should of done was flash the image first then update the radio but just search the forums theres bound to be someone with the same problem or even a google search might help
Click to expand...
Click to collapse
But I can't use my phone to make a Goldcard because I can't get it booted up to a point where i can use adb shell. Only Fastboot
use a card reader. if you don't have one, go buy one, they are very useful to have lying around...
hi
please please please my phone is completely dead can i use the blue led mode ?? or the gold card to revive it and use fastboot again????
march83 said:
use a card reader. if you don't have one, go buy one, they are very useful to have lying around...
Click to expand...
Click to collapse
How does a card reader help me get the cid number off the phone? Don't i still need to get to adb mode to do that? which means booting the phone up which it won't do...
What's your HBOOT version? I got that while upgrading my RADIO. All I had to do was install an engineering SPL first. Then I was able to flash the new SPL.
you need to post more info. what radio did u upgrade to and whats your spl/hboot? Also, what recovery did u use?
I also noticed you saying something about the blueLED, I thought you could still get into fastboot...
can you still get into fastboot? I'm confused, cause you went from being able to go into fastboot and then now it's completely dead?
current set up
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT - 1.33.0010
CPLD-12
RADIO-6.35.00.29 (was 3.22.20.17 before update)
June 2 2009, 17:28:28
I the current recovery is RA-magic-v1.2.3H and I was trying to upgrade to RA-hero-v1.6.2 and Hboot 1.76.2007.
I got the radio upgraded but when I go to Fastboot to flash the hboot i get the (Failure: remote not allowed) error. So I can't change anything with the current hboot. I'm guessing I need a goldcard since I can't get to recovery mode, but every set of instructions for making a Goldcard requires the phone to be in adb shell mode which i can't get too.
At this point i don't care if i get the new radio on or not I just want it working again. I was running the SuperD 1.9.3 ROM with the Old radio...
The Blue LED issue wasn't me, I dont know who that is or what that was about.. I CAN still get to fastboot
Um, is that an engineering SPL? I believe you need one before doing this.
Did you try flashing the old radio again? Also, how did you upgrade your radio? Did you use Fastboot or Recovery?
If you can't flash anything.. well I dunno what else to do, never seen this problem yet. Maybe someone else with some more knowledge can help you, but try searching. I'm sure you're not the only one who's been through this situation.
Give this a try, I have no idea if it works though.
(Read this off unlockr)
Download the Hero Recovery Image
Put it in your androidsdk/tools folder
in fastboot, type
fastboot boot NameOfRecoveryImage.img
The only way i know how to change the Radio back is to Flash it through fastboot and this is the message i get when flashing anything through fastboot:
FAILED <remote: not allow>
The first time i changed the Radio to the new one I did it through recovery mode
I can't make it in to recovery mode anymore...
help?...
If you flash an engineering SPL you'll be able to continue. Flash 1.33.2010 and then continue from there. That happened to me too.
If you can read:
Prerequisites:
- HTC Magic / Sapphire 32A
- Engineering SPL
----- 1.33.2005
----- 1.33.2009
----- 1.33.2010
----- If you boot into fastboot and have issues with "fastboot:remote not allow", then your SPL won't work. Upgrade to Engineering SPL before continuing.
----- If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
- Working ADB/Fastboot Drivers
- Basic knowledge or modding your phone
Click to expand...
Click to collapse
This is the very top of the topic.
rquattro said:
If you flash an engineering SPL you'll be able to continue. Flash 1.33.2010 and then continue from there. That happened to me too.
If you can read:
This is the very top of the topic.
Click to expand...
Click to collapse
how do I flash it through recovery if I can't boot into recovery?
can your computer detect the device? can ADB detect it? Can you get into fastboot mode (Power+Back)? You could try to flash the engineer SPL (and the old radio) through command prompt:
Do it in this order:
Code:
fastboot flash radio Radio_HTC_PVT_32A_3.22.20.17.img
fastboot flash hboot hboot-1.33.2010.img
fastboot flash recovery recovery-RA-sapphire-v1.5.2H.img
fastboot erase system -w
fastboot reboot-bootloader
The files you'll need are all at this topic.
perhaps you missed the part about any fastboot command giving me a
FAILURE <remote: not allow> error
The one thing that gives me hope is that I get about 1-2 seconds of response from adb during boot up before it shuts down and starts the boot process again. If I knew how to run an update.zip from adb shell in one or two commmands maybe i have a chance at loading the old radio or engineering SPL or something. If I try to get to recovery mode it locks up after a second and I can't run the update through the menu...
??
fibofan said:
How does a card reader help me get the cid number off the phone? Don't i still need to get to adb mode to do that? which means booting the phone up which it won't do...
Click to expand...
Click to collapse
If you have fastboot, can't you fastboot boot recovery.img?
It's like a liveCD boot. Or maybe flash the old radio back on.
You did say you have fastboot, right?
HBoot mode?
fibofan said:
perhaps you missed the part about any fastboot command giving me a
FAILURE <remote: not allow> error
The one thing that gives me hope is that I get about 1-2 seconds of response from adb during boot up before it shuts down and starts the boot process again. If I knew how to run an update.zip from adb shell in one or two commmands maybe i have a chance at loading the old radio or engineering SPL or something. If I try to get to recovery mode it locks up after a second and I can't run the update through the menu...
Click to expand...
Click to collapse
Isn't there an HBoot mode that applies whatever is in an update.zip file? You may be able to recover your radio that way.
Windos or Lenox
i have bricked my mytouch the red screen of death VodaFone. i am trying the unbrick method (fastboot boot recover.img)
which some have said it works. would i have a better change of success on windows or lenox. cant
bricked mytouch1.0 with the new software 1.6 from htc gold card the vodafone sap.img because the usa was giving a version on device is older.
i was trying to change radio then spl looked like flash radio just fine went to the reboot then never came back from the vodafone screen.
cant fastboot and cant go to recovery
charging light just fine
Brick
ive came to the concluion that i did everything right it just bricked anyways. i think im going to send it to htc and see how much they will charge me
My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?
well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!
Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.
what all does it say on your bootloader screen now?
It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.
Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium
I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.
rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium
WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.
Have you tried a different SD card?
mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.
rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?
Hey, First post and it going to be about whether my phone is bricked for good or not. =/ I'd really appreciate some help as I've clearly not researched enough into this.
-My Rogers HTC One X had previously been rooted and unlocked to hboot 1.09 with cyanogenmod.
-I wanted to install Android Revolution HD, so i figure I needed an hboot update. I went ahead and flashed the phone with the 'firmware.zip' in 'OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.32.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl6j.zip' (HUGE MISTAKE)
-After flashing, I tried to install Android Revolution HD but it had crashed mid way.
-Im able to access hboot and Im also able to go into fastboot and recovery (recovery-clockwork-6.0.2.8-evita).
-Rebooting the phone results in a blank screen after the HTC loading screen. So no adb.
My hboot shows this:
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I've tried locking it, flashing it with PJ83IMG.zip but it says: 'FAILED (remote: 44 hboot version check fail)'.
I've tried running 'RUU_Evita_UL_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe' but it gets half way and has Error 155.
Can anyone recommend a rom that will work in this configuration?
Any chance that I can still get S-off on the phone?
Any way to recover the phone at all? Just to be clear, I've flashed my Rogers phone with a Rogers OTA.
Thanks!
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Nevermind
Sent from my One XL using XDA Premium
Also that Rom is for the international HTC one x if the install hadn't crashed it would have bricked your phone
Sent from my HTC One X using Tapatalk 2
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
certitude said:
exad, Thanks for taking the time to write up the instructions for me. I've been able to get the phone to boot again. =) I do have some reading to do haha.
Given whats already done, did I put my phone in a situation where I've limited myself for future modding? What I'm really wondering is if I should be trying to get S-off so I can downgrade my firmware? Will I run into any issues with just running the phone as it is?
Click to expand...
Click to collapse
If you are going to s off, no need to really downgrade. This because you are turning security checks off. So it actually makes things a bit easier, and decreases the chances of bricking. I'm s off and on hboot 1.14 and was able to flash plenty of roms without a computer.
Sent from my Carbon-ize Evita using xda-developers app
You're not limited. You just need to fastboot flash boot boot.img any time you flash a ROM. If you're not a flashaholic like most of us, it's no big deal.
I wouldn't RUU with S-ON though, even though you didn't supercid, I bricked without supercid running an RUU after rooting.
So, if you don't plan to RUU you don't need to S-OFF either.
If you do intend to S-OFF, since you didn't need to supercid to unlock your bootloader, you would need to hex edit your CID to 11111111 if you wanted to S-OFF.
If you have any other questions, don't hesitate to ask but I suggest reading the stickies in all the sections. Good Luck
Thanks for the info everyone. I'll be keeping that in mind.
exad said:
Dude you are ****ed! no way to recover from that!..
J/K
All joking aside.
Download TWRP 2.3.3.1 It is compatible with the most ROMS and isn't buggy. Check MD5 and fastboot flash recovery twrprecovery.zip <-- replace with actual zip file name.
then fastboot erase cache
Boot to recovery
Wipe cache dalvik system and factory reset and flash any ROM designed for evita.
Because you're S-ON and on an HBOOT >= 1.14, you'll also have to extract the boot.img from the rom and flash it separately "fastboot flash boot boot.img", unless otherwise indicated on the ROM's thread, usually in the OP.
As a side note, you shouldn't have rooted, you have a lot of reading to do.
Click to expand...
Click to collapse
I got a Telus HTC one x yesterday. Spent all day reading about rooting etc and finally went ahead and did it. The unlocking part went without a hitch. I then went to install the clockwork recovery and I think I used an outdated one, because after I did it, it wouldn't boot into recovery. I could get into the bootloader, but checking anything else it wouldn't do anything. At that time I was still able to boot up my phone as normal. I then saw an updated clockwork recovery and tried that one, and it still wouldn't respond when I clicked on recovery. Now I can't do anything except get into the bootloader. My screen says the exact same thing as the original poster in terms of
UNLOCKED
EVITA PVT SHIP S-ON RL
HBOOT - 2.14.0000
RADIO - 23a.32.09.29
OPENDSP - v31.1.0.45.0815
eMMC-boot
Nov 26 2012,18:37:14:-1
I'm so upset right now. I read your instructions on what you suggested to the OP but theirs was Rogers and mines Telus, and I never did have a custom ROM on there, and I don't have a clear cache option, just a 'clear storage'
Even selecting the 'reset phone' doesn't work. I'm ready to cry lol. I don't want to touch anything without guidance so I don't screw it up even further. I know this is the rogers forum but it's what came up when doing a google search.
Please help me. Please tell me this can be fixed. :crying:
Don't use CWM, use TWRP instead. Find version 2.3.3.1 at goo.im (just Google TWRP 2.3.3.1 evita download). Check the md5 of the download is correct. I'm assuming you have fastboot on your pc.
Put the TWRP recovery.img in your fastboot folder
Boot phone into bootloader, wait for it to say "fastboot usb" on the screen of your phone
Open a command prompt in that folder on your pc
Type in the following command:
fastboot flash recovery openrecovery-TWRP-2.3.3.1-evita.img (whatever the name of the recovery image is, I think that's right)
It will now write the recovery to your phone, wait for it to finish, it should only take a few seconds
Now type the following command in:
fastboot erase cache
fastboot reboot-bootloader
Now you should be able to disconnect your phone and flash superuser.zip in your new recovery and have root access.
Sent from my HTC One XL using xda premium
omg!!!!! TY TY TY TY TY!!!!!!!!
It flashed into recovery!!!!!
I can't find where my superuser went...is there a way I can get it onto my phone? At this point I'm so nervous about screwing anything up that I'm afraid to play (which is rare for me as I'm normally quite good at all this stuff)
Do I really need the superuser? I'm planning on putting the ViperXL 3.2.7 rom on my phone. Can I just go straight to installing the rom?
I know where I went wrong now though. I used the international root instructions and not the AT&T ones as I assumed since I was Telus instead of Rogers or AT&T that that was the one I needed. Ugh! I feel like such an idiot!! I had android for quite a while then went to iphone for a little while (mistake) and had gotten so good at doing everything with those and forgot most of the steps involved with rooting android and the terminology. I'm happy to be back home with android!
You can just go ahead and flash ViperXL, that is pre-rooted so you'll be good to go. I just assumed you had a ROM running, so flashing the superuser zip would have just given that ROM root access.
Now, just make sure you stay here in the One XL (AT&T) forum. Make sure you only flash ROMs from here, because flashing one of the International ROMs can brick your phone, and we don't want that.
Sent from my HTC One XL using xda premium
I will be staying here!! lol
Just to be sure I have this correct...
I downloaded Viper and the boot img.
I'm going to go back to my cmd prompts, install the boot img
I'm getting hung up with understanding how to place the zip on my phone storage...My computer isn't showing it as being a separate drive.
I keep getting 'failed' errors with everything in TWRP. If I try to mount as USB storage, my computer says it needs to be formatted...
When I try to do anything else it shows up with failed.
Ok here's what you'll need to do:
Boot your phone into the bootloader (hold power and volume down key together, release power after a second but keep holding volume down until you're in bootloader)
Select recovery
Once recovery boots up, connect to pc with usb cable, select mount in recovery menu, then select mount storage
Your phone should now show up on your pc as a drive, copy the entire ROM zip to your phone
Once it's copied, do eject and safely remove the drive from your pc, and hit unmount on your phone screen
Hit the home button (little house on bottom left) in recovery
From main recovery select wipe, once in wipe menu you must wipe cache, dalvik cache, factory reset, and system
Once you've wiped all those, hit the home button again
Select install from the main recovery menu, then find the ROM you previously copied to your sd card and select it, then swipe to install, let the install finish (please note: if you're installing viper, it will have a few options to select during the install, select the ones you want. But right at the end of the install process there will be a checkbox for "reboot device now" and it will be checked, make sure you uncheck that before you hit finish/done)
Now you'll see two options, wipe cache/dalvik is one, do that, once that's done hit the home button again
From the main menu, hit reboot, and then bootloader, your phone will now boot back into the bootloader and fastboot usb should show up in red text on your screen if your usb cable is still connected
Now back to the pc, Copy the boot.img from the ROM zip and place it in your fastboot folder
Make sure you're connected with usb and fastboot usb is showing on your phone screen
Open a command prompt in your fastboot folder on pc and type in:
fastboot devices
You should see a device number return in the command prompt, if that shows up you're connected properly, so now type in the following command:
fastboot flash boot boot.img
This will flash the boot.img to your phone, let it finish
Once that's done you can reboot and you should be able to reboot into your new ROM
Sent from my Evita
It's not mounting...just keep getting a message from my computer that the drive needs to be formatted before I can use it...
btw, ty for all your help on this you've been amazingly helpful!
You may have corrupted your sd card. You'll have to format it, which means you'll lose all your data off it unfortunately. Do that first and then start again.
Sent from my Evita
It worked!!!!!! It booted up into Viper!!!!! TY a million times over!!!!!!!!!!
Awesome, so glad to see you got it going :thumbup:
And no problem at all, my pleasure, this is what XDA is all about.
Sent from my Evita
I'm posting this in a single thread to minimize clutter.
I recently ran Easy Ace Root tool as instructed on my inspire. The bootloader unlocked, CWM flashed, but there was an error during superuser flash.
After a reflash of superuser things looked okay, but superuser began not responding. I re-flashed superuser twice in attempt to fix it using the Easy Ace Root Tool.
EDIT: I have discovered that superuser will only function with "USB debug mode" enabled. I've tried it on and off several times, and each time it malfunctions but function returns without a problem.
The backup I have been restoring seems to work because it was created with the debug mode enabled. Took a while to see it.
Second, CWM started to exhibit the "power off, charge" recovery bug where CWM opens.
Last, I attempted to install/flash 4ext Recovery Touch twice to address the CWM bug. Both times it hung at "flashing recovery" (approx 20 mins. both times). Eventually, it indicated that 4ext was installed. However, booting into recovery shows that I still have CWM. I used two different versions (RC8 & RC 7) in the attempt.
I'm now using the restored and working ROM. Solutions to the superuser debug issue I haven't seen posted
The failure to flash 4ext is troubling.
Questions
1. Could these issues be related? Or, what should I be looking for?
2. The recovery issue seems to be the most important. What might be the cause of 4ext to fail in this manner?
3. Can the Easy Ace Root Tool be rerun on the unlocked bootloader, and would that fix anything?
4. Is there reason to worry about flashing with CWM?
I see a number of possible solutions, the main one is to flash a new ROM, which I have already downloaded a couple, but doesn't adress the recovery problems.
The issue with CWM and 4ext leave me less than confident in using it to flash with, although CWM seems okay. The other item is that some ROMs indicate that S-off in required, but many of the threads are a couple years old.
5. Is it correct that S-off is not required to flash ROMs (I read it somewhere)?
I found an answer: NO, YOU DON'T NEED S-OFF TO FLASH ROMS....
Solving the issues are good lessons
Stock AT&T ROM
Android 2.3.5, Sense 3.0
Bootloader screen indicates-
UNLOCKED
S_ON
I know that's a lot for one thread but I'm just looking for a direction and I'll do the search.
If anyone has suggestions, directions, or ideas fire away.
Thanks
I think the fact that you are still S-ON is causing problems with the recovery flashing, since S-ON basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-ON still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Evil_ryan said:
I think the fact that you are still S-OFF is causing problems with the recovery flashing, since S-OFF basically means that the recovery partition is not-writeable.
Have you tried using fastboot to flash a new recovery? Plug your phone into a computer, get into the bootloader, select "fastboot" (if not already selected), wait for "FASTBOOT USB" to appear, and then run the following on the computer:
Code:
fastboot flash recovery <path to recovery.img>
However that S-OFF still worries me. You might have to do things manually:
Code:
androidforums.com/desire-hd-all-things-root/702100-how-manually-achieve-s-off-simunlock-supercid-inspire-4g-dhd.html
(Sorry for the broken URL - I had to disguise it. Blargh, I hate being a n00b.)
Click to expand...
Click to collapse
Thanks, I think you meant to say the fact that I am still S-ON? The S_ON part shouldn't be an issue from all that I've gathered. In fact, that's how I have CWM. The Easy Ace Root Tool does CWM, with an unlocked bootloader S_ON. Nothing I have come across states that S_OFF is required to flash 4ext recovery.
Other noobs might find this other thread useful as there is some info and links to recovery images. http://forum.xda-developers.com/showthread.php?p=22489317#post22489317
No I haven't tried the fastboot yet. That is an option, I've got it and adb setup on my computer already. I have looked at AAHK, but as it says its no longer supported, and I don't think I need of S_OFF. Taking it slow to sort out the problems so I don't do sumthin stooopid.
How are you flashing 4ext? From fastboot?
Right, S-ON, that's what I get for writing this at 12 AM.
Don't bother with AAHK, it's discontinued, and even if you still had a copy it couldn't download the necessary files.
bananagranola said:
How are you flashing 4ext? From fastboot?
Click to expand...
Click to collapse
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Cremnomaniac said:
bananagranola,
I used the 4Ext Recovery Updater for both attempts. As I said in the OP, both attempts hung at "flashing recovery" approx 20 mins, and eventually indicated that 4ext was installed. In Recovery Updater it listed/highlighted the version I thought I had installed, but CWM was still the recovery that booted.
Click to expand...
Click to collapse
Try doing it from fastboot.
bananagranola said:
Try doing it from fastboot.
Click to expand...
Click to collapse
I thought that would be next.
Can you confirm for me that the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1848846 are correct for the Inspire 4G?
It's the EVO 3D forum. And I have some other links to using fastboot I'll check before doing it.
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Evil_ryan said:
Yes, those instructions will work. If you can't boot into fastboot through the GUI, you can also power on the phone while holding the volume down button, and that will get you into the bootloader.
Click to expand...
Click to collapse
Okay, great. This is the only recovery .img that I have found 4EXT-recovery-2.2.7_RC5.img - 3.33 MB
If I install the 4ext recovery Updater after flashing it should work okay?
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Cremnomaniac said:
If I install the 4ext recovery Updater after flashing it should work okay?
Click to expand...
Click to collapse
Probably. But I don't think it really matters, since if you can flash a recovery using fastboot, you can do everything that 4ext updater otherwise would.
Cremnomaniac said:
And, Will I be able to update once I have flashed it (assuming it works) and have installed the recovery Updater?
Click to expand...
Click to collapse
See above.
If 4ext doesn't work, you can also try CWM and TWRP (TeamWin Recovery Project). I use the latter with my Inspire 4g.
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
bananagranola said:
I strongly advise you use the app to download the recovery, unzip, and then flash it from fastboot.
Click to expand...
Click to collapse
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Cremnomaniac said:
I'll take "strongly" as more than a suggestion. Thanks, it had not occurred to me to get the recovery.img from the updater.
I had actually found several other images and was trying to figure out what was what. That saved me some time, but I did read a lot about 4ext.
I was considering trying the Recovery Updater one more time. Bad Idea?
Click to expand...
Click to collapse
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
bananagranola said:
I have a hunch that if you are S-On, you can only write to the recovery partition from fastboot.
Click to expand...
Click to collapse
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Cremnomaniac said:
I am S-ON. Does that present an issue with fastboot of the recovery.img?
I'm just going to overwrite the current recovery. Nothing else needs to be done does it?
Click to expand...
Click to collapse
No.
bananagranola said:
No.
Click to expand...
Click to collapse
Solved the 4EXT flashing issue. Looks like 4ext flashed okay with fastboot, and the 4EXT Recovery Control works. Rebooted into recovery a couple times just to be sure. That kills 2 birds the CWM bug and the recovery flash.
Thanks for the help and suggestions all.
Some notes from a noobs experience -
Setting up ADB and Fastboot is very easy.
If your cautious as I am run some basic commands in ADB and Fastboot that won't do damage [devices, reboot, reboot-bootloader, etc.]
If you get "error: cannot load 'recovery.img" make sure you navigate to folder that recovery.img is located. Then run "Fastboot flash recovery [Filename]." Even though I set system variables on my desktop to point to adb and fastboot, it won't find the recovery image if you start from the wrong directory in terminal (i.e., C:\)
If you're in ADB and you use the command "adb reboot-bootloader" it will boot the device straight to "Fastboot USB".
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
bananagranola said:
Don't forget that each time you flash a ROM from recovery, you still need to fastboot flash its boot.img separately.
Click to expand...
Click to collapse
Thanks for the reminder. I just spent an hour looking at 4EXT "smartflash no available". I hav some links for doing fastboot flash of the boot.img. I think I'm good there.
One question from my OP remains. Superuser only works (i.e., grants root access) when I have USB debug mode selected. When it's off superuser says the app (e.g., Titanium BU) is granted permission but just hangs until I force close it and re-enable USB debug. i can't find anything on this problem.
Is it an issue to run my phone in USB debug mode all the time? Or, any clue to the problem?
I've looked everywhere for something like this, and so far no one has experienced this.
Okay, so check this out:
I've already rooted and S-Off and SuperCID and all of that, the works. Had ViperROM XL and everything. I got curious to try out KarbonRom 4.4, and tried to flash it in TWRP, didn't work obviously, blah blah blah, short story is, I RELOCKED and installed the AT&T 3.18 RUU. At that point, TAMPERED was gone, and I had RELOCKED there instead, S-Off and SuperCID persisted.
I used the WinDroid Toolkit to originally root and S-Off my Evita. I tried it again. I succeeded in unlocking the bootloader, no problems there. When I go to flash TWRP on it, it says it succeeds. Now, here's when things get weird: I go to push Superuser, and at first it gave me all kinds of hassle, saying the toolkit wasn't detecting my phone, to saying it failed and to try again in a few moments. It was only until I booted back to stock and tried pushing Superuser that it gave me a success message and began to reboot to recovery. It's here that the phone fails to do this, every time. The screen goes black, and when plugged into my PC a Found New Hardware message pops up, asking me to search for drivers for QHSUSB_DLOAD, or something or other. I'm like, "no, that's not right." So after figuring out the 2-button reset to go back to HBOOT, I try to manually boot into recovery; no dice. Same results. So basically, I cannot access any recovery. Furthermore, my HBOOT says UNLOCKED and S-Off and CID-11111111, but TAMPERED is MIA. Not sure if that has anything to do with this, but I certainly did not have this problem the first time I unlocked everything. For your information, I'm on 2.14 HBOOT, 3.18 RUU. Thanks for any points in the right direction.
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
timmaaa said:
First thing, you didn't need to relock your bootloader to run the RUU, having s-off means that isn't necessary. Secondly, ditch the toolkit, it's unnecessary and causing problems.
I think you're possibly a bit confused about what you need to be doing. If your end goal was to flash a KitKat ROM why were you attempting to root the stock ROM? The tampered flag is missing from your bootloader because you don't have a custom recovery installed. Exactly which version of TWRP did the toolkit say it was installing? Hopefully all you need to do is flash a working recovery, then you can flash a ROM.
Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now hopefully you can enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the swift reply, I'm gonna go ahead and give this a try. To answer your question, through trying to flash KarbonRom, I wiped and factory reset without backing anything up, silly, I know, but I live a little too dangerously I suppose. I tend to get to cocky with this stuff, through all the devices I've rooted and so on. After failing to flash it, I knew I was stuck, which is why I came to the conclusion the only way out was to revert to stock RUU. If there was anything else I could do, I wasn't thinking of it. In hindsight, I suppose I could have ADB Sideloaded Viper XL again. Also, I was unaware that I didn't need to relock the bootloader to install the stock RUU, this is news to me, so thank you for that. I'll reply again after trying your link.
EDIT: This worked, thank you again. You've made me wiser in the ways.
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
timmaaa said:
One thing I forgot to mention. The QHSUSB_DLOAD that your phone was showing up as when connected to your PC usually means that a device is bricked. So, under no circumstances should you use that toolkit ever again, because whatever it was doing wasn't good at all.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the heads up, I'll keep it in mind. It seems the most reliable way to do this stuff is just do it yourself. I'm still green to the ways of adb and fastboot, I've always let one-clicks and toolkits do the work for me, but I'm learning that just doing it yourself is the most reliable method. Thanks again, man, your insight has always helped me out of tough situations.
Doing it yourself is definitely the most reliable method. It might seem daunting at first, but I can assure you it's totally simple, and once you've done it a couple times you'll see that. The manual way is the best way, hands down. A bonus is that it feels great to learn something and to have an extra bit if control over your device.
Sent from my Evita