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'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
please..
i have problem with bootloader version 41.1A
i want to Downgrade to version 41.18 or 41.19
anyone know ..??
please share it
thank you
Up
Me too
My bootloader v 41.1A I downgrade 41.18 Help
Why do you need to downgrade? Messing with Bootloaders can destroy your phone.
even i want to downgrade... I cant flash custom recovery on 41.1A
poran123 said:
even i want to downgrade... I cant flash custom recovery on 41.1A
Click to expand...
Click to collapse
Bootloader cannot be downgraded. You're stuck on w/e version you have currently installed.
Okay so I'm stuck on 41.1A and my phone will continue to restart itself and then stuck in bootloop till the battery dies... and then when I connect it to the charger boot's up normally...
@lost101
Can you please let me know how to check bootloader version?
I am using Moto G XT1033 model(Asia).
It was updated to Lollipop 5.0.2 by Motorola Stock Lollipop update.
Later on I had unlocked bootloader and downgraded it to Kitkat 4.4.4 using this thread.
I don't have any clue about current version of bootloader in my Moto G.
I want to try Lollipop 5.1 Optimized stock rom link here, so just wanted to ensure compatibility of bootloader so that my phone works after flashing it.
kalpesh.fulpagare said:
@lost101
Can you please let me know how to check bootloader version?
Click to expand...
Click to collapse
Enter bootloader (hold volume-down while turning it on), read text on screen (second line).
I too want to know if there is a way to downgrade or at least reflash my damaged bootloader which is causing weird behaviour.
Sent from my Nexus 6P using Tapatalk
I have the exact same problem.
Stuck on 41.1A
Was on a slim6 rom before. Tried to return to STOCK_ASIA_RETAIL. All fastboot commands successfully executed but no apparent change. I have the exact same wallpaper, the same layers RRO navbars, everything. I would not need to go to STOCK but since the slim installation is unstable and everything force closes, the phone is unusable.
Additional note: Somehow even TWRP is stuck in the splash screen, so cant flash any other ROM. Even tried to access TWRP using adb, but the TWRP service fails to start.
I fastboot flashed phillz recovery, stock recovery & newer TWRP versions, but nothing happens. Phone still stuck in TWRP screen.
To my surprise I was able to pull my personal files from the internal SD using ADB (which still works btw).
But I'm left with a phone in a zombie unusable condition, it just doesn't react to anything.
Any help from the XDA community would be greatly appreciated. I am still keeping my fingers crossed, so that one day a guide comes up to brick my device (STOCK 5.1 bootloader) and unbrick it using some sort of unbrick tool.
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
SLATE21&MOTOG said:
Why is not possible to create a flashable zip with the bootloader inside? I want to downgrade to KitKat bootloader too
Click to expand...
Click to collapse
Creating such a zip is possible, but flashing it may either not work or hard brick your phone.
How to install working recovery on 41.1A bootloader
I had the situation on my Moto G XT1039 where I had formatted the partitions on my phone (using my old CWM recovery), then flashed the 41.1A bootloader, but 41.1A would not allow me to flash any recovery.
So I had a working bootloader, but no recovery and no OS. And apparently no way to install a recovery, to install an OS...
I got the phone back like this:
- Flashed 4.4.4 stock manually using the bootloader (if you do this, DO NOT flash the 4.4.4 motoboot.img, according to everything on here that will permanently brick your phone; I am not sure about partition gpt.bin - I flashed this, but I was already on the 4.4.4 partition layout anyway). Do flash boot.img, that is the OS boot.
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
From there I now had the correct recovery in place to flash the 5.1 Optimized distro (which I would definitely recommend - clean, stable, excellent battery life!).
Yay!
Bmju said:
- So now I had a bootable phone OS (back on 4.4.4 again, with a flickering screen), but still no recovery.
- From the bootloader, I booted into an old recovery which I knew had previously worked with my phone:
Code:
fastboot boot clockworkmodrecovery.6051.peregrine.img
(this boots into a temporary copy of the recovery, without actually installing it on the recovery partition).
- Using that, I installed the SuperSU binary.
- Then I booted back into my 4.4.4 OS, installed the SuperSU app, checked it was working, then installed the TWRP Manager app (which requires root, hence the previous steps), then used that to successfully install the TWRP recovery on my phone.
Click to expand...
Click to collapse
Why didn't you simply fastboot flash a TWRP image?
_that said:
Why didn't you simply fastboot flash a TWRP image?
Click to expand...
Click to collapse
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Bmju said:
I hope I haven't misunderstood, but isn't the whole point of this thread that the 41.1A bootloader won't let some poeple (including me) successfully flash anything to the recovery partition? You can run the command, but the recovery won't boot up. At least that's how it was for me.
Click to expand...
Click to collapse
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
_that said:
I see. So "fastboot boot" worked, but "fastboot flash" wouldn't write anything? In that case you could probably also have used fastboot boot with TWRP and then use TWRP's "install image" feature to flash it.
Click to expand...
Click to collapse
Thanks! I definitely tried that first! Maybe this bit I didn't make clear in my post, but actually:
- fastboot boot was only working for me with older recovery ROMS, i.e. the older CWM recovery which I mentioned, which I had lying around from when I first rooted my phone on 4.4.4, and also - not that it's much use - with the recovery in the 4.4.4 image, which just brings up the dead Android logo
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Bmju said:
- fastboot flash recovery was not working at all, not even with the recovery roms which would boot with fastboot boot
Click to expand...
Click to collapse
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Bmju said:
- but fastboot flash to all the other partitions seemed to work fine (I could see that it seemed to be working because I was able to flash different logo.bin files to change the phone logo which shows before the phone tries to boot into recovery or OS) and as per my post this was how I was able to get my phone back eventually
Click to expand...
Click to collapse
That doesn't make any sense. Not that I don't believe you, I just can't explain how fastboot could fail writing recovery but succeed in writing a different partition.
Bmju said:
This thread was the only place I could find which seems to represent people having the same set of problems, so I thought the above workaround might be useful in future to someone in the same situation.
Click to expand...
Click to collapse
Thanks for sharing your experience though, maybe it will help someone who has the same weird issue.
_that said:
So far nobody has posted a terminal transcript of "not working". Did it appear to succeed or did you get an error message?
Click to expand...
Click to collapse
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Bmju said:
It appears to succeed, except that it gives the 'mismatched partition size error' on the bootloader screen at the end of flashing. (Although other posts seem to state that this is normal for a non-strock recovery?)
Click to expand...
Click to collapse
Yes, I've got that one too, but my flashed recovery then worked fine. However I upgraded my bootloader by installing the complete 5.1 stock ROM, maybe your bootloader update was somehow incomplete.
I tried to flash cm12.1 using flashyfy (a complete foolishness). And now i don't have any os. I am bootloader unlocked, rooted and S-on. Whenever i tried to turn on my device first it shows common HTC booting screen, then some sentences comes under HTC logo (this built is for development purpose only.........). Then phone turn off and this keep looping. Since I can't boot into system so i am not able to s-off my device. i tried to flash custom using fastboot, but it doesn't work. I unzipped cm12.1 and did fastboot flash boot boot.img, does this even work because original zipped file was like 200 Mb, but boot.img was like only 5 Mb. Can i get custom ROM in img format?
What am i suppose to do with my phone???
[Anyway I repaired my phone. I flashed viperxl 3.2.6. First I flashed boot.img via fastboot then went immediately to recovery without reboot and flashed the zip. Then i followed this link ( http://forum.xda-developers.com/showthread.php?t=2155071 ) and got S-OFF.]
Mr. Alpha said:
I tried to flash cm12.1 using flashyfy (a complete foolishness). And now i don't have any os. I am bootloader unlocked, rooted and S-on. Whenever i tried to turn on my device first it shows common HTC booting screen, then some sentences comes under HTC logo (this built is for development purpose only.........). Then phone turn off and this keep looping. Since I can't boot into system so i am not able to s-off my device. i tried to flash custom using fastboot, but it doesn't work. I unzipped cm12.1 and did fastboot flash boot boot.img, does this even work because original zipped file was like 200mb, but boot.img was like only 5mb. Can i get custom rom in img format?
Whast am i suppose to do with my phone???
Click to expand...
Click to collapse
Wrong forum here is International HOX Endeavoru forum not AT&T Evita.
Reported and will be moved.
I unlocked my phone, installed twrp and I tried to flash the ROMAur and now it stuck on the boot screen in both slots. Does anyone have a flashablale TMobile zip?
mackentosh said:
I unlocked my phone, installed twrp and I tried to flash the ROMAur and now it stuck on the boot screen in both slots. Does anyone have a flashablale TMobile zip?
Click to expand...
Click to collapse
Did you install the global version first? I don't think that room will work for TMobile ROM
Exathi said:
Did you install the global version first? I don't think that room will work for TMobile ROM
Click to expand...
Click to collapse
Yes I tried the global room first and it gets stuck on the boot screen. The RomAur room will boot and get all the way to the wifi selection screen then reboot back to twrp
mackentosh said:
Yes I tried the global room first and it gets stuck on the boot screen. The RomAur room will boot and get all the way to the wifi selection screen then reboot back to twrp
Click to expand...
Click to collapse
Normally what I do if something like that happens is erase the entire operating system install TWRP then flash OxygenOS via USB flash drive in both slots.
Exathi said:
Normally what I do if something like that happens is erase the entire operating system install TWRP then flash OxygenOS via USB flash drive in both slots.
Click to expand...
Click to collapse
I'll try that
Ok I did it I flashed the international ROM on the T-Mobile variant no issues so far. Rooted also
mackentosh said:
Ok I did it I flashed the international ROM on the T-Mobile variant no issues so far. Rooted also
Click to expand...
Click to collapse
can you explain the process you took to convert to international?
mackentosh said:
Ok I did it I flashed the international ROM on the T-Mobile variant no issues so far. Rooted also
Click to expand...
Click to collapse
I downloaded the 9.5.4 fastboot zip extracted it then put the phone on fastboot mode. Install the twrp.img Format all data then go back into fastboot mode. Then in the extracted zip find the flash all-partitions and click it, let it do it's thing. Once that's done it may reboot and get hung up on the boot screen. Just go back to fastboot mode and flash "flash-system-boot-vender". Once it's done It may reboot again and get stuck on the boot screen. Go back into fastboot mode then flash the twrp.img and get into twrp, there you should be able to flash the twrp.zip if not you may have to adb sideload it. After that it should boot up into the international ROM. If you can't get WiFi to show up youll have to flash the sky dragon kernal.
you can find the fastboot zips here https://androidfilehost.com/?w=files&flid=294300
*You do this at your own risk*
Don't blame me if you screw something up. If I screwed it up I would've simply took it back to tmo for a new one