Related
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
Hi all,
I have a bit of a problem here, whenever I try to flash a .zip file in Cyanogen Recovery (CM12) it says: E: signature verification failed. Installation aborted.
Does anyone know how to solve it?
Thanks in advance!
xChillz (C6603)
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Parker-ivxx said:
I had that issue with the same recovery on a number of zips. Have you considered using another recovery?
Click to expand...
Click to collapse
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
xChillz said:
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Click to expand...
Click to collapse
It replaces your Rom with what exactly
Try formatting the FOTAKernel either using xperia recovery manager or flashtool and then flash twrp/cwm and report back.
xChillz said:
Yes I did, noone seems to be able to answer this question, so I'm going to plan B.
I would like to know how I can install TWRP over the CM12 recovery again, because when I flash the TWRP .img file with fastboot, it replaces my whole CM12 Rom.
Could someone explain to me how I can keep both CM12 + TWRP recovery?
Thanks in advance!
Click to expand...
Click to collapse
I had the same problem.And i got permission denied when flashing fotakernal in flashboot mode.
I solved it by using "[ROOT] Rashr - Flash" Tool.It is in google play.
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
candyman0629 said:
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
Click to expand...
Click to collapse
You need to do a XDA search and look for some kernels and roms to put on a micro SD card and flash it
candyman0629 said:
I was trying to install clockwork mod to my devices. I have TWRP (And NOTHING but TWRP at that...) and that i accidentally wiped my whole OS off of my device... Help me? It's Cricket Wireless btw. Black.
Click to expand...
Click to collapse
At this point I will suggest that you download a RUU and use that to restore your phone. Or you could flash a custom rom for the 32bit version of this phone, If the TWRP recovery is working. If the recovery is not working your only option would be the RUU. If you still have any questions don't hesitate to ask.
I am in the same boat!
I know I can NOT get into recovery TWRP. I know I am still unlocked. I am going to make sure I know which version I have. I know it was Boost Mobile. I have searched for correct RUU. Not sure if I can find a good one. To install the RUU I need to mount my SD. I can not find a way to mount. Since I am rooted I thought ES explorer will let me in. No Dice. RUU sources?
Reason for doing this: I want to flash a 5.1 rom. I was directed to update TWRP to fix the failed message I was receiving on flashing the ROM file. That is where I lost recovery altogether.
Hi, I recently switched to OOS 5.0 .I got Error 7 in twrp, So I forced to boot with Stock Recovery,
Now I want to install Custom Recovery TWRP and Root the Device with Magistk..
I'm a noob in sideload kinda things,, and I'm on Windows 10 in PC.
How could i go around to root my device!?!?
Regards
vettayyan said:
Hi, I recently switched to OOS 5.0 .I got Error 7 in twrp, So I forced to boot with Stock Recovery,
Now I want to install Custom Recovery TWRP and Root the Device with Magistk..
I'm a noob in sideload kinda things,, and I'm on Windows 10 in PC.
How could i go around to root my device!?!?
Regards
Click to expand...
Click to collapse
By searching and not creating a thread just for your question answered ~1000 times.
Please use the search function before posting. Read the Forum Rules if you're a newbie.
Is there any other way to install or Flash TWRP other than Fastboot mode???
vettayyan said:
Is there any other way to install or Flash TWRP other than Fastboot mode???
Click to expand...
Click to collapse
Not without ROOT, still even that has already been answered to many times.
vettayyan said:
Is there any other way to install or Flash TWRP other than Fastboot mode???
Click to expand...
Click to collapse
Flashing TWRP by fastboot is a single command. I think you are making the solution more complicated than the problem. Downloading TWRP, putting it in the right place, and flashing with fastboot can all be done in about 3 minutes.
vettayyan said:
Hi, I recently switched to OOS 5.0 .I got Error 7 in twrp, So I forced to boot with Stock Recovery,
Now I want to install Custom Recovery TWRP and Root the Device with Magistk..
I'm a noob in sideload kinda things,, and I'm on Windows 10 in PC.
How could i go around to root my device!?!?
Regards
Click to expand...
Click to collapse
Since u had TWRP before, it should not be difficult for u to flash oreo TWRP with fastboot commend. U r even able to flash back to stock recovery. Your question is not making sense. ?
Noob here in flashing in partitions
I recently brought mi a2
I unlocked bootloader and critical also
Flashed magisk modified boot
I want to flash twrp
I can boot into temp twrp but when I try to start sideload it gets stuck at 0%
When I try to flash from internal it shows in text which is not readable
Anyhow can help how can I flash permanent twrp and custom rom
No one is answering... Even i want to know how to flash twrp... Everything is so confusing in this forum. Other device it's very easy
poran123 said:
No one is answering... Even i want to know how to flash twrp... Everything is so confusing in this forum. Other device it's very easy
Click to expand...
Click to collapse
Your memory is crypted, you have to decrypt it first. Or side load twrp 3.3.1.-3. You have tutorial here on xda, just folow it: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Im sending you pm link for 3.3.1.-3 twrp