I was installing trickdroid and everything froze up. I cannot get into my recovery and even if I could trickdroid ended up deleting EVERYTHING I had on my sd card even though what I was doing had nothing to do with the contents of my sd.
I am able to get into fastboot. And have managed to install TWRP on my phone. I don't have any recoveries on the phone itself so even twrp is useless to me right now.
I have tried multiple times to go into cmd and use the fastboot command line and tried doing a few recoveries. They all seem to go through but upon reboot it just gets stuck on the htc developers screen forever.
WTF can I do?? =/
Solved.
Took a few hours but I finally managed to find a ruu for my usa tmobile device that had the 1.84 update.
With this I was able to get into my bootloader
using the cmd prompt i did an oem lock and locked up my bootloader (this all over xda and you can find out how to use it that way, it's a lot more detailed)
i was then able to install the ruu through fastboot on my pc
that's the only way I was able to get a single damn thing working.
this morning i tried trickdroid again and the same **** happened. something about the boot.img they have you install, who knows.
I assume your phone is s4 since you are in US
Make sure the Trickdroid you are installing is for your phone--which one you doing
How are you flashing boot.img and when. I wipe all including System, flash rom, reboot into bootloader and fastboot boot.img "fastboot flash boot boot.img" where boot.img is exact name of the boot file image
What is your hboot
Wipe System also as part of your flashing and don't rewipe in Aroma
The OP pages have detailed info on flashing Rom and how to do Tweaks when you get to that point
rugmankc said:
I assume your phone is s4 since you are in US
Make sure the Trickdroid you are installing is for your phone--which one you doing
How are you flashing boot.img and when. I wipe all including System, flash rom, reboot into bootloader and fastboot boot.img "fastboot flash boot boot.img" where boot.img is exact name of the boot file image
What is your hboot
Wipe System also as part of your flashing and don't rewipe in Aroma
The OP pages have detailed info on flashing Rom and how to do Tweaks when you get to that point
Click to expand...
Click to collapse
I made certain I was using an s4 version of the roms. I believe the last one I tried was 7.0?
I was using the boot.img through fastboot. Perhaps I was doing that wrong... i put the phone in fastboot. then it reads fastboot usb. from my computer i went to the folder where i have all my android files and typed in the command for the cmd prompt to run the boot.img and then it showed it installed correctly. but nope.
I played with it again today and I seem to be able to flash ANY rom I have tried so long as I don't actually fastboot any boot.img files. The mixture between the rom and flashing the boot.img on trickdroid really screwed things up but at least I'm up and running again /sigh
I've used trickdroid for a while so it was very surprising that things went so wrong.
Now i just have to wait for the more popular roms to hopefully add wifi calling lol. For right now I've flashed the latest cm10 nightly. Everything is working as it should.
if you are under .13 hboot you don't need to fastboot the kernels. don't remember if you said which hboot you are on
but, glad you got it
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 been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
obg8 said:
I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
Click to expand...
Click to collapse
If you are s-off you shouldn't need to flash the kernel seperately.. However use "fastboot devices" instead of "adb devices". When you are connected to a computer via USB it should indicate that on the bootloader.
Before I was s-off I'd flash the rom then return to the bootloader directly and flash the kernel before attempting to boot for the first time.
The post above mine is correct. If you are s-off you don't have to flash the boot.img. Going by what you posted it doesn't look like you wiped your data in recovery, which is something you have to wipe when flashing a new ROM. That's probably why it didn't boot properly. Try again doing a full wipe/factory reset from recovery.
Sent from my One X using Tapatalk 2
Hi, i tried to install a custom rom on a mytouch 4g slide and may have bricked the phone. I am now trying to see if I can recover it. I had CWM on the phone but after trying to install a stock rom I can no longer access it and the phone won't boot only, just staying on the splash screen. I can access the boot loader but if I try to go into recovery I get an icon of a phone with a red triangle and exclamation mark.
If I connect the phone to a PC, no devices are listed under 'adb devices'. I believe I need to install the stock rom (PG59IMG.zip) from the boot loader to recover the phone. I have a couple of different stock roms and although these are automatically loaded by the bootloader without error, the phone doesn't boot.
Not sure if anyone knows of a confirmed clean stock rom or another method I could use.
The bootloader is unlocked but the phone is S-ON, H-BOOT 1.45.0013.
Thanks
clarkbanks said:
Hi, i tried to install a custom rom on a mytouch 4g slide and may have bricked the phone. I am now trying to see if I can recover it. I had CWM on the phone but after trying to install a stock rom I can no longer access it and the phone won't boot only, just staying on the splash screen. I can access the boot loader but if I try to go into recovery I get an icon of a phone with a red triangle and exclamation mark.
If I connect the phone to a PC, no devices are listed under 'adb devices'. I believe I need to install the stock rom (PG59IMG.zip) from the boot loader to recover the phone. I have a couple of different stock roms and although these are automatically loaded by the bootloader without error, the phone doesn't boot.
Not sure if anyone knows of a confirmed clean stock rom or another method I could use.
The bootloader is unlocked but the phone is S-ON, H-BOOT 1.45.0013.
Thanks
Click to expand...
Click to collapse
Because you are S-ON, you need to flash the boot image as well. Extract the boot.img file from the ROM, and (while in FASTBOOT USB mode) run fastboot (on the connected computer) like the following:
fastboot flash boot boot.img
AFAIK, adb only works when you are fully booted up, fastboot is what to use while in the bootloader. Blue6IX has a return-to-stock RUU as well, but we'll cross that bridge if/when we come to it.
SOLVED
joel.maxuel said:
Because you are S-ON, you need to flash the boot image as well. Extract the boot.img file from the ROM, and (while in FASTBOOT USB mode) run fastboot (on the connected computer) like the following:
fastboot flash boot boot.img
AFAIK, adb only works when you are fully booted up, fastboot is what to use while in the bootloader. Blue6IX has a return-to-stock RUU as well, but we'll cross that bridge if/when we come to it.
Click to expand...
Click to collapse
That is what I was missing. Many thanks
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.