So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.
You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.
Yeah that's what I did yesterday thanks for the response!
Related
Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...
What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?
If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...
Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.
hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?
Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device
Hi, I have foolishly (possibly?) wiped Android off of my OneX
I was attempting to apply the Tegra tweak and well things went downhill.
I successfully unlocked the bootloader from HTCdev.
I proceeded to apply Interim ClockworkMod to gain root access
This is where things started to go wrong. Any new reboot would only take me to Clockworkmod screen.
I tried http://forum.xda-developers.com/showthread.php?t=1599748
clear cache, davik cache... relocking the bootloader - This results in the device constantly rebooting.
I attempted to apply the RUU ROM's ( from: http://forum.xda-developers.com/showthread.php?t=1543604)
From within ClockworkMod I was then able to:
adb push One_X_1.26.401.2_odexed.zip /sdcard/
Once there I used ClockworkMod to apply an update zip (which I was hoping was the Stock ROM).
A reboot just brought me back to Clockwork.
I then locked the bootloader ( fastboot oem lock. ) hoping it would then proceed to boot as expected.
It didn't just going to HBOOT or an attempted recovery (isometric view of a phone with a green arrowed circle -> RED triangle).
Please someone help, starting to panic a bit. The fact I can upload, the fact that there is some basic interactions should imply this is fixable, but how?
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
mwhincup said:
The boot to recovery sounds like you have the same problem that I had.
Perhaps you followed the same incorrect instructions as I did. See here for a solution.
Click to expand...
Click to collapse
This may help.
with the locked bootloader you will only be able to run a proper ruu so before even attempting the instruction above unlock your bootloader again and proceed from there.
I might start working on some core .IMG files that can be flashed through fastboot to get you going again tomorrow
Sent from my HTC One X using XDA
THANKS!!!
booted back to the lovely ICS desktop
It looks like I did end up flashing RUU since none of the Vodafone branding is present (and it is actually better!)
No idea what went wrong but probably flashed over the boot as hinted at in the other thread.
The provided img files assisted. just need to get this Tegra thing working (not showing up as a running/registered process but thats another story)
Thanks all
right
i am going to have send my a100 back. the touchscreen issue is driving me nuts and i cant keep it in its crrent state. i am shipping it back to the retailer for a full refund rather than pay to ship it back to acer. at the end of the day i cant be doing with the hassle. so i need to know how i go about unrooting it and locking the boot loader back up and basically restoring it to stock.
i will have a read of the forums but with work being all rather busy and a deadline for return i am a little pushed for time so if anyone out there knows and would be kind enough to link me to a thread or simply tell me that would be appreciated.
cheers
You could flash stock boot loader and flash an official ota
sent from your future.
das_webos_transformer said:
You could flash stock boot loader and flash an official ota
sent from your future.
Click to expand...
Click to collapse
If hes just rooted just run the ota it'll do boot loader too. He didn't mention a custom rom or recovery, but if he does then doing it in that order will lock it up. Stock recovery then stock rom then bootloader last. Basically stock recovery > ota then you're fine.
Tapatalked from my Galaxy S II.
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
rockmonkey1973 said:
hey guys thanks for the replies.
ok sorry i should have said i have unlocked the boot loader rooted it and instaled twrp recovery. i never got round to putting a rom on it (i have only had it about 6 or 7 days), i removed root by accident when i wiped it but obviously the unlocked bootloader and recovery remained. so with this in mind then exactly what would i do?
flash stock rom>flash stock bootloader?
would that also remove recovery?
edit sorry i didnt remove root when i wiped it i merely lost the superuser app so i am actually still rooted.
Click to expand...
Click to collapse
Root occurs in system, which isn't affected by wipes, so yeah SU is still there, just the app to control it is gone, which you discovered already.
As you have twrp, unlocked a200 bootloader but stock rom, the process is pretty simple.
Get the ics ota, name it update.zip place it on the root of the external sd card, no folders.
Power on holding volume - (closes to lock switch) and press power for 3 seconds, once the text starts up in the upper left corner, let everything go.
Should install stock rom, which will do the following:
1 wipe cache
2 flash new rom system
3 "flash" a100 bootloader
4 reboot into android
5 flash over twrp and place stock recovery in place
This will all occur on it's own once you get it loading up update.zip
5 only happens if it boots and is completely stock with /system/etc/install-recovery.sh intact.
3 can happen as long as it uses the update.zip
2 can fail, if it does but proceeds to flash bootloader twrp will be locked out, however a stock rooted rom as you have will still boot, and we can cover replacing the recovery with stock at that point if needed.
1 always happens, regardless of any other steps being met or finished.
mate thanks for helping here. i had to fix my phone which died after a bad flash of a back up in cwm... long story wont go into it... but it did eat up a good one or two days. so i havent gotten round to sorting anything out here with the tablet.
now i am going to try to flash the build prop and install one or two roms. flex reapers and cm10 all look good and i am hoping that that combination with maybe with over clocked kernal will be enough to fix the screen problem.
now i know it is unlikely if it is a hardware fault but i need to try because i would like to keep this tablet and the place i got it from havent got any more. it was pretty inexpensive at 127 pounds and i will be unlikely to find any other store that has stock at that price so if it goes back it goes back for good. hence me wanting to try to keep it.
so i am gonna flash the roms and the build prop now. if it doesnt fix it then i will be back for a little help in reverting it back to stock. by the way where can i find the ota ics release?
i will have a look on the forum i am sure it has to be here somewhere but just in case!!!
edit: got them edit no i havent i cant download them? the site is offline... anywhere else they can be gotten from? maybe acers website? will check now. just realised i have the stock rom installed! will make a back up now.
http://forum.xda-developers.com/showthread.php?t=1307046
so you reckon it could be as simple as simply flashing the official rom to take the tablet all the way back to stock including the locking of the bootloader and removing the recovery? that would be nice and simple and easy which will be a real welcome change from the norm. fingers crossed that is all that is needed.
To go stock that is all that's needed. In vaches thread there is one decrypted on a drop box, that's our only one unless vache brings his stuff back online.
Well there is the service ROM which will be stock, but not what is supposed to be there. At first glance its stock though. Wouldn't suggest it for a return.
Tapatalked from my Galaxy S II.
ok this post was confusing. i am running stock ics at the moment. the bootlaoder is unlocked i have root and the recovery is twrp.
so i have downloaded the update found in the drop box folder here.
http://forum.xda-developers.com/showthread.php?t=1307046
it was already called update and it has a zip extension. so it is update.zip.
i have put it in both mnt/external_sd/ and also /sdcard/ none of them work.
all i get when i hold the volume and power button is taken into twrp recovery.
i thought it flashed automatically? can i flash it through recovery? bit worried about doing that because if it removes recovery while it is flashing i will be screwed.
will wait here now until someone can confirm what i am doing wrong because i cant afford to brick it.
i can be a bit to smart for my own good at times.
could the problem be that i am already running the latest ics official release? should i flash a custom rom? just throwing out some ideas here because i aint got a clue why it hasnt worked.
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
rockmonkey1973 said:
anyone know? i need to ship this back to the retaler tomorrow and i would prefer not to do it with an unlocked bootloader and custom recovery.
things is i am stumped because i thought i had done all that should be needed to flash the update and the only thing i can think of is because the firmware is up to date (possibly even newer than the update.zip) it wont update.
Click to expand...
Click to collapse
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
pio_masaki said:
In that case flash the stock recovery and run the bootloader for a100 that came in the unlock boot loader zip. Run the a100 script instead of the a200 script, that will lock it. Do this after stock recovery flashing.
Or, put back install-recovery.sh and reboot, that will replace the stock recovery then run the a100 boot loader script. You'll still be rooted but try update.zip again after stock recovery and boot loader are done.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
rockmonkey1973 said:
mate you have been incredibly helpful. i mean seriously.
i will do as you suggest however i have a question how am i supposed to flash these files? do i do it through recovery? please dont say adb because i have never used that program dont know why i just tended to stay away from it zips and nandroids always seemed so much easier.
i have edited this post due to being slightly confused and thought it best to save the gushing praise until after the tab is stock! sorry mate i hate being a pain and i am reading all i can on locking the bootloader but there doesnt seem to be any guide i can follow. most of the threads i have found are for bricks and my tab is certainly not beicked... and i want it to stay that way.
Click to expand...
Click to collapse
Well....adb. You used it before with the scripts to unlock the boot loader.
http://forum.xda-developers.com/showthread.php?p=23868002
Right above the download it mentions running the a100 script to revert to locked a100 boot loader.
Only do this with a stock ROM installed!
After that it'll be manually installing the recovery with fast boot or replace the stock /system/etc/install-recovry.sh
If it was just renamed, then name it back. If it was deleted it'll need replaced, it will revert to stock recovery on its own after booting with it in place.
Tapatalked from my Kindle Fire - Jellytime AOSP
thanks again my friend. funny i never realised i was flashing stuff with adb when i was doing things like that!
i always thought adb was a command line interface like say ssh and that you needed to use some sort of software like putty.
anyways just to bring this to a close. i never got time to flash it back to stock. i simply left the official ota on and reset it. have already received the refund so all is good. shame i am unlucky with tablets. i had a faulty archos 80 g9 and then this. guess i will hold off for a while maybe until i feel my luck has changed for the better.
cheers again mate.
Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk
First, let me start off by saying I'm an idiot; my phone was stuck in a bootloop and out of panic I tried to fix the problem and only made it worse. Now I'm left with no OS installed and I'm stuck at my custom recovery.
I am using twrp as my custom recovery and I'm able to use my mac to send files successfully to my phone. The problem arises when I try to flash the zip and I am prompted with the message that says that the file is corrupted. I tried installing multiple zip files onto my phone and when returning it to stock did not work I even tried to flash Cyanogen Mod. Each time I was greeted with the same message.
This sucks because I just bought my nexus 5x and I don't want to lose it to a stupid mistake. If anyone could help in anyway that would be amazing. If not I will still accept prayers for my potentially dead phone.
-Carlos
Edit: problem solved. I did what you guys said and returned to stock and didn't panic. Thanks so much.
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Giorgos Chatziioannou said:
you mean the unlocked bootloader message? thats nothing
or maybe the md5 message, which also is normal?
to me sounds like you are panicking for no reason, but anyway, search for nexus root toolkit, install it, and choose the option to revert stock + unroot
Click to expand...
Click to collapse
Yeah as said above there is no need for panic.
Even if your recovery wont flash the zips you can flash the stock factory images via fastboot manually (i dont now if its available on mac if not boot a linux live disk).
And if your bootloader is still locked unlock it reboot to bootloader and then flash the images.
By the way you should provide more information such as os details twrp version bootloader state and so on...:fingers-crossed: