I rooted my phone without knowing about s-off and its s-on and i installed miui and i cant boot that room it gets to the miui logo and just sits there is there anyway at all to fix this
Edit:
ok now it wont turn i connect my usb to the phone and the orange light appears i get the sounds on windows saying its connected then it disconnects and then dose this over and over again so i have no idea what is going on please please help its really annoying me
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Spectrejester said:
If you are still s-on you need to manualy flash the boot.img or it will just boot loop. I use Flash Image GUI but there are other ways
Sent from my Vivid 4G using xda premium
Click to expand...
Click to collapse
could u give me more info please
new problem
re edited to top post
Your battery is dead and cwm doesn't support off-mode charging, hence the reason you get the orange light but only for a moment. You can't charge the phone while its off..and you incorrectly flashed a custom rom. If you can find a way to charge your batt out of the phone you can fix this by either flashing the proper boot.IMG for the ROM from fastboot, or by running the appropriate ruu and starting from scratch. I highly recommend doing the s-off procedure. Its not difficult, and it makes customizing the phone so much simpler.
Sent from my PAC MAN Raider using XDA Premium
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
N-rG said:
i have the same problem man did it just minutes before...i have only a black screen, the display gives a vibration feedback. i see the sdcards in windows but cant open them
What can i do help please!
Edit: Ok screen is on "htc" and keeps so for minutes and hours
Any solution?
Click to expand...
Click to collapse
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
homeslice976 said:
Boot to bootloader (pwr and vol-). Does it say locked or unlocked? Does it say s-on or s-off? Select recovery. Does it still boot to custom recovery or do you get the android with the exclamation point? If the bootloader says locked, and you get the android with the !, you need to unlock the bootloader, fastboot flash a custom recovery, boot to that custom recovery, and flash your ROM. If bootloader is s-on, you'll also need to fastboot flash a boot.img that's compatible with the ROM you're flashing (can be found in the ROM's .zip)
Click to expand...
Click to collapse
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
N-rG said:
Thank you so much for your answer
It says "unlocked"
It says "s-on"
It boots to nothing. When i start the phone there is only standing "htc" nothing more happend. No explantion Mark But i can get into the bootloader.
Or what do you mean with "it still boot to custom recovery or do you get the android with the exclamation point?"
How do I do that with the boot.img? Please i am such a noob im so sorry i dont unterstand a lot im so angry about myself that i did it, please can you exactly tell me what i should do and what i need?
I did a backup before but there is no "boot.img"
And how can i use the boot.img wenn i cant get access to the sd memory?
Click to expand...
Click to collapse
When you boot to bootloader, scroll down and select recovery. What happens?
As far as flashing the boot.img, when you downloaded the ROM's .zip, inside the .zip should have been a file called boot.img. You need to drag that to the directory where you have fastboot installed, boot to bootloader, connect your phone, select fastboot. It should now say "fastboot usb". Now in the directory where you have fastboot and boot.img (with neither selected), shift+right click, choose "Open command window here". You need to enter "fastboot flash boot boot.img" and hit enter. Then reboot
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
N-rG said:
At first, thaaank you so much for your help, i feel so lost....
Ah ok i understand, you mean the "[ROM][ICEss v 0.4][Stockish ICS/SENSE 3.6" -that is what i downloaded.
When i am in the bootloader menu and activate recovery the htc symbol appears with a white backround...nothing more happen for minutes
unfortuneately there is not boot.img in this zip
I did the whole procedure with the Vivid_All-In-One_Kit_v2.2 and not fastboot.
Ok i now downloaded fastboot and put it to c:/fastboot
I do what you say and reach your point " It should now say "fastboot usb" thats right, it works. But i dont have the boot.img where can i get it?
Click to expand...
Click to collapse
There's not a boot.img in the zip you downloaded? Then you need to read the thread and see what kernel they recommend, get the boot.img, and fastboot flash it. You're getting close.
It sounds like you may have lost your custom recovery along the way too (in which case more may have broke) - you'll need to get a custom recovery .img (wcx or twrp) and fastboot flash it (fastboot flash recovery <nameofrecovery>.img). Then fastboot flash boot.img, then boot to recovery and reflash the ROM and hopefully you'll be all set.
Thanks again, im getting closer! I read the whole thread and found that "Holics_Kernel_0730_S-ON" is recommended. I downloaded and found the boot.img I put it in the fastboot folder.
But i dont understand what do you mean with "you'll need to get a custom recovery .img (wcx or twrp)"
Do you mean the recovery i created with my old working Gingerbread or a recovery form the custom rum i downloaded?
When last, where can i get such a recovery.img?
Hey man btw. you gave me so much hope at the moment, thats incredible, thank you!
Check the dev section. Everything you will need is in the stickied threads. Twrp recovery also has its own thread
bypruv oculus
Okay i'll do meanwhile there is something new. I create use fastboot, the boot.img of the new kernel and do it with the command line like you said.
The phone now boots one step more to "htc quietly brilliant" and then restarts over and over again to this screen, like a loop.
---------- Post added at 11:42 PM ---------- Previous post was at 11:25 PM ----------
ahhh i reach Android System Recovry with several menus. I didnt find any help in google what i have to do now.
Backup google propritary System, nand backup, Nand Restore, Restore google proprietary System? Or something else?
No.. at this point you should wipe cache, dalvik cache, system, an data. This can all be done In Recovery's wipe menu. Them recovery should have a flash zip menu. Flash the ROM .zip
Put the brakes on!
I saw gingerbread...
When you boot to bootloader...
There is a line labeled hboot
What's the number next to it?
If its 1.85... you good...
If its 1.83... thou shalt find an ICS ruu for your carrier.
Almost none of the ROMs you find here run on 1.83
Sent from my Vivid 4G using Tapatalk 2
Good catch!
Hey,
i bring it to run! I restored every part manuall...system, cache, data. Only restore boot didnt work. I suggest its because Rom Manager/ClockworkMod didn't created such a file (boot.img) So i downloaded a custom kernel für Gingerbread.
Vola, handy startet, Os is on. Loggin into network worked!
BUT! I cannot use Wlan/wifi or mobile networking. I suppose its because the rom right?
I mentioned that i have the same phone here from my girlfriend.
How and can i make a boot.img of her phone? Please tell my how and then i have finished everything i hope
You can't. S*on devices can't flash boot.IMG or back up boot.IMG in recovery. You have to fast boot flash the boot.IMG. this is also why wifis broken
The kernel and ramdisk and some other things are packed into boot.IMG, and are made by ROM or kernel devs. Actually now that you're booting, you can use an app called flash image GUI to flash the boot.img
Ok I expressed something wrong, sorry (im not a native speaker u might noticed long before ^^ ). So i try again like I said i did the manuell recovery of everything except the boot.img.
Thats why i loaded this kernel for Gingerbread (http://forum.xda-developers.com/showthread.php?t=1351717) and installed the boot.img with fastboot "flash boot boot.img"
Fastboot said well done. Phone startet.
I think i understand what you are writing, but i dont understand which boot.img do you mean i need. I have no boot.img from my backup before flashing with custom rom without this boot.img i cant flash the not working one of the ICS on my phone am i right?
So thats why i thought i can take the phone of my girlfriend, create a boot.img and use it for my phone. So thats the only problem, i need working boot.img and then flash with fastboot oder the app you mentioned How to get the boot.img
Related
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618
I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.
Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123
Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?
The stock recovery says it's not available anymore.
If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.
I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.
This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?
aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?
tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Would ADB be any better?
Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.
I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol
aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.
There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.
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, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.
Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------
its the peanut said:
Try re download the zip (or try an other rom)maybe you just got an false download. i also had some trouble with my m7 back in the day.
But in your case now you are stuck with no os or bootloop, i give you as advice to follow an soft unbrick method it worked for me, or if you have an usb otg cable and usb or and usb otg thumbstick, put the rom on that usb and connect it to your phone and then try to flash it (if your using twrp you have an option to choose from wich storage you want to use)
Also a piece of advice, when flashing roms, kernels etc please have your phone charged above 50% (just in case).
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Click to expand...
Click to collapse
Also make sure you downloaded the rom made for your phone model!
Sent from my HUAWEI P7-L10 using XDA Free mobile app
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Can you please post the output of
Code:
fastboot getvar all
please remove your imei and serial number.
Depending on which variant of the M7 you have you probably just need a different version of recovery to install a CM rom. I think they prefer TWRP 2.7.x.x. Post the getvar and we can see what you have. then I can give you a better informed instruction. :good:
P.s also check the md5 of the rom zip you downloaded. Use this tool www.winmd5.com the correct md5 should be listed with the link you downloaded the rom from
failed to mount /dev/block/blah blah blah = needs "block:by-name" support which twrp 2.6.3.3 doesn't have
everything explained here
So update your recovery
and do what danny said above so he can confirm you have the right rom/recovery for your device.
Burky1996 said:
I really messed my phone up its got no OS and its stuck in bootloop iv tried pushing cm-12 onto it and installing it but i keep getting error codes with what you see in the picture. can anyone help.
Click to expand...
Click to collapse
Your getvar looks fine this rom should work fine with your device. Download this version of TWRP https://www.androidfilehost.com/?fid=23501681358561860 (2.7.1.2). dropthe file in your fastboot folder and flash it with fastboot.
Code:
fastboot flash recovery "name-of-recovery".img
fastboot erase cache
fastboot reboot-bootloader
Once thats done reflash the rom with the new version of TWRP. It should flash just fine :good:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Burky1996 said:
iv managed to flash cm12.1 now, thanks guys, is there anyway i could get the HTC software back on.
Click to expand...
Click to collapse
There are a number of ways to return to stock software. You can simply flash a stock rom through twrp or use a stock nandroid. look for rom that match your version main. 7.19.401.22
I think there is even an lollipop 7.19.401.22 RUU for your device but I'm not sure if it will work with s-on though because it's a zip but it certainly wouldnt hurt to try it though. You will need to relock your bootloader and flash it with fastboot.
I'll edit this post with links when I find them unless some one beats me to it
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Burky1996 said:
Hey Dan do you think we could skype and you could talk me through it, it would be much easier?
Click to expand...
Click to collapse
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Burky1996 said:
i did what you said when i applied the system update my phone turned on booted to a white screen with the green htc logo then it turned off the battery symbol came up its like its turned off. i tryed to lock the boot loader to see if it would work then but it never, when i appy the update it dosent even boot into the recovery.
Click to expand...
Click to collapse
Okay try this. Download the OTA but select the option "Install Later" connect your m7 to your pc and browse your storage. In the download folder on your phone you should find the OTA in zip format. Copy it to your pc.
Now open the OTA zip on your pc. Inside you'll find another zip called "firmware.zip" extract it then open it. Inside you'll find a recovery.img. extract the recovery file and flash it with fastboot. Now reboot to android and continue to install the OTA. :fingers-crossed:
Sent from my SM-T230 using Tapatalk
im going to have to unlock the boot loader again and then do it
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
its still not working so i mite just install twrp and restore to cm12.1
Burky1996 said:
im going to have to unlock the boot loader again and then do it
Click to expand...
Click to collapse
Yes you will need to unlock the bootloader to flash the recovery, Dont forget to fastboot erase cache after flashing the recovery that is cruicial. You don't need to be relocked to install the OTA though.
When you select install now, the device should reboot to the Stock Recovery. At first the screen will just be black for a short while. Then you'll see an image of a phone with a Green ring and download arrow. If you hold Volume up and press the power button you will see the Stock Recovery and its progress in installing the OTA.
I'm not sure why your device was hanging on boot after installing the OTA. Maybe a bad recovery.img. that's why I say to get the recovery from the OTA file.
Danny201281 said:
Sorry I am at work so availability is scetchy. I found the ruu but it's for the older 7.19.401.2 lollipop, this won't work for you because your s-on. Downgrading firmware is only possible with s-off.
You can use this stock rom though http://forum.xda-developers.com/htc-one/development/rom-100-pure-stock-5-0-2-7-19-401-2-t3044041 just flash it with twrp. The thread recommends TWRP 2.8.5.X no need to relock the bootloader or anything silly, just flash it like any other rom :good:
You'll notice that this rom is also for the older 7.19.401.2 so you will need to install the last OTA update to bring your rom in line with your firmware. Flash this recovery with the same method as twrp. (Stock recovery required for installing the OTA) http://sourceforge.net/projects/htcone/files/Recovery/STOCK/7.19.401.2_recovery.img/download reboot then just go to Settings>About>Check for updates.
Click to expand...
Click to collapse
could it be not working coz my hboot has changed to 1.51.
Burky1996 said:
could it be not working coz my hboot has changed to 1.51.
Click to expand...
Click to collapse
Your still stuck with this? Try starting the process over, but do not relock your bootloader at any point.
Wipe system data and cache partitions with TWRP Advanced wipe
Flash the Rom with twrp as a clean install.
Reboot and download the OTA. Choose install later, then copy the OTA to your pc. Extract the Stock Recovery and flash it with fastboot. Reboot and install the OTA.
But do not relock your boot loader. Because when you unlock the bootloader, it wipes the device including the data/preload folder. If the preload folder is not intact the OTA will fail
Sent from my M7 Running ARHD 92.x
I have the bootloader unlocked and everything ready to go.
However, when I execute "fastboot flash recovry <recovery_file_name>.img" the first thing that pops up on the cmd is:
(bootloader) has_slot:recovery not found
(bootloader) is_logical:recovery not found
After this it continues the flashing process and finishes with the okay status
However, after rebooting using "fastboot reboot" when I go back into the bootloader and select the recovery option I end up with the droid on his back and an orange triangle with an exclamation mark over him and No Command written under him
Can anyone help with this issue? I really want to flash a new ROM onto my nexus and I also really really want TWRP to work
Thanks,
Danush
Have you tried spelling "recovery" with an "e"?
It may be that your file name isn't properly spelled. I either rename the image to "TWRP. img" or copy the file name in Explorer and paste it into the CMD window so that there is no possibility of mis-spelling.
And another thought - is the TWRP image in the same directory as the fastboot exe?
dahawthorne said:
Have you tried spelling "recovery" with an "e"?
Click to expand...
Click to collapse
Oh yeah that's just a typo in my post ?
Thanks for pointing it out.
I do spell the "recovery" with an "e" and yet I have these issues
I added more comments while you were replying.
Try this:
https://forum.xda-developers.com/showpost.php?p=73648849&postcount=6
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Thanks so much for all the help!! After you mentioned it, it kinda hit me that yeah maybe that is what is happening since I used to reboot the device so maybe it was replacing TWRP with the stock recovery.
Hi,
My problem with Redmi Note 4 Snapdragon 625 2,02 GHz and unlocked trying to flash TWRP is like this (phone is in fastboot mode):
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot devices
55050ae09804 fastboot
PS C:\Users\Dell\Downloads\platform-tools-latest-windows\platform-tools> fastboot flash recovery
fastboot: error: ANDROID_PRODUCT_OUT not set
How can I solve it? Please, help!
Didgeridoohan said:
Do you have stock Android installed? It will replace any custom recovery with the stock recovery when you boot, unless you've flashed a kernel, mod (e.g. Magisk) or similar that disables that feature.
Don't reboot the device after flashing, boot to recovery instead.
(Don't bother with those "errors", they're just telling you that your device isn't A/B or have logical partitions.)
Edit: oh yeah... Should have checked the link @dahawthorne posted before posting myself. It tells you the same thing. D'oh!
Click to expand...
Click to collapse
Don't reboot after flashing? Like when i try it says img unsigned or corrupted, and when i try to then boot into recovery via "fastboot boot recovery" i get sent to the normal Android OS, so what im getting from this is that i somehow have to manually get into the "no command" error window and then power+volume up and that just works? Ill test that, would be really awesome if it does.
Oh yea and booting into the twrp image with "fastboot boot twrp.img" sends to normal os aswell btw.